New
#1
BSOD Help
recently ive got a bsod and not sure what is the cause. could anyone help me out. Thank very much.
recently ive got a bsod and not sure what is the cause. could anyone help me out. Thank very much.
ASACPI.sys the 2005 version is a huge cause of BSODs
InformationThe 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
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 12th 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).
BSOD caused by a component of Apple iTunes, remove that softwareCode:ASACPI.sys fffff880`047f5000 fffff880`047fd000 0x00008000 0x42476c4c 28/03/2005 06:30:36
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa80062f8800, fffff80000b9c518, fffffa8006d998a0} *** WARNING: Unable to verify timestamp for usbaapl64.sys *** ERROR: Module load completed but symbols could not be loaded for usbaapl64.sys Probably caused by : usbaapl64.sys DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa80062f8800, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa8006d998a0, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa8006d998a0 DEVICE_OBJECT: fffffa80062f8800 DRIVER_OBJECT: fffffa800634de70 IMAGE_NAME: usbaapl64.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4bb410ef MODULE_NAME: usbaapl64 FAULTING_MODULE: fffff8800767c000 usbaapl64 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002b3eb52 to fffff80002ad2640 STACK_TEXT: fffff800`00b9c4c8 fffff800`02b3eb52 : 00000000`0000009f 00000000`00000003 fffffa80`062f8800 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02ade062 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x34a90 fffff800`00b9c570 fffff800`02addf06 : fffffa80`0518f450 fffffa80`0518f450 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`02adddee : 00000050`7366338e fffff800`00b9cc58 00000000`0021cc1f fffff800`02c47668 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02addbd7 : 00000073`435187c4 00000073`0021cc1f 00000073`435187ac 00000000`0000001f : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02aca36a : fffff800`02c44e80 fffff800`02c52cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_usbaapl64.sys BUCKET_ID: X64_0x9F_IMAGE_usbaapl64.sys Followup: MachineOwner ---------