Code:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c56e50
Debug session time: Mon Nov 15 05:03:00.581 2010 (GMT-5)
System Uptime: 0 days 0:02:12.329
Loading Kernel Symbols
..............................................Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffffa7ff3ffffe0, 2, 1, fffff80002ad1e89}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffa7ff3ffffe0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ad1e89, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc10e0
fffffa7ff3ffffe0
CURRENT_IRQL: 2
FAULTING_IP:
nt!MmZeroPageThread+3d4
fffff800`02ad1e89 f0410fba6d1000 lock bts dword ptr [r13+10h],0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff880009a9a80 -- (.trap 0xfffff880009a9a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000006b rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ad1e89 rsp=fffff880009a9c10 rbp=00000000000000ff
r8=0000000000000000 r9=0000058000000000 r10=0000000000000002
r11=fffff880009a9c08 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!MmZeroPageThread+0x3d4:
fffff800`02ad1e89 f0410fba6d1000 lock bts dword ptr [r13+10h],0 ds:a410:00000000`00000010=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a8a469 to fffff80002a8af00
STACK_TEXT:
fffff880`009a9938 fffff800`02a8a469 : 00000000`0000000a fffffa7f`f3ffffe0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009a9940 fffff800`02a890e0 : 00000000`00000000 ffffffff`ffbfffff 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009a9a80 fffff800`02ad1e89 : 00000000`000000ff 00000000`0000000f 00000000`00000002 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009a9c10 fffff800`02d2e166 : fffffa80`03b4a410 00000000`00000080 fffffa80`03b4a990 fffff800`02a69479 : nt!MmZeroPageThread+0x3d4
fffff880`009a9d40 fffff800`02a69486 : fffff800`02c03e80 fffffa80`03b4a410 fffff800`02c11c40 8b4c7024`7c8b4868 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MmZeroPageThread+3d4
fffff800`02ad1e89 f0410fba6d1000 lock bts dword ptr [r13+10h],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MmZeroPageThread+3d4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
BUCKET_ID: X64_0xA_nt!MmZeroPageThread+3d4
Followup: MachineOwner
---------
Debug session time: Sun Nov 28 12:34:49.728 2010 (GMT-5)
System Uptime: 0 days 4:57:49.102
Loading Kernel Symbols
...............................................................
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {1f, fffff8a00d17ce50, 0, 3fe2a9}
Probably caused by : watchdog.sys ( watchdog!WdLogEvent5+11b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e)
The video memory manager encountered a condition that it can't recover from. By crashing,
the video memory manager is attempting to get enough information into the minidump such that
somebody can pinpoint what lead to this condition.
Arguments:
Arg1: 000000000000001f, The subtype of the bugcheck:
Arg2: fffff8a00d17ce50
Arg3: 0000000000000000
Arg4: 00000000003fe2a9
Debugging Details:
------------------
BUGCHECK_STR: 0x10e_1f
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88002ae322f to fffff80002ac8f00
STACK_TEXT:
fffff880`01f35878 fffff880`02ae322f : 00000000`0000010e 00000000`0000001f fffff8a0`0d17ce50 00000000`00000000 : nt!KeBugCheckEx
fffff880`01f35880 fffff880`03f1c098 : fffff8a0`0d17ce50 fffff8a0`0d17ce50 00000000`003fe2a9 00000000`00000000 : watchdog!WdLogEvent5+0x11b
fffff880`01f358d0 fffff8a0`0d17ce50 : fffff8a0`0d17ce50 00000000`003fe2a9 00000000`00000000 00000000`00000000 : 0xfffff880`03f1c098
fffff880`01f358d8 fffff8a0`0d17ce50 : 00000000`003fe2a9 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff8a0`0d17ce50
fffff880`01f358e0 00000000`003fe2a9 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`05819000 : 0xfffff8a0`0d17ce50
fffff880`01f358e8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`05819000 fffff880`03f198af : 0x3fe2a9
STACK_COMMAND: kb
FOLLOWUP_IP:
watchdog!WdLogEvent5+11b
fffff880`02ae322f cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: watchdog!WdLogEvent5+11b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: watchdog
IMAGE_NAME: watchdog.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc53f
FAILURE_BUCKET_ID: X64_0x10e_1f_watchdog!WdLogEvent5+11b
BUCKET_ID: X64_0x10e_1f_watchdog!WdLogEvent5+11b
Followup: MachineOwner
---------
Debug session time: Sun Nov 28 16:29:58.498 2010 (GMT-5)
System Uptime: 0 days 2:39:43.887
Loading Kernel Symbols
..............................................Unable to add module at ffffffff`ffffffff
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
.
Loading User Symbols
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
...Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {7, 109094, 40a94, 0}
Probably caused by : Unknown_Module_fffff880`00de6060 ( Unknown_Module_fffff880`00de6060>+2e1d792 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 0000000000109094, page frame number
Arg3: 0000000000040a94, 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: 0
IP_MODULE_UNLOADED:
Unknown_Module_fffff880`00de6060>+2e1d792
fffff880`03c037f2 ?? ???
LAST_CONTROL_TRANSFER: from fffff80002a9ca3a to fffff88003c037f2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02a9ca3a : 00000000`002fd8ea fffffa80`051cfdd8 fffff800`02c15c40 00000000`00000001 : <Unloaded_Unknown_Module_fffff880`00de6060>+0x2e1d792
fffff800`00b9cca0 fffff800`02a976cc : fffff800`02c07e80 fffff800`00000000 00000000`00000000 fffff880`01431c50 : nt!PoIdle+0x53a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
Unknown_Module_fffff880`00de6060>+2e1d792
fffff880`03c037f2 ?? ???
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Unknown_Module_fffff880`00de6060>+2e1d792
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module_fffff880`00de6060
IMAGE_NAME: Unknown_Module_fffff880`00de6060
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_0x4E_7_Unknown_Module_fffff880_00de6060_+2e1d792
BUCKET_ID: X64_0x4E_7_Unknown_Module_fffff880_00de6060_+2e1d792
Followup: MachineOwner
---------
Debug session time: Sun Nov 28 16:38:10.804 2010 (GMT-5)
System Uptime: 0 days 0:00:26.194
Loading Kernel Symbols
..............................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {200, 2, 1, fffff880009ce1e8}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+53a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 0000000000000200, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880009ce1e8, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbf0e0
0000000000000200
CURRENT_IRQL: 0
FAULTING_IP:
+60e3952f00d0da0c
fffff880`009ce1e8 ?? ???
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from fffff80002a96a3a to fffff88003c5e7f2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02a96a3a : 00000000`002fd8f4 fffffa80`04f60a48 fffff800`02c0fc40 00000000`00000002 : 0xfffff880`03c5e7f2
fffff800`00b9cca0 fffff800`02a916cc : fffff800`02c01e80 fffff800`00000000 00000000`00000000 fffff880`014d5c50 : nt!PoIdle+0x53a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!PoIdle+53a
fffff800`02a96a3a 0fba2506fc17000f bt dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`02c16648)],0Fh
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PoIdle+53a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600
FAILURE_BUCKET_ID: X64_0xD1_nt!PoIdle+53a
BUCKET_ID: X64_0xD1_nt!PoIdle+53a
Followup: MachineOwner
---------
I have to agree with Jonathan. I think your motherboard may be at fault or possibly you power supply. Do you have access to another known good power supply you could try?