BSOD many times, Mostly hypervision error and soemtimes LMode exception not handled. Haven't been able to fix this.

Question

BSOD many times, Mostly hypervision error and soemtimes LMode exception not handled. Haven't been able to fix this.

Kaizer Mc 20

Here are my specs:

Installed RAM 16.0 GB (15.6 GB usable)

Graphics card NVIDIA GeForce RTX 4060 Laptop GPU (8 GB)

Intel(R) UHD Graphics (128 MB)

Storage 417 GB of 954 GB used

System type 64-bit operating system, x64-based processor

I am currently using a ROG laptop.

I have tried various solutions online including using the command prompt, the bitlocker, running my computer on safemode, installing latest NVIDIA drivers, using Armoury Crate and updating drivers, running an extended check and unplugging all my things.

My CPU temp sits at nearly 65%+ on idle. and my GPU sits around 40%+, which I think is abnormally higher than what its supposed to be. I have pulled drivers that have shown to be malfunctioning but I'm not sure how to fix them,

drivers shown to had error 219:

The driver \Driver\WUDFRd failed to load.

Device: HID\VID_0B05&PID_19B6&Col02\6&15ae9f2&0&0001

Status: 0xC0000365

The driver \Driver\WUDFRd failed to load.

Device: PCI\VEN_8086&DEV_A71D&SUBSYS_14D31043&REV_01\3&11583659&0&20

Status: 0xC0000365

The driver \Driver\WUDFRd failed to load.

Device: ROOT\DISPLAY\0000

Status: 0xC0000365

And I also have a minidump folder that I've placed in this google drive link to have access to.

https://drive.google.com/file/d/1G5JRvsxOOx6WOvRUWi_yaZIm1KMJwt7V/view?usp=drive_link

Please help me.

0 comments

2 answers

Your answer

Answer 1

DaveM121 937K Independent Advisor

All your minidump files indicate a driver associated to your Intel processor is causing your system to crash.

You indicate your CPU sits at 65%+ on idle, that should not be happening, your processor should idle at 0% - 5% on idle and this may be related to the system crashes.

Restart (not shut down) your system to flush out your ram and let your system idle and do not open any apps.

Open Task Manager, then select the Processes tab.

If your CPU is the idling at a high percentage, click the CPU column header so the arrow on that header points down.

Please provide a screenshot of that Processes tab.

Kaizer Mc 20 Reputation points

2026-10-04T08:13:45.45+00:00
I'd like to reitterate that it's not my CPU Usage that sits high, but my CPU temperature. It was shown through Armoury crate, but regardless here in th1e picture/screenshot.

I've also looked through Safe Mode again and have found multiple concerning exclamation marks, trying to update the drivers don't do anything...
DaveM121 937K Reputation points Independent Advisor

2026-10-04T08:19:38.8233333+00:00

Okay, so it is not 65% just 65°C your processor is at on idle, that is normal, that does not indicate any problems.

In Safe Mode, many of the main device drivers are not loaded, if you open Device Manager with Windows in normal Windows mode, do any of the device driver sections have an exclamation mark beside them, if so, please provide a screenshot of that window.
Kaizer Mc 20 Reputation points

2026-10-04T08:24:50.9366667+00:00

sorry for the trouble, none of them show exclaimation marks. But how would I go about solving the drivers issue afformentioned?
DaveM121 937K Reputation points Independent Advisor

2026-10-04T08:31:27.82+00:00

1

The Device ID's indicated in your original question are Asus drivers for the RGB lighting on your system, usually installed by either the Armory Crate or Asus Aura utility.

Temporarily uninstall that utility to test if your system is stable.

2

Also, because the minidump files all indicate a driver associated to your processor.

If you are overclocking your processor, disable that.

Then, go to the support page for your laptop on the Asus website to download and reinstall (not update) the version of Intel Chipset drivers and Intel Storage drivers they provide.
Kaizer Mc 20 Reputation points

2026-10-04T09:12:24.04+00:00

thanks for the steps, I've Uninstalled Armoury Crate but while I was figuring out how to reinstall instead of update my drivers, my computer encountered Hypercisoon bsod a number of times in a row again, causing me to get locked out of my computer for the next two hours. In the mean time, could I ask how to fully reinstall them and which drivers I need to uninstall to have Intel chip set software and Intel storage to replace? thank you for your patience
DaveM121 937K Reputation points Independent Advisor

2026-10-04T09:27:35.9166667+00:00

Usually you just need to go to the support page for your system on the manufacturers website to download the driver installers, then when you run the installer, you will have the option to Install/Repair/Uninstall the drivers, the best option is to uninstall the drivers, then run the installer again and use that to reinstall the drivers.

If you have any difficulty locating that support page, click your Start Button, then just type msinfo and press Enter, please provide a screenshot of the resulting System Information window.
Kaizer Mc 20 Reputation points

2026-10-04T11:25:45.8766667+00:00

Here is the screenshot..

I went to Asus's official website and installed this,

but it did not give me an option to reinstall/uninstall my drivers, but to install it only. This also shows up as "Updater" When I downlaoded it. Any help on this?
DaveM121 937K Reputation points Independent Advisor

2026-10-04T11:30:39.36+00:00

That is the correct driver you need to reinstall, if you have now done that, wait to see if your system is stable.
Kaizer Mc 20 Reputation points

2026-10-04T11:45:49.1233333+00:00

hihi, they don't give me the option to reinstall it and only update over existing drivers. I'm not sure which drivers im supposed to uninstall for these ones to take over?
DaveM121 937K Reputation points Independent Advisor

2026-10-04T11:48:22.7766667+00:00

Okay, then please use the option to update over the current drivers and wait to see if your system is stable.
Kaizer Mc 20 Reputation points

2026-10-04T12:28:09.9866667+00:00

comign with an update, I styill get BSODS and if not, slightly more often now(?) Here are the minidump files

unsure where i went wrong

https://drive.google.com/drive/folders/1RgDV1E1Jwt4zcAYBlKAKjK8_Xzb7dkV7?usp=drive_link
DaveM121 937K Reputation points Independent Advisor

2026-10-04T12:42:05.3166667+00:00

Two of those minidump files also indicate the driver (intelppm.sys) associated to your processor as the cause of the system crashes, the other two just indicate generic RAM corruption errors.

1

Before proceeding, create a System Restore point on your PC.

2

Click your Start Button, type regedit and hit Enter to open the Registry Editor.

Click View and make sure 'Address Bar' is turned on.

Paste this into the Address Bar at the top and hit Enter.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelppm

Right click the intelppm folder (key) on the left side and select the option to backup that key to a registry file.

On the right hand pane, double click the Start entry.

Change its Data Value from 3 to 4 and click OK to save that setting.

Then, restart (not shut down) your PC to apply the change.
Kaizer Mc 20 Reputation points

2026-10-04T12:57:25.2033333+00:00

sorry for all the questions, how do I backup the key to a registry file?
DaveM121 937K Reputation points Independent Advisor

2026-10-04T12:59:55.56+00:00

No problem at all, click the Export option on the right click menu to backup the intelppm key.
Kaizer Mc 20 Reputation points

2026-10-04T13:15:42.94+00:00

I've finished all your instructions! so far I havent had a BSOD, which happened so often during the time I was following these steps, (around 40 seconds after my laptop boots up for the 20th time) I will report back here if the BSOD happens again, but all in all thank you so much for your help :,,,,
Kaizer Mc 20 Reputation points

2026-10-05T08:29:53.7766667+00:00

hello again, my computer has ran into another Hypervisor erorr, but this time it is staying on the error screen whereas last time it almost immediately restarted. I've forced shut down my laptop, but when trying to turn it back on it only shows me a black screen, and my keyboard lights up for a while before it shut itself off. The logo doesn't pop up on start up either. Is this an entirely new issue I need to open a question for?
Kaizer Mc 20 Reputation points

2026-10-05T10:29:28.2233333+00:00

Here is the link to the drive with the minidump files, my laptop booted up after a few more attempts. From this startup i've noticed my system clock is now showing th ewrong time, not sure if its relevant at all though
Kaizer Mc 20 Reputation points

2026-10-05T10:31:22.8766667+00:00

https://drive.google.com/drive/folders/1pbrLoV_p5icXH8QqZnR0hoi_-imPzEfJ?usp=drive_link

Answer 2

Given the steps already tried, the next supported path is to focus on general stop-code isolation and hardware/driver checks.

Start in Safe Mode again and use it only for troubleshooting.
- Go to Settings > Update and Security > Recovery > Advanced startup.
- Select Troubleshoot > Advanced Options > Startup Settings > Restart.
- After restart, choose option 4, 5, or 6 for Safe Mode.
- Safe Mode loads only the minimum required drivers and services, which helps isolate whether a driver or startup component is involved.
Check Device Manager for failing devices or drivers.
- Right-click Start > Device Manager.
- Look for devices marked with an exclamation point (!).
- Open the device properties and review the driver details and events.
- Try Update driver first. If that does not help, disable or uninstall the affected device temporarily for testing.
Remove or roll back anything recently added or changed.
- Remove any recently added hardware.
- If crashes started after a driver, app, or update change, use System Restore or another recovery option.
Install Windows updates.
- Go to Start > Settings > Update & Security > Windows Update.
- Select Check for Windows updates.
- This is also the recommended path to receive the latest updates and drivers.
Check disk free space.
- Windows should have sufficient free space for swap files and system operations.
- A good target is 10% to 15% free space.
- The listed storage usage appears to leave enough space, so this is less likely the root cause.
Run memory diagnostics.
- In Control Panel, search for Memory.
- Select Diagnose your computer's memory problems.
- After the test, open Event Viewer and check the System log for MemoryDiagnostics-Results.
Check Event Viewer around the crash time.
- Look in the System log for critical errors that occurred at the same time as the BSOD.
- Focus on entries that identify a device, driver, or hardware-related failure.
Run manufacturer hardware diagnostics.
- Since the system is a ROG laptop and idle temperatures are unusually high, hardware diagnostics from the system manufacturer are relevant.
- Also confirm any recently installed hardware is compatible with the installed version of Windows.
If the issue points to graphics or timeout behavior, verify graphics software is current.
- For video timeout-related crashes, update the identified driver and confirm graphics-related software such as DirectX and OpenGL and any graphics-intensive apps are fully patched.
If the crashes continue, use crash-dump analysis.

Configure the PC to generate a complete memory dump.
Copy memory.dmp from the Windows directory to another PC.
Install Debugging Tools for Windows from the Windows SDK.
In WinDbg, set the symbol path to the Microsoft public symbol server: https://msdl.microsoft.com/download/symbols
Open the dump with Open Crash Dump and analyze it.

What the provided symptoms suggest from supported guidance:

Stop-code errors are commonly caused by third-party drivers, hardware, or related software.
Repeated crashes after already updating drivers make driver conflict, hardware diagnostics, memory testing, and dump analysis the strongest next steps.
The WUDFRd event entries alone do not identify the root cause in the provided material, so they should be treated as supporting clues rather than the confirmed cause.

If a recent change triggered the problem, System Restore is the most direct recovery step before considering a reset or reinstall.

References: