Random BSOD, ntoskrnl.exe tcpip.sys

Hey I'v been trying to replicate my BSOD problem for that last day or so trying to nail down what it is but I just cant figure it out. It seems to happen at random times. I can have just a few programs turned on and it can go. At first I thought it was steam cause it always seemed to be open in the background when I Bluescreened but I cant think how Steam would do that.

My PC specs are:

OS Version: Microsoft Windows 7 Home Premium, Service Pack 1, 64 bit
Processor: Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz, Intel64 Family 6 Model 42 Stepping 7
Processor Count: 8
RAM: 16365 Mb
Graphics Card: AMD Radeon HD 6800 Series, 1024 Mb
Hard Drives: C: Total - 132043 MB, Free - 24905 MB; D: Total - 476936 MB, Free - 171928 MB; Z: Total - 1907726 MB, Free - 488020 MB;
Motherboard: Acer, Predator G5910
Antivirus: Microsoft Security Essentials, Updated and Enabled

I downloaded BluescreenViewer to attempt to work it all out, but I just cant nail it. It keeps saying the exact same thing from every dump though:
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
And the 2 files always in red (with the same hex offset after them)
notskrnl.exe+f20c4
tcpip.sys+6420e


EDIT:
Some extra info that I just remembered. I've run chkdsk /r /f on both my C: and my D: with no errors to report. (C: is a SSD). I've also run memtest86+ over my ram with no errors [only ran for 1 pass]


Any help would be much appreciated,
Thanks for your time,
Nickflame

Hello Nick.

It appears that the BSOD is caused by Intel Gigabit network adapter driver.

Code:

fffff880`0af31a28  fffff880`058514c7Unable to load image \SystemRoot\system32\DRIVERS\e1c62x64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
 e1c62x64+0x2f4c7

And the driver is old.

Code:

fffff880`05822000 fffff880`0587d000   e1c62x64 T (no symbols)           
    Loaded symbol image file: e1c62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
    Image name: e1c62x64.sys
    Timestamp:        Thu Dec 01 04:39:31 2011 (4ED6B7AB)
    CheckSum:         0006396D
    ImageSize:        0005B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it from https://downloadcenter.intel.com/default.aspx

Update your ATI/AMD display driver.
You can get it from the link in our forum, Latest AMD Catalyst Video Driver for Windows 7, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.


During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Let us know the results. Also upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Ok So I updated the LAN driver and things were going well. I am unsure how to replicate the BSOD so I just open quite a few internet based apps and see how it goes. I was watching a youtube video in fullscreen (1080p) and bam, just BSOD'd again; HOWEVER its a different error this time. NETIO.sys

As for the Graphics driver, I had updated them about 2 days before I posted so I didn't bother doing it again.

I've attached the new dmp file and the MSINFO file you requested.

I am hoping its not a virus? I've scanned all my HDDs with MSE like 5 times just to be sure. Its just I'v never had problems like this before, so I am wondering why its all of a sudden chosen to crap itself.

Do one thing as a check. Change the virtualbox network configuration to Host only; your current configuration is bridged. After applying that change, run the computer normally and check if it is causing more BSODs or not.

For the windows 8 related issues, post in Windows 8 Forums.

As this thread is of no use any more, you may close it by marking it as solved.

In your case, it was some driver related issues as far as I have checked, and hopefully those would have been recoverable. Sometimes troubleshooting takes a time to yield a result :)