Code:
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\010812-18564-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`03094670
Debug session time: Sun Jan 8 08:33:49.687 2012 (UTC - 7:00)
System Uptime: 0 days 1:11:39.249
Loading Kernel Symbols
.................................................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {ffffffffc0000005, fffff8800fd7dfe8, fffff88004330698, fffff8800432fef0}
Probably caused by : ntkrnlmp.exe ( nt!PoIdle+52a )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800fd7dfe8, The address that the exception occurred at
Arg3: fffff88004330698, Exception Record Address
Arg4: fffff8800432fef0, 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:
+3732313831663533
fffff880`0fd7dfe8 ?? ???
EXCEPTION_RECORD: fffff88004330698 -- (.exr 0xfffff88004330698)
Cannot read Exception record @ fffff88004330698
CONTEXT: fffff8800432fef0 -- (.cxr 0xfffff8800432fef0)
Unable to read context, Win32 error 0n30
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002ed54a9 to fffff8800456b7f2
STACK_TEXT:
fffff800`00b9cc98 fffff800`02ed54a9 : 00000000`ffffffed fffffa80`04f965d8 fffff800`0304fcc0 00000000`00000001 : 0xfffff880`0456b7f2
fffff800`00b9cca0 fffff800`02ec393c : fffff800`03041e80 fffff800`00000000 00000000`00000000 fffff880`0f1140b0 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c
FOLLOWUP_IP:
nt!PoIdle+52a
fffff800`02ed54a9 0fba25570e18000f bt dword ptr [nt!PerfGlobalGroupMask+0x8 (fffff800`03056308)],0Fh
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PoIdle+52a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
STACK_COMMAND: .cxr 0xfffff8800432fef0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!PoIdle+52a
BUCKET_ID: X64_0x7E_nt!PoIdle+52a
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\NassiC\Windows_NT6_BSOD_jcgriff2\010812-20872-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`0305c670
Debug session time: Sun Jan 8 13:45:13.647 2012 (UTC - 7:00)
System Uptime: 0 days 0:06:29.207
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Probably caused by : hidusb.sys ( hidusb!HumReadReport+13f )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.
FAULTING_IP:
+3838303532303231
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002f8b568 -- (.exr 0xfffff88002f8b568)
ExceptionAddress: fffff880019e8dd4 (usbccgp!UsbcAcquireRemoveLock+0x00000000000000bc)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002f8b610 -- (.trap 0xfffff88002f8b610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00fffa8005611d38 rbx=0000000000000000 rcx=fffffa800562fc40
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880019e8dd4 rsp=fffff88002f8b7a0 rbp=fffffa8004cba760
r8=fffff88002f8b7d0 r9=0000000000000000 r10=fffff88002f63b20
r11=fffffa80045df7b8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
usbccgp!UsbcAcquireRemoveLock+0xbc:
fffff880`019e8dd4 4c8918 mov qword ptr [rax],r11 ds:0c70:00fffa80`05611d38=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e8b5fe to fffff80002e93c10
STACK_TEXT:
fffff880`02f8a648 fffff800`02e8b5fe : fffffa80`04cc91a0 fffff880`014d3569 fffff880`02f8adc0 fffff800`02ebf830 : nt!KeBugCheck
fffff880`02f8a650 fffff800`02ebf4fd : fffff800`0309d71c fffff800`02fdac30 fffff800`02e17000 fffff880`02f8b568 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02f8a680 fffff800`02ebe2d5 : fffff800`02fde0fc fffff880`02f8a6f8 fffff880`02f8b568 fffff800`02e17000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02f8a6b0 fffff800`02ecf361 : fffff880`02f8b568 fffff880`02f8adc0 fffff880`00000000 fffffa80`00000003 : nt!RtlDispatchException+0x415
fffff880`02f8ad90 fffff800`02e932c2 : fffff880`02f8b568 00000000`00000000 fffff880`02f8b610 fffffa80`0562fb58 : nt!KiDispatchException+0x135
fffff880`02f8b430 fffff800`02e91bca : fffffa80`04fda000 fffffa80`04cba998 00000000`00000000 00000000`00000004 : nt!KiExceptionDispatch+0xc2
fffff880`02f8b610 fffff880`019e8dd4 : 00000000`00000324 00000000`00000000 fffffa80`0562fb58 00000000`000007ff : nt!KiGeneralProtectionFault+0x10a
fffff880`02f8b7a0 fffff880`019e350c : 00000000`0000000f fffffa80`05623b50 fffffa80`05623b58 fffffa80`04cba760 : usbccgp!UsbcAcquireRemoveLock+0xbc
fffff880`02f8b800 fffff880`0445e48f : fffffa80`05623a00 fffffa80`04cba701 00000000`00000000 00000000`000007ff : usbccgp!USBC_Dispatch+0xbc
fffff880`02f8b880 fffff880`0445df5b : fffffa80`04cba9e0 fffffa80`05636c01 fffff880`02f8b940 fffffa80`05636b30 : hidusb!HumReadReport+0x13f
fffff880`02f8b8d0 fffff880`05014555 : fffffa80`0562db01 fffffa80`0562dbb0 fffffa80`04cba760 00000000`00000008 : hidusb!HumInternalIoctl+0x137
fffff880`02f8b940 fffff880`05014d75 : fffffa80`0562dbb0 fffffa80`05636ca0 00000000`00000000 00000000`00000008 : HIDCLASS!HidpSubmitInterruptRead+0xdd
fffff880`02f8b9a0 fffff800`02e97021 : fffffa80`04cba9e3 00000000`00000000 fffffa80`05636b01 fffffa80`04cba700 : HIDCLASS!HidpInterruptReadComplete+0x37d
fffff880`02f8ba30 fffff880`04013631 : fffffa80`04ac0050 fffffa80`04749800 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02f8bb20 fffff880`04013b0f : fffffa80`04759c02 fffffa80`04cba760 00000000`ffffffff fffffa80`04ac0eb0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02f8bc00 fffff880`0401166f : fffffa80`04ac0eb0 fffffa80`04ac01a0 fffffa80`04ac1050 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f8bc60 fffff880`04002f89 : fffffa80`04ac0050 00000000`00000000 fffffa80`04ac0e02 fffffa80`04ac0eb0 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f8bca0 fffff800`02e9f0ac : fffff880`02f63180 fffffa80`04ac0eb0 fffffa80`04ac0ec8 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f8bcd0 fffff800`02e8b96a : fffff880`02f63180 fffff880`02f6dfc0 00000000`00000000 fffff880`04002db0 : nt!KiRetireDpcList+0x1bc
fffff880`02f8bd80 00000000`00000000 : fffff880`02f8c000 fffff880`02f86000 fffff880`02f8bd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
hidusb!HumReadReport+13f
fffff880`0445e48f 488b4c2460 mov rcx,qword ptr [rsp+60h]
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: hidusb!HumReadReport+13f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hidusb
IMAGE_NAME: hidusb.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a665
FAILURE_BUCKET_ID: X64_0x1E_0_hidusb!HumReadReport+13f
BUCKET_ID: X64_0x1E_0_hidusb!HumReadReport+13f
Followup: MachineOwner
---------
Update the following drivers. If you need help finding drivers, refer to Driver Reference for drivers and Drivers and Downloads for drivers' manufacturers. Also, Installing and updating drivers in 7 may be a helpful resource.
Code:
ASACPI fffff880`04181000 fffff880`04189000 Sun Mar 27 20:30:36 2005 (42476c4c) 00003c77 ASACPI.sys
nvm62x64 fffff880`0446b000 fffff880`044ced80 Fri Oct 17 15:01:06 2008 (48f8fd12) 0006f977 nvm62x64.sys
Especially recommend updating ASACPI.SYS as it is a known BSOD problem on Windows 7. Update the driver by:
1. Going to the Asus motherboard support site
When you reach the website:
2. Scroll down the page and click Utilities
3. Hold Ctrl and press f (ctrl+f) to enter the browser's find feature
4. Search for "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" (without quotes)
5. Download and install the driver.
6. After installation is complete, verify that it installed correctly.
a. Click Start Menu
b. Click My Computer
c. Go to C:\WIndows\System32\drivers\
d. Verify that the ASACPI.SYS file is dated 2009 or newer (2010,etc.)
Thanks to JMH and zigzag3143 for the above information.