BSOD Solution for Intel Ether-Driver!

[ihatebsofd]

Hey guys, so after about 3 weeks of searching the deepest corners of the web I think i finally have a positive result and thought I'd share it with the fellow members of this site who helped me in the process.

For those who get the BSOD "tcpip.sys" and "e1q62x64.sys" this if for you.

If you get this, you probably have a new Asus Crosshair Formula motherboard of some sort, or a motherboard with an Intel Ethernet Adapter.
When people analyze the bluescreens you upload here, they will say that you need to update your Intel ethernet adapter driver, because thats what it says in the report.
While this is good, if you dont have the latest driver, I came to find that the problem is actually microsoft's fault and they've admitted to it.

When an outgoing clear text packet is sent by using the IPSec tunnel, an access violation occurs. This behavior triggers this error message:

0x000000D1 (parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL

- The four parameters in this error message vary. This depends on the configuration of the computer.
- Not all " 0x000000D1" Stop error codes are caused by this problem.

I dont know why they haven't dealt with this in a windows update, but heres a HOTFIX download that i recommend if you are having the same problems I had / possibly will have. It's supposed to fix it. At the moment of writing i am downloading at full network capacity and have been doing so for the last 20 minutes without a crash.

 

[fimble]

Hi ihatebsofd.

You lost me when you posted that screenshot in the other thread !( Windows 7 - BSOD tcpip.sys & e1q62x64.sys).

But a good find here. I've made a note of the link. Let us know how you get on.

 

[ihatebsofd]

Hi ihatebsofd.

You lost me when you posted that screenshot in the other thread !( Windows 7 - BSOD tcpip.sys & e1q62x64.sys).

But a good find here. I've made a note of the link. Let us know how you get on.

Yeah fimble, that was CHKDISK on startup that screwed up most of my registry files.. this happened to me before aswell, so i just formatted my HD and reinstalled windows.

 

[ihatebsofd]

Another possible solution I found, this is for WIRELESS( e1k62x64.sys ) so I don't know how this would apply / how I would go about fixing it with my problem which is ( e1q62x64.sys )

The cause of the blue screen is a missing entry in the driver install information file (INF). You could edit the file, uninstall the Intel(R) Network Connections software, and then install again from a software copy with the edited INF file.



Follow these steps.


Make a copy of the original software package before you do the other steps so you can go back to the original file if you make a mistake.

Open your software package with WinZip* or a similar program.

In the PRO1000\Winx64\NDIS62 directory you will find the e1k62x64.inf file.

Open the file.

Find the [E10EA.HW] and [E10EB.HW] sections

Add this line to each of the above sections
AddReg = MSI.reg

Save the file and install the drivers and software.




The edited sections should look like this example when you are done.

[E10EA.HW]
Include = machine.inf
Needs = PciIoSpaceNotRequired
AddReg = MSI.reg



[E10EB.HW]
Include = machine.inf
Needs = PciIoSpaceNotRequired
AddReg = MSI.reg

Let us know how this works out for you.



Anyways if anyone has an input please do tell.

EDIT: My question is, whats the difference between e1q62x64 and e1k62x64 ? from what i read on Intel forums, they actually forgot to put in lines in the inf file, which is whats causing the crashes