BSOD when rebooting/restarting

mzimmer4 · 27 Aug 2010

The crashes and restarts seem to be happening more frequently now. Nothing has really changed, but the system can't even stay on for more than 20 minutes or so without crashing... even with NO activity whatsoever. Is it possible that something is physically wrong with the motherboard? Or is this most likely a software issue?

**Capt.Jack Sparrow** · 27 Aug 2010

If possible disconnect your DVD Drive for few hours and see if your System crashes. Its a vague thought Make sure you disconnect the cable from Motherboard. Its some Hardware troubleshooting always makes hard if its some Hardware component is causing the issue.

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Bugcheck:

Code:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff800031b7548, The address that the exception occurred at
Arg3: fffff880031a19f8, Exception Record Address
Arg4: fffff880031a1260, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
nt!CmpDereferenceKeyControlBlock+5c
fffff800`031b7548 f7b618060000    div     eax,dword ptr [rsi+618h]

EXCEPTION_RECORD:  fffff880031a19f8 -- (.exr 0xfffff880031a19f8)
ExceptionAddress: fffff800031b7548 (nt!CmpDereferenceKeyControlBlock+0x000000000000005c)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880031a1260 -- (.cxr 0xfffff880031a1260)
rax=000000000a3a81f4 rbx=0000000000000000 rcx=00000000ee6b281c
rdx=0000000000000000 rsi=fffff8a000027620 rdi=fffff8a003444a70
rip=fffff800031b7548 rsp=fffff880031a1c30 rbp=0000000000000001
 r8=fffff8a000066808  r9=000000001ea79bab r10=fffff8a0034446f8
r11=fffffa80039f9b60 r12=00000000f8a5aa10 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010212
nt!CmpDereferenceKeyControlBlock+0x5c:
fffff800`031b7548 f7b618060000    div     eax,dword ptr [rsi+618h] ds:002b:fffff8a0`00027c38=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

LAST_CONTROL_TRANSFER:  from fffff800031b79c4 to fffff800031b7548

STACK_TEXT:  
fffff880`031a1c30 fffff800`031b79c4 : 00000000`00000000 00000000`00000001 fffff8a0`00027620 fffffa80`039f9b60 : nt!CmpDereferenceKeyControlBlock+0x5c
fffff880`031a1c80 fffff800`02ed1961 : fffff800`031b78dc fffff800`030695f8 fffffa80`039f9b60 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xe8
fffff880`031a1cb0 fffff800`03168c06 : 00000000`00000000 fffffa80`039f9b60 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02ea2c26 : fffff880`02f63180 fffffa80`039f9b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a19f0 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP: 
nt!CmpDereferenceKeyControlBlock+5c
fffff800`031b7548 f7b618060000    div     eax,dword ptr [rsi+618h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpDereferenceKeyControlBlock+5c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880031a1260 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c

BUCKET_ID:  X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c

Followup: MachineOwner


PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 00000000000aaed8, page frame number
Arg3: 0000000000000001, current share count
Arg4: 0000000000000000, 0

Debugging Details:
------------------


BUGCHECK_STR:  0x4E_7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002f1ff09 to fffff80002ebf740

STACK_TEXT:  
fffff880`02f8b638 fffff800`02f1ff09 : 00000000`0000004e 00000000`00000007 00000000`000aaed8 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f8b640 fffff800`02f33e5e : fffffa80`04938890 00000000`00000000 00000000`00000000 fffff880`0107efbc : nt! ?? ::FNODOBFM::`string'+0x16dc6
fffff880`02f8b680 fffff800`02ec1ae8 : fffffa80`0569000b 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x348b9
fffff880`02f8b710 fffff880`0187b8ee : 00000000`00000000 fffff800`02f73001 fffffa80`067d3428 00000000`00000000 : nt!IopfCompleteRequest+0x168
fffff880`02f8b7f0 fffff800`02ec1d26 : 00000000`00000000 fffff800`02e0b156 fffffa80`047dd4f0 00000000`00001000 : CLASSPNP!TransferPktComplete+0x1ce
fffff880`02f8b870 fffff880`0104d41a : 00000000`00000000 00000000`00000001 fffffa80`067d3340 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02f8b950 fffff880`0104d242 : fffffa80`067d3340 fffffa80`047dd4f0 fffffa80`067d3340 fffffa80`047e37d0 : ataport!IdeCompleteScsiIrp+0x62
fffff880`02f8b980 fffff880`01047e32 : 00000000`00000000 00000000`00000000 fffffa80`047e2a00 fffff800`02e31c60 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`02f8b9b0 fffff880`010507ed : fffffa80`047cf1a0 fffffa80`067d3340 00000000`00000000 fffffa80`067d3340 : ataport!IdeTranslateCompletedRequest+0x236
fffff880`02f8bae0 fffff880`010500ec : fffffa80`047cf1a0 00000000`00000000 fffffa80`047cf1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02f8bc10 fffff800`02ecabfc : fffff880`02f63180 0000000c`e08a3b21 fffffa80`047cf050 fffffa80`047cf118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02f8bcd0 fffff800`02ec7eea : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`0104ff44 : nt!KiRetireDpcList+0x1bc
fffff880`02f8bd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
CLASSPNP!TransferPktComplete+1ce
fffff880`0187b8ee 837c243002      cmp     dword ptr [rsp+30h],2

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  CLASSPNP!TransferPktComplete+1ce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: CLASSPNP

IMAGE_NAME:  CLASSPNP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11e

FAILURE_BUCKET_ID:  X64_0x4E_7_CLASSPNP!TransferPktComplete+1ce

BUCKET_ID:  X64_0x4E_7_CLASSPNP!TransferPktComplete+1ce

Followup: MachineOwner
---------

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002fb40bf, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880073b8a70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExDeferredFreePool+233
fffff800`02fb40bf 4c395008        cmp     qword ptr [rax+8],r10

CONTEXT:  fffff880073b8a70 -- (.cxr 0xfffff880073b8a70)
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa800395b6e0
rdx=fffff8a0091aafd0 rsi=fffff8a0091de000 rdi=fffff8a0091dc010
rip=fffff80002fb40bf rsp=fffff880073b9440 rbp=0000000000000004
 r8=0000000000000000  r9=fffff8a0091aafd0 r10=fffff8a0091aafe0
r11=0000000000000001 r12=fffffa800395b280 r13=0000000000000000
r14=000000000000001d r15=0000000000000001
iopl=0         nv up ei ng nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
nt!ExDeferredFreePool+0x233:
fffff800`02fb40bf 4c395008        cmp     qword ptr [rax+8],r10 ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80002fb40bf

STACK_TEXT:  
fffff880`073b9440 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExDeferredFreePool+0x233


