Share via

Various BSODs (KMODE_EXCEPTION_NOT_HANDLED, IRQL_NOT_LESS_OR_EQUAL, others)

Anonymous
2020-09-27T20:08:58+00:00

Hi,

I'm having constant trouble with BSODs on my computer, mostly stuff like IRQL_NOT_LESS_OR_EQUAL. I'm pretty sure it's some faulty driver, because I've ran memtest86 and the RAM has come up not faulty. If you need any more information, please let me know.

Here are all of the files from my Minidump folder:

https://drive.google.com/file/d/1PW9kFcFV3SAUOjAAAx7Jc-VZCfR\_zT4I/view?usp=sharing

Can anyone see a specific driver that's freaking out?

Windows for home | Windows 10 | 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

10 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-28T18:55:19+00:00

    Unfortunately I had a blue screen just now again, IRQL_NOT_LESS_OR_EQUAL. I uninstalled my mouse driver and let Windows install it back to default on reboot, and also rolled back my Nvidia drivers to an earlier version. I was playing Path of Exile when the crash happened.

    Here's the dump:

    https://drive.google.com/file/d/1pybgKMdiWsXJ5wT8jq0kJ5OJF3cIpulU/view?usp=sharing

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-09-28T14:43:17+00:00

    Okay, I hope it works for you.

    Good luck.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-09-28T14:26:39+00:00

    Thank you, I will try these suggestions and report back.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-09-27T21:01:47+00:00

    Hi tiny,

    I'm Paul, an Independent Advisor and a Windows 10 expert. I hope I can help you with your concern.

    This is the analysis report.

    A. 092720-10218-01.dmp and 092620-12140-01.dmp

    IRQL\_NOT\_LESS\_OR\_EQUAL (a) and   DRIVER\_OVERRAN\_STACK\_BUFFER (f7)

IMAGE\_NAME: ntkrnlmp.exe

    B. 092720-9890-01.dmp

     KMODE\_EXCEPTION\_NOT\_HANDLED (1e)

\*\*\* WARNING: Unable to verify timestamp for nvlddmkm.sys

IMAGE\_NAME:  Pool\_Corruption

    C. 092620-10406-01.dmp

    TIMER\_OR\_DPC\_INVALID (c7)

 IMAGE\_NAME:  dxgkrnl.sys

    D. 092220-9937-01.dmp

    IRQL\_NOT\_LESS\_OR\_EQUAL (a)

IMAGE\_NAME:  mouclass.sys

    Please try the following solutions.

    1. Install the latest Windows updates.
    2. Update or Rollback the Nvidia Graphics driver (nvlddmkm.sys) in the Device Manager.

    Open Device Manager >> click Display Adapter>> right- click your Display driver >> click Update Driver.

    If the system says that you have the latest driver installed. Try to Roll back the driver. Right-click your Display driver >> click Properties >> click Driver tab >> click Roll back driver.

    1. Update or Rollback the mouse driver ( mouclass.sys) in the Device Manager.

    Open Device Manager >> click MOuse and other pointing device >> right- click your mouse driver >> click Update Driver.

    If the system says that you have the latest driver installed. Try to Roll back the driver. Right-click your mouse driver >> click Properties >> click Driver tab >> click Roll back driver.

    1. Use System File Checker to check and fix corrupted system files which may be the cause of the issue. Please refer to the link.

    https://support.microsoft.com/en-ph/help/402652...

    1. Repair Upgrade.

    Follow the guide by Andre Da Costa.

    https://www.groovypost.com/howto/perform-repair...

    I hope this helps. Feel free to ask back any questions and keep me posted.

    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?

    0 comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more