Share via

IRQL_NOT_LESS_OR_EQUAL Blue Screen caused by ntoskrnl.exe Windows 8.1

Anonymous
2015-04-27T06:49:50+00:00

Today, I just got the Blue Screen of Death IRQL_NOT_LESS_OR_EQUAL caused by that dreaded ntoskrnl.exe. It's only happened once, but I had to restart again because my internet connection stopped working. I then downloaded BlueScreenView and here's what I got:

Crash Information

Here's what it said: (Windows XP display)

A problem has been detected and Windows has been shut down to prevent damage

to your computer.

The problem seems to be caused by the following file: ntoskrnl.exe

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen,

restart your computer. If this screen appears again, follow

these steps:

Check to make sure any new hardware or software is properly installed.

If this is a new installation, ask your hardware or software manufacturer

for any Windows updates you might need.

If problems continue, disable or remove any newly installed hardware

or software. Disable BIOS memory options such as caching or shadowing.

If you need to use safe mode to remove or disable components, restart

your computer, press F8 to select Advanced Startup Options, and then

select Safe Mode.

Technical Information:

*** STOP: 0x0000000a (0x00000000, 0x00000002, 0x00000000, 0x812ae64f)

*** ntoskrnl.exe - Address 0x8136a570 base at 0x8126f000 DateStamp 0x550f4146

The crash happened when I was running Classic Shell and I had ticked the box "Disable taskbar transparency." Might that have caused the issue?

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2015-04-29T07:45:27+00:00

These crashes were related to memory corruption (probably caused by a driver). Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

If you are over-clocking anything reset to default before running these tests.

In other words STOP!!!  If you do not know what this means you probably are not



1-Driver verifier (for complete directions see our wiki here)

**2-Memtest. (**You can read more about running memtest here)


Was this answer helpful?

0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-04-29T06:31:06+00:00

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-04-27T10:06:02+00:00

    We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.



    Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here

    If you have any questions about the procedure please ask

    Was this answer helpful?

    0 comments No comments