Question Bsod software or hardware

Jul 18, 2020
Recently over the last week I've had more bsod erros than I ever had in 5 years of owning a pc. I've reinstalled windows fresh, note it's on an hdd not ssd, I usually get these blue screen here are the dumps The thing is i don't know wether is hardware or software as when I'm in safe mode with networking on it never bsod but when I'm in normal it doesn't go 10 minutes before bsod , my specs are ryzen 35600 Rtx 2060 super 500w plus 80 evga psu 16gb ddr4 2400mhz 4x4 MSI b350 mortar artic If anyone has a fix for this that would be a life saver as this is rendering my PC unusable but I want to be sure that's it a software issue before I start working out for some hardware thanks.


I hope I got the right dumps. The power just went out and PC rebooted. Dumps were still on my desktop after I booted back up and this tab re-opened.

I ran the dump files through the debugger and got the following information:

File information:071820-23859-01.dmp (Jul 18 2020 - 07:51:14)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 0 Hour(s), 23 Min(s), and 25 Sec(s)

File information:071720-27703-01.dmp (Jul 17 2020 - 16:56:06)
Probably caused by:memory_corruption (Process: chrome.exe)
Uptime:0 Day(s), 0 Hour(s), 14 Min(s), and 23 Sec(s)

Comment: The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)

Possible Motherboard page:
You have the latest BIOS already installed.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.


Win 10 Master
Chrome crashed twice... and that 2nd error makes me think that the problem is internet drivers.

What Wifi card are you using?
May 28 2015 - netr28ux.sys - Ralink Wireless Adapter driver
those aren't win 10 drivers, and hopefully we can find newer ones.

your ethernet drivers aren't bad although there are newer
May 24 2019 - rt640x64.sys - Realtek NICDRV 8169 PCIe GBE Family Controller driver


Jun 5, 2017
For the DPC crash we'll need a kernel dump, it contains far too little information to track down any drivers causing it.

Upload the file C:\Windows\MEMORY.dmp to easyupload and post a share link please.

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: fffff80243cfa318, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding the cumulative timeout
Arg4: 0000000000000000

3: kd> .formats 0000000000001e00
Evaluate expression:
  Hex:     00000000`00001e00
  Decimal: 7680
  Octal:   0000000000000000017000
  Binary:  00000000 00000000 00000000 00000000 00000000 00000000 00011110 00000000
  Chars:   ........
  Time:    Thu Jan  1 03:08:00 1970
  Float:   low 1.0762e-041 high 0
  Double:  3.79442e-320

3: kd> .formats 0000000000000001
Evaluate expression:
  Hex:     00000000`00000001
  Decimal: 1
  Octal:   0000000000000000000001
  Binary:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000001
  Chars:   ........
  Time:    Thu Jan  1 01:00:01 1970
  Float:   low 1.4013e-045 high 0
  Double:  4.94066e-324

3: kd> .formats 0000000000000002
Evaluate expression:
  Hex:     00000000`00000002
  Decimal: 2
  Octal:   0000000000000000000002
  Binary:  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000010
  Chars:   ........
  Time:    Thu Jan  1 01:00:02 1970
  Float:   low 2.8026e-045 high 0
  Double:  9.88131e-324
If you look at 'Time' you can see in the latter 2 .formats that each increase in the parameter given is equivalent to 1 second. The first .formats shows that the DPC watchdog period was about 3 minutes long, practically that means multiple drivers (or at least DPCs) are involved which is impossible to investigate in a minidump.