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: