[SOLVED] Require help! (BSOD) DRIVER_IRQL_NOT_LESS_OR_EQUAL tcpip.sys

[captainmike196]

Hello, my PC randomly crashed on me with this error,
DRIVER_IRQL_NOT_LESS_OR_EQUAL
What failed: tcpip.sys

I had this issue about few month ago where it kept randomly crashing with this error and it wouldn't restart when the bsod reached 100%. After a few days it stopped and didn't happen for 2 months or so. I thought it was just random, but then just now it bsod the same screen but this time it restarted my pc like it should had! So hopefully the dmp files are more useful and not corrupted.

My original thread: http://www.tomshardware.com/forum/id-3699398/bsod-driver-irql-equal-tcpip-sys.html?xtor=EREC-8889

Here's the new dump file: https://drive.google.com/open?id=1J7dgpeIbEcrwvOzP1aGo6wKTmQY9PYxe

 

[gardenman]

Hi, it appears as if your Killer Networking drivers crashed. This dump file is better, not corrupt. It says:

PROCESS_NAME: firefox.exe
Probably caused by : e2xw10x64.sys

Programs usually don't cause crashes (Firefox). Drivers do (e2xw10x64.sys). Driver files usually end in ".sys". Since it's likely Firefox was connecting to the internet then it makes sense for a driver that has to do with the internet to crash. tcpip.sys is also a "internet" related driver. (I think you know that, sorry, it's hard to tell who knows what and keep up with that info on here).

My description for e2xw10x64.sys is "Killer PCI-E Gigabit Ethernet Controller driver http://www.killernetworking.com/ ".

Try updating the driver again. Or try a different version of the driver if possible.

Dump information: https://pste.eu/p/h79E.html

File: 071718-23218-01.dmp (Jul 17 2018 - 16:04:15)
BugCheck: [DRIVER_IRQL_NOT_LESS_OR_EQUAL (D1)]
Probably caused by: e2xw10x64.sys (Process: firefox.exe)
Uptime: 0 Day(s), 0 Hour(s), 31 Min(s), and 40 Sec(s)

If it doesn't fix your problem, I would consider new hardware. Killer Networking often comes up on here when talking about BSODs.

Why the new name?

 

[captainmike196]

Thank you very much, I wasn't able to figure it out before but now that I atleast know that my network drivers are the cause, it makes me feel alot of relief because it was a complete shot in the dark before.

I'll update the drivers again and if that doesn't fix it i'll reinstall an older verison.

I changed my name because I couldn't log into my old account so I just quickly made this in a hurry, lol

I'll update if anything else goes wrong
quick edit: I notice theres a newer verison of my drivers so im gonna go ahead and install that

 

[gardenman]

I take it back when I said "consider new hardware". I should know better with the number of BSOD question we have answered on here that it's not always so simple. While we both may be right, it may very well be the network card or drivers, let's wait and see.

If you get any more crashes upload the new dump files.

 

[Colif]

@ CaptainMike, I sent you a Private Message