My PC keeps crashing, The previous system shutdown was unexpected

Hi Ali,

My name is Igor, I have 12 Microsoft MVP awards. It's a pleasure for me to help others and I'll do all my best to help you. I'm sorry you have a problems.

Kernel-Power 41 (63) error mostly means the problem with power supplying. It may mean problems with power management in BIOS or motherboard too.

You may try to turn off all CPU power saving modes in BIOS (different C states) to check if the problem is in motherboard.

See some details at https://docs.microsoft.com/en-us/windows/client...

I got the replacement. Same thing. Seems to be an issue with AMD drivers. I am experimenting with shutting of HPET from Device manager and setting a minimum clock of 1001mhz instead of 0. As well as checking out some other fixes. Hopefully they fix this in the future since it seems to be WINDOWS RELATED ISSUE where windows like to mess around with the game drivers and pcie power draw and clock speed.
Disabling game mode as well, as well as game driver. R6 seems to be fine after this but Valorant is still experiencing severe issues with stutters.

Again, my mother board is a Asus Prime B450-M A

Running a EVGA GOLD 700W PSU

Ryzen 5 2600

RX 6700 XT

16GB RAM (Vengeance LPX) [ I removed the other 16 RGB versions thinking that this may fix this]

ADATA SSD

SEAGATE SSD

---

Still UNSOLVED . Even contacted AMD and no solution was given yet. I'll keep you guys posted. Thank you so much for your timely response, I really appreciate it.

I ran this software and after a little over 38 mins of testing it said:

_________________________________________________________________________________________________________

CONCLUSION

_________________________________________________________________________________________________________

Your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.

LatencyMon has been analyzing your system for 0:38:22 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: COTTONCANDY

OS version: Windows 11, 10.0, version 2009, build: 22000 (x64)

Hardware: Butt Cheeks, Butt Cheeks

BIOS: 2807

CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor

Logical processors: 12

Processor groups: 1

Processor group size: 12

RAM: 16297 MB total

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed (WMI): 3850 MHz

Reported CPU speed (registry): 3850 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________

MEASURED INTERRUPT TO USER PROCESS LATENCIES

_________________________________________________________________________________________________________

The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 1143.30

Average measured interrupt to process latency (µs): 6.401422

Highest measured interrupt to DPC latency (µs): 1137.30

Average measured interrupt to DPC latency (µs): 3.389032

_________________________________________________________________________________________________________

REPORTED ISRs

_________________________________________________________________________________________________________

Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 217.710130

Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.005648

Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.005661

ISR count (execution time <250 µs): 1645523

ISR count (execution time 250-500 µs): 0

ISR count (execution time 500-1000 µs): 0

ISR count (execution time 1000-2000 µs): 0

ISR count (execution time 2000-4000 µs): 0

ISR count (execution time >=4000 µs): 0

_________________________________________________________________________________________________________

REPORTED DPCs

_________________________________________________________________________________________________________

DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 1709.749870

Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total DPC routine time (%): 0.057787

Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.105669

DPC count (execution time <250 µs): 3681356

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-10000 µs): 101

DPC count (execution time 1000-2000 µs): 8

DPC count (execution time 2000-4000 µs): 0

DPC count (execution time >=4000 µs): 0

_________________________________________________________________________________________________________

REPORTED HARD PAGEFAULTS

_________________________________________________________________________________________________________

Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: tiworker.exe

Total number of hard pagefaults 162489

Hard pagefault count of hardest hit process: 94201

Number of processes hit: 91

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 101.714886

CPU 0 ISR highest execution time (µs): 217.710130

CPU 0 ISR total execution time (s): 1.240517

CPU 0 ISR count: 1185678

CPU 0 DPC highest execution time (µs): 1709.749870

CPU 0 DPC total execution time (s): 25.950312

CPU 0 DPC count: 3172624

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 10.082982

CPU 1 ISR highest execution time (µs): 17.250130

CPU 1 ISR total execution time (s): 0.003652

CPU 1 ISR count: 3469

CPU 1 DPC highest execution time (µs): 272.990130

CPU 1 DPC total execution time (s): 0.289533

CPU 1 DPC count: 41987

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 11.969625

CPU 2 ISR highest execution time (µs): 0.0

CPU 2 ISR total execution time (s): 0.0

CPU 2 ISR count: 0

CPU 2 DPC highest execution time (µs): 279.020

CPU 2 DPC total execution time (s): 0.604467

CPU 2 DPC count: 86122

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 8.509227

CPU 3 ISR highest execution time (µs): 0.0

CPU 3 ISR total execution time (s): 0.0

CPU 3 ISR count: 0

CPU 3 DPC highest execution time (µs): 46.160

CPU 3 DPC total execution time (s): 0.031293

CPU 3 DPC count: 5667

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 9.868295

CPU 4 ISR highest execution time (µs): 0.0

CPU 4 ISR total execution time (s): 0.0

CPU 4 ISR count: 0

CPU 4 DPC highest execution time (µs): 198.680

CPU 4 DPC total execution time (s): 0.263256

CPU 4 DPC count: 40121

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 7.785921

CPU 5 ISR highest execution time (µs): 0.0

CPU 5 ISR total execution time (s): 0.0

CPU 5 ISR count: 0

CPU 5 DPC highest execution time (µs): 278.109870

CPU 5 DPC total execution time (s): 0.058229

CPU 5 DPC count: 9789

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 10.271866

CPU 6 ISR highest execution time (µs): 0.0

CPU 6 ISR total execution time (s): 0.0

CPU 6 ISR count: 0

CPU 6 DPC highest execution time (µs): 252.040

CPU 6 DPC total execution time (s): 0.976319

CPU 6 DPC count: 166352

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 6.286838

CPU 7 ISR highest execution time (µs): 0.0

CPU 7 ISR total execution time (s): 0.0

CPU 7 ISR count: 0

CPU 7 DPC highest execution time (µs): 53.170130

CPU 7 DPC total execution time (s): 0.054132

CPU 7 DPC count: 8889

_________________________________________________________________________________________________________

CPU 8 Interrupt cycle time (s): 9.870680

CPU 8 ISR highest execution time (µs): 13.420

CPU 8 ISR total execution time (s): 0.226098

CPU 8 ISR count: 342763

CPU 8 DPC highest execution time (µs): 269.520

CPU 8 DPC total execution time (s): 0.522787

CPU 8 DPC count: 84568

_________________________________________________________________________________________________________

CPU 9 Interrupt cycle time (s): 6.096769

CPU 9 ISR highest execution time (µs): 14.310130

CPU 9 ISR total execution time (s): 0.007627

CPU 9 ISR count: 8803

CPU 9 DPC highest execution time (µs): 58.520

CPU 9 DPC total execution time (s): 0.066234

CPU 9 DPC count: 10317

_________________________________________________________________________________________________________

CPU 10 Interrupt cycle time (s): 8.042638

CPU 10 ISR highest execution time (µs): 13.950130

CPU 10 ISR total execution time (s): 0.024696

CPU 10 ISR count: 32143

CPU 10 DPC highest execution time (µs): 79.520

CPU 10 DPC total execution time (s): 0.256942

CPU 10 DPC count: 39299

_________________________________________________________________________________________________________

CPU 11 Interrupt cycle time (s): 8.752199

CPU 11 ISR highest execution time (µs): 14.989870

CPU 11 ISR total execution time (s): 0.061699

CPU 11 ISR count: 72667

CPU 11 DPC highest execution time (µs): 266.30

CPU 11 DPC total execution time (s): 0.124640

CPU 11 DPC count: 15730

_________________________________________________________________________________________________________

I removed 2 of my sticks of ram, since they were a different model and had different timings. That fixed the stuttering, however after I set them up to 3200mhz (They were previously 2133mhz to no interfere with the timing of the other 16gbs) [Total 32gbs, 16 LPX vengeance and the other 16 Vengeance rgb model]

Now it crashed randomly while I was benchmarking the rig on FiveM after various Dxdiag driver errors like DXGI_ERROR_DEVICE_REMOVED

That error was patched up with deleting the cache, but I have a suspicion that something with the GPU drivers isn't adding up

Here are the new Admin Events and msinfo32:

Msinfo32:

https://1drv.ms/u/s!Ar5BlOrWiK6SgQXDpMrM-OHUYXY4?e=HMkylI

Administrative Events: https://1drv.ms/u/s!Ar5BlOrWiK6SgQOP7__6ItA33l5k?e=eASqTC(Just in case these are important) ||

               V

LocaleMetaData:

https://1drv.ms/u/s!Ar5BlOrWiK6SgQLW-lZIuduxISAw?e=xVwdjW

Application Events: https://1drv.ms/u/s!Ar5BlOrWiK6SgQjHfSN4qJtnTV5x?e=ZAwb60

Greetings.

I had been having blue error screen issue which often restarted the Asus tuf gaming a15 laptop at random times in my possession currently. Eventually I had to contact Microsoft support on their official website for help. Some of the earlier suggestion given to me did not fully solve my issue. Latter on, I was directed to check the 'device manager' in Windows control panel for missed potential problem. There I found some of the associated component with the Asus laptop appeared to be missing their respective drivers counterpart. Hopefully after installing the requisite drivers my issue will be solved.

Just wanted to share my experience on crashed operating system related issue in this forum.

Thank you and Kind Regards, Derik I Salem