IRQL LESStHAN OR EQUAL TO when playing online video for extended time.

Hello Ten Forums!

I recently had thought that I had cleared up a problem by having my RAM run at 2133 MHZ to clear up any memory incompatibility issue (per the great AXE0's suggestion), but BSOD still came back with IRQL not equal but less frequently, and with Bluescreen view, the issues point to "ntoskrnl.exe" once again. I googled around and saw that this could mean anything. Once again, I am stumped and I looked through windbg to try and find a driver at fault but I still cannot find anything. Any help would be appreciated! Thank you for your time!

Sincerely,

Carelesswhisper

Hi carelesswhisper,

Please upload a new zip, the current uploaded zip is from the previous thread.

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Incorrect and partly correct.

The tcpip.sys is a Windows driver, from Windows drivers we can assume they are not the cause. If Windows drivers were the cause many systems running Windows would be very unstable as it is a fact that Windows drivers very often show up in the dumps.

Some Windows drivers do give indications towards possible causes where we come with the 'partly correct'.
When a Windows network driver is flagged there are more possible causes than just the network drivers from the network adapters.
AV programs, AM programs, VPN programs, USB network adapters, etc., all those are also included when Windows network drivers are flagged.
If you're certain your physical network adapters (wifi, lan, usb) are perfectly fine, but crashes keep showing that the network drivers are causing the crashes. There are various reasons why this occurs for which some more analysis and troubleshooting is required, but you need to include all possibilities, else someone would replace the whole system without knowing that a single driver from the AV is causing problems. A simple removal of the program would do the job.

In your case I found the LAN driver being the possible cause, check ASRock for driver updates :)

Code:

1: kd> lmvm e1i63x64
Browse full module list
start             end                 module name
fffff80d`d7400000 fffff80d`d7486000   e1i63x64 T (no symbols)           
    Loaded symbol image file: e1i63x64.sys
    Image path: \SystemRoot\System32\drivers\e1i63x64.sys
    Image name: e1i63x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar 04 22:46:29 2016 (56DA0235)
    CheckSum:         00086238
    ImageSize:        00086000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please update the BIOS to see if that helps.
ASRock > Z170M-ITX/ac

If a BIOS update doesn't help then you have a hardware issue.