Hi all,
I have been running IDM (Internet Download Manager) for a while now. While downloading several files, and I close the lid, usually after a while I'll open the lid and a BSOD with a driver_equal_to_less than, please take a look
Windows 7 Ultimate 32 bit Retail
Toshiba AA505-6980 Laptop (1year old)
Last edited by jeffro0625; 28 Aug 2010 at 06:26.
jeff hi and welcome
these were both caused by DRIVER_POWER_STATE_FAILURE (9f). This means that a driver doesnt respond within a specified time. I really, really think it is your aspi32.sys driver which is dated 2002.
You need to update all the drivers listed below and then we may be able to resolve any other outstanding issue
How To Find Drivers:- - The most common drivers are listed on this page: Driver Reference- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: Drivers and Downloads
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\Windows_NT6_BSOD_jcgriff2\081710-119995-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: *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe - Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.x86fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0x83405000 PsLoadedModuleList = 0x8354d810 Debug session time: Tue Aug 17 15:36:28.532 2010 (GMT-4) System Uptime: 0 days 20:48:10.264 *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe - Loading Kernel Symbols ............................................................... ................................................................ ...................................................... Loading User Symbols Loading unloaded module list ...... 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 00000003, A device object has been blocking an Irp for too long a time Arg2: 869fb690, Physical Device Object of the stack Arg3: 8078adb0, Functional Device Object of the stack Arg4: fbb59e00, The blocked IRP Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IRP *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IRP *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IRP *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: nt FAULTING_MODULE: 83405000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c3fac DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fbb59e00 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 83441054 to 834e1d10 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8078ad64 83441054 0000009f 00000003 869fb690 nt!KeBugCheckEx+0x1e 8078add0 834408e8 8078ae70 00000000 865dcb10 nt!KeInsertQueue+0xae8 8078ae08 8346f04d 83546a20 00000000 7ca84641 nt!KeInsertQueue+0x37c 8078ae4c 8346eff1 8352ed20 8078af78 00000001 nt!KeWaitForMultipleObjects+0xe96 8078af38 8346eeae 8352ed20 8078af78 00000000 nt!KeWaitForMultipleObjects+0xe3a 8078afac 8346d20e 00494073 9a97dd34 00000000 nt!KeWaitForMultipleObjects+0xcf7 8078aff4 8346c9dc 9a97dce4 00000000 00000000 nt!KiDispatchInterrupt+0x85e 8078aff8 9a97dce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c 8346c9dc 00000000 0000001a 00d6850f bb830000 0x9a97dce4 STACK_COMMAND: kb FOLLOWUP_IP: nt!KeInsertQueue+ae8 83441054 cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KeInsertQueue+ae8 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: ntkrpamp.exe BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------Code:aspi32.sys 0x9c306000 0x9c30a080 0x00004080 0x3d3595b4 7/17/2002 12:05:08 secdrv.SYS 0x9c36a000 0x9c374000 0x0000a000 0x45080528 9/13/2006 09:18:32 pcouffin.sys 0x90fc8000 0x90fd3900 0x0000b900 0x457584b9 12/5/2006 10:39:53 TVALZ_O.SYS 0x8bc52000 0x8bc56180 0x00004180 0x4733cf02 11/8/2007 23:07:46 UVCFTR_S.SYS 0x92dac000 0x92db4000 0x00008000 0x4863526f 6/26/2008 04:25:19 ISODrive.sys 0x90b85000 0x90b9c000 0x00017000 0x4991473f 2/10/2009 05:22:07 mcdbus.sys 0x90fde000 0x90ffa800 0x0001c800 0x49a3cf05 2/24/2009 06:42:13 lirsgt.sys 0x9c365000 0x9c369880 0x00004880 0x49b29007 3/7/2009 11:17:27 point32k.sys 0x916a9000 0x916b4000 0x0000b000 0x4a03eedb 5/8/2009 04:35:39 atksgt.sys 0x9c30b000 0x9c34e000 0x00043000 0x4a06e9d2 5/10/2009 10:50:58 spldr.sys 0x8bc59000 0x8bc61000 0x00008000 0x4a084ebb 5/11/2009 12:13:47 GEARAspiWDM.sys 0x913e5000 0x913ea280 0x00005280 0x4a1151b5 5/18/2009 08:16:53 amdxata.sys 0x8b6da000 0x8b6e3000 0x00009000 0x4a12f30f 5/19/2009 13:57:35 Thpevm.SYS 0x8bc57000 0x8bc58900 0x00001900 0x4a487836 6/29/2009 04:15:50 rimspe86.sys 0x91347000 0x9135c000 0x00015000 0x4a4bf636 7/1/2009 19:50:14 rixdpe86.sys 0x9135c000 0x913ae000 0x00052000 0x4a4f22c2 7/4/2009 05:37:06
Quote