Share via

IRQL NOT LESS OR EQUAL ; What failed: ntoskrnl.exe

Anonymous
2023-05-02T16:57:03+00:00

Hello, this is my first time asking a question on this forum

I've been getting a lot of BSODs recently

The BSOD says:

IRQL_NOT_LESS_OR_EQUAL

What failed: ntoskrnl.exe

I have also been getting many other BSODs, like DRIVER_OVERRAN_STACK_BUFFER, SYSTEM_SERVICE_EXCEPTION, KMODE_EXCEPTION_NOT_HANDLED etc.

I've been trying a lot of things to try and fix this issue, but nothing has worked.

If someone could help me fix this, it would mean a lot!

Windows for home | Windows 11 | Performance and system failures

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

31 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. David-M 112.1K Reputation points Independent Advisor
    2023-05-03T18:24:49+00:00

    One of your minidumps indicates the driver "amdkmdag.sys" as the cause of the crash. This driver belongs to your AMD graphics card.

    Download the latest driver for your graphics card from the AMD website. Then use the free DDU tool to remove the current driver. Then install the latest driver using the installer you downloaded.

    DDU: https://www.guru3d.com/files-details/display-dr...

    AMD driver download: https://www.amd.com/en/support

    See if the system will work stable after this.

    ________________________________________________________

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  2. David-M 112.1K Reputation points Independent Advisor
    2023-05-03T11:48:11+00:00

    The minidump generated by Driver Verifier indicates it was caused by the driver "vgk.sys", which belongs to the Vanguard anti-cheat.

    I suggest you uninstall Vanguard and reinstall it.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. David-M 112.1K Reputation points Independent Advisor
    2023-05-02T17:28:08+00:00

    Hi. I'm David, and I'm happy to help you.

    See if your computer is creating minidump files. These files may help to determine the cause of the error.

    These files are in "C:\Windows\Minidump".

    Copy any files you have to your desktop and store them in a ZIP file. Then upload the ZIP file to the cloud (OneDrive, Google Drive, Dropbox, etc...), choose to share it, and get the link.

    Post the link to the ZIP file here so I can have a look.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-05-09T06:38:19+00:00

    Hi David,

    (This is my 3rd time writing a reply because the system loves crashing)

    It has been a few days. I was trying to give the system some time to see how many times it could crash, and why.

    A lot of the time, the display would just go black, and a force shutdown would be required.

    There would also be sometimes when the display would just freeze, and a force shutdown would be required.

    The system apparently doesn't log everything. It only logs when the system shows a BSOD.

    There were some instances when a BSOD would show up but it wouldn't even say what the error was.

    These are nearly all the minidumps the system created (some of them got automatically deleted for whatever reason)

    Here are the minidumps:

    https://1drv.ms/u/s!AnNjpyBRTJ79iSr0RVGi7E2OI9_r?e=iUXqST https://1drv.ms/u/s!AnNjpyBRTJ79iTPklNgTc2JFj-hT?e=n7BnS2

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. David-M 112.1K Reputation points Independent Advisor
    2023-05-02T18:04:43+00:00

    The minidumps do not mention any driver as causing the crashes.

    I suggest you use the Driver Verifier utility. This utility is used to force the system to show the driver causing the problem.

    Before turning on Driver Verifier, I like to create a restore point just in case. I suggest doing the same.

    https://support.microsoft.com/en-us/windows/cre...

    Turn on Driver Verifier, let the system crash 3 times, then turn off Driver Verifier. Send the minidumps that the crashes created.

    See the article below for instructions.

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments