12-08-2009 09:32 AM
I recently completely reset my system with the ThinkVantage solution - bringing it back to the original settings - reinstalling XP and everything
then all the service packs and updates have been downloaded
I have one problem now
When I have activated my Intel Gigabit LAN connection, and when I wake my laptop from hibernate it will (i guess almost every time) crash with a bluescreen
it is always the same driver
On Tue 08.12.2009 05:07:40 your computer crashed
This was likely caused by the following module: e1y5132.sys
Bugcheck code: 0x40000080 (0x8991BAD0, 0x89694C10, 0x805512BC, 0x1)
Dump file: C:\WINDOWS\Minidump\Mini120809-01.dmp
file path: C:\WINDOWS\system32\drivers\e1y5132.sys
product: Intel(R) Gigabit Network Connection
company: Intel Corporation
description: Intel(R) Gigabit Network Connection NDIS 5.1 deserialized driver
I already updated it making sure to have the newest (from the Intel site) but the problem persists.
adapter is Intel 82567LM Gigabit Network
driver is 22.214.171.124 (26-march-09)
THANKS SO MUCH
12-09-2009 12:38 PM
I am having the same problem when the machine comes back from sleep mode. It connects to a wireless network OK, but when I come back into work the next day and plug into the LAN it blue screens. It even blue screened the one time I connected to a physical LAN at home (the wireless was acting up after waking up from sleep and not seeing any connections, and I did not want to reboot). I thought it was something screwy with this work network (though what can you do to make it kill the machine? Ultimate DOS Attack!) but now I am thinking it is a bug?
Hopefully there are answers somewhere?
12-09-2009 08:59 PM
12-11-2009 05:27 AM
Just a reminder that this is a user-to-user help community, moderated by volunteers like me. Although employees do fly by from time to time, it is not a monitored Lenovo support channel.
12-15-2009 07:33 PM
I know this is a dumb solution, but at least you can power off at night vs hibernate and power on in the morning. It's a pain, but it is a work around. At least you have a work around.
12-16-2009 05:48 PM
thanks but this workaround does not really help
oftentimes when on the move i have to quickly power off and this means hibernate instead of waiting hours for windows to shut down and reboot a new loading all drivers
there must be a solution
01-06-2010 08:40 AM - edited 01-06-2010 08:42 AM
I was just about to open a topic about this very same problem!
Firstly, I would not recommend using drivers supplied by anyone other than Lenovo. Who knows what Lenovo adds/removes when they (re)distribute the driver.
I've gone so far as to download, from MS, their WinDBG application to look at the minidumps that get generated when this happens.
The output that I see is:
This is the NDIS Driver Bugcheck for Windows 2000 and Windows XP.
For Windows Server 2003 and later, see 0x7C, BUGCODE_NDIS_DRIVER.
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.
LAST_CONTROL_TRANSFER: from b9cdb821 to 804f9f43
805511f8 b9cdb821 40000080 8a21dad0 89b6d698 nt!KeBugCheckEx+0x1b
80551258 ad5ce1f8 00107770 805512bc 00000003 NDIS!ethFilterDprIndicateReceivePacket+0x5fe
WARNING: Stack unwind information not available. Following frames may be wrong.
80551274 ad5d732c 8a0f3988 805512bc 00000003 e1y5132+0x21f8
80551294 ad5d97ca 8a0e5c40 00000000 805512bc e1y5132+0xb32c
805513cc ad5d42e1 01206000 00000003 00000000 e1y5132+0xd7ca
80551404 ad5cd371 00206000 80551428 b9cd0e99 e1y5132+0x82e1
80551410 b9cd0e99 8a0f3988 8055c0c0 ffdff9c0 e1y5132+0x1371
80551428 80545e7f 8a206860 8a20684c 00000000 NDIS!ndisMDpcX+0x21
80551450 80545d64 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
80551454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28
ad5ce1f8 ?? ???
Interestingly enough, I can't even find a "e1y5132.sys" file on my system.
So, the question to be asked: Did Lenovo screw up with a recent Intel LAN driver update? Or am I mis-reading what this is trying to tell me?