Question Updated Title: BSOD after upgrading Ryzen 5 3600 CPU

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Dec 4, 2019
I'm running with lastest bios. It's version code F50d.

Could it be because of bios. Maybe I should roll back previous F50a version and see if it will work.

Also I ran LatencyMon application. When running Winamp in background I've opened up Edge browser and music crippled for a second. When I checked out LatencyMon it came out like this:


(Insert Image section didn't work)
Dec 4, 2019
My PC frozen again and this time it even couldn't enter the bsod. I can't use my PC more than 30 minutes. Somethings seems teribbly wrong here.
Looking at your system specs, the red flag I immediately see is the RM PSU. How old is that? Is that the first version or the revised version. The originals were terrible PSUs that had weak capacitors sensitive to heat, compounded by the fact that they used a semi-passive design. The newer design is a little bit better but if it's old it will have enough ripple to break your CPU clocks, especially with a weaker, older motherboard (again aging caps).


This MOBO supports 3th gen Ryzens:

And "put your old CPU back in?" Are you making fun of me?
Your motherboard may technically support 3rd-gen but your particular sample may be too borderline to RELIABLY support 3rd-gen.

Put the old CPU in and see if all the problems go away. If they do, then you know with reasonable certainty that your suspects are either the new CPU being bad or the motherboard not being up to par as far as 3rd-gen is concerned.

AMD had to jump through many hoops to maintain backward compatibility with Zen 2. Some older motherboards falling short of working properly with them is to be expected and this may unfortunately be what you have run into.
Dec 4, 2019
Sorry. I'm really on edge right now. I better make a clean windows installation and see if problems go away. Right now I'm getting all kinds of bsods. "DPC_WATCHDOG_VIOLATION", "APC_INDEX_MISSMATCH" etc.
Sorry. I'm really on edge right now. I better make a clean windows installation and see if problems go away. Right now I'm getting all kinds of bsods. "DPC_WATCHDOG_VIOLATION", "APC_INDEX_MISSMATCH" etc.
Actually it would be pointless to install anything while your hardware is unstable, as it is likely to corrupt. You are better off making a boot drive with a working computer, and using that to stress test your problem computer.

Speaking of which, what are you using for storage?
Dec 4, 2019
Made a clean Win10 2004 installation, rolled back to previous F50a bios version and still nothings changed. I've swiched back to my previous R5 1600 CPU. I didn't get any blue screens so far but somethings still feels wrong. When I ran LatencyMon test, it gave a report like this: "
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:26:38 (h🇲🇲ss) on all processors.

OS version: Windows 10 , 10.0, build: 19041 (x64)
Hardware: AB350-Gaming, Gigabyte Technology Co., Ltd., AB350-Gaming-CF
CPU: AuthenticAMD AMD Ryzen 5 1600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16335 MB total

Reported CPU speed: 3194 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.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.

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): 1252,90
Average measured interrupt to process latency (µs): 6,901312

Highest measured interrupt to DPC latency (µs): 1136,40
Average measured interrupt to DPC latency (µs): 2,993526

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): 294,391985
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0,026782
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0,028389

ISR count (execution time <250 µs): 307267
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 109
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0

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): 1069,775830
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0,011158
Driver with highest DPC total execution time: Wdf01000.sys - Çekirdek Modu Sürücü Çatısı Çalıştırma Zamanı, Microsoft Corporation

Total time spent in DPCs (%) 0,042670

DPC count (execution time <250 µs): 745914
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 118
DPC count (execution time 1000-1999 µs): 1
DPC count (execution time 2000-3999 µs): 0
DPC count (execution time >=4000 µs): 0

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: msmpeng.exe

Total number of hard pagefaults 3485
Hard pagefault count of hardest hit process: 2277
Number of processes hit: 26

CPU 0 Interrupt cycle time (s): 41,197220
CPU 0 ISR highest execution time (µs): 294,391985
CPU 0 ISR total execution time (s): 5,406955
CPU 0 ISR count: 268150
CPU 0 DPC highest execution time (µs): 1069,775830
CPU 0 DPC total execution time (s): 7,206209
CPU 0 DPC count: 638165
CPU 1 Interrupt cycle time (s): 8,485160
CPU 1 ISR highest execution time (µs): 75,952411
CPU 1 ISR total execution time (s): 0,009981
CPU 1 ISR count: 5420
CPU 1 DPC highest execution time (µs): 235,762054
CPU 1 DPC total execution time (s): 0,145870
CPU 1 DPC count: 7689
CPU 2 Interrupt cycle time (s): 6,220530
CPU 2 ISR highest execution time (µs): 6,061365
CPU 2 ISR total execution time (s): 0,000035
CPU 2 ISR count: 6
CPU 2 DPC highest execution time (µs): 707,737007
CPU 2 DPC total execution time (s): 0,110660
CPU 2 DPC count: 16720
CPU 3 Interrupt cycle time (s): 5,686335
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): 233,097057
CPU 3 DPC total execution time (s): 0,013567
CPU 3 DPC count: 2024
CPU 4 Interrupt cycle time (s): 5,424165
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): 267,000626
CPU 4 DPC total execution time (s): 0,497791
CPU 4 DPC count: 53467
CPU 5 Interrupt cycle time (s): 5,080306
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): 236,824045
CPU 5 DPC total execution time (s): 0,011110
CPU 5 DPC count: 1751
CPU 6 Interrupt cycle time (s): 2,851714
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): 234,088917
CPU 6 DPC total execution time (s): 0,032996
CPU 6 DPC count: 6097
CPU 7 Interrupt cycle time (s): 2,254628
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): 198,993112
CPU 7 DPC total execution time (s): 0,006134
CPU 7 DPC count: 1185
CPU 8 Interrupt cycle time (s): 3,982890
CPU 8 ISR highest execution time (µs): 13,976205
CPU 8 ISR total execution time (s): 0,014629
CPU 8 ISR count: 19168
CPU 8 DPC highest execution time (µs): 251,170946
CPU 8 DPC total execution time (s): 0,082697
CPU 8 DPC count: 8701
CPU 9 Interrupt cycle time (s): 2,734408
CPU 9 ISR highest execution time (µs): 2,765185
CPU 9 ISR total execution time (s): 0,000406
CPU 9 ISR count: 451
CPU 9 DPC highest execution time (µs): 202,930495
CPU 9 DPC total execution time (s): 0,008770
CPU 9 DPC count: 1457
CPU 10 Interrupt cycle time (s): 3,367252
CPU 10 ISR highest execution time (µs): 4,157796
CPU 10 ISR total execution time (s): 0,001883
CPU 10 ISR count: 2321
CPU 10 DPC highest execution time (µs): 208,931747
CPU 10 DPC total execution time (s): 0,036232
CPU 10 DPC count: 4425
CPU 11 Interrupt cycle time (s): 3,021977
CPU 11 ISR highest execution time (µs): 16,460864
CPU 11 ISR total execution time (s): 0,013268
CPU 11 ISR count: 11860
CPU 11 DPC highest execution time (µs): 294,221666
CPU 11 DPC total execution time (s): 0,035332
CPU 11 DPC count: 4352

BTW I running my OS on my SSD.
Last edited: