Windows 10: Multiple IRQL_NOT_LESS_EQUAL & Hypervisor BSODs

Hi Team,


I've been getting multiple BSODs per day for some weird reason. I have a Dell XPS 9370. Dell customer support has run a hardware scan and made sure that all drivers and BIOS were up to date.


The crashes happen whether I'm browsing the internet or looking at outlook. Nothing weird installed on my laptop either.


Thanks

:)

 

HYPERVISOR ERROR BSOD

Hi, today I've been getting repeated BSODs with the HYPERVISOR error and one time the SYSTEM_SERVICE_EXCEPTION error. I've tried doing a clean reinstall of graphics drivers. I can't find much online so I'd really appreciate some help.

Thanks

 

IRQL_NOT_LESS_EQUAL ndis.sys error

Several different possibilities from your description:
- other, network related programs/drivers, are interfering with the networking
- hardware problems
- antivirus/antimalware programs conflicting with networking
- other stuff (just a catch-all

I'd suggest trying to run Driver Verifier according to these instructions: Enable and Disable Driver Verifier in Windows 10 Recurring IRQL_NOT_LESS_EQUAL errors are mostly found to be software related, so Driver Verifier is the place to start. Please let it crash the system (that's what it does) and ensure that there is a memory dump that's been created (in C:\Windows\Minidump - they're named with a date in the filename).
Then, zip it up and upload it with your next post.

- - - Updated - - -

Asus M5A97 R2.0 motherboard BIOS dates from 2009.
I strongly suggest:
- installing the latest available version for your system that's available from the Asus support website for your model.
- checking with Asus to see if they support W10 on this board.

The Realtek driver is present in the stack text just before the ndis.sys error causes the BSOD.
As you've recently updated this driver, my next suggestion (after Driver Verifier) is to try a Clean Boot according to these instructions: Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts

If the clean boot stops the BSOD's - then it's a simple matter of re-enabling things a few-at-a-time until you discover the faulting entry. If it doesn't stop the BSOD's, then we'll move on to other troubleshooting.

 

Multiple BSOD

Bug Check 0x1A: MEMORY_MANAGEMENT

Bug Check 0x1A MEMORY_MANAGEMENT - Windows drivers

MEMORY_MANAGEMENT BSODs, accompanied by occasional app crashes/GPUTDR.

MEMORY_MANAGEMENT BSODs, accompanied by occasional app crashes/GPUTDR.

The relevant Parameter appears to be 0x41284 which means, A PTE or the working set list is corrupted, which in itself means nothing to most of us poor Windows users. I still wonder if this is not just bad RAM?

Is it possible to remove one stick of RAM for testing purposes and then test all sticks one at a time (that's is you have multiple sticks of RAM, otherwise it is a daft suggestion on my part).