 | |
| |
| 21 Dec 2009 | #1 |
| | 2 Clean Installs - Still crashes in sleep mode Even after two clean installs, Windows 7 still crashes when my computer goes into sleep mode. I used the Windows debugging tool (Windbg) to isolate the cause. The analysis of the minidump file is attached as a pdf file. It shows a driver for the network adapter is causing the problem. I rolled the driver back, and thought that would be solution, but I'm still getting the crash. The Intel site says this driver is for Windows 7 and the Windows Update identified the older (rolled back) driver as the correct driver. I'd appreciate any help anyone might be able to offer. Thanks |
My System Specs | |
| 21 Dec 2009 | #2 |
| | 
Quote: Originally Posted by ejscharf  Even after two clean installs, Windows 7 still crashes when my computer goes into sleep mode. I used the Windows debugging tool (Windbg) to isolate the cause. The analysis of the minidump file is attached as a pdf file. It shows a driver for the network adapter is causing the problem. I rolled the driver back, and thought that would be solution, but I'm still getting the crash. The Intel site says this driver is for Windows 7 and the Windows Update identified the older (rolled back) driver as the correct driver. I'd appreciate any help anyone might be able to offer. Thanks Thanks Ken J+ |
| My System Specs |
| 21 Dec 2009 | #3 |
| | The dump file is attached. Thanks for your help. |
| My System Specs |
| . |
| |
| 22 Dec 2009 | #4 |
| |
Quote: Originally Posted by ejscharf The dump file is attached. Thanks for your help. Ken J+ |
| My System Specs |
| 22 Dec 2009 | #5 |
| | Hopefully, the dump file is now attached Hopefully, the dump file is now uploaded, with this message. |
| My System Specs |
| 23 Dec 2009 | #6 |
| |
Quote: Originally Posted by ejscharf Hopefully, the dump file is now uploaded, with this message. this dmp reflects a device that is taking far too long to respond. when it times out it hoses the system. that device (e1e6232e.sys) driver is your network nic I believe. There is very little info on how to cure it (other than to update driver or get a new nic). Since your driver appears current I cant even give you that as a recommendation. 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\122109-19983-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c4c0?
Symbol search path is: SRV*d:\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`02a0d000 PsLoadedModuleList = 0xfffff800`02c4ae50
Debug session time: Mon Dec 21 15:02:12.593 2009 (GMT-5)
System Uptime: 0 days 2:11:23.294
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa8005e7da20, fffff80000b9c4d8, fffffa8005fff7d0}
*** 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> !anaylze -v
No export anaylze found
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: fffffa8005e7da20, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa8005fff7d0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IRP_ADDRESS: fffffa8005fff7d0
DEVICE_OBJECT: fffffa8007a9d050
DRIVER_OBJECT: fffffa8007ad5d10
IMAGE_NAME: e1e6232e.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a296d39
MODULE_NAME: e1e6232e
FAULTING_MODULE: fffff88004f82000 e1e6232e
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002aede23 to fffff80002a7ef00
STACK_TEXT:
fffff800`00b9c488 fffff800`02aede23 : 00000000`0000009f 00000000`00000003 fffffa80`05e7da20 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`02a8afa6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c530 fffff800`02a8a326 : fffffa80`05892168 fffffa80`05892168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02a8ae7e : 00000012`5acf3f32 fffff800`00b9cc18 00000000`0007b5f8 fffff800`02bfc188 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02a8a697 : 00000004`c4a4eac3 00000004`0007b5f8 00000004`c4a4ea17 00000000`000000f7 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02a876fa : fffff800`02bf7e80 fffff800`02c05c40 00000000`00000000 fffff880`04802db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 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
--------- |
| My System Specs |
| 23 Dec 2009 | #7 |
| | Thanks. I came to the same conclusion, which led me to make my original post. As I mentioned, I even rolled the driver back, with no luck. So, I guess I'm stuck waiting for Intel, the NIC's manufacturer, to come out with another driver. Yet another reason why I loathe Mr. Gates. I never had this problem with Vista or XP. Of course, the only reason I moved this early to Windows 7 was that I was forced to take Vista on my computer when I bought it, and never liked it. I usually wait for an OS to be out for at least a year, before I move to it, so all the manufacturers of hardware can catch up with their drivers. |
| My System Specs |
 |
2 Clean Installs - Still crashes in sleep mode problems?
| Thread Tools | |
| Similar help and support threads for: 2 Clean Installs - Still crashes in sleep mode | ||||
| Thread | Forum | |||
| Laptop crashes during sleep mode | Performance & Maintenance | |||
| Crashes in Sleep mode | BSOD Help and Support | |||
| Windows 7 Crashes upon Sleep mode | BSOD Help and Support | |||
| Sleep mode crashes PC | BSOD Help and Support | |||
| Windows 7 Crashes in sleep mode | BSOD Help and Support | |||
All times are GMT -5. The time now is 12:52 PM.
