Windows 7 Frequent System Crashes at Night: Need Help Analyzing Minidump

hvaughan

New Member
Joined
Jun 12, 2011
Messages
6
Every night my system crashes. I have to power it back up each morning. Please help. Ihave copied the minidump to my desktop and zipped it.
Thanks,
hvaughan
 


Solution
Hello there!


Seems like your dumps are blaming e1e6232.sys which is a LAN driver (network adapter) for the crashes. Please download a new version and uninstall the old driver and install the new open.

Code:
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: 85c76030, Physical Device Object of the stack
Arg3: 82971ae0, Functional Device Object of the stack
Arg4: 887eec20, The blocked IRP

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

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

DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS...
Hello there!


Seems like your dumps are blaming e1e6232.sys which is a LAN driver (network adapter) for the crashes. Please download a new version and uninstall the old driver and install the new open.

Code:
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: 85c76030, Physical Device Object of the stack
Arg3: 82971ae0, Functional Device Object of the stack
Arg4: 887eec20, The blocked IRP

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

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

DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  887eec20

DEVICE_OBJECT: 853c5028

DRIVER_OBJECT: 86b981a8

IMAGE_NAME:  e1e6232.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a296d0a

MODULE_NAME: e1e6232

FAULTING_MODULE: 94b89000 e1e6232

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82910f35 to 82928f2c

STACK_TEXT:  
82971a94 82910f35 0000009f 00000003 85c76030 nt!KeBugCheckEx+0x1e
82971b00 82910fae 82971ba0 00000000 8297e380 nt!PopCheckIrpWatchdog+0x1f5
82971b38 828c4039 8298c6e0 00000000 ca6f20e7 nt!PopCheckForIdleness+0x73
82971b7c 828c3fdd 82974d20 82971ca8 00000001 nt!KiProcessTimerDpcTable+0x50
82971c68 828c3e9a 82974d20 82971ca8 00000000 nt!KiProcessExpiredTimerList+0x101
82971cdc 828c200e 0031e8eb 87e214d8 8297e380 nt!KiTimerExpiration+0x25c
82971d20 828c1e38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82971d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_e1e6232.sys

BUCKET_ID:  0x9F_IMAGE_e1e6232.sys

Followup: MachineOwner
 


Solution
Thank you so much, Captain Jack. I had to reinstall Windows on my machine. (There went a weekend). I am sure that the drivers were out of date. i have reinstalled all of the drivers, and the problem has gone away.

Many thanks again,
hvaughan
 


Back
Top