[SOLVED] - Bugcheck 0x0000007e, BSOD, and Event ID 41 (63) Kernel-Power issue (2024)

Hi, all.

(System specs are at the end of this message.)

I'm running into a seemingly random, yet consistent, BSOD issue that seems to be the result of a bugcheck. The most recent error I've received is:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80016e70e36, 0xfffff900c0fbddf8, 0xfffff900c0fbd630). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 83482fe2-5a39-43de-9752-4d6166d90c7e.

This results in the predictable critical error event ID 41 (63) Kernel-Power notification that "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

These BSODs only happen when I'm gaming, I'm pretty sure all of these BSODs have occurred while I was playing Assassin's Creed Valhalla... there might have been one when I was playing War Thunder weeks ago, but I can definitely say that the vast majority of times it was during Valhalla play. Initially, the BSOD would happen, my machine would reboot, and then it would act like nothing happened, other than the info showing in the Event Viewer. But otherwise the machine would seem to function as expected, until the next BSOD. I hardly ever got these sorts of BSODs, but in the last few weeks it's become much more frequent. (And I'm not aware of any major changes I've made on my end prior to these BSODs, other than Windows updates.)

My machine started acting even more oddly three days ago after I ran OCCT (v7.2.5) stress tests to see if the PSU was stable. (In my research of the bugchecks, it seems like it's usually power-related, so I wanted to see if it was my PSU.) Ran multiple OCCT tests for the full hour and everything passed. So it seemed like the PSU wasn't the culprit. However, after running those tests, I'm now unable to either put or let my machine go to sleep per usual. Now when it sleeps, the display powers off, but the RGB lighting remains on and the fans go to full speed, and I'm unable to wake it via the mouse or keyboard as usual. I have to push the power button on the case to shut it down. I can restart it without issue. I'm not sure if it's simply coincidental, but that particular issue only occurred after I used OCCT (and that was the first time I ever used it.)

Two days ago I did the following:

  1. Updated BIOS to the most recent (American Megatrends P7.30, dated 1/23/2018, from the ASRock site)
  2. Disabled the sleep function from the BIOS settings (so the fans don't go nuts when it tries to sleep)
  3. Fiddled around with the various power setting/profile options from within Windows (doesn't seem to make a difference which profile I'm using, etc.)
  4. Confirmed GPU drivers are the most recent (Nvidia GeForce 461.9)
  5. Ran the Intel Processor Diagnostic Tool 64-bit (no issues found, everything passed)

After I did all that, I only have two shut-down options (restart, shut down) in Windows as expected, since I disabled sleep from BIOS. I can hit restart and it does just that and everything is as expected. But when I hit shut down, the machine does what it did before when it was trying to sleep - display powers off, RGB lighting remains on, and the fans go to full power. Hmm.

The machine ran overnight as expected (which is fine, since I rarely ever power it off so backups and AV/AM scans can run in the wee hours of the night when I'm not on the machine). Everything was fine all yesterday morning. And then yesterday afternoon, I started playing Assassin's Creed Valhalla and initially it was fine; I bet I was playing for 60-90 mins without any issues. Then whammo. BSOD with the bugcheck code mentioned above. That's when I threw my hands in the air and decided I needed to ask for help from folks who are far more knowledgeable than I am. And now I'm here. [SOLVED] - Bugcheck 0x0000007e, BSOD, and Event ID 41 (63) Kernel-Power issue (1)

Thanks in advance for any help you can provide.

_
System Specs:
OS: Windows 10 Pro Version 20H2 (OS Build 19042.746)
Case: CoolerMaster HAF 932
Motherboard: ASRock ATX DDR4 FATAL1TY Z170 GAMING K4
CPU: Intel Core I7-6700 FC-LGA14C 3.40 GHz 8 M Processor Cache 4 LGA 1151 BX80662I76700
GPU: EVGA RTX 2080 XC (08G-P4-2182-KR)
SFX: Creative Sound Blaster ZX
Monitor: ASUS Swift PG278Q Gaming
CPU cooling: Only using fans (CPU and 5 other various case fans - not OCing, so temps have never been an issue)
RAM: G.SKILL 32GB (2 x 16GB) Ripjaws V Series DDR4 PC4-25600 3200MHz
PSU: EVGA SuperNOVA 850 G2 80+ GOLD, 850W
Primary SSD: Samsung 840 EVO 250GB
Storage SDD: Samsung 860 EVO 2TB
Optical 1: Pioneer BDR-206D 12x BD/DVD/CD Burner
Optical 2: Sony Optiarc AD-7261S CD/DVD Burner
Network card: None (using mobo’s integrated Killer E2400 Series LAN chipset)

[SOLVED] - Bugcheck 0x0000007e, BSOD, and Event ID 41 (63) Kernel-Power issue (2024)

FAQs

What is Windows kernel Power Error 41 63? ›

You can check if your system has overclocking enabled as it may cause Kernel-Power error 41 (63). To disable overclocking, follow the given steps: Reboot your Windows system and when it starts showing you the Windows logo on the screen, turn it off again using the Power key.

What is BSOD kernel error 41? ›

And the kernel power 41 error is often caused by an underpowered or failing power supply, but there are some other reasons such as an outdated driver. Sometimes the kernel power 41 error often causes a BSOD followed by the 0x8000400000000002 error code.

What is BSOD 0x0000007E Windows 10? ›

Ensure all your device drivers are up-to-date, as this could help resolve 0x0000007E errors. You can go to Settings > Windows update > Search for Update to update a driver. There you can see if there are any new updates for your computer's drivers. You can also check updates on the manufacturer's web page.

How do I fix kernel BSoD? ›

I survived a scary Blue Screen of Death, the dreaded Kernel Security Check Failure. Here's how.
  1. Boot into Safe Mode. ...
  2. Scan for Malware. ...
  3. Scan for Disk Corruption and Corrupt Files. ...
  4. Check Recent Updates, Software Installs and Drivers. ...
  5. Check Bluescreen View. ...
  6. Uninstall and Reinstall Graphics Driver (in my case)
Jan 20, 2024

How to fix kernel power problem? ›

Common causes of the Kernel-Power error include outdated Windows, enabled Windows fast startup, and faulty RAM or graphics card. Fix the error by updating Windows, disabling fast startup, reseating RAM and graphics card, testing for faulty PSU, and running CHKDSK and SFC.

Is a BSOD a kernel panic? ›

In Windows, kernel panic is typically characterized by the appearance of a BSOD error message stating that the system needs a restart.

What is event 41 kernel power windows 11? ›

The warning "The system has rebooted without cleanly shutting down first" is associated with the event 41 kernel power, which indicates that something unexpected occurred that prevented Windows from going off properly. The system could experience this error if it abruptly crashed, stopped responding, or lost power.

Should I be worried if I get a BSOD? ›

An occasional BSOD that you never see again could be harmless. However, regular blue screens can be problematic and frustrating because they may indicate a deeper malaise and force you to lose data upon every reboot.

How do I fix kernel mode? ›

Read on.
  1. Fix 1. Check RAM to Fix Unexpected Kernel Mode Trap Error.
  2. Fix 2. Troubleshoot Hardware Failures to Fix Unexpected Kernel Mode Trap Error.
  3. Fix 3. Check Windows to Update.
  4. Fix 4. Run CHKDSK or SFC Scan.
  5. Fix 5. Update or Uninstall Drivers.
  6. Fix 6. Disable Overclocking and Memory Caching.
  7. Fix 7. Update Firmware.
  8. Fix 8.
Jul 24, 2023

What is the kernel issue in Windows? ›

The “Kernel Security Check Failure” is caused by outdated or corrupted drivers, corrupted registry files, viruses, or faulty Windows updates. The error can be fixed by updating your drivers, running the PC in safe mode, checking the disk for errors, re-setting Windows, or reinstalling the Windows OS.

What is the Windows Live kernel error? ›

This error is often associated with your graphics card driver. It could also be due to hardware issues, such as problems with your GPU, memory, or hard disk.

References

Top Articles
Latest Posts
Article information

Author: Rubie Ullrich

Last Updated:

Views: 5983

Rating: 4.1 / 5 (52 voted)

Reviews: 91% of readers found this page helpful

Author information

Name: Rubie Ullrich

Birthday: 1998-02-02

Address: 743 Stoltenberg Center, Genovevaville, NJ 59925-3119

Phone: +2202978377583

Job: Administration Engineer

Hobby: Surfing, Sailing, Listening to music, Web surfing, Kitesurfing, Geocaching, Backpacking

Introduction: My name is Rubie Ullrich, I am a enthusiastic, perfect, tender, vivacious, talented, famous, delightful person who loves writing and wants to share my knowledge and understanding with you.