FOLLOWUP_IP: 
nt!ExDeferredFreePool+233
fffff800`02fb40bf 4c395008        cmp     qword ptr [rax+8],r10

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!ExDeferredFreePool+233

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

STACK_COMMAND:  .cxr 0xfffff880073b8a70 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+233

BUCKET_ID:  X64_0x3B_nt!ExDeferredFreePool+233

Followup: Pool_corruption

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000eef112, The address that the exception occurred at
Arg3: fffff880031cb808, Exception Record Address
Arg4: fffff880031cb070, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
Wdf01000!imp_WdfRequestWdmGetIrp+66
fffff880`00eef112 66394108        cmp     word ptr [rcx+8],ax

EXCEPTION_RECORD:  fffff880031cb808 -- (.exr 0xfffff880031cb808)
ExceptionAddress: fffff88000eef112 (Wdf01000!imp_WdfRequestWdmGetIrp+0x0000000000000066)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000057ffc5375f0
Attempt to read from address 0000057ffc5375f0

CONTEXT:  fffff880031cb070 -- (.cxr 0xfffff880031cb070)
rax=0000000000001008 rbx=fffffa8003ac8a10 rcx=0000057ffc5375e8
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa800552b9c0
rip=fffff88000eef112 rsp=fffff880031cba40 rbp=0000057ffc621200
 r8=000000000000064b  r9=fffff88000f53310 r10=0000000000016a15
r11=fffff88002fd3180 r12=00000000002d0940 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
Wdf01000!imp_WdfRequestWdmGetIrp+0x66:
fffff880`00eef112 66394108        cmp     word ptr [rcx+8],ax ds:002b:0000057f`fc5375f0=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000057ffc5375f0

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b20e0
 0000057ffc5375f0 

FOLLOWUP_IP: 
cdrom!RequestPostWorkMcnRequest+45
fffff880`01905cb5 440fb6938b000000 movzx   r10d,byte ptr [rbx+8Bh]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88001905cb5 to fffff88000eef112

STACK_TEXT:  
fffff880`031cba40 fffff880`01905cb5 : 00000000`00000000 00000000`00000001 fffffa80`06553cb0 fffffa80`0552b9c0 : Wdf01000!imp_WdfRequestWdmGetIrp+0x66
fffff880`031cba90 fffff880`018fcdb8 : fffffa80`05633a00 0000057f`00000000 fffffa80`05633af0 fffff880`031cbb90 : cdrom!RequestPostWorkMcnRequest+0x45
fffff880`031cbb70 fffff880`00f0b6fb : 00000000`00000000 00000000`00000001 fffffa80`0552bf10 fffff800`0301f5f8 : cdrom!RequestProcessSerializedIoctl+0x590
fffff880`031cbc50 fffff800`03176c43 : fffffa80`05525720 fffff800`0307fe00 fffffa80`039ebb60 fffffa80`039ebb60 : Wdf01000!FxWorkItem::WorkItemThunk+0x113
fffff880`031cbc80 fffff800`02e87961 : fffff800`0316d800 fffff800`0316d8dc fffffa80`039ebb60 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031cbcb0 fffff800`0311ec06 : 00000000`00000000 fffffa80`039ebb60 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111
fffff880`031cbd40 fffff800`02e58c26 : fffff880`02f63180 fffffa80`039ebb60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : fffff880`031cc000 fffff880`031c6000 fffff880`031cb770 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  cdrom!RequestPostWorkMcnRequest+45

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdrom

IMAGE_NAME:  cdrom.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11a

STACK_COMMAND:  .cxr 0xfffff880031cb070 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_cdrom!RequestPostWorkMcnRequest+45

BUCKET_ID:  X64_0x7E_cdrom!RequestPostWorkMcnRequest+45

Followup: MachineOwner

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff8a00753bd00, the pool entry being checked.
Arg3: fffff8a00753bd00, the read back flink freelist value (should be the same as 2).
Arg4: fffff8a00753bf00, the read back blink freelist value (should be the same as 2).

Debugging Details:
------------------


BUGCHECK_STR:  0x19_3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002fb910b to fffff80002e86740

STACK_TEXT:  
fffff880`0828f8b8 fffff800`02fb910b : 00000000`00000019 00000000`00000003 fffff8a0`0753bd00 fffff8a0`0753bd00 : nt!KeBugCheckEx
fffff880`0828f8c0 fffff800`02fbb4c1 : 00000000`00000001 fffff8a0`07db1a40 00000000`00000001 00000000`00000000 : nt!ExDeferredFreePool+0xc7b
fffff880`0828f950 fffff800`02e8b8bc : fffffa80`0656d060 00000000`00000000 fffff880`656b6f54 fffffa80`03967e50 : nt!ExFreePoolWithTag+0x411
fffff880`0828fa00 fffff800`03156735 : fffff880`0828fca0 00000000`00000000 fffff8a0`07db1aa0 00000000`00000001 : nt!ObfDereferenceObject+0xdc
fffff880`0828fa60 fffff800`02e85993 : fffffa80`0656d060 fffffa80`0656d060 fffffa80`0656d060 00000000`00000001 : nt!NtSetInformationThread+0x254
fffff880`0828fc20 00000000`7776fe2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`038ee988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7776fe2a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!ExDeferredFreePool+c7b
fffff800`02fb910b cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExDeferredFreePool+c7b

FOLLOWUP_NAME:  Pool_corruption

IMAGE_NAME:  Pool_Corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: Pool_Corruption

FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c7b

BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+c7b

Followup: Pool_corruption

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff96000142c6e, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88005dde0d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!TimersProc+142
fffff960`00142c6e 488910          mov     qword ptr [rax],rdx

CONTEXT:  fffff88005dde0d0 -- (.cxr 0xfffff88005dde0d0)
rax=0000000000000000 rbx=fffff900c1aafa00 rcx=fffff900c1abc1e8
rdx=fffff900c1aafa60 rsi=0000000000004479 rdi=fffff900c1aafa18
rip=fffff96000142c6e rsp=fffff88005ddeaa0 rbp=0000000000000270
 r8=fffffa80054560e8  r9=0000000000000000 r10=fffffffffffffffe
r11=0000000000000000 r12=0000000000000000 r13=fffff9600035f2c0
r14=0000000000000002 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
win32k!TimersProc+0x142:
fffff960`00142c6e 488910          mov     qword ptr [rax],rdx ds:002b:00000000`00000000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff960001436a4 to fffff96000142c6e

STACK_TEXT:  
fffff880`05ddeaa0 fffff960`001436a4 : 00000000`00000000 fffff960`0035fa90 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x142
fffff880`05ddeaf0 fffff960`000d46cc : fffffa80`0000007b 00000000`0000000f fffff880`00000001 00000000`00000000 : win32k!RawInputThread+0x9b4
fffff880`05ddebc0 fffff960`00153fa6 : fffffa80`00000002 fffff880`05da2f40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`05ddebf0 fffff800`02ecb993 : fffffa80`05cf6b60 00000000`00000004 000007ff`fffae000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`05ddec20 000007fe`fd043d3a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00e6fe78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd043d3a


FOLLOWUP_IP: 
win32k!TimersProc+142
fffff960`00142c6e 488910          mov     qword ptr [rax],rdx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!TimersProc+142

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c483f

STACK_COMMAND:  .cxr 0xfffff88005dde0d0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!TimersProc+142

BUCKET_ID:  X64_0x3B_win32k!TimersProc+142

Followup: MachineOwner
---------

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff780c0000000
Arg3: 0000000000001d60
Arg4: 00000da700003ec0

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ee1091 to fffff80002e71740

STACK_TEXT:  
fffff880`069bf2d8 fffff800`02ee1091 : 00000000`0000001a 00000000`00005003 fffff780`c0000000 00000000`00001d60 : nt!KeBugCheckEx
fffff880`069bf2e0 fffff800`02e8e776 : fffff6fc`c0061af8 00000000`00000001 fffff880`00000001 ffffffff`ffff0001 : nt! ?? ::FNODOBFM::`string'+0x2a1af
fffff880`069bf450 fffff800`02e9d7c1 : fffff980`0c35f000 00000000`0285f000 fffff880`00000004 fffff880`069bf638 : nt!MmCheckCachedPageStates+0x4d6
fffff880`069bf600 fffff800`02e9d434 : fffffa80`03d74e10 00000000`01961e40 fffff880`069bf740 00000000`00000000 : nt!CcMapAndCopyInToCache+0x301
fffff880`069bf6f0 fffff880`012e7fb8 : 00000000`0286f275 fffffa80`03d72400 fffff880`069bf7e0 fffffa80`00010000 : nt!CcCopyWrite+0x194
fffff880`069bf780 fffff880`01001132 : fffffa80`03d724a0 fffff880`01004732 00000000`00010000 00000000`00010001 : Ntfs!NtfsCopyWriteA+0x208
fffff880`069bf970 fffff880`01004c2a : fffff880`069bfa40 fffffa80`03d60968 00000000`01961e00 00000000`00010000 : fltmgr!FltpPerformFastIoCall+0xf2
fffff880`069bf9d0 fffff880`010227fe : 00000000`00010000 00000000`00000000 fffffa80`03d724a0 fffff880`069bfb40 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`069bfa10 fffff800`0318880e : fffffa80`03d72514 fffff880`069bfad8 00000000`00000000 fffffa80`03d72514 : fltmgr!FltpFastIoWrite+0x1ce
fffff880`069bfab0 fffff800`02e70993 : 00000000`00000101 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x5ad
fffff880`069bfbb0 00000000`76cffdda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000bb0c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76cffdda


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2a1af
fffff800`02ee1091 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2a1af

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a1af

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a1af

Followup: MachineOwner
---------

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001014442, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b80e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
volsnap!VspLookupTableEntryWorker+12
fffff880`01014442 498911          mov     qword ptr [r9],rdx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffb510 -- (.trap 0xfffff88002ffb510)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000009 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa800490b8b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001014442 rsp=fffff88002ffb6a0 rbp=0000000000000000
 r8=fffffa80060fc720  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
volsnap!VspLookupTableEntryWorker+0x12:
fffff880`01014442 498911          mov     qword ptr [r9],rdx ds:0003:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e7fca9 to fffff80002e80740

STACK_TEXT:  
fffff880`02ffb3c8 fffff800`02e7fca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02ffb3d0 fffff800`02e7e920 : 00000000`00000200 fffffa80`0490b8b0 fffffa80`04295440 fffffa80`04914b60 : nt!KiBugCheckDispatch+0x69
fffff880`02ffb510 fffff880`01014442 : 00000000`00000000 fffffa80`04a69000 fffffa80`04903d90 fffffa80`04903c40 : nt!KiPageFault+0x260
fffff880`02ffb6a0 fffff880`01017f99 : fffffa80`0490bb7b 00000000`00000000 00000000`00000000 fffffa80`3fffffff : volsnap!VspLookupTableEntryWorker+0x12
fffff880`02ffb6d0 fffff800`02e82d26 : fffffa80`0490bb33 fffffa80`048fdcd0 fffffa80`0490b8b0 fffffa80`0490b8b0 : volsnap!VspLookupTableEntry+0x9
fffff880`02ffb710 fffff880`018c48ee : 00000000`00000000 fffff800`02f34001 fffffa80`04295140 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02ffb7f0 fffff800`02e82d26 : 00000000`00000000 fffff800`033f1156 fffffa80`04804ea0 00000000`00004000 : CLASSPNP!TransferPktComplete+0x1ce
fffff880`02ffb870 fffff880`00c5241a : 00000000`00000000 00000000`00000001 fffffa80`04295010 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02ffb950 fffff880`00c52242 : fffffa80`04295010 fffffa80`04804ea0 fffffa80`04295010 fffffa80`048067d0 : ataport!IdeCompleteScsiIrp+0x62
fffff880`02ffb980 fffff880`00c4ce32 : 00000000`00000000 00000000`00000000 fffffa80`04805a00 fffff800`03417c60 : ataport!IdeCommonCrbCompletion+0x5a
fffff880`02ffb9b0 fffff880`00c557ed : fffffa80`047ec1a0 fffffa80`04295010 00000000`00000000 fffffa80`04295010 : ataport!IdeTranslateCompletedRequest+0x236
fffff880`02ffbae0 fffff880`00c550ec : fffffa80`047ec1a0 00000000`00000000 fffffa80`047ec1a0 00000000`00000000 : ataport!IdeProcessCompletedRequests+0x4d5
fffff880`02ffbc10 fffff800`02e8bbfc : fffff880`02fd3180 00000001`18ba4e65 fffffa80`047ec050 fffffa80`047ec118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`02ffbcd0 fffff800`02e88eea : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`00c54f44 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
volsnap!VspLookupTableEntryWorker+12
fffff880`01014442 498911          mov     qword ptr [r9],rdx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  volsnap!VspLookupTableEntryWorker+12

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: volsnap

IMAGE_NAME:  volsnap.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc128

FAILURE_BUCKET_ID:  X64_0xD1_volsnap!VspLookupTableEntryWorker+12

BUCKET_ID:  X64_0xD1_volsnap!VspLookupTableEntryWorker+12

Followup: MachineOwner
---------

3: kd> lmvm volsnap
start             end                 module name
fffff880`01000000 fffff880`0104c000   volsnap    (pdb symbols)          k:\symbols\volsnap.pdb\EF40184814C849B584803DCF471EA1DE2\volsnap.pdb
    Loaded symbol image file: volsnap.sys
    Mapped memory image file: K:\Symbols\volsnap.sys\4A5BC1284c000\volsnap.sys
    Image path: \SystemRoot\system32\DRIVERS\volsnap.sys
    Image name: volsnap.sys
    Timestamp:        Tue Jul 14 04:50:08 2009 (4A5BC128)
    CheckSum:         000568C8
    ImageSize:        0004C000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     volsnap.sys
    OriginalFilename: volsnap.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  Volume Shadow Copy Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.



SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800453ad45, The address that the exception occurred at
Arg3: fffff880023bf6a8, Exception Record Address
Arg4: fffff880023bef10, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79
fffff880`0453ad45 ff90a8000000    call    qword ptr [rax+0A8h]

