This is a Driver Verifier enabled dump. The error code is A, IRQL_NOT_LESS_OR_EQUAL. The dump blames dxgkrnl.sys which is a Direct X driver. This is very likely not the actual cause. The system crashed early and that indicates a hardware problem
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_082610-31640-01.zip\082610-31640-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a0e000 PsLoadedModuleList = 0xfffff800`02c4be50
Debug session time: Thu Aug 26 16:52:18.765 2010 (GMT-4)
System Uptime: 0 days 0:00:12.125
Loading Kernel Symbols
...............................................................
............................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff80002a9e2b3}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoInitializeFdo+11d )
Followup: MachineOwner
---------
2: 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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80002a9e2b3, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb60e0
0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!IopCompleteRequest+ae3
fffff800`02a9e2b3 488b09 mov rcx,qword ptr [rcx]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0xA
PROCESS_NAME: System
IRP_ADDRESS: ffffffffffffff89
TRAP_FRAME: fffff88002fc37b0 -- (.trap 0xfffff88002fc37b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88002fc3f80 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a9e2b3 rsp=fffff88002fc3940 rbp=fffff88002fc3a90
r8=fffff88002fc3a48 r9=fffff88002fc3a40 r10=0000000000000002
r11=fffff80002a9d7d0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
nt!IopCompleteRequest+0xae3:
fffff800`02a9e2b3 488b09 mov rcx,qword ptr [rcx] ds:00d5:00000000`00000000=????????????????
Resetting default scope
LOCK_ADDRESS: fffff80002c82400 -- (!locks fffff80002c82400)
Resource @ nt!PiEngineLock (0xfffff80002c82400) 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 : 0xfffff80002c82400
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002a7dca9 to fffff80002a7e740
STACK_TEXT:
fffff880`02fc3668 fffff800`02a7dca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fc3670 fffff800`02a7c920 : fffff880`02fc3730 fffff980`0290aee0 00000000`00000000 fffff880`02fc35a0 : nt!KiBugCheckDispatch+0x69
fffff880`02fc37b0 fffff800`02a9e2b3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02fc3940 fffff800`02a5b0c7 : 00000000`00000001 fffff800`02dc17f3 fffffa80`05d3f000 fffff880`00000000 : nt!IopCompleteRequest+0xae3
fffff880`02fc3a10 fffff800`02a5b487 : fffff8a0`00003170 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
fffff880`02fc3a90 fffff800`02d72d5b : 00000000`00000000 00000000`00000003 00000000`00000240 00000000`00000011 : nt!KiApcInterrupt+0xd7
fffff880`02fc3c20 fffff800`02d77ab5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000200 : nt!ObReferenceObjectByHandleWithTag+0xfb
fffff880`02fc3cf0 fffff800`02d7ce4d : fffffa80`05d3f010 fffff880`02fc3e50 fffffa80`00000240 fffffa80`03718270 : nt!ObpLookupObjectName+0x1b5
fffff880`02fc3df0 fffff800`02d5bdcc : ffffffff`8000005c 00000000`00000000 00000000`00000000 fffff800`02f19ca5 : nt!ObOpenObjectByName+0x1cd
fffff880`02fc3ea0 fffff800`02d5efca : fffff880`02fc4288 fffff800`00020019 fffff880`02fc41f0 00000000`00000000 : nt!CmOpenKey+0x28a
fffff880`02fc3ff0 fffff800`02a7d993 : fffff880`02fc4030 fffff6fb`7e000000 00000000`00000000 00000000`000001f0 : nt!NtOpenKey+0x12
fffff880`02fc4030 fffff800`02a79f30 : fffff800`02cef498 00000000`00000000 fffffa80`00000000 fffff880`02fc4288 : nt!KiSystemServiceCopyEnd+0x13
fffff880`02fc41c8 fffff800`02cef498 : 00000000`00000000 fffffa80`00000000 fffff880`02fc4288 fffff800`02d3a3f4 : nt!KiServiceLinkage
fffff880`02fc41d0 fffff800`02b6633a : fffffa80`056c9bc0 fffff880`02fc4300 00000000`00000001 fffff800`02a79f30 : nt!IopOpenRegistryKeyEx+0x38
fffff880`02fc4230 fffff800`02e7311d : fffffa80`05311708 00000000`00000000 ffffffff`8000005c fffff8a0`00000004 : nt!PipCheckForDenyExecute+0x9a
fffff880`02fc4280 fffff800`02e7336e : 00000000`00000000 fffffa80`056c9bc0 fffffa80`05311708 fffff880`02fc43a0 : nt!IopRegisterDeviceInterface+0x14d
fffff880`02fc4340 fffff880`043714d1 : 00000000`0000003c fffffa80`056c95d0 fffffa80`056c9480 fffffa80`056c9500 : nt!IoRegisterDeviceInterface+0xce
fffff880`02fc43a0 fffff880`0436bfe6 : 00000000`fffff90d 00000000`00000307 00000000`00000000 ffffffff`00000014 : dxgkrnl!DpiFdoInitializeFdo+0x11d
fffff880`02fc4430 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DpiAddDevice+0x8c6
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgkrnl!DpiFdoInitializeFdo+11d
fffff880`043714d1 4863f8 movsxd rdi,eax
SYMBOL_STACK_INDEX: 11
SYMBOL_NAME: dxgkrnl!DpiFdoInitializeFdo+11d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ac5509e
FAILURE_BUCKET_ID: X64_0xA_VRF_dxgkrnl!DpiFdoInitializeFdo+11d
BUCKET_ID: X64_0xA_VRF_dxgkrnl!DpiFdoInitializeFdo+11d
Followup: MachineOwner
---------
I find an out of date driver on your system. Windows & does not like older drivers. I cannot say this driver contributed to the crash; but try to update it to eliminate it as a problem. Update it from the NVidia website.
nvsmu.sys Mon Jun 29 03:36:37 2009 - nVidia nForce System Management Controller (nVidia nForce chipset driver) Drivers - Download NVIDIA Drivers
Since you are getting the BSOD so quickly and it is pointing to Microsoft files, turn Driver Verifier off. Did you go through any of the troubleshooting procedures in these links?
https://www.sevenforums.com/crash-loc...tml#post567135
https://www.sevenforums.com/crashes-debugging/35427-win-7-clock-interrupt-bsod-101-error.html#post356791
If not, please do so and report back with what you did and what you found. We will go from there.