(Løst) Datamaskinen får bluescreen under spilling

[Gakks]

- edit -

Har løst problemet, var for høy varme i CPU-en som gjorde at maskinen klikket så mye. Fikset med litt kjølepasta og støvfjerning.

 

Hei, har nettopp fått meg ny SATA disk og DVD brenner, og da startet problemene. Jeg har fått veldig mange bluescreen of death hvilket jeg ikke fikk før jeg byttet ut hardware.

 

Har kjørt komplett harddisk test for min nye SATA disk uten å finne feil, har også kjørt minnetest uten å få feil. Har to ganger prøvd å kjøre CPU test og da har skjermen endt opp med å bli svart og jeg måtte starte maskinen på nytt. Alle testene er utført med programmer fra ultimatebootcd.com

 

Men om CPU-en skulle være årsaken til BSOD som jeg har begynt å få, hvorfor fikk jeg ikke de da før med min gamle IDE disk og vanlig DVD ROM?

 

En annen ting som er mer enn rart er at jeg ikke klarer å få innstallert windows 32 bit, kun 64 bit. Maskinen fungerer greit når jeg bare er i windows og surfer, bruker IRC eller msn og ser film. Men når jeg f.eks. prøver å spille World of Warcraft så bam, BSOD. Siden det er variabelt med tidsforbruk i WoW før BSOD inntreffer kan det jo være varmeproblemer pga. støv, men jeg tok ut CPU viften og støvsugde bort støvet uten at det har hjulpet på feilene.

 

Jeg har prøvd å ta ut hardware og bare boote med SATA disken, skjermkort, hovedkort, minne og CPU men fikk fortsatt BSOD. Jeg har også prøvd å laste ned drivere til hovedkortet for å oppdatere de uten at det løste problemet.

 

Jeg har hentet opp nyeste minidump fil med Windows Debugging Tool, kan jo være noen her skjønner den bedre enn meg. Hvis ønskelig kan jeg sikkert hente opp flere og poste de.

 

 

Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini080308-06.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp2_rtm.070216-1710

Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d5100

Debug session time: Sun Aug 3 17:56:16.171 2008 (GMT+2)

System Uptime: 0 days 0:34:40.330

Loading Kernel Symbols

..........................................................................................

......................................

Loading User Symbols

Loading unloaded module list

.............

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 3D, {0, 0, 0, fffff8000102fea3}

 

Unable to load image \SystemRoot\system32\DRIVERS\AmdK8.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for AmdK8.sys

*** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys

Probably caused by : hardware ( nt!KiInterruptHandler+28 )

 

Followup: MachineOwner

---------

 

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

INTERRUPT_EXCEPTION_NOT_HANDLED (3d)

Arguments:

Arg1: 0000000000000000

Arg2: 0000000000000000

Arg3: 0000000000000000

Arg4: fffff8000102fea3

 

Debugging Details:

------------------

 

 

CUSTOMER_CRASH_COUNT: 6

 

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

 

BUGCHECK_STR: 0x3D

 

PROCESS_NAME: Idle

 

CURRENT_IRQL: 0

 

EXCEPTION_RECORD: fffff800001179b0 -- (.exr 0xfffff800001179b0)

ExceptionAddress: fffff8000102fea3 (nt!KiInterruptDispatchNoLock+0x0000000000000063)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: 0000000000000180

Attempt to read from address 0000000000000180

 

TRAP_FRAME: fffff80000117a40 -- (.trap 0xfffff80000117a40)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000065ac5dae rbx=0000000000002626 rcx=000000000032235c

rdx=0000000000000056 rsi=fffff80000117c50 rdi=0000000000000000

rip=fffff8000102fea3 rsp=fffff80000117bd0 rbp=fffff80000117c50

r8=00000001bc32235c r9=0000000001000000 r10=00000004d7f954bd

r11=fffff800011b3450 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up di pl zr na po nc

nt!KiInterruptDispatchNoLock+0x63:

fffff800`0102fea3 0fae142580010000 ldmxcsr dword ptr [180h] ds:1100:00000000`00000180=????????

Resetting default scope

 

MISALIGNED_IP:

nt!KiInterruptDispatchNoLock+63

fffff800`0102fea3 0fae142580010000 ldmxcsr dword ptr [180h]

 

LAST_CONTROL_TRANSFER: from fffff8000102e674 to fffff8000102e950

 

STACK_TEXT:

fffff800`00116a18 fffff800`0102e674 : 00000000`0000003d 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

fffff800`00116a20 fffff800`0102f538 : fffff800`00116cd0 00000000`00000000 fffff800`001179b0 fffff800`0102fea3 : nt!KiBugCheckDispatch+0x74

fffff800`00116ba0 fffff800`010549fd : fffff800`001179b0 00000000`001173c0 00000000`00000000 fffff800`00117ac0 : nt!KiInterruptHandler+0x28

fffff800`00116bd0 fffff800`01054f93 : fffff800`00116cc0 fffff800`001173c0 00000000`00000000 00000000`001173c0 : nt!RtlpExecuteHandlerForException+0xd

fffff800`00116c00 fffff800`0100b901 : fffff800`00000000 fffff800`001173c0 fffff800`001179b0 fffff800`00117ac0 : nt!RtlDispatchException+0x2c0

fffff800`001172c0 fffff800`0102e76f : fffff800`001179b0 fffff800`010274a9 fffff800`00117a40 00000000`00000000 : nt!KiDispatchException+0xd9

fffff800`001178c0 fffff800`0102d5e1 : 00000000`00000212 fffff800`00000018 00000000`00092700 fffffadf`cd596d90 : nt!KiExceptionExit

fffff800`00117a40 fffff800`0102fea3 : fffffadf`ce226248 00000000`00000001 fffff800`011b3480 fffffadf`ce664760 : nt!KiPageFault+0x1e1

fffff800`00117bd0 fffffadf`c86f7a72 : fffffadf`c86f7089 fffff800`011b5940 fffffadf`ce2737f0 fffff800`00117d90 : nt!KiInterruptDispatchNoLock+0x63

fffff800`00117d68 fffffadf`c86f7089 : fffff800`011b5940 fffffadf`ce2737f0 fffff800`00117d90 fffffadf`ce664760 : AmdK8+0x4a72

fffff800`00117d70 fffff800`011b5940 : fffffadf`ce2737f0 fffff800`00117d90 fffffadf`ce664760 fffff800`011b3450 : AmdK8+0x4089

fffff800`00117d78 fffffadf`ce2737f0 : fffff800`00117d90 fffffadf`ce664760 fffff800`011b3450 fffff800`010319cc : nt!KiInitialProcess

fffff800`00117d80 fffff800`00117d90 : fffffadf`ce664760 fffff800`011b3450 fffff800`010319cc fffff800`00111000 : 0xfffffadf`ce2737f0

fffff800`00117d88 fffffadf`ce664760 : fffff800`011b3450 fffff800`010319cc fffff800`00111000 fffff800`011b5901 : 0xfffff800`00117d90

fffff800`00117d90 fffff800`011b3450 : fffff800`010319cc fffff800`00111000 fffff800`011b5901 fffff800`011b3450 : 0xfffffadf`ce664760

fffff800`00117d98 fffff800`010319cc : fffff800`00111000 fffff800`011b5901 fffff800`011b3450 00000000`0005ffd4 : nt!KiInitialPCR+0x2450

fffff800`00117da0 fffff800`01067cde : fffff800`011b1180 fffff800`011b1180 fffff800`011b5500 fffffadf`ce2737f0 : nt!PopProcessorIdle+0x114

fffff800`00117dd0 fffff800`014151d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x1e

fffff800`00117e00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1bf

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

nt!KiInterruptHandler+28

fffff800`0102f538 90 nop

 

SYMBOL_STACK_INDEX: 2

 

SYMBOL_NAME: nt!KiInterruptHandler+28

 

FOLLOWUP_NAME: MachineOwner

 

IMAGE_NAME: hardware

 

DEBUG_FLR_IMAGE_TIMESTAMP: 0

 

MODULE_NAME: hardware

 

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

 

BUCKET_ID: X64_IP_MISALIGNED

 

Followup: MachineOwner

---------

 

 

 

 

Min hardware er som følger:

 

AMD Athlon 64 X2 6000+ 3.0GHz Socket AM2

ASUS M2N-E SLI, nForce 500 SLI, DDR2, Socket-AM2, GbLAN, ATX, PCI-Ex16 (M2N-E SLI)

CORSAIR Powersupply 450W, 120mm Vifte, 6xSATA, ATX/EPS, 1xPCI-E, 20/24pin (CMPSU-450VXEU)

CORSAIR TWIN2X 6400 DDR2, 2048MB CL5 Kit w/two matched CM2X1024A-6400 Dimm's (TWIN2X2048-6400)

ASUS GeForce 8600GT 256MB GDDR3 Silent, PCI-Express, Tv-Out/ 2xDVI-I/ HDTV/ HDCP (EN8600GT SILENT/HTDP/256M/

 

Problemene startet etter at jeg monterte denne hardwaren:

Samsung DVD-brenner SH-S202J IDE

Western Digital Caviar GP 750GB SATA2

 

Disken er som sagt ny og jeg har vel formatert og prøvd å legge inn windows 10 ganger nå, så kan utelukke virus/malware/spyware/. Siden maskinen fungerte fint før jeg fikk ny hardware tror jeg heller ikke problemet ligger i vifte til strømforsyning eller CPU. Varmen på CPU-en er dog høy, over 55 grader celcius når jeg har sjekket i BIOS.

 

I noen av BSOD jeg har fått nevnes det shadowing og caching i BIOS, men jeg har blitt forklart av en kompis at dette er ganske standard feilmeldinger og ikke mye å bry seg om. Jeg har derfor ikke prøvd å oppdatere BIOS.

 

Har også prøvd Windows Driver Verifier etter å ha lest den sticky tråden her, valgte kun Windows drivere og da fikk jeg BSOD mens Windows var i ferd med å starte opp og måtte inn i sikkerhetsmodus og fjerne innstillingene jeg gjorde i Driver Verifier for å få startet maskinen som normalt.

 

Kan det tenkes at jeg rett og slett er ute for en uheldig Windows her og driverproblematikk i 64 bit gir meg problemer?

 

Takker på forhånd for all hjelp, har slitt med dette i 5 dager nå og begynner å bli veldig, veldig lei.

Endret 6. august 2008 av Gakks

[Applebee]

Uten å ha noe viten om bluescreen, så kan det være varme-utvikling.

Har merket selv at hvis jeg klokker grafikk-kortet opp for mye, kan jeg få blue-screen..

 

(Repeating: Trenger ikke å være dette, men det er den eneste grunnen til at jeg fikk bluescreen, to ganger )

[Gakks]

Har ikke klokket opp noe.

[Gakks]

Seneste krasj i Windows Debugging Tool:

 

Microsoft ® Windows Debugger Version 6.9.0003.113 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini080408-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 3790.srv03_sp2_gdr.070321-2337

Kernel base = 0xfffff800`01000000 PsLoadedModuleList = 0xfffff800`011d4140

Debug session time: Mon Aug 4 17:32:51.593 2008 (GMT+2)

System Uptime: 0 days 0:03:33.290

Loading Kernel Symbols

..........................................................................................

....................................

Loading User Symbols

Loading unloaded module list

.......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 50, {fffff800014141d1, 0, fffff8000104f236, 0}

 

 

Could not read faulting driver name

Unable to load image \SystemRoot\system32\DRIVERS\AmdK8.sys, Win32 error 0n2

*** WARNING: Unable to verify timestamp for AmdK8.sys

*** ERROR: Module load completed but symbols could not be loaded for AmdK8.sys

Probably caused by : AmdK8.sys ( AmdK8+4a72 )

 

Followup: MachineOwner

---------

 

1: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except,

it must be protected by a Probe. Typically the address is just plain bad or it

is pointing at freed memory.

Arguments:

Arg1: fffff800014141d1, memory referenced.

Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.

Arg3: fffff8000104f236, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 0000000000000000, (reserved)

 

Debugging Details:

------------------

 

 

Could not read faulting driver name

 

READ_ADDRESS: fffff800014141d1

 

FAULTING_IP:

nt!RtlVirtualUnwind+132

fffff800`0104f236 440fb603 movzx r8d,byte ptr [rbx]

 

MM_INTERNAL_CODE: 0

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0x50

 

PROCESS_NAME: Idle

 

CURRENT_IRQL: 1

 

TRAP_FRAME: fffffadfc8e1da20 -- (.trap 0xfffffadfc8e1da20)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000000 rbx=0000000054434168 rcx=000000000100000d

rdx=0000000000800054 rsi=0000000000000000 rdi=0000000000000000

rip=fffff800010296a4 rsp=fffffadfc8e1dbb0 rbp=fffffadfc8e1dc30

r8=000000002dbfd28a r9=0000000001000000 r10=000000007f217b11

r11=fffffadfc8a6d450 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up di pl nz na po cy

nt!KiSecondaryClockInterrupt+0xc4:

fffff800`010296a4 440f22c1 mov cr8,rcx

Resetting default scope

 

EXCEPTION_RECORD: fffffadfc8e1d990 -- (.exr 0xfffffadfc8e1d990)

ExceptionAddress: fffff800010296a4 (nt!KiSecondaryClockInterrupt+0x00000000000000c4)

ExceptionCode: c0000096

ExceptionFlags: 00000000

NumberParameters: 0

 

LAST_CONTROL_TRANSFER: from fffff800010a6072 to fffff8000102e890

 

STACK_TEXT:

fffffadf`c8e1c8f8 fffff800`010a6072 : 00000000`00000050 fffff800`014141d1 00000000`00000000 fffffadf`c8e1c9d0 : nt!KeBugCheckEx

fffffadf`c8e1c900 fffff800`0102d459 : 00000000`00000000 fffffadf`cc94a000 00000000`00000000 fffffadf`cc94a010 : nt!MmAccessFault+0xa1f

fffffadf`c8e1c9d0 fffff800`0104f236 : fffffadf`cc987af0 fffffadf`cd763228 fffffadf`cde7a2b0 fffffadf`c8222903 : nt!KiPageFault+0x119

fffffadf`c8e1cb60 fffff800`01054a97 : fffffadf`cde7a201 fffffadf`c8e1ddb0 00000000`00000000 00000000`c8e1d3a0 : nt!RtlVirtualUnwind+0x132

fffffadf`c8e1cbe0 fffff800`0100b901 : fffffadf`c8e1d990 fffffadf`c8e1d3a0 fffffadf`c8e1d990 fffffadf`c8e1daa0 : nt!RtlDispatchException+0x10b

fffffadf`c8e1d2a0 fffff800`0102e6af : fffffadf`c8e1d990 fffffadf`ce42acf0 fffffadf`c8e1da20 fffffadf`ce42ae98 : nt!KiDispatchException+0xd9

fffffadf`c8e1d8a0 fffff800`0102d30d : 00000000`00000000 fffffadf`ce7c0120 fffffadf`ce42acf0 00000000`00000000 : nt!KiExceptionExit

fffffadf`c8e1da20 fffff800`010296a4 : 54446c75`5444706c 00000002`46586670 fffffadf`c8a6d480 fffffadf`cebe1ac0 : nt!KiGeneralProtectionFault+0xcd

fffffadf`c8e1dbb0 fffffadf`c87a2a72 : fffffadf`c87a2089 fffff800`011b4940 fffffadf`ce95ba60 fffffadf`c8e1dd70 : nt!KiSecondaryClockInterrupt+0xc4

fffffadf`c8e1dd48 fffffadf`c87a2089 : fffff800`011b4940 fffffadf`ce95ba60 fffffadf`c8e1dd70 fffffadf`cebe1ac0 : AmdK8+0x4a72

fffffadf`c8e1dd50 fffff800`011b4940 : fffffadf`ce95ba60 fffffadf`c8e1dd70 fffffadf`cebe1ac0 fffffadf`c8a6d450 : AmdK8+0x4089

fffffadf`c8e1dd58 fffffadf`ce95ba60 : fffffadf`c8e1dd70 fffffadf`cebe1ac0 fffffadf`c8a6d450 fffff800`0103190c : nt!KiInitialProcess

fffffadf`c8e1dd60 fffffadf`c8e1dd70 : fffffadf`cebe1ac0 fffffadf`c8a6d450 fffff800`0103190c fffffadf`c8a6d600 : 0xfffffadf`ce95ba60

fffffadf`c8e1dd68 fffffadf`cebe1ac0 : fffffadf`c8a6d450 fffff800`0103190c fffffadf`c8a6d600 fffff800`011b4901 : 0xfffffadf`c8e1dd70

fffffadf`c8e1dd70 fffffadf`c8a6d450 : fffff800`0103190c fffffadf`c8a6d600 fffff800`011b4901 fffffadf`c8a6d450 : 0xfffffadf`cebe1ac0

fffffadf`c8e1dd78 fffff800`0103190c : fffffadf`c8a6d600 fffff800`011b4901 fffffadf`c8a6d450 00000000`00000000 : 0xfffffadf`c8a6d450

fffffadf`c8e1dd80 fffff800`01067bde : fffffadf`c8a6b180 fffffadf`c8a6b180 fffffadf`c8a73680 fffffadf`ce95ba60 : nt!PopProcessorIdle+0x114

fffffadf`c8e1ddb0 fffff800`014141d1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x1e

fffffadf`c8e1dde0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemStartup+0x1bf

 

 

STACK_COMMAND: kb

 

FOLLOWUP_IP:

AmdK8+4a72

fffffadf`c87a2a72 ?? ???

 

SYMBOL_STACK_INDEX: 9

 

SYMBOL_NAME: AmdK8+4a72

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: AmdK8

 

IMAGE_NAME: AmdK8.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP: 44a8bf55

 

FAILURE_BUCKET_ID: X64_0x50_AmdK8+4a72

 

BUCKET_ID: X64_0x50_AmdK8+4a72

 

Followup: MachineOwner

---------

 

 

 

 

Det som skjedde feil, slik jeg forstår det, er en driver til AMD Cool N' Quiet. Har sjekket i BIOS etter et par BSOD og sett at CPU temperaturen har ligget på over 80 grader celsius, tyder på varmeproblemer.