Edit:
Arc,
Sorry, crappy internet connection here
jonathanwu,
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION
Usual causes: System service, Device driver, graphics driver, ?memory
STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Usual causes: Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack
STOP 0x000000C2: BAD_POOL_CALLER
Usual causes: Device driver, ?Memory
___________________________________________
- Check your RAM. Your dump files indicate possible memory corruption, especially the Bugcheck 7F.
:ar: http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Make at least 8 passes. also take note on point #3.
See Arc's post above
- Do you, by any chance, overclock? If yes, return to stock settings. Overclock often results in system instability
Code:
4: kd> !sysinfo cpuspeed
CPUID: "Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz"
[B][COLOR="Red"]MaxSpeed: 2800
CurrentSpeed: 2801[/COLOR][/B]
- Try to update your DirectX drivers as it is causing the crash also
Code:
Loaded symbol image file: dxgkrnl.sys
Image path: \SystemRoot\System32\drivers\dxgkrnl.sys
Image name: dxgkrnl.sys
[B][COLOR="red"]Timestamp: Tue Jul 14 06:38:56 2009 (4A5BC590)[/COLOR][/B]
:ar:
Download DirectX End-User Runtime Web Installer from Official Microsoft Download Center
- Check for possible system file damage
On elevated command prompt, run these two commands:
:ar:
chkdsk /r /f
:ar:
SFC /scannow
Let us know the results (Arc's catchprase
)
_____________________________________________
BSOD ANALYSIS
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8800255fbf9, fffff8800a18dac0, 0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
Probably caused by : memory_corruption
Followup: memory_corruption
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff88003c78785}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Unable to open image file: C:\ProgramData\dbg\sym\dxgkrnl.sys\4A5BC590f4000\dxgkrnl.sys
The system cannot find the file specified.
Probably caused by : dxgkrnl.sys ( dxgkrnl+32785 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff880043ab403, 0, 2b1c203dce0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
Probably caused by : memory_corruption
Followup: memory_corruption
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 1097, 34edd, fffff900c20d4ba0}
fffff900c20d40f0 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...
GetUlongFromAddress: unable to read from fffff800030331b0
Probably caused by : win32k.sys ( win32k!memset+10a0 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41201, fffff680000407d0, 80600003a5d3e847, fffffa80100a3c60}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bf2 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
