Hi all,
I have win 7 x64 running on a custom built machine. Every now and then the machine freezes up when I try to wake it up from sleep (usually overnight). I have not made changes to make it hybernate. I experienced this again last night and am wondering if I could get some help analyzing this minidump as I don't know how to analyze it.
Any help will be appreciated.
Thanks!
Hello IndianinIA,
I wonder if that was caused by your network driver. Try uninstalling and reinstalling that driver, e1e6032e.sys, and make sure that you get the latest version.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\020810-18921-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500? Symbol search path is: SRV*c:\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.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c3de50 Debug session time: Sun Feb 7 23:28:12.828 2010 (GMT-5) System Uptime: 0 days 13:16:53.125 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8007425a20, fffff80000b9c518, fffffa800a040e10} *** WARNING: Unable to verify timestamp for e1e6032e.sys *** ERROR: Module load completed but symbols could not be loaded for e1e6032e.sys Probably caused by : e1e6032e.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: fffffa8007425a20, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa800a040e10, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800a040e10 DEVICE_OBJECT: fffffa800808c050 DRIVER_OBJECT: fffffa800809f7d0 IMAGE_NAME: e1e6032e.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49c923b3 MODULE_NAME: e1e6032e FAULTING_MODULE: fffff88004a6a000 e1e6032e CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002ae0e23 to fffff80002a71f00 STACK_TEXT: fffff800`00b9c4c8 fffff800`02ae0e23 : 00000000`0000009f 00000000`00000003 fffffa80`07425a20 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02a7dfa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`00b9c570 fffff800`02a7d326 : fffff800`02c20700 00000000`002eb148 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`02a7de7e : 0000006f`52d7e4d6 fffff800`00b9cc58 00000000`002eb148 fffff800`02bedb88 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02a7d697 : 0000001a`17a08dc1 0000001a`002eb148 0000001a`17a08d0d 00000000`00000048 : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02a7a6fa : fffff800`02beae80 fffff800`02bf8c40 00000000`00000000 fffff880`00dc4f44 : 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_e1e6032e.sys BUCKET_ID: X64_0x9F_IMAGE_e1e6032e.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: fffffa8007425a20, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa800a040e10, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800a040e10 DEVICE_OBJECT: fffffa800808c050 DRIVER_OBJECT: fffffa800809f7d0 IMAGE_NAME: e1e6032e.sys DEBUG_FLR_IMAGE_TIMESTAMP: 49c923b3 MODULE_NAME: e1e6032e FAULTING_MODULE: fffff88004a6a000 e1e6032e CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002ae0e23 to fffff80002a71f00 STACK_TEXT: fffff800`00b9c4c8 fffff800`02ae0e23 : 00000000`0000009f 00000000`00000003 fffffa80`07425a20 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02a7dfa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`00b9c570 fffff800`02a7d326 : fffff800`02c20700 00000000`002eb148 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`02a7de7e : 0000006f`52d7e4d6 fffff800`00b9cc58 00000000`002eb148 fffff800`02bedb88 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02a7d697 : 0000001a`17a08dc1 0000001a`002eb148 0000001a`17a08d0d 00000000`00000048 : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02a7a6fa : fffff800`02beae80 fffff800`02bf8c40 00000000`00000000 fffff880`00dc4f44 : 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_e1e6032e.sys BUCKET_ID: X64_0x9F_IMAGE_e1e6032e.sys Followup: MachineOwner ---------
Thanks for the quick analysis Jonathan! Excellent response!
I forgot to mention in my previous post that on some other occasions while I am working on something on my machine, when I am trying to save a file to a NAS that I have, windows freezes and most of the time going through performance monitor it seems to be a network I/O issue. Both together now seem to make sense at least for the time being.
I will look for the latest drivers and update and post back if that has fixed the issue.
Thanks!
Well, I updated the network adapter driver by downloading the latest one and installing it. It woke up fine this morning when I tried logging in, but while emailing and browsing I had to step away. When I came back the monitors (which are set to sleep after 15 minutes) were dark and I could not wake up the machine again. I got a new minidump file that I have attached. Any help will be appreciated.
Thanks.
For any of the experts out there, here is the code:
It still looks like a network driver issue. Could I suggest uninstalling it, rebooting, and letting Windows automatically find a driver for it?Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\Desktop\020910-19750-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`03fe6500? Symbol search path is: SRV*c:\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.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02a62000 PsLoadedModuleList = 0xfffff800`02c9fe50 Debug session time: Tue Feb 9 06:53:22.031 2010 (GMT-5) System Uptime: 0 days 10:38:36.921 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8007424a20, fffff80003fe6518, fffffa800a84aab0} *** WARNING: Unable to verify timestamp for e1e6232e.sys *** ERROR: Module load completed but symbols could not be loaded for e1e6232e.sys Probably caused by : e1e6232e.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: fffffa8007424a20, Physical Device Object of the stack Arg3: fffff80003fe6518, Functional Device Object of the stack Arg4: fffffa800a84aab0, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800a84aab0 DEVICE_OBJECT: fffffa80080ac050 DRIVER_OBJECT: fffffa80080aa680 IMAGE_NAME: e1e6232e.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a9d8135 MODULE_NAME: e1e6232e FAULTING_MODULE: fffff88004800000 e1e6232e CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002b42e23 to fffff80002ad3f00 STACK_TEXT: fffff800`03fe64c8 fffff800`02b42e23 : 00000000`0000009f 00000000`00000003 fffffa80`07424a20 fffff800`03fe6518 : nt!KeBugCheckEx fffff800`03fe64d0 fffff800`02adffa6 : fffff800`03fe6600 fffff800`03fe6600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`03fe6570 fffff800`02adf326 : fffff800`02c82700 00000000`00256b3b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`03fe65e0 fffff800`02adfe7e : 00000059`36aa48be fffff800`03fe6c58 00000000`00256b3b fffff800`02c4f9e8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`03fe6c30 fffff800`02adf697 : 00000014`e8fa47c1 00000014`00256b3b 00000014`e8fa47b0 00000000`0000003b : nt!KiTimerExpiration+0x1be fffff800`03fe6cd0 fffff800`02adc6fa : fffff800`02c4ce80 fffff800`02c5ac40 00000000`00000000 fffff880`0142ec50 : nt!KiRetireDpcList+0x277 fffff800`03fe6d80 00000000`00000000 : fffff800`03fe7000 fffff800`03fe1000 fffff800`03fe6d40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_e1e6232e.sys BUCKET_ID: X64_0x9F_IMAGE_e1e6232e.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: fffffa8007424a20, Physical Device Object of the stack Arg3: fffff80003fe6518, Functional Device Object of the stack Arg4: fffffa800a84aab0, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800a84aab0 DEVICE_OBJECT: fffffa80080ac050 DRIVER_OBJECT: fffffa80080aa680 IMAGE_NAME: e1e6232e.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a9d8135 MODULE_NAME: e1e6232e FAULTING_MODULE: fffff88004800000 e1e6232e CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002b42e23 to fffff80002ad3f00 STACK_TEXT: fffff800`03fe64c8 fffff800`02b42e23 : 00000000`0000009f 00000000`00000003 fffffa80`07424a20 fffff800`03fe6518 : nt!KeBugCheckEx fffff800`03fe64d0 fffff800`02adffa6 : fffff800`03fe6600 fffff800`03fe6600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330 fffff800`03fe6570 fffff800`02adf326 : fffff800`02c82700 00000000`00256b3b 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`03fe65e0 fffff800`02adfe7e : 00000059`36aa48be fffff800`03fe6c58 00000000`00256b3b fffff800`02c4f9e8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`03fe6c30 fffff800`02adf697 : 00000014`e8fa47c1 00000014`00256b3b 00000014`e8fa47b0 00000000`0000003b : nt!KiTimerExpiration+0x1be fffff800`03fe6cd0 fffff800`02adc6fa : fffff800`02c4ce80 fffff800`02c5ac40 00000000`00000000 fffff880`0142ec50 : nt!KiRetireDpcList+0x277 fffff800`03fe6d80 00000000`00000000 : fffff800`03fe7000 fffff800`03fe1000 fffff800`03fe6d40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_IMAGE_e1e6232e.sys BUCKET_ID: X64_0x9F_IMAGE_e1e6232e.sys Followup: MachineOwner ---------
Thanks for the suggestion Jonathan_King. I will take that route and see how far I get. I did not actually uninstall and reboot, but installed it over the existing one. So, let me try what you suggested and see what happens.
Thanks for your analysis once more!
This seems very basic, but I am having difficulty uninstalling the network adapter driver. I went into Device Manager, picked out the network adapter and am trying to uninstall the driver - it just seems to go into an infinite loop - I get a dialog box that says Intel(R) PRO/1000 PL Network Connection - Uninstalling devices, but nothing happens even though there seems to be progress with a green bar moving, but no percentages showing or any thing to tell me that there actually is progress. I tried it after disabling the network adapter and before - both instances I get a hung process it seems. How do I uninstall the network adapter driver now?
Thanks for your help.
Simple things one overlooks!
I will try that route and report back.
Well - so far so good! I uninstalled the adapter drivers after starting up in Safe Boot. The motherboard has a built-in ethernet port and I had an older ethernet adapter card. While these incidents were happening, I was using the motherboard ethernet port. I decided to instead use the one on the adapter. I uninstalled that one as well and then after re-boot allowed Windows to find the most suitable drivers. I have since then, disabled the motherboard ethernet adapter and just enabled the adapter card.
So far no frozen Windows or BSODs!!!
Hopefully that fixed it. Thanks for all of your help!
Quote