Windows 10 BSOD and I can't figure if it's hardware, driver, or third party software

  • Thread starter Thread starter AlexandreSeverino
  • Start date Start date
A

AlexandreSeverino

I have recently upgraded my computer.


My graphics card was working flawlessly until I upgrade the rest (motherboard, ram, and CPU).


I have already updated all the drivers I could find, and have run the Windows memory check 2 passes.


My hardware is as follow:


CPU: AMD Ryzen 7 3800X, 3900 Mhz

GPU: Geforce RTX 2060

RAM: DDR4 G Skill Flare X 2x8GB
Board: Gigabyte GA-AB350M-DS3H V2

PSU: Corsair VS 550


Windows Version: 10.0.18362 Build 18362


I'm getting BSOD every day at least once.


The file dump gives me this info:


*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



WHEA_UNCORRECTABLE_ERROR (124)

A fatal hardware error has occurred. Parameter 1 identifies the type of error

source that reported the error. Parameter 2 holds the address of the

WHEA_ERROR_RECORD structure that describes the error conditon.

Arguments:

Arg1: 0000000000000004, PCI Express Error

Arg2: ffffe68b5f12a038, Address of the WHEA_ERROR_RECORD structure.

Arg3: 0000000000000000

Arg4: 0000000000000000



Debugging Details:

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





BUGCHECK_STR: 0x124_AuthenticAMD



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: CODE_CORRUPTION



PROCESS_NAME: audiodg.exe



CURRENT_IRQL: b



ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre



STACK_TEXT:

fffff802`16098ce8 fffff802`135a4fe8 : 00000000`00000124 00000000`00000004 ffffe68b`5f12a038 00000000`00000000 : nt!KeBugCheckEx

fffff802`16098cf0 fffff802`143a1920 : ffffe68b`5f193800 00000000`00000000 ffffe68b`5f12a038 00000000`00000000 : hal!HalBugCheckSystem+0xd8

fffff802`16098d30 fffff802`13940952 : ffffe68b`5f193800 fffff802`16098db9 00000000`00000000 ffffe68b`5f12a038 : PSHED!PshedBugCheckSystem+0x10

fffff802`16098d60 fffff802`14ace474 : 00000000`00000000 00000000`00000000 ffffe68b`5f1941b0 ffffe68b`5f129010 : nt!WheaReportHwError+0x382

fffff802`16098e20 fffff802`14acebf2 : ffffaf01`d2503a00 fffff802`16098ec0 ffffaf01`d2503ab0 fffff802`16098ee0 : pci!ExpressRootPortAerInterruptRoutine+0x270

fffff802`16098e80 fffff802`14aceca9 : ffffaf01`d2503a00 00000000`00000001 ffff0138`68246259 00006d59`f59cd2d0 : pci!ExpressRootPortInterruptRoutine+0x22

fffff802`16098ee0 fffff802`13714081 : 00006d59`f59d3894 fffff802`0d583180 00000000`00000286 fffff802`135601e1 : pci!ExpressRootPortMessageRoutine+0x9

fffff802`16098f10 fffff802`13602a25 : ffff8401`4243e240 fffff802`135cc090 fffff802`0d583180 fffff802`13602a25 : nt!KiInterruptMessageDispatch+0x11

fffff802`16098f40 fffff802`137c2cff : ffff8401`4243e240 ffffaf01`d2503a00 fffff802`234b4df8 ffffaf01`d2503a00 : nt!KiCallInterruptServiceRoutine+0xa5

fffff802`16098f90 fffff802`137c2fc7 : ffffe68b`7a3ca0c0 ffff8401`4243e240 fffff802`135cbfe0 ffff8401`4243e2b9 : nt!KiInterruptSubDispatch+0x11f

ffff8401`4243e1c0 fffff802`212b4476 : 00000000`00000000 0000ffff`f802212b ffff9efa`64c00000 fffff802`212b442d : nt!KiInterruptDispatch+0x37

ffff8401`4243e350 00000000`00000000 : 0000ffff`f802212b ffff9efa`64c00000 fffff802`212b442d ffffe68b`6e3fdbf0 : nvhda64v+0x4476





STACK_COMMAND: kb



CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase

ffff96c12d443f99-ffff96c12d443f9e 6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49

[ ff 15 11 28 1a 00:e8 02 13 21 00 90 ]

ffff96c12d444009-ffff96c12d44400a 2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x70)

[ 48 ff:4c 8b ]

ffff96c12d444010-ffff96c12d444013 4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)

[ 0f 1f 44 00:e8 0b 14 21 ]

ffff96c12d445195-ffff96c12d445196 2 bytes - win32kbase!GreSfmDwmShutdown+35 (+0x1185)

[ 48 ff:4c 8b ]

ffff96c12d44519c-ffff96c12d44519f 4 bytes - win32kbase!GreSfmDwmShutdown+3c (+0x07)

[ 0f 1f 44 00:e8 7f 02 21 ]

ffff96c12d4451a5-ffff96c12d4451a6 2 bytes - win32kbase!GreSfmDwmShutdown+45 (+0x09)

[ 48 ff:4c 8b ]

ffff96c12d4451ac-ffff96c12d4451af 4 bytes - win32kbase!GreSfmDwmShutdown+4c (+0x07)

[ 0f 1f 44 00:e8 6f 02 21 ]

24 errors : !win32kbase (ffff96c12d443f99-ffff96c12d4451af)



MODULE_NAME: memory_corruption



IMAGE_NAME: memory_corruption



FOLLOWUP_NAME: memory_corruption



DEBUG_FLR_IMAGE_TIMESTAMP: 0



MEMORY_CORRUPTOR: LARGE



FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE



BUCKET_ID: MEMORY_CORRUPTION_LARGE



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:memory_corruption_large



FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}



Followup: memory_corruption

Continue reading...
 

Similar threads

C
Replies
0
Views
20
CédricJestin
C
M
Windows 10 BSOD -
Replies
0
Views
29
Magical Pickle
M
D
Replies
0
Views
56
DannyYang3
D
L
Replies
0
Views
53
LudwvinMartinez
L
Back
Top