Question BSOD issues

Dec 18, 2021
I keep getting BSODs and I'm feeling like I'm running out of options on how to fix it. I was having a lot of problems after initially upgrading my CPU, RAM, MOBO, and PSU but a lot of problems went away after I got rid of my old HDD and replaced it with the 2TB SSD listed below. About a month or two went by and now I still have BSOD issues but they are rarer. I have not been able to replicate them. A couple days ago I upgraded my GPU from a 1060 to a 3060 and re-installed the driver just to be safe to see if the old GPU was the issue (was 5 years old) and I just got another BSOD while watching youtube; a dpc watchdog violation. I'm at my wits end. Most BSODs are unexpected kernel traps. Only 2 parts that I can guess now are the older SSD or maybe I got bad RAM? RAM was new not used though. what else can I do?

minidumps (all but the one that just happened cuz I can't get the website to work) -

More info I just got - in event viewer I am seeing a lot of warnings labeled event 225, Kernel PnP that I haven't seen before.

My computer parts and peripherals - - -
CPU - Intel(R) Core(TM) i9-10850K CPU @ 3.60GHz 3.60 GHz (bought last fall)
GPU - Asus nividia 3060 12gb (new)
MOBO - asrock H507M Pro (bought last fall)
SSD model - samsung 870 QVO Sata III 2.5" SSD 2TB (MZ-77Q2T0B) (bought last fall)
SSD model - TEAM T253X2512G (little over 3 years old)
RAM - CORSAIR - VENGEANCE LPX 32GB (2 x 16GB) DDR4 3600 (PC4-28800) C18 1.35V (new)
PSU - Corsair RMX Series, RM750x, 750 Watt, 80+ Gold Certified, Fully Modular (bought last fall)
OS - windows 10

CPU cooler is just a basic cooler master fan

Mouse - logitech g604
Keyboard - razer blackwidow v2
Headset - razer kraken tournament edition with THX audio
Two monitors - a 144hz acer brand, 60hz asus brand (i can find specifics if needed)
Basic logitech speakers plugged into the green output hole
A CD/DVD player
Wacom drawing tablet (problems occurred before and after having this so don’t think its related)
Last edited:
Dec 18, 2021
Here is the most recent dmp after being put through windbg -
: kd> !analyze -v
  • *
  • Bugcheck Analysis *
  • *

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff807404fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:

  • *
  • *
  • Either you specified an unqualified symbol, or your debugger *
  • doesn't have full symbol information. Unqualified symbol *
  • resolution is turned off by default. Please either specify a *
  • fully qualified symbol module!symbolname, or enable resolution *
  • of unqualified symbols by typing ".symopt- 100". Note that *
  • enabling unqualified symbol resolution with network symbol *
  • server shares in the symbol path may cause the debugger to *
  • appear to hang for long periods of time when an incorrect *
  • symbol name is typed or the network symbol server is down. *
  • *
  • For some commands to work properly, your symbol path *
  • must point to .pdb files that have full type information. *
  • *
  • Certain .pdb files (such as the public OS symbols) do not *
  • contain the required information. Contact the group that *
  • provided you with these symbols if you need this command to *
  • work. *
  • *
  • Type referenced: TickPeriods *
  • *


Key : Analysis.CPU.mSec
Value: 2905

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 4590

Key : Analysis.Init.CPU.mSec
Value: 359

Key : Analysis.Init.Elapsed.mSec
Value: 9280

Key : Analysis.Memory.CommitPeak.Mb
Value: 90

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1

FILE_IN_CAB: 051122-4937-01.dmp




BUGCHECK_P3: fffff807404fb320



TRAP_FRAME: fffffa0a32791470 -- (.trap 0xfffffa0a32791470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffc30ac71923b0
rdx=ffffb281f49c0180 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8073fb61ffc rsp=fffffa0a32791600 rbp=fffffa0a32791a80
r8=ffffc30ac7f8c080 r9=0000000000000000 r10=ffffc30ac7f8c004
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
fffff8073fb61ffc 488b07 mov rax,qword ptr [rdi] ds:0000000000000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)



PROCESS_NAME: Razer Synapse Service.exe

ffffb281f49d9e18 fffff8073fc36f70 : 0000000000000133 0000000000000001 0000000000001e00 fffff807404fb320 : nt!KeBugCheckEx
ffffb281f49d9e20 fffff8073fa5f393 : 0000450f00426dba ffffb281f49c0180 0000000000000000 ffffb281f49c0180 : nt!KeAccumulateTicks+0x1d5380
ffffb281f49d9e80 fffff8073fa5ee7a : ffffc30ab1aea780 fffffa0a327914f0 0000000001550800 000000000197efc0 : nt!KeClockInterruptNotify+0x453
ffffb281f49d9f30 fffff8073fa2da15 : ffffc30ab1aea780 0000000000000000 0000000000000000 ffff8c0f18ac665f : nt!HalpTimerClockIpiRoutine+0x1a
ffffb281f49d9f60 fffff8073fbf97fa : fffffa0a327914f0 ffffc30ab1aea780 0000000001550868 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffb281f49d9fb0 fffff8073fbf9d67 : 000000003b90d1e3 000000003fe1860e 0000000000000000 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffa0a32791470 fffff8073fb61ffc : 000000000197efc0 0000000000000010 0000000000000001 fffffa0a32791a80 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffa0a32791600 fffff8073fa57e27 : ffffc30ac7192350 0000000000000000 ffffc30ab1402340 ffffc30a00000000 : nt!KxWaitForSpinLockAndAcquire+0x2c
fffffa0a32791630 fffff8073fa58b6e : ffffc30ab1ae1220 fffff807404538c0 0000000000000000 0000000000000001 : nt!IoRemoveIoCompletion+0x3e7
fffffa0a32791760 fffff8073fc096b5 : fffffa0a32791a18 0000000000000000 0000000000000000 ffffc30ac86789e0 : nt!NtWaitForWorkViaWorkerFactory+0x38e
fffffa0a32791990 00007ff9b8bf0794 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25
000000000197e898 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`b8bf0794

SYMBOL_NAME: nt!KeAccumulateTicks+1d5380


IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1682

STACK_COMMAND: .cxr; .ecxr ; kb


FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release


OSNAME: Windows 10

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup: MachineOwner
Mod Edit: Added huge log file to a spoiler to keep the forum page scrolling down.
Last edited by a moderator:


Hi, I ran the dump files through the debugger and got the following information: This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.
File information:0i1cs6.dmp (Apr 27 2022 - 10:23:42)
Probably caused by:memory_corruption (Process running at time of crash: csrss.exe)
Uptime:0 Day(s), 0 Hour(s), 14 Min(s), and 26 Sec(s)

File information:5me3eu.dmp (May 6 2022 - 10:56:11)
Probably caused by:memory_corruption (Process running at time of crash: svchost.exe)
Uptime:0 Day(s), 16 Hour(s), 43 Min(s), and 10 Sec(s)

File information:mte0nl.dmp (Apr 20 2022 - 14:01:45)
Probably caused by:memory_corruption (Process running at time of crash: GameOverlayUI.exe)
Uptime:2 Day(s), 4 Hour(s), 55 Min(s), and 10 Sec(s)

File information:q3xv2o.dmp (May 1 2022 - 18:57:36)
Probably caused by:memory_corruption (Process running at time of crash: System)
Uptime:0 Day(s), 0 Hour(s), 21 Min(s), and 03 Sec(s)

File information:wbc6cc.dmp (May 1 2022 - 18:36:11)
Probably caused by:memory_corruption (Process running at time of crash: steamwebhelper.exe)
Uptime:4 Day(s), 5 Hour(s), 23 Min(s), and 30 Sec(s)
Comment: The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)

Possible Motherboard page: Pro4/index.asp
There is a BIOS update available for your system. You are using version 1.5. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
Dec 18, 2021
For those curious - the above reply mentions that I had Intel Extreme Tuning Utility. I never used it for overclocking. I used it a couple months back to stress test the CPU in hopes to see if I could replicate a BSOD. It never did cause a BSOD while I was using it. I have now uninstalled it as I just simply don't use.