Hey guys, I keep getting BSOD and I'm not sure how to do this so I'll post the DMG files (sorry I had to use winRAR).
Interesting to note I keep getting dsklhost.exe unable to load at startup so I don't know if that has anything to do w/ it but it correlates to the same time the BSOD started happening more frequently.
These crashes are blamed on windows 7 OS files, but I strongly suspect that your problem is being caused by the old drivers listed below. The ASACPI.sys is dated 2005 and is a known cause of all sorts of hardware problems and crashes.
Remedies
1-Update all the drivers especially the ASACPI.SYS (update to the 2010 version).
ASACPI.sys Sun Mar 27 22:30:36 2005
The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).
2-Run a system file check
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\090310-20529-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4e000 PsLoadedModuleList = 0xfffff800`0308be50
Debug session time: Fri Sep 3 20:42:21.238 2010 (GMT-4)
System Uptime: 0 days 1:49:40.017
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}
*** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
Probably caused by : usbohci.sys ( usbohci+1d4c )
Followup: MachineOwner
---------
3: 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:
+5c3e952f037fd920
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002ffb888 -- (.exr 0xfffff88002ffb888)
ExceptionAddress: fffff8800483fd4c (usbohci+0x0000000000001d4c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002ffb930 -- (.trap 0xfffff88002ffb930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=bffffa8006f70ae0 rbx=0000000000000000 rcx=fffffa80057435a0
rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800483fd4c rsp=fffff88002ffbac0 rbp=fffffa8006f70fc0
r8=000000004f444648 r9=fffffa8006f70fc0 r10=00000000ffffffff
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
usbohci+0x1d4c:
fffff880`0483fd4c f60001 test byte ptr [rax],1 ds:c9c0:bffffa80`06f70ae0=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002eb646e to fffff80002ebe710
STACK_TEXT:
fffff880`02ffa978 fffff800`02eb646e : 00000000`00000000 fffff880`00e2e6d4 fffff880`02ffb0f0 fffff800`02eeb668 : nt!KeBugCheck
fffff880`02ffa980 fffff800`02ee440d : fffff800`030ccb7c fffff800`03006e84 fffff800`02e4e000 fffff880`02ffb888 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa9b0 fffff800`02eeba90 : fffff800`0300db14 fffff880`02ffaa28 fffff880`02ffb888 fffff800`02e4e000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa9e0 fffff800`02ef89ef : fffff880`02ffb888 fffff880`02ffb0f0 fffff880`00000000 fffff880`06d02800 : nt!RtlDispatchException+0x410
fffff880`02ffb0c0 fffff800`02ebdd82 : fffff880`02ffb888 fffffa80`06f70d5c fffff880`02ffb930 fffff880`06d02810 : nt!KiDispatchException+0x16f
fffff880`02ffb750 fffff800`02ebc68a : fffffa80`043df5d0 fffffa80`045f8002 fffffa80`04577da0 fffff880`0433287b : nt!KiExceptionDispatch+0xc2
fffff880`02ffb930 fffff880`0483fd4c : fffffa80`06f70d48 fffffa80`05ae5250 fffffa80`049de001 fffff880`03faed70 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffbac0 fffff880`0483ff7d : 00000000`0000000f fffffa80`05ae5250 fffffa80`05645101 fffffa80`05ae5250 : usbohci+0x1d4c
fffff880`02ffbb30 fffff880`04842744 : fffffa80`05ae5250 fffffa80`05ae5010 fffffa80`056451a0 fffffa80`056451a0 : usbohci+0x1f7d
fffff880`02ffbb80 fffff880`03f82e8b : 00000000`00000002 fffffa80`05ae5010 fffffa80`056451a0 00000000`00000000 : usbohci+0x4744
fffff880`02ffbbb0 fffff880`03f879b1 : 00000000`00000010 00000000`00000004 fffffa80`05ae5010 fffffa80`05645050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`02ffbbe0 fffff880`03f93043 : fffffa80`056451a0 00000000`00000010 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`02ffbc40 fffff880`03f83f89 : fffffa80`05645050 00000000`00000000 fffffa80`05645a02 fffffa80`05645a10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
fffff880`02ffbca0 fffff800`02ec9bfc : fffff880`02fd3180 fffffa80`05645a10 fffffa80`05645a28 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffbcd0 fffff800`02ec6eea : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`03f83db0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usbohci+1d4c
fffff880`0483fd4c f60001 test byte ptr [rax],1
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: usbohci+1d4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbohci
IMAGE_NAME: usbohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc06
FAILURE_BUCKET_ID: X64_0x1E_usbohci+1d4c
BUCKET_ID: X64_0x1E_usbohci+1d4c
Followup: MachineOwner
---------
3: 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:
+5c3e952f037fd920
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x1E
PROCESS_NAME: System
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff88002ffb888 -- (.exr 0xfffff88002ffb888)
ExceptionAddress: fffff8800483fd4c (usbohci+0x0000000000001d4c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff88002ffb930 -- (.trap 0xfffff88002ffb930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=bffffa8006f70ae0 rbx=0000000000000000 rcx=fffffa80057435a0
rdx=000000004f444648 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800483fd4c rsp=fffff88002ffbac0 rbp=fffffa8006f70fc0
r8=000000004f444648 r9=fffffa8006f70fc0 r10=00000000ffffffff
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
usbohci+0x1d4c:
fffff880`0483fd4c f60001 test byte ptr [rax],1 ds:c9c0:bffffa80`06f70ae0=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002eb646e to fffff80002ebe710
STACK_TEXT:
fffff880`02ffa978 fffff800`02eb646e : 00000000`00000000 fffff880`00e2e6d4 fffff880`02ffb0f0 fffff800`02eeb668 : nt!KeBugCheck
fffff880`02ffa980 fffff800`02ee440d : fffff800`030ccb7c fffff800`03006e84 fffff800`02e4e000 fffff880`02ffb888 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`02ffa9b0 fffff800`02eeba90 : fffff800`0300db14 fffff880`02ffaa28 fffff880`02ffb888 fffff800`02e4e000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`02ffa9e0 fffff800`02ef89ef : fffff880`02ffb888 fffff880`02ffb0f0 fffff880`00000000 fffff880`06d02800 : nt!RtlDispatchException+0x410
fffff880`02ffb0c0 fffff800`02ebdd82 : fffff880`02ffb888 fffffa80`06f70d5c fffff880`02ffb930 fffff880`06d02810 : nt!KiDispatchException+0x16f
fffff880`02ffb750 fffff800`02ebc68a : fffffa80`043df5d0 fffffa80`045f8002 fffffa80`04577da0 fffff880`0433287b : nt!KiExceptionDispatch+0xc2
fffff880`02ffb930 fffff880`0483fd4c : fffffa80`06f70d48 fffffa80`05ae5250 fffffa80`049de001 fffff880`03faed70 : nt!KiGeneralProtectionFault+0x10a
fffff880`02ffbac0 fffff880`0483ff7d : 00000000`0000000f fffffa80`05ae5250 fffffa80`05645101 fffffa80`05ae5250 : usbohci+0x1d4c
fffff880`02ffbb30 fffff880`04842744 : fffffa80`05ae5250 fffffa80`05ae5010 fffffa80`056451a0 fffffa80`056451a0 : usbohci+0x1f7d
fffff880`02ffbb80 fffff880`03f82e8b : 00000000`00000002 fffffa80`05ae5010 fffffa80`056451a0 00000000`00000000 : usbohci+0x4744
fffff880`02ffbbb0 fffff880`03f879b1 : 00000000`00000010 00000000`00000004 fffffa80`05ae5010 fffffa80`05645050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`02ffbbe0 fffff880`03f93043 : fffffa80`056451a0 00000000`00000010 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`02ffbc40 fffff880`03f83f89 : fffffa80`05645050 00000000`00000000 fffffa80`05645a02 fffffa80`05645a10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
fffff880`02ffbca0 fffff800`02ec9bfc : fffff880`02fd3180 fffffa80`05645a10 fffffa80`05645a28 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffbcd0 fffff800`02ec6eea : fffff880`02fd3180 fffff880`02fddfc0 00000000`00000000 fffff880`03f83db0 : nt!KiRetireDpcList+0x1bc
fffff880`02ffbd80 00000000`00000000 : fffff880`02ffc000 fffff880`02ff6000 fffff880`02ffbd40 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usbohci+1d4c
fffff880`0483fd4c f60001 test byte ptr [rax],1
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: usbohci+1d4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbohci
IMAGE_NAME: usbohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc06
FAILURE_BUCKET_ID: X64_0x1E_usbohci+1d4c
BUCKET_ID: X64_0x1E_usbohci+1d4c
Followup: MachineOwner
---------
Old drivers
Code:
ASACPI.sys fffff880`04feb000 fffff880`04ff3000 0x00008000 0x42476c4c 3/27/2005 22:30:36
RTCore64.sys fffff880`03bcf000 fffff880`03bd5000 0x00006000 0x42941d90 5/25/2005 02:39:12
NuidFltr.sys fffff880`05a4a000 fffff880`05a53000 0x00009000 0x4a03f30b 5/8/2009 04:53:31
spldr.sys fffff880`0145a000 fffff880`01462000 0x00008000 0x4a0858bb 5/11/2009 12:56:27
ladfSBVMamd64.sys fffff880`06071000 fffff880`060cbb00 0x0005ab00 0x4a0dcf7f 5/15/2009 16:24:31
ladfDHP2amd64.sys fffff880`05a89000 fffff880`05a96c00 0x0000dc00 0x4a0dcf8a 5/15/2009 16:24:42
GEARAspiWDM.sys fffff880`04fde000 fffff880`04feb000 0x0000d000 0x4a1151c0 5/18/2009 08:17:04
amdxata.sys fffff880`00c44000 fffff880`00c4f000 0x0000b000 0x4a12f2eb 5/19/2009 13:56:59