EXCEPTION_RECORD:  fffff880023bf6a8 -- (.exr 0xfffff880023bf6a8)
ExceptionAddress: fffff8800453ad45 (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x0000000000000079)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000000a8
Attempt to read from address 00000000000000a8

CONTEXT:  fffff880023bef10 -- (.cxr 0xfffff880023bef10)
rax=0000000000000000 rbx=fffff8a008d4b840 rcx=fffffa8005ecfec0
rdx=fffffa8003c4c800 rsi=fffffa8005ec2000 rdi=fffffa8005ec2000
rip=fffff8800453ad45 rsp=fffff880023bf8e0 rbp=fffffa8006d1d050
 r8=fffffa8003cc5c00  r9=0000000000000000 r10=0000000000000000
r11=0000000000000006 r12=fffffa8003c4c800 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x79:
fffff880`0453ad45 ff90a8000000    call    qword ptr [rax+0A8h] ds:002b:00000000`000000a8=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000000a8

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ae0e0
 00000000000000a8 

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79
fffff880`0453ad45 ff90a8000000    call    qword ptr [rax+0A8h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff88004537ed3 to fffff8800453ad45

STACK_TEXT:  
fffff880`023bf8e0 fffff880`04537ed3 : 00000000`00000000 fffffa80`03cf0018 00000000`00000003 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+0x79
fffff880`023bf910 fffff880`0455265d : 00000000`00000000 fffff8a0`08cf44f0 fffffa80`00000000 fffffa80`03cc5c30 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x43f
fffff880`023bfae0 fffff880`04552398 : fffff880`009ecf40 fffff880`04551d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`023bfcd0 fffff880`04551e96 : 00000000`00000000 fffffa80`03c7a830 00000000`00000080 fffffa80`054e4010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`023bfd00 fffff800`0311ac06 : 00000000`0279c5bc fffffa80`05ea9770 fffffa80`0396c890 fffffa80`05ea9770 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`023bfd40 fffff800`02e54c26 : fffff880`009e8180 fffffa80`05ea9770 fffff880`009f2fc0 fffff880`01268534 : nt!PspSystemThreadStartup+0x5a
fffff880`023bfd80 00000000`00000000 : fffff880`023c0000 fffff880`023ba000 fffff880`023bf690 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

STACK_COMMAND:  .cxr 0xfffff880023bef10 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79

Followup: MachineOwner
---------

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002fa790d, The address that the exception occurred at
Arg3: fffff880031af078, Exception Record Address
Arg4: fffff880031ae8e0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!ExAllocatePoolWithTag+53d
fffff800`02fa790d 48895808        mov     qword ptr [rax+8],rbx

EXCEPTION_RECORD:  fffff880031af078 -- (.exr 0xfffff880031af078)
ExceptionAddress: fffff80002fa790d (nt!ExAllocatePoolWithTag+0x000000000000053d)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880031ae8e0 -- (.cxr 0xfffff880031ae8e0)
rax=69634d4300010103 rbx=fffffa800395a2a0 rcx=fffff8a0034207a0
rdx=000000000000001c rsi=0000000000001000 rdi=0000000000000001
rip=fffff80002fa790d rsp=fffff880031af2b0 rbp=fffffa800395a140
 r8=0000000000000001  r9=fffffa800395a2a0 r10=fffffa800395a148
r11=0000000000000001 r12=0000000000000003 r13=0000000000000000
r14=fffffa80039ff040 r15=0000000065536f49
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ExAllocatePoolWithTag+0x53d:
fffff800`02fa790d 48895808        mov     qword ptr [rax+8],rbx ds:002b:69634d43`0001010b=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ab0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
USBPORT!USBPORT_CreateRootHubPdo+16e
fffff880`048f45ae 488d4c2468      lea     rcx,[rsp+68h]

BUGCHECK_STR:  0x7E

LOCK_ADDRESS:  fffff80003077400 -- (!locks fffff80003077400)

Resource @ nt!PiEngineLock (0xfffff80003077400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80003077400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff800031a211b to fffff80002fa790d

STACK_TEXT:  
fffff880`031af2b0 fffff800`031a211b : fffffa80`00000001 fffff8a0`00001540 00000000`00000000 fffff880`00000000 : nt!ExAllocatePoolWithTag+0x53d
fffff880`031af3a0 fffff800`030e19d8 : 00000000`0000002a 00000000`00000002 fffff880`031af548 fffff800`02e75d26 : nt! ?? ::NNGAKEGL::`string'+0x9d1d
fffff880`031af400 fffff800`030e0208 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff880`031af638 : nt!IopCreateDefaultDeviceSecurityDescriptor+0x88
fffff880`031af450 fffff880`048f45ae : fffffa80`055dc801 fffffa80`054ac1a0 fffffa80`054ac050 00000000`00000000 : nt!IoCreateDevice+0xa8
fffff880`031af5d0 fffff880`048ee3f9 : fffffa80`054ac1a0 fffffa80`055dc6f0 fffffa80`055dc850 fffffa80`055dc850 : USBPORT!USBPORT_CreateRootHubPdo+0x16e
fffff880`031af710 fffff880`048d98d5 : 00000000`00000000 fffff880`031af880 fffffa80`055dc6f0 fffffa80`039bea20 : USBPORT!USBPORT_FdoPnP+0xb91
fffff880`031af7c0 fffff800`0323206e : 00000000`00000000 00000000`00000000 fffffa80`056f4810 fffff880`02f63180 : USBPORT!USBPORT_DispatchPnP+0x1d
fffff880`031af7f0 fffff800`032323da : 00000000`00000000 fffffa80`056f4810 fffff800`02f72d30 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031af830 fffff800`032346c7 : fffff800`030771c0 fffffa80`043c9b10 00000000`00000002 00000000`00000000 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031af8f0 fffff800`032602cc : fffffa80`043c9b10 fffffa80`03a3003c fffffa80`03a31d90 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`031af950 fffff800`032607fc : fffff800`03074d80 00000000`00000000 00000000`00000001 fffff800`030e0840 : nt!PipProcessDevNodeTree+0x21c
fffff880`031afbc0 fffff800`02f75382 : 00000001`00000003 fffff800`030185f8 00000000`00000001 00000000`00000000 : nt!PiProcessStartSystemDevices+0x7c
fffff880`031afc10 fffff800`02e80961 : fffff800`02f75080 fffff800`030df001 fffff800`03018500 480fe783`c78b4800 : nt!PnpDeviceActionWorker+0x302
fffff880`031afcb0 fffff800`03117c06 : 000001fc`e9c00000 fffffa80`039ff040 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111
fffff880`031afd40 fffff800`02e51c26 : fffff880`02f63180 fffffa80`039ff040 fffff880`02f6dfc0 8b4cf702`41f7f748 : nt!PspSystemThreadStartup+0x5a
fffff880`031afd80 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`031af0f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  USBPORT!USBPORT_CreateRootHubPdo+16e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME:  USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc07

STACK_COMMAND:  .cxr 0xfffff880031ae8e0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_USBPORT!USBPORT_CreateRootHubPdo+16e

BUCKET_ID:  X64_0x7E_USBPORT!USBPORT_CreateRootHubPdo+16e

Followup: MachineOwner
---------


SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 00000000000cef03, The address that the exception occurred at
Arg3: fffff880031bd668, Exception Record Address
Arg4: fffff880031bced0, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+16
00000000`000cef03 ??              ???

EXCEPTION_RECORD:  fffff880031bd668 -- (.exr 0xfffff880031bd668)
ExceptionAddress: 00000000000cef03
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 00000000000cef03
Attempt to execute non-executable address 00000000000cef03

CONTEXT:  fffff880031bced0 -- (.cxr 0xfffff880031bced0)
rax=00000000000cef03 rbx=0000000000000000 rcx=00000000000cef05
rdx=fffffa800529ccd0 rsi=fffffa800481b1b0 rdi=fffffa800529cc88
rip=00000000000cef03 rsp=fffff880031bd8a8 rbp=fffff880031bd918
 r8=fffff880031bd901  r9=0000000000000001 r10=fffffa8004c56d30
r11=fffff880031bd870 r12=fffffa8004929c28 r13=fffff880031bdb20
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010292
00000000`000cef03 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  00000000000cef03

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800031080e0
 00000000000cef03 

FOLLOWUP_IP: 
ataport!IdePortTranslateSrbToCrb+4f
fffff880`010405ab 3bc3            cmp     eax,ebx

FAILED_INSTRUCTION_ADDRESS: 
+64cb952f0091de0c
00000000`000cef03 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff880010405ab to 00000000000cef03

STACK_TEXT:  
fffff880`031bd8a8 fffff880`010405ab : fffffa80`0529cc88 fffffa80`04929b10 fffff880`00000020 fffffa80`05325001 : 0xcef03
fffff880`031bd8b0 fffff880`010449b3 : fffffa80`0481b060 fffffa80`0529cc88 fffffa80`0481b1b0 fffff880`00e2f016 : ataport!IdePortTranslateSrbToCrb+0x4f
fffff880`031bd8e0 fffff880`010404ee : fffffa80`04929b10 00000000`00000000 fffffa80`03957e40 fffffa80`04929b10 : ataport!IdePortPdoDispatch+0x87
fffff880`031bd910 fffff880`00e29787 : fffffa80`04929b10 fffffa80`04929c01 fffffa80`04929c01 fffffa80`04929c48 : ataport!IdePortDispatch+0x16
fffff880`031bd940 fffff880`00e31751 : fffff880`00e4fb50 fffff880`00c0b77b fffff880`031bdb20 fffffa80`04929c28 : ACPI!ACPIDispatchForwardIrp+0x37
fffff880`031bd970 fffff880`00e29a1f : fffff880`00e4fb50 fffffa80`039a0a00 fffffa80`04929b10 fffff880`00c877c0 : ACPI!ACPIIrpDispatchDeviceControl+0x75
fffff880`031bd9a0 fffff880`00c0e0c2 : fffffa80`05525540 fffff880`031bdb50 fffff880`00c877c0 fffffa80`05325020 : ACPI!ACPIDispatchIrp+0x12b
fffff880`031bda20 fffff880`00c2359f : fffffa80`05325020 fffffa80`00000000 00000000`00000000 fffff880`019b05d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`031bdad0 fffff880`019cb012 : fffffa80`00000020 fffffa80`05525540 fffffa80`05325020 fffffa80`0531ca20 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`031bdb20 fffff880`019c1dab : fffffa80`0529cc00 0000057f`f9414bf8 00000000`00000000 fffff880`0177d180 : cdrom!RequestSendMcnRequest+0x5a
fffff880`031bdb70 fffff880`00c406fb : 00000000`00000000 00000000`00000000 fffffa80`0531dbf0 fffff800`030755f8 : cdrom!RequestProcessSerializedIoctl+0x583
fffff880`031bdc50 fffff800`031ccc43 : fffffa80`0531fc70 fffffa80`049fde00 fffffa80`039ff680 fffffa80`039ff680 : Wdf01000!FxWorkItem::WorkItemThunk+0x113
fffff880`031bdc80 fffff800`02edd961 : fffff800`03075500 fffff800`031ccc20 fffffa80`039ff680 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031bdcb0 fffff800`03174c06 : 00000000`00000000 fffffa80`039ff680 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111
fffff880`031bdd40 fffff800`02eaec26 : fffff880`02f63180 fffffa80`039ff680 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031bdd80 00000000`00000000 : fffff880`031be000 fffff880`031b8000 fffff880`031bd9f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ataport!IdePortTranslateSrbToCrb+4f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc118

STACK_COMMAND:  .cxr 0xfffff880031bced0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_ataport!IdePortTranslateSrbToCrb+4f

BUCKET_ID:  X64_0x7E_BAD_IP_ataport!IdePortTranslateSrbToCrb+4f

Followup: MachineOwner

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800031a4916, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880069e3ab0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!CmpAllocateKeyControlBlock+72
fffff800`031a4916 48895808        mov     qword ptr [rax+8],rbx

CONTEXT:  fffff880069e3ab0 -- (.cxr 0xfffff880069e3ab0)
rax=0000000000000000 rbx=fffff800030cb040 rcx=fffff8a002969ee8
rdx=fffff880069e44e8 rsi=fffff8a0006f9010 rdi=0000000000000001
rip=fffff800031a4916 rsp=fffff880069e4480 rbp=000000000249f1f8
 r8=fffff8a00696e1fc  r9=fffff8a002b656f8 r10=fffff8a008d9c132
r11=0000000000000000 r12=0000000000000000 r13=ffffffffffffffff
r14=fffff8a00696e1fc r15=fffff8a002b656f8
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
nt!CmpAllocateKeyControlBlock+0x72:
fffff800`031a4916 48895808        mov     qword ptr [rax+8],rbx ds:002b:00000000`00000008=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff800031a4916

STACK_TEXT:  
fffff880`069e4480 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpAllocateKeyControlBlock+0x72


FOLLOWUP_IP: 
nt!CmpAllocateKeyControlBlock+72
fffff800`031a4916 48895808        mov     qword ptr [rax+8],rbx

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpAllocateKeyControlBlock+72

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880069e3ab0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpAllocateKeyControlBlock+72

