[SOLVED] Windows 10 BSOD problem

Rush12049

Reputable
Oct 23, 2014
3
0
4,510
My PC seems to bluescreen every few days at random. Usually if I leave it at the desktop, or even leave it on the browser and don't touch it for a period of time. I ran MemTest86 4 passes, no memory issues, although from what I have read about, seems bad RAM causes it. Any ideas what might be causing it? Also all drivers are up to date. The system never crashes when I am playing games though. Been dealing with BSOD issues ever since I reinstalled Windows on my new SSD last month. Ran perfectly fine on my old Samsuing SSD, never had crashes.

Attached is copy of the minidumps: https://filebin.net/q902j4u2szxu4y1q


PC Specs are as follow:

Asus X370 Crosshair VI Hero

Ryzen 3700X

EVGA SuperNOVA 750 G+


Crucial 1TB MX500

Crucial Ballistix Sport 16gb 3200 DDR4

MSI R9 290 Gaming 4G
 
Solution
091019-6578-01

DPC_WATCHDOG_VIOLATION (133)

Arg1: 0000000000000001

PROCESS_NAME: EncoderServer

MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe

OSBUILD: 18362
OSSERVICEPACK: 329

=============================

091119-6171-01

IRQL_NOT_LESS_OR_EQUAL (a)

Arg1: fffff80700140009, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :

PROCESS_NAME: System

MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe

OSBUILD: 18362
OSSERVICEPACK: 356

============================

091119-6250-01

IRQL_NOT_LESS_OR_EQUAL (a)

Arg1: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :

PROCESS_NAME: SecurityHealth

MODULE_NAME: nt
IMAGE_NAME: memory_corruption...
091019-6578-01

DPC_WATCHDOG_VIOLATION (133)

Arg1: 0000000000000001

PROCESS_NAME: EncoderServer

MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe

OSBUILD: 18362
OSSERVICEPACK: 329

=============================

091119-6171-01

IRQL_NOT_LESS_OR_EQUAL (a)

Arg1: fffff80700140009, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :

PROCESS_NAME: System

MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe

OSBUILD: 18362
OSSERVICEPACK: 356

============================

091119-6250-01

IRQL_NOT_LESS_OR_EQUAL (a)

Arg1: 00000000000000b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :

PROCESS_NAME: SecurityHealth

MODULE_NAME: nt
IMAGE_NAME: memory_corruption

==============================

091119-6078-01

INVALID_PROCESS_DETACH_ATTEMPT (6)

Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

PROCESS_NAME: svchost.exe

MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe

==============================

091119-6703-01

APC_INDEX_MISMATCH (1)

Arg1: 00000000778b1cbc, Address of system call function or worker routine
Arg2: 0000000000000000, Thread->ApcStateIndex
Arg3: 0000000000000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: fffff98b4be6fb80, Call type (0 - system call, 1 - worker routine)

PROCESS_NAME: Steam.exe

MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe

------------------------------------------------------------------------------------

BIOS_VERSION: 7403
BIOS_DATE: 08/20/2019

-----------------------------------------------------------------------------------

amdgpio2.sys.....................................May 17 2019
amdgpio3.sys.....................................Mar 14 2016
AMDPCIDev.sys.............................Jul 24 2019
amdpsp.sys........................................Jun 19 2019
AMDRyzenMasterDriver.sys.....May 28 2019
AtihdWT6.sys..................................Nov 16 2017
atikmdag.sys.....................................Sep 3 2019
atikmpag.sys.....................................Sep 3 2019
e1r68x64.sys...................................May 9 2019
Netwbw02.sys................................Apr 29 2019

RTCore64.sys..................................Sep 30 2016 (Afterburner ?)
RTKVHD64.sys..............................Jan 2 2018

dc1-controller.sys (xbox driver ? )
File version: 1.0.0.1

unloaded:
xinputhid.sys (xbox controller)
MbamElam.sys (malwarebytes ? )
 
Solution
Additional info for others to possibly help:
Memory: CRUCIAL BLS8G4D32AESTK

Not on the QVL, but if the system was stable prior to that, would think it would be a low priority.

Some things to try 1st:

Drop clocks to stock
Unload Afterburner if running

Is the computer sleeping after a set number of minutes and crashing upon waking? Try disabling the hibernation system


I'm sure other users will chime in. LOTS of experienced people here, and always a great learning oppurtunity
 

TRENDING THREADS