Win7 64bit E1K62x64.exe Crash

[SavellM]

Hey Guys,

Im constantly having thise BSOD about once a day.
From what I have read its to do with my NIC, but I have the latest NIC drivers from Dell.

Is Windows 7 . . .
- x86 (32-bit) or x64: 64bit
- the original installed OS on the system: Yes, and have reformatted a number of times
- an OEM or full retail version: OEM

- What is the age of system (hardware): 2 Weeks
- What is the age of OS installation: Fresh
I have attached the BSOD folder as asked.
If you would like any more info let me know

 

[jcgriff2]

Hi -

Update your Intel 82577LM Gigabit NIC driver - v 15.5 out 29 July 2010 - from the Intel Download Center -

[FONT=lucida console]e1k62x64.sys Tue [COLOR=red]Apr 06[/COLOR] 03:37:39 [COLOR=red]2010[/COLOR] (4BBAE4C3) - [URL="http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Ethernet+Components&ProductLine=Ethernet+Controllers&ProductProduct=Intel%C2%AE+82577+Gigabit+Ethernet+PHY"]http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Ethernet+Components&ProductLine=Ethernet+Controllers&ProductProduct=Intel%C2%AE+82577+Gigabit+Ethernet+PHY[/URL][/FONT]

Intel Download --> http://downloadcenter.intel.com/Sea...ductProduct=Intel®+82577+Gigabit+Ethernet+PHY

I would advise that you remove NIS/ 360 from your system --> NIS/ N360 Removal -- jcgriff2.com

If BSODs persist, run the Driver Verifier --> Driver Verifier - jcgriff2.com

Windbg Logs
--> http://jcgriff2.com/dbug_logs/_99-dbug_SavellM_Windows7x64_09-02-2010_jcgriff2_.txt
--> http://jcgriff2.com/dbug_logs/_99-dbug_SavellM_Windows7x64_09-02-2010_jcgriff2_.txt.zip

Regards. . .

jcgriff2

