BSOD after Standby or Hibernation

Not to muscle in on trashcan's crisis or anything, but I also have a brand-new Inspiron 530s and it's just done the same thing, BSOD after being woken up from hibernation. I found this thread by googling the error codes and also found someone over here who seems to be having the same problem with the same model (they don't say anything about it happening after hibernation, but maybe they haven't made the connection). Anyway, you seem a lot more helpful and knowledgeable over here, so here's my debug file:

Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini042708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_qfe.070227-2300
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Sun Apr 27 15:28:37.000 2008 (GMT-5)
System Uptime: 0 days 4:38:38.681
Loading Kernel Symbols
..................................................................................................................
Loading User Symbols
Loading unloaded module list
.................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 40000080, {89cc1ad0, 896d3698, ba4d3bb8, 1}

Unable to load image e1e5132.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1e5132.sys
*** ERROR: Module load completed but symbols could not be loaded for e1e5132.sys

Probably caused by : e1e5132.sys ( e1e5132+21f8 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_ID_DRIVER (40000080)
This is the NDIS Driver Bugcheck for Windows 2000 and Windows XP.
For Windows Server 2003 and later, see 0x7C, BUGCODE_NDIS_DRIVER.
DESCRIPTION
The meaning of the bug check parameters cannot be determined by examining the
parameters alone. You must also examine the text of a DbgPrint message.
For details, see either the debugger documentation or the DDK documentation.
Arguments:
Arg1: 89cc1ad0
Arg2: 896d3698
Arg3: ba4d3bb8
Arg4: 00000001

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

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x40000080

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b9d8a921 to 804f9f13

STACK_TEXT:
ba4d3af4 b9d8a921 40000080 89cc1ad0 896d3698 nt!KeBugCheckEx+0x1b
ba4d3b54 b971e1f8 89cc1ad0 ba4d3bb8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5fd
WARNING: Stack unwind information not available. Following frames may be wrong.
ba4d3b70 b972835c 899701b8 ba4d3bb8 00000001 e1e5132+0x21f8
ba4d3b90 b972ab3d 89969208 00000000 ba4d3bb8 e1e5132+0xc35c
ba4d3cc8 b9724341 01921000 00000001 00000001 e1e5132+0xeb3d
ba4d3d04 b971d371 00921000 ba4d3d28 b9d7ff09 e1e5132+0x8341
ba4d3d10 b9d7ff09 899701b8 8055b0a0 ba3389c0 e1e5132+0x1371
ba4d3d28 805451ff 89921b24 89921b10 00000000 NDIS!ndisMDpcX+0x21
ba4d3d50 805450e4 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
ba4d3d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28

STACK_COMMAND: kb

FOLLOWUP_IP:
e1e5132+21f8
b971e1f8 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: e1e5132+21f8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: e1e5132

IMAGE_NAME: e1e5132.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 461fe440

FAILURE_BUCKET_ID: 0x40000080_e1e5132+21f8

BUCKET_ID: 0x40000080_e1e5132+21f8

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

I see that e1e5132.sys seems to be the problem, and I googled "unable to load image e1e5132.sys" and found several more people on yet another forum dealing with the same problem on Inspiron 530s. This is very discouraging, as I bought this computer based on positive reviews. :thumbsup:

Anyway, someone over there said he seemed to have solved the problem by reinstalling TrendMicro and updating the video card drivers--well, I was only going to keep TrendMicro through the end of the trial period anyway and then use a combination of AVG and ZoneAlarm, so I think I will just uninstall TM now, update the drivers, and see what happens. I seem to have solved my own problem (but I wouldn't have figured it out without your directions in this thread), so I guess this is all just FYI in case you get more people having this same problem, which certainly seems likely. Thanks!

This post has been edited by garmanma: 27 April 2008 - 05:17 PM
Reason for edit: Split topic to start own thread

BleepingComputer.com: BSOD after Standby or Hibernation