BUCKET_ID:  X64_0x3B_nt!CmpAllocateKeyControlBlock+72

Followup: MachineOwner
---------

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff8800318c368
Arg3: fffff8800318bbd0
Arg4: fffff80002fb0327

Debugging Details:
------------------


EXCEPTION_RECORD:  fffff8800318c368 -- (.exr 0xfffff8800318c368)
ExceptionAddress: fffff80002fb0327 (nt!ExFreePoolWithTag+0x0000000000000277)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000080
Attempt to read from address 0000000000000080

CONTEXT:  fffff8800318bbd0 -- (.cxr 0xfffff8800318bbd0)
rax=0000000000000200 rbx=fffff8a008475a70 rcx=00000000000005a5
rdx=fffff88002f64180 rsi=0000000000000003 rdi=0000000000000001
rip=fffff80002fb0327 rsp=fffff8800318c5a0 rbp=0000000000000000
 r8=0000000000002d28  r9=0000000000000030 r10=fffff80002e0b000
r11=0000000000000121 r12=0000000000000003 r13=fffff8a008475a80
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!ExFreePoolWithTag+0x277:
fffff800`02fb0327 458b8780000000  mov     r8d,dword ptr [r15+80h] ds:002b:00000000`00000080=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000080

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b30e0
 0000000000000080 

FOLLOWUP_IP: 
fileinfo!FIStreamLog+89
fffff880`010cf55d 4c8b1534c5ffff  mov     r10,qword ptr [fileinfo!FIGlobals+0x798 (fffff880`010cba98)]

FAULTING_IP: 
nt!ExFreePoolWithTag+277
fffff800`02fb0327 458b8780000000  mov     r8d,dword ptr [r15+80h]

BUGCHECK_STR:  0x24

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff800032c7bec to fffff80002fb0327

STACK_TEXT:  
fffff880`0318c5a0 fffff800`032c7bec : fffff800`0301cc88 fffff880`04168332 00000000`4b466650 00000000`00000000 : nt!ExFreePoolWithTag+0x277
fffff880`0318c650 fffff800`02f9c559 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`0847e140 : nt!PfpRpFileKeyUpdate+0x4cc
fffff880`0318c6e0 fffff880`010cf55d : 00000000`00000000 00000000`00000000 fffff880`0318c860 fffff880`0318ca90 : nt!PfFileInfoNotify+0x549
fffff880`0318c770 fffff880`010cf746 : fffff8a0`07dd75c0 fffff8a0`07dd75c0 00000000`00000000 00000000`00000000 : fileinfo!FIStreamLog+0x89
fffff880`0318c840 fffff880`0108865e : fffff880`0416cecc 00000000`00000000 ffffffff`ffffffff fffffa80`03d2f590 : fileinfo!FIStreamCleanup+0x96
fffff880`0318c890 fffff880`010a422d : fffff8a0`07dd7578 fffff880`0107a000 00000000`00000000 00000000`00000001 : fltmgr!DoFreeContext+0x7e
fffff880`0318c8c0 fffff880`0109fbc1 : fffffa80`04abf010 00000000`00000130 fffff8a0`0847e140 fffff8a0`0847e140 : fltmgr! ?? ::NNGAKEGL::`string'+0x1196
fffff880`0318c8f0 fffff880`0109fb7b : fffffa80`04abf010 fffff8a0`0847e3a8 fffffa80`04abf010 00000000`00000000 : fltmgr!CleanupStreamListCtrl+0x21
fffff880`0318c920 fffff800`0316a896 : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`0719c660 : fltmgr!DeleteStreamListCtrlCallback+0x6b
fffff880`0318c950 fffff880`012b0bcc : fffff8a0`0847e140 fffffa80`03a70680 fffff880`0318ca28 00000000`00000706 : nt!FsRtlTeardownPerStreamContexts+0xe2
fffff880`0318c9a0 fffff880`012b08d5 : 00000000`00000000 00000000`00000000 fffff800`03020500 00000000`00000001 : Ntfs!NtfsDeleteScb+0x108
fffff880`0318c9e0 fffff880`01223cb4 : fffff8a0`0847e040 fffff8a0`0847e140 fffff800`03020500 00000000`00000000 : Ntfs!NtfsRemoveScb+0x61
fffff880`0318ca20 fffff880`012ae2dc : fffff8a0`0847e010 fffff800`030205a0 fffff880`0318cb52 fffffa80`05628010 : Ntfs!NtfsPrepareFcbForRemoval+0x50
fffff880`0318ca50 fffff880`0122c882 : fffffa80`05628010 fffffa80`05628010 fffff8a0`0847e010 00000000`00000000 : Ntfs!NtfsTeardownStructures+0xdc
fffff880`0318cad0 fffff880`012c5813 : fffffa80`05628010 fffff800`030205a0 fffff8a0`0847e010 00000000`00000009 : Ntfs!NtfsDecrementCloseCounts+0xa2
fffff880`0318cb10 fffff880`0129f38f : fffffa80`05628010 fffff8a0`0847e140 fffff8a0`0847e010 fffffa80`04a70180 : Ntfs!NtfsCommonClose+0x353
fffff880`0318cbe0 fffff800`02e88961 : 00000000`00000000 fffff800`03136d00 fffffa80`03a70601 00000000`00000002 : Ntfs!NtfsFspClose+0x15f
fffff880`0318ccb0 fffff800`0311fc06 : 00000000`00000000 fffffa80`03a70680 00000000`00000080 fffffa80`03a4d040 : nt!ExpWorkerThread+0x111
fffff880`0318cd40 fffff800`02e59c26 : fffff880`02f64180 fffffa80`03a70680 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0318cd80 00000000`00000000 : fffff880`0318d000 fffff880`03187000 fffff880`0318c9f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  fileinfo!FIStreamLog+89

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fileinfo

IMAGE_NAME:  fileinfo.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc481

STACK_COMMAND:  .cxr 0xfffff8800318bbd0 ; kb

FAILURE_BUCKET_ID:  X64_0x24_fileinfo!FIStreamLog+89

BUCKET_ID:  X64_0x24_fileinfo!FIStreamLog+89

Followup: MachineOwner
---------


SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960000c6f14, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88006ea5660, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!DecPaintCount+4
fffff960`000c6f14 8382e0010000ff  add     dword ptr [rdx+1E0h],0FFFFFFFFh

CONTEXT:  fffff88006ea5660 -- (.cxr 0xfffff88006ea5660)
rax=0000000000000000 rbx=0000000000000001 rcx=fffff900c080ff40
rdx=000000000002c018 rsi=0000000000000000 rdi=fffff900c080ff40
rip=fffff960000c6f14 rsp=fffff88006ea6038 rbp=fffff9600035ac00
 r8=0000000000000000  r9=0000000000000000 r10=fffff80002e01000
r11=fffff88006ea6030 r12=0000000000000000 r13=ffffffffffffffff
r14=0000000000000002 r15=00000000000500b2
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!DecPaintCount+0x4:
fffff960`000c6f14 8382e0010000ff  add     dword ptr [rdx+1E0h],0FFFFFFFFh ds:002b:00000000`0002c1f8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960000c6f14

STACK_TEXT:  
fffff880`06ea6038 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!DecPaintCount+0x4


FOLLOWUP_IP: 
win32k!DecPaintCount+4
fffff960`000c6f14 8382e0010000ff  add     dword ptr [rdx+1E0h],0FFFFFFFFh

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!DecPaintCount+4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c483f

STACK_COMMAND:  .cxr 0xfffff88006ea5660 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!DecPaintCount+4

BUCKET_ID:  X64_0x3B_win32k!DecPaintCount+4

Followup: MachineOwner


CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8005d81b30, Terminating object
Arg3: fffffa8005d81e10, Process image file name
Arg4: fffff800031d75d0, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa8005d81b30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BUGCHECK_STR:  0xF4_C0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`05fd9b08 fffff800`03258652 : 00000000`000000f4 00000000`00000003 fffffa80`05d81b30 fffffa80`05d81e10 : nt!KeBugCheckEx
fffff880`05fd9b10 fffff800`032013e3 : ffffffff`ffffffff fffffa80`05d7db60 fffffa80`05d81b30 fffffa80`05d81b30 : nt!PspCatchCriticalBreak+0x92
fffff880`05fd9b50 fffff800`0318980c : ffffffff`ffffffff 00000000`00000001 fffffa80`05d81b30 fffffa80`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17946
fffff880`05fd9ba0 fffff800`02ecb993 : fffffa80`05d81b30 000007ff`c0000005 00000000`c0000001 fffffa80`05d7db60 : nt!NtTerminateProcess+0x20c
fffff880`05fd9c20 00000000`777c001a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0018f2a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x777c001a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_C0000005_IMAGE_wininit.exe

Followup: MachineOwner


SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff800031b7548, The address that the exception occurred at
Arg3: fffff880031a19f8, Exception Record Address
Arg4: fffff880031a1260, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

FAULTING_IP: 
nt!CmpDereferenceKeyControlBlock+5c
fffff800`031b7548 f7b618060000    div     eax,dword ptr [rsi+618h]

EXCEPTION_RECORD:  fffff880031a19f8 -- (.exr 0xfffff880031a19f8)
ExceptionAddress: fffff800031b7548 (nt!CmpDereferenceKeyControlBlock+0x000000000000005c)
   ExceptionCode: c0000094 (Integer divide-by-zero)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880031a1260 -- (.cxr 0xfffff880031a1260)
rax=000000000a3a81f4 rbx=0000000000000000 rcx=00000000ee6b281c
rdx=0000000000000000 rsi=fffff8a000027620 rdi=fffff8a003444a70
rip=fffff800031b7548 rsp=fffff880031a1c30 rbp=0000000000000001
 r8=fffff8a000066808  r9=000000001ea79bab r10=fffff8a0034446f8
r11=fffffa80039f9b60 r12=00000000f8a5aa10 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei pl nz ac pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010212
nt!CmpDereferenceKeyControlBlock+0x5c:
fffff800`031b7548 f7b618060000    div     eax,dword ptr [rsi+618h] ds:002b:fffff8a0`00027c38=00000000
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION}  Integer division by zero.

LAST_CONTROL_TRANSFER:  from fffff800031b79c4 to fffff800031b7548

STACK_TEXT:  
fffff880`031a1c30 fffff800`031b79c4 : 00000000`00000000 00000000`00000001 fffff8a0`00027620 fffffa80`039f9b60 : nt!CmpDereferenceKeyControlBlock+0x5c
fffff880`031a1c80 fffff800`02ed1961 : fffff800`031b78dc fffff800`030695f8 fffffa80`039f9b60 00000000`00000000 : nt!CmpDelayDerefKCBWorker+0xe8
fffff880`031a1cb0 fffff800`03168c06 : 00000000`00000000 fffffa80`039f9b60 00000000`00000080 fffffa80`0396c890 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02ea2c26 : fffff880`02f63180 fffffa80`039f9b60 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a19f0 00000000`00000000 : nt!KxStartSystemThread+0x16


FOLLOWUP_IP: 
nt!CmpDereferenceKeyControlBlock+5c
fffff800`031b7548 f7b618060000    div     eax,dword ptr [rsi+618h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CmpDereferenceKeyControlBlock+5c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

STACK_COMMAND:  .cxr 0xfffff880031a1260 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c

BUCKET_ID:  X64_0x7E_nt!CmpDereferenceKeyControlBlock+5c

Followup: MachineOwner
---------

Hope this helps,
Captain

jcgriff2 · 27 Aug 2010

Hi -

16 BSODs < 24 hours; 9 different bugchecks is indicative of unknown hardware failure.

When you replaced the HDD, did you install Windows 7 on to it from DVD or use image from old HDD?

At this time, I would suggest that you wipe the HDD clean and reinstall Windows 7. See if system is stable before installing any 3rd party apps.

Use KillDisk to wipe HDD --> Format HDD jcgriff2.com

Windbg Logs
--> http://jcgriff2.com/dbug_logs/_99-db..._jcgriff2_.txt
--> http://jcgriff2.com/dbug_logs/_99-db...riff2_.txt.zip

Regards. . .

jcgriff2

`

BSOD BUGCHECK SUMMARY

Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 20:47:05.418 2010 (GMT-4)
System Uptime: 0 days 0:00:13.838
Probably caused by : ntkrnlmp.exe ( nt!CmpDereferenceKeyControlBlock+5c )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
Bugcheck code 1000007E
Arguments ffffffff`c0000094 fffff800`031b7548 fffff880`031a19f8 fffff880`031a1260
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 20:45:20.469 2010 (GMT-4)
System Uptime: 0 days 0:00:20.264
BugCheck F4, {3, fffffa8005d81b30, fffffa8005d81e10, fffff800031d75d0}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
BUGCHECK_STR:  0xF4_C0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`05d81b30 fffffa80`05d81e10 fffff800`031d75d0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 16:33:03.647 2010 (GMT-4)
System Uptime: 0 days 0:21:13.067
Probably caused by : win32k.sys ( win32k!DecPaintCount+4 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`000c6f14 fffff880`06ea5660 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 16:11:23.374 2010 (GMT-4)
System Uptime: 0 days 0:26:07.794
Probably caused by : fileinfo.sys ( fileinfo!FIStreamLog+89 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`0318c368 fffff880`0318bbd0 fffff800`02fb0327
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 15:27:03.255 2010 (GMT-4)
System Uptime: 0 days 0:07:09.050
Probably caused by : ntkrnlmp.exe ( nt!CmpAllocateKeyControlBlock+72 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  explorer.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`031a4916 fffff880`069e3ab0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 15:19:27.579 2010 (GMT-4)
System Uptime: 0 days 0:05:06.000
Probably caused by : ataport.SYS ( ataport!IdePortTranslateSrbToCrb+4f )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 00000000`000cef03 fffff880`031bd668 fffff880`031bced0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 13:48:24.983 2010 (GMT-4)
System Uptime: 0 days 0:00:11.778
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_CreateRootHubPdo+16e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff800`02fa790d fffff880`031af078 fffff880`031ae8e0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 07:31:52.126 2010 (GMT-4)
System Uptime: 0 days 0:23:12.921
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+79 )
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`0453ad45 fffff880`023bf6a8 fffff880`023bef10
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 07:08:06.820 2010 (GMT-4)
System Uptime: 0 days 0:28:34.240
BugCheck D1, {0, 2, 1, fffff88001014442}
Probably caused by : volsnap.sys ( volsnap!VspLookupTableEntryWorker+12 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
Bugcheck code 000000D1
Arguments 00000000`00000000 00000000`00000002 00000000`00000001 fffff880`01014442
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 06:38:31.920 2010 (GMT-4)
System Uptime: 0 days 0:16:31.714
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a1af )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  WerFault.exe
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff780`c0000000 00000000`00001d60 00000da7`00003ec0
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 06:20:58.639 2010 (GMT-4)
System Uptime: 0 days 0:10:10.434
Probably caused by : win32k.sys ( win32k!TimersProc+142 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff960`00142c6e fffff880`05dde0d0 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 06:09:47.652 2010 (GMT-4)
System Uptime: 0 days 0:05:20.072
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+c7b )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 00000019
Arguments 00000000`00000003 fffff8a0`0753bd00 fffff8a0`0753bd00 fffff8a0`0753bf00
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 06:03:26.219 2010 (GMT-4)
System Uptime: 0 days 2:48:30.014
Probably caused by : cdrom.sys ( cdrom!RequestPostWorkMcnRequest+45 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
Bugcheck code 1000007E
Arguments ffffffff`c0000005 fffff880`00eef112 fffff880`031cb808 fffff880`031cb070
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 03:13:55.448 2010 (GMT-4)
System Uptime: 0 days 0:11:50.243
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+233 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02fb40bf fffff880`073b8a70 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Aug 27 03:01:01.890 2010 (GMT-4)
System Uptime: 0 days 5:35:33.685
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
BUGCHECK_STR:  0x4E_7
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
Bugcheck code 0000004E
Arguments 00000000`00000007 00000000`000aaed8 00000000`00000001 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Aug 26 20:36:16.707 2010 (GMT-4)
System Uptime: 0 days 4:06:07.501
Probably caused by : afd.sys ( afd!AfdTimerWheelHandler+19d )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments 00000000`00000030 00000000`00000002 00000000`00000001 fffff800`028dd6ef
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
by jcgriff2     
 
        J. C. Griffith, Microsoft MVP   
 
          https://mvp.support.microsoft.com/profile/Griffith   
 
          www.jcgriff2.com 
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

mzimmer4 · 28 Aug 2010

I did use the installation DVD when reinstalling Windows on the new hard drive. Going to try your KillDisk boot CD recommendation for now. I'll post back in a few once I reinstall Windows again.

mzimmer4 · 28 Aug 2010

While I wait (KillDisk is kind of a lengthy process for a 1TB hard drive)... is it possible that something may be corrupt on the Windows 7 OEM disc? Or with the motherboard itself?

mzimmer4 · 28 Aug 2010

So... I wiped the hard drive with the bootable KillDisk, but now I don't even think I'm able to reinstall Windows. I get to the beginning of the installation where it says "Setup is starting..." after I click "Install Now" and then I get a BSOD. I'll keep trying and post back if I have any success. Any ideas?

EDIT: I'm including some info about the crash during the Windows installation (since I can't really show dump files or error reports)...

An error has occurred and Windows has been shut down to prevent damage to your system...

PAGE_FAULT_IN_NONPAGED_AREA

Blah blah blah blah blah

Technical Information:
***STOP: 0x00000050 (0xFFFFF88003FACF90, 0x0000000000000000, 0xFFFFF8000CE7CA99, x0000000000000000

mzimmer4 · 28 Aug 2010

Got a little bit farther with the last attempt, but I keep getting crashes during installation.

karlsnooks · 28 Aug 2010

OK. Let's assume you have a hardware problem.

Now disconnect anything and everything. Remove all boards. Remove all memory. Disconnect your monitor, your keyboard, your mouse.

Be sure the the case is off so you can observe if the fans are spiinning and also so you can listen for the beep codes.

Trust only the mobo manufacturer's manual for the meaning of the beep codes.

If you don't get one then you are really in trouble.

If the beep code says no memory, then stick in one stick. Keep adding memory upto what ever you have.

Keep working thru the bios codes. All this time you keep a close eye on those fans that they are spiinning. Keep the cover off of the the computer thru out this entire exercise.

More often than not, although the user doesn't believe it.... Heat is your big enemy.

mzimmer4 · 28 Aug 2010

Followed instructions in previous post to the tee... disconnected all external devices like mouse, keyboard, monitor, ethernet cable, speakers... basically everything internally from the motherboard (except the beeper, case's power button, cpu, and all fans).

With no externals hooked up to the I/O panel in the back, I received a single short beep (meaning system boots successfully). Took out the memory... With no memory inserted I received continuous long beeps (mobo's book says this means graphics card not inserted properly)... put memory back in and got a single short beep (meaning system boots successfully). With no graphics card inserted, I received one long beep, 2 short beeps (meaning monitor or graphics card error). The book doesn't give a very detailed list of beep codes, and I tried to search online for some and was unsuccessful... yes, even tried Gigabyte's website. Turns out that Gigabyte doesn't provide a detailed list of beep codes and a lot of other people have had trouble finding the same information. Here's all that the book gives me:

1 short: System boots successfully
2 short: CMOS setting error
1 long, 1 short: Memory or motherboard error
1 long, 2 short: Monitor or graphics card error
1 long, 3 short: Ketboard error
1 long, 9 short: BIOS ROM error
Continuous long beeps: Graphics card not inserted properly
Continuous short beeps: Power error

As far as heat goes, it's in a fairly cool environment with 3 fans running in the case (not including the 2 fans in the power supply). I remember looking at the CPU temperature in the BIOS and it said it was 47 degrees Celsius if I remember correctly.

mzimmer4 · 28 Aug 2010

Conveniently, my 30-day replacement for the motherboard from Newegg ran out last week; however, Gigabyte carries a 3-year warranty on their motherboards. Should I look into that? Or do you guys think I'll run into the same problems even with a new motherboard? I've ran the recommended hardware and memory tests and they've all come back clean. But I'm still having trouble with crashes simply installing Windows. Is this a problem with the Windows disc I received or something with the motherboard?