BSOD occurs a while after waking up from sleep. Event manager shows the error "The driver for device \Device\Scsi\Ultra1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition" had occurred before the blue screen. I have a Promise Ultra133 IDE controller; perhaps that's not cooperating with the sleep function?
Thanks in advance.
this crash was caused by disk.sys. It can mean either the win 7 file (disk.sys) is corrupt or there is a problem with the controller.
I would run a system file check to verify the system files
to do that type cmd in search>right click and run as admin>>dfc /scannow (note the space between sfc and "/")
Let us know the results as you may have to re-run it.
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\032810-24133-01 - Copy.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`0402e500? Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a59000 PsLoadedModuleList = 0xfffff800`02c96e50 Debug session time: Sun Mar 28 00:54:25.760 2010 (GMT-4) System Uptime: 0 days 7:06:01.399 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa80026df050, fffff8000402e518, fffffa8005636910} Probably caused by : disk.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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: fffffa80026df050, Physical Device Object of the stack Arg3: fffff8000402e518, Functional Device Object of the stack Arg4: fffffa8005636910, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa8005636910 DEVICE_OBJECT: fffffa80027f4060 DRIVER_OBJECT: fffffa80027f1730 IMAGE_NAME: disk.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11d MODULE_NAME: disk FAULTING_MODULE: fffff880018d0000 disk DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002b39e23 to fffff80002acaf00 STACK_TEXT: fffff800`0402e4c8 fffff800`02b39e23 : 00000000`0000009f 00000000`00000003 fffffa80`026df050 fffff800`0402e518 : nt!KeBugCheckEx fffff800`0402e4d0 fffff800`02ad6fa6 : fffff800`0402e600 fffff800`0402e600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`0402e570 fffff800`02ad6326 : fffffa80`0679d430 fffffa80`0679d430 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`0402e5e0 fffff800`02ad6e7e : 0000003b`83c8040a fffff800`0402ec58 00000000`0019008c fffff800`02c47408 : nt!KiProcessExpiredTimerList+0xc6 fffff800`0402ec30 fffff800`02ad6697 : 0000000c`666937c3 0000000c`0019008c 0000000c`666937dc 00000000`0000008c : nt!KiTimerExpiration+0x1be fffff800`0402ecd0 fffff800`02ad36fa : fffff800`02c43e80 fffff800`02c51c40 00000000`00000000 fffff880`01454d80 : nt!KiRetireDpcList+0x277 fffff800`0402ed80 00000000`00000000 : fffff800`0402f000 fffff800`04029000 fffff800`0402ed40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_disk.sys BUCKET_ID: X64_0x9F_IMAGE_disk.sys Followup: MachineOwner ---------
No integrity violations were found. This only happens occasionally after waking up from sleep. The aforementioned error "The driver for device \Device\Scsi\Ultra1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition" always precedes the bugcheck in Event Viewer. Perhaps the IDE controller is the culprit? Device manager says the drivers are up to date.
I guess I should avoid the sleep function then...
the problem is finding and isolating the offending driver , vista was full of power state failiures after resuming from sleep , but more often that not it was due to an ethernet or network driver , yours points to disk.sys (your hard drive controller) so it may be helpfull to download and install the latest version from your mobo manufacturers website (sata drivers) Its a longshot but worth a try
Quote