Brand new install, same problems. Chrome/Brave shutdowns + random reboots of Windows

tormi

Member
Joined
Mar 14, 2025
Messages
4
Hi.
If anybody could take a look I would be very grateful. This started a few months ago, when Chrome and Brave browsers regularly would close, if my computer went to sleep. Everytime I woke it up the browsers would be closed.

A month ago I resintalled Windows 11 as I thought that would fix it, but still random crashes. Last night my computer rebooted twice, without any special activity on it.

Today I have had several crashes on browsers, and even Excel. I have never experienced anything like this. Only game I play is Dota2, and strangely 0 crashes happen while playing this game.

I think all requirements for help is in the Zip file. Any help GREATLY appreciated.
 
Solution
Kernel-Power Event ID 41 errors indicate that your system lost power unexpectedly, but by themselves they don't pinpoint whether it's due to driver conflicts or power delivery issues. Here are some steps you can take to further diagnose the problem:
• Run an Energy Report
Open an elevated Command Prompt and run the command “powercfg /energy” (this scans your system for power efficiency issues over about 60 seconds and saves an HTML report). This report can flag devices that are misbehaving or drawing unusual power, which might indicate power delivery problems.
• Examine the Reliability Monitor and Event Viewer
Use Windows’ Reliability Monitor (found in Control Panel under Security and Maintenance or by searching “Reliability Monitor”)...
Sort by date Sort by votes
Here is the attachment.

Even posting her crashes my browser...

PS: I can't see if my zip file was attached here... Tried 3 times. Images worked though.
 

Attachments

  • About.webp
    39.1 KB · Views: 0
  • Bench.webp
    26 KB · Views: 0
  • CPU.webp
    49.9 KB · Views: 0
  • Graphics.webp
    32.6 KB · Views: 0
  • Mainboard.webp
    37.9 KB · Views: 0
  • Memory.webp
    33.1 KB · Views: 0
  • SPD1.webp
    21.6 KB · Views: 0
  • SPD2.webp
    44.4 KB · Views: 0
  • SPD3.webp
    21.7 KB · Views: 0
  • SPD4.webp
    44.3 KB · Views: 0
Upvote 0 Downvote
Thanks for attaching the zip file, tormi. I'll take a close look at its contents for any error codes or logs that could reveal why your Chrome and Brave browsers (and even Excel) are closing when your PC wakes from sleep.
From similar cases on the forum, a few common culprits have emerged:
• BIOS/Driver Issues: Outdated BIOS or drivers—especially for your chipset or graphics—can cause instability during sleep/wake cycles. If you haven’t yet, double-check that your BIOS is fully updated and that you're running the latest drivers from your system or GPU manufacturer.
• Hardware Acceleration Conflicts: Both Chrome and Brave use hardware acceleration to boost performance, but this may lead to crashes if there’s a conflict with your current drivers or power management settings. Disabling hardware acceleration in the browser settings has helped some users stabilize similar issues.
• Power Settings and Fast Startup: Windows’ Fast Startup or certain power configurations can sometimes trigger abrupt shutdowns or reboots. Consider disabling Fast Startup and adjusting your advanced power settings (like hybrid sleep) to see if that improves stability.
• Event Logs & Kernel-Power Errors: Although you mentioned minimal logging, it’s worth checking Windows’ Event Viewer or Reliability Monitor for any Kernel-Power (Event ID 41) or related errors at the time of these crashes. These might point to issues with power delivery or driver conflicts.
I'll review the attached logs for any hints—such as repeated error entries or dump file details—that can further pinpoint the issue. If you notice any specific error messages or events in Event Viewer (or in the log file) that you think might be relevant, please let me know.
In the meantime, testing adjustments like updating your BIOS, updating key drivers, and disabling browser hardware acceleration might offer a quick win. Let’s see what your logs reveal and we can dive further from there.
— ChatGPT
 
Upvote 0 Downvote
I can see several Kernel-Power (Event ID 41) errors in Event Viewer. How can I find out if I have driver conflicts or power delivery problems?
 
Upvote 0 Downvote
Kernel-Power Event ID 41 errors indicate that your system lost power unexpectedly, but by themselves they don't pinpoint whether it's due to driver conflicts or power delivery issues. Here are some steps you can take to further diagnose the problem:
• Run an Energy Report
Open an elevated Command Prompt and run the command “powercfg /energy” (this scans your system for power efficiency issues over about 60 seconds and saves an HTML report). This report can flag devices that are misbehaving or drawing unusual power, which might indicate power delivery problems.
• Examine the Reliability Monitor and Event Viewer
Use Windows’ Reliability Monitor (found in Control Panel under Security and Maintenance or by searching “Reliability Monitor”) to see whether there are consistent warnings or error events before the Kernel-Power log. Often, errors related to device drivers or power management will appear just before a shutdown event. In Event Viewer, check for any driver-related errors or warnings that occur immediately prior to the Kernel-Power events.
• Check Device Manager
Open Device Manager and look for any devices marked with a yellow exclamation. These icons can indicate problematic drivers that might be causing instability.
• Analyze Mini-Dump Files
If your system is set to create minidump files during crashes, using a tool like BlueScreenView or WinDbg can help you identify if a specific driver is implicated in the crash. Sometimes, repeated mention of a particular driver module can point to a conflict or an out-of-date driver causing the issue.
• Driver Verifier and BIOS/Chipset Updates
Although more advanced—and use with caution—you can use the Driver Verifier tool to stress test non-Microsoft drivers. Make sure to have current BIOS and chipset drivers from your manufacturer, as outdated firmware can occasionally cause power management conflicts.
By gathering insights from these reports, you should be able to determine whether a driver or a power delivery anomaly is at play. Let us know what you find or if you need further guidance on any of these steps.
— ChatGPT
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.