BSOD - dumping physical memory

[ConeX]

Hei, trenger litt hjelp med å finne ut hva som får datan til å krasje.

 

Krasjet oppstår forskjellig steder hver gang. Noen ganger blir skjermen helt svart, andre ganger kommer det noen rare farge mønstre opp så krasjer maskinen. Det kommer som regel når jeg spiller.

 

Har lagt ved en dump fil fra BSOD.

 

Windows 7 x64

Asus Crosshair III Formula AM3

AMD Phenom II X4 965

4 x OCZ PC3-12800 Black Edition Ready CL8 Dual

Ati Sapphire Radeon HD 5870

 

 

Takk for hjelpen!

062510-20046-01.zip

Endret 25. juni 2010 av ConeX

[ConeX]

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Users\xxxx\Desktop\062510-20046-01\062510-20046-01.dmp]

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

 

Symbol search path is: *** Invalid ***

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

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

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

Executable search path is:

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

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909

Machine Name:

Kernel base = 0xfffff800`02811000 PsLoadedModuleList = 0xfffff800`02a4ee50

Debug session time: Fri Jun 25 02:07:09.429 2010 (GMT+2)

System Uptime: 0 days 0:10:22.162

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

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

....

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 1A, {41287, 5560001, 0, 0}

 

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

 

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

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

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Probably caused by : ntoskrnl.exe ( nt+70600 )

 

Followup: MachineOwner

---------

Endret 25. juni 2010 av ConeX

[Kakeshoma]

Oppdater drivere, oppdater Direct X, kjør windows update.

 

Har du overklokket?

[3rd_SQD]

Hvilken hastighet kjører du minnet på? (CPU-z)

Har du riktig spenning på brikkene?

 

Kan hende du må ned på hastigheten på minnet når du kjører 8GB/4 brikker.

 

Jeg hadde tidligere OCZ, men byttet de til Corsair etter mye trøbbel.

Men jeg kjører kun på 1333 MHz.

[ConeX]

Jeg er litt usikkert på det er overklokket, fordi med hovedkortet følgte det ett program som heter AMD Overdrive, de lastet automatisk ned nye profiler for minnebrikkene. Er disse profilene fortsatt aktive ettersom jeg har formatert?

 

Takk kakeshoma, har akkurat oppdatert directx - har ikke opplevd noe krasj enda.

 

3rd_SQD - NB Frequency 2006,8 MHz? Skal se om jeg får lastet opp noen bilder.

 

Antar at de er klokket siden standard er:

CAS Latency: 8

tRCD: 8

tRP: 8

tRAS: 24

Endret 25. juni 2010 av ConeX

[ZERO6237]

On Fri 25.06.2010 00:41:24 your computer crashed

This was likely caused by the following module: dxgmms1.sys

Bugcheck code: 0xA (0x40E0, 0x2, 0x1, 0xFFFFF80002879BD8)

Error: IRQL_NOT_LESS_OR_EQUAL

Dump file: 062510-18330-01.dmp

file path: C:\Windows\system32\drivers\dxgmms1.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: DirectX Graphics MMS

 

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

 

 

 

 

 

On Fri 25.06.2010 00:08:34 your computer crashed

This was likely caused by the following module: ntoskrnl.exe

Bugcheck code: 0x1A (0x41287, 0x5560001, 0x0, 0x0)

Error: MEMORY_MANAGEMENT

Dump file: 062510-20046-01.dmp

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

 

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

 

EDIT: Ser ut som det er noe driver problemer?

EDIT2: og på den andre ser det ut som ramen din kranglet litt.

Endret 25. juni 2010 av ZERO6237

[Kakeshoma]

edit: slett

Endret 25. juni 2010 av Kakeshoma

[ConeX]

Jeg får vel kjøre en memtest!

Endret 28. juni 2010 av ConeX

[Kakeshoma]

fått flere BSODer?

[ConeX]

Nei, men jeg har fått noen svarte skjermer og noen med heftig farge mønstre. Pluss at ingen programmer vil starte opp lengre.

Endret 28. juni 2010 av ConeX

[3rd_SQD]

Jeg er litt usikkert på det er overklokket, fordi med hovedkortet følgte det ett program som heter AMD Overdrive, de lastet automatisk ned nye profiler for minnebrikkene. Er disse profilene fortsatt aktive ettersom jeg har formatert?

De er nok borte etter formatering.

3rd_SQD - NB Frequency 2006,8 MHz? Skal se om jeg får lastet opp noen bilder.

 

Antar at de er klokket siden standard er:

CAS Latency: 8

tRCD: 8

tRP: 8

tRAS: 24

Minnet ditt kjører på 1066 Mhz på 7-7-7-16 (533 + 533 = 1066Mhz)

Se her for tips.

[ConeX]

Jeg har kjørt memtest86, uten å få noen som helst feilmelding. Har prøvd å bytte disk for å installere nytt os, men fortsatt slutter programmer å kjøre og jeg får BSOD.

[ConeX]

Jeg var nesten sikker på at maskinen min fungerte som den skulle etter at jeg fjernet ett gammelt nettverkskort som satt i maskinen. Det gikk noen dager uten noen som helst feilmelding eller BSOD.

 

Men da jeg i dag skulle skru på maskinen etter at den hadde vært i sleep mode over natta, klikka det igjen. BSOD.

 

 

Microsoft ® Windows Debugger Version 6.11.0001.404 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\070310-18392-01.dmp]

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

 

Symbol search path is: *** Invalid ***

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

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

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

Executable search path is:

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

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7600 MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909

Machine Name:

Kernel base = 0xfffff800`02863000 PsLoadedModuleList = 0xfffff800`02aa0e50

Debug session time: Thu Jul 1 19:37:15.036 2010 (GMT+2)

System Uptime: 0 days 0:03:59.643

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

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

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

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

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

Loading User Symbols

Loading unloaded module list

.....

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 19, {3, fffff80002a62d90, fffff800027c2d90, fffff80002a62d90}

 

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

 

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

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

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

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

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

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

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

Probably caused by : ntoskrnl.exe ( nt+70600 )

 

Followup: MachineOwner

---------

 

 

[Malvado]

Anbefaler du tar en kjapp sjekk på følgende punkter :

 

*S.M.A.R.T status på harddiskene, Acronis har et kurrant gratisprogram som kan benyttes.

*I og med du får litt feil farger på skjermen kan det være at du bør teste skjermkortet, prøv en annen driver og se om du får kjørt Occt perestroika sin gpu test. I tilegg bør du kunne fullføre både linpack testen og psu stress testen uten problemer.