Random Unexpected Shutdowns

For the past month or so, I have been seeing the message that Windows recovered from an unexpected error and I select the option to report and find out why, but of course it never comes back with anything.

I am running Win 7 Professional version, retail version. (Downloaded). I've had it on this computer for probably a year or more, and never had any problems. I can be using the computer all day, and never had a problem. But then overnight or when the computer is idle for a few hours, I will come back and it will have reboot and the error message. I have attached the files as requested.

Thank You

douggw said:

For the past month or so, I have been seeing the message that Windows recovered from an unexpected error and I select the option to report and find out why, but of course it never comes back with anything.

I am running Win 7 Professional version, retail version. (Downloaded). I've had it on this computer for probably a year or more, and never had any problems. I can be using the computer all day, and never had a problem. But then overnight or when the computer is idle for a few hours, I will come back and it will have reboot and the error message. I have attached the files as requested.

Thank You

Your Intel Pro 10/100 driver crashes every time. It is three years old and seriously needs updating

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\New folder\122910-39827-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82b44ad4?
Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82a1e000 PsLoadedModuleList = 0x82b66810
Debug session time: Wed Dec 29 10:54:14.331 2010 (GMT-5)
System Uptime: 0 days 9:13:22.266
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
........................
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: 85373690, Physical Device Object of the stack
Arg3: 82b44ae0, Functional Device Object of the stack
Arg4: 850c6118, The blocked IRP

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for e100b325.sys
*** ERROR: Module load completed but symbols could not be loaded for e100b325.sys

DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  850c6118

DEVICE_OBJECT: 864ed028

DRIVER_OBJECT: 864cdab0

IMAGE_NAME:  e100b325.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  473de72c

MODULE_NAME: e100b325

FAULTING_MODULE: 95a00000 e100b325

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82a5a054 to 82afad10

STACK_TEXT:  
82b44a94 82a5a054 0000009f 00000003 85373690 nt!KeBugCheckEx+0x1e
82b44b00 82a598e8 82b44ba0 00000000 82b51280 nt!PopCheckIrpWatchdog+0x1f5
82b44b38 82a8804d 82b5fa20 00000000 a435279a nt!PopCheckForIdleness+0x73
82b44b7c 82a87ff1 82b47d20 82b44ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82b44c68 82a87eae 82b47d20 82b44ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82b44cdc 82a8620e 002079d0 87148030 82b51280 nt!KiTimerExpiration+0x25c
82b44d20 82a86038 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82b44d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_e100b325.sys

BUCKET_ID:  0x9F_IMAGE_e100b325.sys

Followup: MachineOwner
---------

Old drivers needing update from as far back as 2005

Code:

ElbyDelay.sys    4/12/2005 3:41:20    0x425b89b0    0x95a27000    0x95a28200        0x00001200                        
ElbyCDIO.sys    4/21/2005 6:40:36    0x42679134    0x951d0000    0x951d2980        0x00002980                        
AnyDVD.sys    1/1/2006 5:13:49    0x43b7ab5d    0x95992000    0x95996b00        0x00004b00                        
mdmxsdk.sys    6/19/2006 16:26:59    0x449716a3    0x951d3000    0x951d6180        0x00003180                        
HSX_CNXT.sys    6/20/2007 13:28:20    0x467971c4    0x95b30000    0x95be5000        0x000b5000                        
HSXHWBS2.sys    6/20/2007 13:28:36    0x467971d4    0x958d8000    0x95924000        0x0004c000                        
HSX_DPV.sys    6/20/2007 13:29:51    0x4679721f    0x95a2d000    0x95b30000        0x00103000                        
xaudio.sys    6/29/2007 19:11:00    0x46859f94    0xaf9cc000    0xaf9d4000        0x00008000                        
e100b325.sys    11/16/2007 13:53:32    0x473de72c    0x95a00000    0x95a26e00        0x00026e00                        
sp_rsdrv2.sys    9/30/2008 8:00:27    0x48e222eb    0x923c2000    0x923e4d00        0x00022d00                        
NuidFltr.sys    5/8/2009 3:35:42    0x4a03eede    0x964f4000    0x964fb000        0x00007000                        
spldr.sys    5/11/2009 11:13:47    0x4a084ebb    0x88e00000    0x88e08000        0x00008000                        
JakNDis.sys    5/11/2009 15:53:58    0x4a089066    0x95822000    0x9582c000        0x0000a000                        
GEARAspiWDM.sys    5/18/2009 7:16:53    0x4a1151b5    0x95997000    0x9599c280        0x00005280                        
amdxata.sys    5/19/2009 12:57:35    0x4a12f30f    0x8895b000    0x88964000        0x00009000                        
netr28.sys    6/19/2009 2:57:13    0x4a3b44d9    0x95833000    0x958ce000        0x0009b000

How To Find Drivers:

- 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.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Hmm.. Let me do some updating then. I thought Windows would automatically update my drivers, but as you can tell, I thought wrong!

Thanks for the clues and heading me in the right direction. Should I also run the Driver Verifyer in Windows?

douggw said:

Hmm.. Let me do some updating then. I thought Windows would automatically update my drivers, but as you can tell, I thought wrong!

Thanks for the clues and heading me in the right direction. Should I also run the Driver Verifyer in Windows?

Driver verifer is for when the offending driver is not identified. Yours is so no need. It can also crash your system and make it un-useable so no.

Updating drivers is easy. google the name and it will tell you who makes it. go to their site and find the driver for your OS.

Ken J

I think I replaced most of the drivers that I could find, including the Intel one. What file can I look in after I re-run the diagnostic tests to generate the files I attached to here, to check and see the dates of my drivers?

The computer still reboots randomly with the unrecoverable error, but it only happens when the computer goes into sleep mode. I disabled the sleep mode and the computer is fine.

I am wondering if I should update the bios too?