`

BSOD BUGCHECK SUMMARY

[FONT=lucida console]Built by: 7600.16617.amd64fre.win7_gdr.100618-1621[/FONT]
[FONT=lucida console]Debug session time: Thu Sep  2 08:44:16.441 2010 (GMT-4)[/FONT]
[FONT=lucida console]System Uptime: 0 days 1:53:30.906[/FONT]
[FONT=lucida console]BugCheck D1, {90, 2, 1, fffff8800468d353}[/FONT]
[FONT=lucida console]*** WARNING: Unable to verify timestamp for e1k62x64.sys[/FONT]
[FONT=lucida console]*** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys[/FONT]
[FONT=lucida console]Probably caused by : e1k62x64.sys ( e1k62x64+1b353 )[/FONT]
[FONT=lucida console]DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT[/FONT]
[FONT=lucida console]BUGCHECK_STR:  0xD1[/FONT]
[FONT=lucida console]PROCESS_NAME:  System[/FONT]
[FONT=lucida console]Bugcheck code 000000D1[/FONT]
[FONT=lucida console]Arguments 00000000`00000090 00000000`00000002 00000000`00000001 fffff880`0468d353[/FONT]
[FONT=lucida console]¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[SavellM]

Cheers mate.

Updated my NIC drivers so will see how this goes.
I cannot remove NIS as its a company laptop.

And if it persists I will run the driver verifyer.

Thanks again

 

[SavellM]

No luck.

I got another BSOD when I was copying files from my network share drive to a USB stick.

With the same E1K62x64 BSOD error message.
I am running the latest Intel NIC drivers (15.5) i think it was.

I am using the laptop on a Docking Station, so I tried to replicate this by copying large files from the network but no crash

Seems to just happen randomly.

Attached is a fresh dump.

 

[Jonathan_King]

Your Intel wireless drivers still show April 6, 2010 as the date. Try installing these drivers again: Software License Agreement

If that doesn't work, I would suggest contacting your manager and see about removing NIS. Perhaps you can convince him to let you remove it, and reinstall it if it doesn't help matters.

...Summary of the Dumps:

[font=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Fri Sep  3 05:26:03.193 2010 (UTC - 4:00)
System Uptime: 0 days 2:31:34.932
BugCheck D1, {90, 2, 1, fffff8800481b353}
*** WARNING: Unable to verify timestamp for e1k62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys
Probably caused by : e1k62x64.sys ( e1k62x64+1b353 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[SavellM]

Hey Jonathan,

Thanks, I have installed the latest Intel Drivers for Wirless.
Let me uninstall it reboot and re-install.

If it still continues, I will remove NIS, as these laptops are my test builds so I can do what I need to do.

 

[SavellM]

Hey Jonathan,

I uninstalled the Intel Wireless, and then rebooted, and re-installed the wireless from the Intel site.
But the driver date is still showing 31/05/2010, but on the Intel Site it shows driver version 02/07/2010.

Am I doing something wrong?
Should I uninstall in Safe Mode, restart and Re-Install in Safe Mode?

 

[SavellM]

Do you really think it could be beacuse of NIS?
If so I will do a complete format and clean install and this time not install NIS.

What you think?

 

[SavellM]

Ok I just got a totally different BSOD.
Here is what happened, I was using my NIC at 100mbps so swapped it over to 1gbit port so its running full capacity.

Wifi was turned OFF...

Started copying large files off the server, and poof, BSOD, but this time different.
This one just said Bad_Pool something and a stop code of C1 instead of the old D1.

Attached is a fresh dump log.
Is it the same thing?

 

[Jonathan_King]

Still, it blames your Intel wireless card. Try disabling it in Device Manager, and see what happens.

NIS (especially older versions), is well known for causing BSODs in the BSOD-analyst community. Since it is surely monitoring all network activity, it would not surprise me at all if it were the case here.

Once you actually disable the Intel wireless card in Device Manager, or physically remove or turn off the card, the drivers should stop getting loaded. A reboot will likely be required after disabling it.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\DOCUME~1\JK\LOCALS~1\Temp\Temporary Directory 2 for Windows_NT6_BSOD_jcgriff2.zip\Windows_NT6_BSOD_jcgriff2\090310-30529-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 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Fri Sep  3 05:27:38.120 2010 (GMT-5)
System Uptime: 0 days 1:00:20.396
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {90, 2, 1, fffff88004676353}

Unable to load image \SystemRoot\system32\DRIVERS\e1k62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1k62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1k62x64.sys
Probably caused by : e1k62x64.sys ( e1k62x64+1b353 )

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

 

[SavellM]

Hey Jonathan,

Are you sure its the wireless card and not the NIC?
That last BSOD had the wireless card turned off.

I can dissable it in Device Manager if you like to confirm 100%

 

[jcgriff2]

http://www.sevenforums.com/936186-post2.html

 

[hellsdriver]

No luck

Hi -

Update your Intel 82577LM Gigabit NIC driver - v 15.5 out 29 July 2010 - from the Intel Download Center -

Thanks, but this won't help.

Simple reason: The above driver package may contain a number of updated drivers but a closer look reveals that the PRO1000 driver, specifically e1k62x64.sys, is still the old, unchanged one!

No luck on Intel's site, there's even a newer driver pack from Oct 1 (v15.6) that still contains the old driver!
I wonder how Intel can have so little interest to support Win 7 x64 for essential network hardware.

I have no clue what to do. Even if I used Driver Verifier and it told me that e1k62x64.sys was faulty, what would I do then?

 

[Jonathan_King]

Hi -

Update your Intel 82577LM Gigabit NIC driver - v 15.5 out 29 July 2010 - from the Intel Download Center -

Thanks, but this won't help.

Simple reason: The above driver package may contain a number of updated drivers but a closer look reveals that the PRO1000 driver, specifically e1k62x64.sys, is still the old, unchanged one!

No luck on Intel's site, there's even a newer driver pack from Oct 1 (v15.6) that still contains the old driver!
I wonder how Intel can have so little interest to support Win 7 x64 for essential network hardware.

I have no clue what to do. Even if I used Driver Verifier and it told me that e1k62x64.sys was faulty, what would I do then?

Hello hellsdriver devil

Intel also releases individual network drivers. Are you having problems with BSODs? If so, please follow these directions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Create a new thread, post the logs, and if the problem is indeed e1k62x64.sys, I'll get you an update.