Issue with PC shutting down unexpectedly while using MS Edge browser (Critical error: Kernel-Power)
Issue with PC shutting down unexpectedly while using MS Edge browser (Critical error: Kernel-Power)
Approximately once every hour (sometimes only a few minutes or occasionally half a day), the system restarts without reason. The only other instance this occurred was with Photoshop. There was no BSOD; after restarting, the system appeared to function normally. The sequence of errors in the system log is as follows:
Log Name: System
Source: Microsoft-Windows-Kernel-PnP
Date: 2023-11-29 12:55:08 AM
Event ID: 219
Task Category: (212)
Level: Warning
Keywords:
User: SYSTEM
Computer: Thinkpad_P16G2
Description:
The driver Driver\WUDFRd failed to load for the device ROOT\WINDOWSHELLOFACESOFTWAREDRIVER\0000.
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 2023-11-29 12:55:08 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Thinkpad_P16G2
Description:
The system restarted after a sudden shutdown. This issue might stem from the system becoming unresponsive, crashing, or losing power unexpectedly.
Log Name: System
Source: volmgr
Date: 2023-11-29 12:55:07 AM
Event ID: 162
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Thinkpad_P16G2
Description:
Dump file generation succeeded.
I’m completely puzzled about the cause. Please run diagnostics and let me know what to check. I’ve attached the event log for the period around the incident in case it contains useful information.
SystemLog
Thank you.
Disabled hardware acceleration in Microsoft Edge and changed power settings to performance. Expect results within a few hours if it fixes the issue. Since Edge was running in the background when Photoshop crashed, it might have been Edge that caused the crash. Other tasks like gaming haven’t led to crashes before.
Known issues with Edge hardware acceleration?
Machine Type: Lenovo Thinkpad P16 Gen 2 Laptop
CPU: Intel Core i7-13850HX
Video Card: NVIDIA RTX 4000 Ada
Before disabling hardware acceleration, the edge://gpu interface indicated:
Graphics Feature Status
=======================
* Canvas: Rendering via hardware
* Canvas out-of-process rasterization: Active
* Direct Rendering Display Compositor: Not used
* Compositing: Rendering via hardware
* Multiple Raster Threads: Active
* OpenGL: Supported
* Rasterization: Rendering via hardware
* Raw Draw: Not enabled
* Skia Graphite: Not active
* Video Decode: Rendering via hardware
* Video Encode: Rendering via hardware
* Vulkan: Not used
* WebGL: Rendering via hardware
* WebGL2: Rendering via hardware
* WebGPU: Rendering via hardware
You are experiencing a hardware-related issue involving a PCIe device. The log records multiple errors, including missing information and failed messages.
The system indicates that the necessary component for Event ID 1001 is either missing or corrupted on your machine. You may need to reinstall or repair it locally.
If the event happened on another machine, ensure the display details were saved with it.
Accompanying data includes a dump file and a message resource, though the message itself could not be located.
Even though those drivers weren't assisting, changing to the Studio Driver instead of Game Ready Driver fixed the issue. The Studio Driver tends to act oddly during gameplay; its temperature falls to 60C, power consumption reduces to 65W, and frame rates in games drop significantly. This led me to examine Card Settings and compare the differences between the 4000 ADA and the 4080 models. The ADA supports ECC memory, whereas the 4080 does not. When I disabled ECC in the NVIDIA Control Panel and returned to the RTX 4070 driver (546.17), the problems with Windows Reboots ceased and performance improved, reaching 80C with 130W draw. Nevertheless, games now crash every few hours, accompanied by specific error messages.
When changing Nvidia drivers and cards, it's best to use DDU to erase all previous driver traces and begin fresh. Then install the newest game-ready driver for the card you intend to use. If you switch cards again for testing, remember to use DDU to remove the driver for the other card.
Good tip.
I hadn't considered what might be left behind from the Studio Driver when switching back to the Game Ready driver. I'll try DDU.
At least the new issue is minor—crashing to Windows is just an annoyance, even if everything works fine otherwise.