Question BSOD/Full Restart during heavy gaming: Event ID 41 BugcheckCode 292

chrisstang

Honorable
May 18, 2017
2
0
10,510
I've been running into my computer blue screening/power cycling while in heavy gaming. Sometimes this occurs instantly while loading into a game, sometimes 30 minutes in, and sometimes some game assets don't even load properly.

I've uploaded the mini dump here: https://www.mediafire.com/file/mbvpgzpo2c1levt/011924-19468-01.dmp/file

After a BSOD I found this in my system event log:
  • * Event 41, Kernel Power
  • * EventData
  • * BugcheckCode 292
  • * BugcheckParameter1 0x10
  • * BugcheckParameter2 0x0
  • * BugcheckParameter3 0x0
  • * BugcheckParameter4 0x0
  • * SleepInProgress 0
  • * PowerButtonTimestamp 0
  • * BootAppStatus 0
  • * Checkpoint 0
  • * ConnectedStandbyInProgress false
  • * SystemSleepTransitionsToOn 0
  • * CsEntryScenarioInstanceId 0
  • * BugcheckInfoFromEFI true
  • * CheckpointStatus 0
  • * CsEntryScenarioInstanceIdV2 0
  • * LongPowerButtonPressDetected false
I recently replaced my CPU and RAM thinking that was the root of the problem but it's still happening. I've tried lower RAM speeds and have also re-installed windows, and gotten a new GPU. The only thing left to replace is my MOBO/Storage!

My current rig is:
  • * Intel i7-9900k
  • * Gigabyte XTreme 3080 Ti
  • * 4x8GB 3200Mhz Trident GSkill Ram
  • * Z390 Asus Maximus XI Formula
  • * 2x NVMes1x SSD1x HDD
Any help would be very much appreciated it. I can't do much gaming while this is ongoing.
 

zinkles

Commendable
Aug 24, 2022
953
265
1,340
what about your power supply? how old is it and what model it is? I think you're not paying attention to it much, thus forgetting to check if it can even deliver enough power in the first place.

attaching a pic of the PSU (upload to imgur.com and link it here) is better.
 

ubuysa

Distinguished
If you recently replaced your CPU are you certain that you pasted it properly? Your symptoms can most easily be explained by an overheating CPU. Run a temperature monitoring tool (like HWMonitor) and post the CPU temps (all cores) both at idle and at maximum load.

The one dump you uploaded (bugcheck 0x3D) fails with an exception code 0f 0xC000001D. That indicates an attempt to execute an illegal instruction. The trap frame shows that this is because the instruction pointer (the RIP register) is misaligned...
Code:
1: kd> .trap ffff8300`2472f840
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc90619106820 rbx=0000000000000000 rcx=00000000c4000000
rdx=ffffc906191060e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8033326b101 rsp=ffff83002472f9d0 rbp=ffff83002472fa80
 r8=0000000000000028  r9=ffffffffffffff00 r10=0000000000001dca
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
nt!KiBeginThreadAccountingPeriod+0x1632f1:
fffff803`3326b101 ff              ???
This could be the result of overheating, as above, but it could also be flaky RAM or even a flaky CPU.

It's thus important to eliminate overheating before we look elsewhere, so please post those HWMonitor temps.
 
Last edited:
Feb 25, 2024
6
0
10
I have been having an identical crash to the one posted above, both in terms of characteristics (anywhere from loading in to a game to a few minutes later) and a perfectly identical event log error. I've read from others having similar issues that some people have been able to fix it by deleting duplicate copies of Windows GameInput (which I did), but I am still experiencing issues.
Temps never reach above 80 C and my hardware has been running flawlessly with heavy game loads for a few years.
I also ran memtest, but after checking all available memory it has found zero errors.
I've upgraded every driver I can think of, dropped my memory to 2666mHz, but the error persists.
 

Recks214

Distinguished
Aug 11, 2014
12
0
18,510
The fact you've replaced CPU, RAM and got a new GPU helps narrow this down.

PSU is a likely culprit, I've had a similar issue. You can confirm this by getting OCCT and running a PSU test

MOBO can also be the cause but motherboards usually don't get damaged too often, but they can happen.