For months I've been using my Toshiba Satellite Laptop then one instance when I was about to shutdown my laptop the BSOD appear indicating the IRQL_NOT_LESS_OR_EQUAL error this happens during my first shutdown of the day then my Laptop would RESTART and when I try to shut it down again it will shutdown normally but it give me discomfort knowing that something is wrong with my Laptop so I've read several solutions posted here at MS Community and different win8 forums, first I tried to follow all the methods that was posted here:

I also enable driver verifier.  

specifically Bennet Martin's Instructions from Methods 1-2 except the Method 3 I've never tried it, then I thought everything was going well but the next day during my first shutdown the IRQL_NOT_LESS_OR_EQUAL error was there again.

Next I tried DISM, sfc/scannow commands in the command prompt and it said that all has been fixed and no violations has been done (that was not really the exact words but something like that) then once again I thought it fixed the problem for good because when I shutdown my Laptop no BSOD appeared, then the  next morning before going to school I opened my Laptop to Login to Facebook for a while then when I was shutting my Laptop down the BSOD IRQL_NOT_LESS_OR_EQUAL error was there again.

Then I've read forums again and look for answers here again, then I tried downloading the Windows Software Development Kit to read my dmp files and it ended up telling me: 

"Probably caused by : ntoskrnl.exe ( nt+14dca0 )

Followup: MachineOwner"

If someone could just help me, I would really appreciate it. 

My dmp file:



The attached DMP file is of the IRQL_NOT_LESS_OR_EQUAL (a) bug check.

This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high. The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.


-- FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KiProcessThreadWaitList+b9

^^ It's a verifier enabled dump (VRF), however it's failing to find any 3rd party drivers making bad function calls. Possible hardware issue with this said.


1. Remove and replace AVG with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:

AVG removal -

Windows Defender (how to turn on after removal) -

2. If the above fails to stop the crashes, please run Memtest for NO LESS than ~8 passes (several hours):


Download Memtest86+ here:

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:



Debugger/Reverse Engineer.

2 people found this reply helpful


Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.


Question Info

Last updated October 25, 2020 Views 35,884 Applies to: