BSODs that occur frequently (Multiple times every few days)

J

JumboCoffee

New member
Joined
Apr 22, 2025
Posts
3
  • 1745341478842.webp1745341513076.webp
  • A brief description of your problem (but you can also include the steps you tried) : I have had frequent BSODs over the past few months, with it happening during gaming sessions (sometimes upon game launch/join, but other times on game change/map changes, or randomly whilst playing game will freeze, audio will loop then BSOD), it has also crashed when installing large games/programs. It sometimes crashed to BSOD, with others instantly restarting or being stuck on a black screen. WhoCrashed and WinDBG lists it as a Authentic.amd WHEA_Uncorrectable_Error. I have DDU'd numerous times, I have also ran Memtest twice with no errors. I am unable to recreate the crash with OCCT Full system stress tests. I have also noticed my C drive (GIGABYTEbeing hot, 50+C at idle, with it sometimes spiking to 80C, both CrystalDiskMark and HardDiskSentinel report no issues with it other than temps, manufacturer software also shows no issues. Unsure if this is related to the crashes. Looking forward to any help, thanks
  • System Manufacturer?
  • Laptop or Desktop?: Desktop
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista) : Windows 10
  • x86 (32bit) or x64 (64bit)? :x64
  • What was original installed OS on system? Windows 10 Home
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Windows 10 Home, Purchased
  • Age of system? (hardware): 3years 8months (MOBO, GPU, 1TB SSD, RAM 16gb, AIO), 1.5year (2TB HDD, RAM 16gb upgrade, Replacement PSU), 10 year old 1TB HDD, 4year old 1TB SSD
  • Age of OS installation? :~4months
  • Have you re-installed the OS? Yes, upon new CPU installation (Aug 2024) and again in January 2025
  • CPU : Ryzen 5700x3D
  • RAM (brand, EXACT model, what slots are you using?) : Corsair Vengeance RGB Pro SL 3600mhz (32GB total, 4x8GB sticks), all 4 channels but set to 3200mhz (seems to be a lil more stable)
  • Video Card : Zotac Trinity RTX3070Ti
  • MotherBoard - (if NOT a laptop) : NZXT N7 B550 (P3.60 Bios Version, installed Aug 22nd 2024)
  • Power Supply - brand & wattage (if laptop, skip this one) Corsair RM850E
  • Is driver verifier enabled or disabled? : Disabled
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) : Windows Defender
  • Are you using proxy, vpn, ipfilters or similar software? : None
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) : None
  • Are you currently under/overclocking? Are there overclocking software installed on your system? : None
http://speccy.piriform.com/results/eLRaLwOvyZxKokutfTDVEuT
 

Attachments

Hi!

Please uninstall altogether (using revo uninstaller that is already installed):
- riot vanguard (vgk.sys)
- msi afterburner
- nzxt cam
- RivaTuner Statistics Server

Verify that vgk.sys has been deleted/removed.

Set the ram speed to 2667.

There are messages about bad blocks: The device, \Device\Harddisk3\DR3, has a bad block.
Check all partitions with chkdsk /F /R /B.
Example:
Code: 
chkdsk /F /R /B D:
chkdsk /F /R /B E:
chkdsk /F /R /B F:
chkdsk /F /R /B C:

Then test the machine in this state for two days (or more) and tell us if the problem has gone away or if it persists.
 
Last edited:
I rather think that this may be an NVMe drive issue. The four 0x124 bugcheck dumps all fail becvause of an NVMe drive controller issue...
Rich (BB code): 
1: kd> !dpx
Start memory scan  : 0xffff820b16570458 ($csp)
End memory scan    : 0xffff820b16571000 (Kernel Stack Base)

               rsp : 0xffff820b16570458 : 0xfffff806469bc14f : nt!WheaReportHwError+0x4cf
0xffff820b16570458 : 0xfffff806469bc14f : nt!WheaReportHwError+0x4cf
0xffff820b165704d8 : 0xfffff806426c10a4 : PSHED!PshedRetrieveErrorInfo+0x94
0xffff820b165704e8 : 0xfffff806466395f9 : nt!EtwWriteEx+0x119
0xffff820b165704f8 : 0xfffff806469bca99 : nt!WheaHwErrorReportSetSeverityDeviceDriver+0x9
0xffff820b16570520 : 0xfffff80648669930 : storport!WheaErrorData
0xffff820b16570528 : 0xfffff806469bcbb9 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
0xffff820b16570540 : 0xffffa2827a4b7070 :  Trap @ ffff820b16570540
0xffff820b16570558 : 0xfffff806469bccd5 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
0xffff820b165705b8 : 0xfffff80648643711 : storport!StorpWheaReportError+0x9d
0xffff820b16570608 : 0xfffff80648662350 : storport!g_StorpSourceGuid
0xffff820b16570618 : 0xfffff806486435c0 : storport!StorpPopulateErrorData+0x120
0xffff820b16570648 : 0xfffff8064863caf0 : storport!StorpMarkDeviceFailed+0x358
0xffff820b165706a8 : 0xfffff8064663c5d9 : nt!KiInsertQueueDpc+0x289
0xffff820b16570718 : 0xfffff806485f1750 :  !du ""Controller Reset failed due to surprise remove""
0xffff820b16570750 : 0xffffa2827a4f69c8 :  !du "stornvme"
0xffff820b165707d0 : 0xfffff806486690ff : storport!SrbShimHooks+0xf
0xffff820b165707e8 : 0xfffff806486388c1 : storport!StorEtwMiniportLogError+0x255
0xffff820b16570820 : 0xffffa2827a4f69c8 :  !du "stornvme"
0xffff820b16570858 : 0xfffff806485f1000 :  !du ""Controller Fatal Status is set""
0xffff820b16570878 : 0xfffff806485f1000 :  !du ""Controller Fatal Status is set""
0xffff820b16570888 : 0xfffff806485f1000 :  !du ""Controller Fatal Status is set""
0xffff820b165708a0 : 0xfffff80647125440 : nt!ExNode0
0xffff820b165708d8 : 0xfffff8064860f0cc : storport!StorPortNotification+0x91c
0xffff820b165708e0 : 0xfffff80648669000 : storport!WPP_GLOBAL_Control
0xffff820b16570900 : 0xfffff806485f1750 :  !du ""Controller Reset failed due to surprise remove""
0xffff820b16570908 : 0xfffff80648610000 : storport!StorPortExtendedFunction+0x980
0xffff820b16570918 : 0xfffff806485d0000 : "stornvme!NVMeIsAllowedWithinThrottleLimit <PERF> (stornvme+0x0)"
0xffff820b16570958 : 0xfffff806485e0b46 : stornvme!NVMeRequestComplete+0x96
0xffff820b16570968 : 0xfffff80647125440 : nt!ExNode0
0xffff820b165709a8 : 0xfffff806485db57d : stornvme!ControllerReset+0x1a1
0xffff820b165709d8 : 0xfffff806485f1750 :  !du ""Controller Reset failed due to surprise remove""
0xffff820b16570a28 : 0xfffff806485de78e : stornvme!NVMeControllerReset+0x10a
0xffff820b16570a58 : 0xfffff806485dd6ef : stornvme!NVMeControllerAsyncResetWorker+0x3f
0xffff820b16570a88 : 0xfffff8064863a1c5 : storport!StorPortWorkItemRoutine+0x45
0xffff820b16570ab0 : 0xfffff8064863a180 : storport!StorPortWorkItemRoutine
0xffff820b16570ab8 : 0xfffff806466dde15 : nt!IopProcessWorkItem+0x135
0xffff820b16570ad8 : 0xfffff80675467050 : usbaudio!USBCaptureRequeueWorker
0xffff820b16570ae8 : 0xfffff806466ddce0 : nt!IopProcessWorkItem
0xffff820b16570b28 : 0xfffff806466489d5 : nt!ExpWorkerThread+0x105
0xffff820b16570b40 : 0xfffff806466ddce0 : nt!IopProcessWorkItem
0xffff820b16570b68 : 0xffffa28276672630 : 0xffffa282766b75e0 : 0xfffff80647050c00 : nt!MiSystemPartition
0xffff820b16570bb0 : 0xfffff806466488d0 : nt!ExpWorkerThread
0xffff820b16570bc8 : 0xfffff806467347d5 : nt!PspSystemThreadStartup+0x55
0xffff820b16570c18 : 0xfffff80646806f38 : nt!KiStartSystemThread+0x28
0xffff820b16570c30 : 0xfffff80646734780 : nt!PspSystemThreadStartup
Check the SMART data of your NVMe drive(s).
 
ubuysa said:
I rather think that this may be an NVMe drive issue. The four 0x124 bugcheck dumps all fail becvause of an NVMe drive controller issue...
Rich (BB code): 
1: kd> !dpx
Start memory scan  : 0xffff820b16570458 ($csp)
End memory scan    : 0xffff820b16571000 (Kernel Stack Base)

               rsp : 0xffff820b16570458 : 0xfffff806469bc14f : nt!WheaReportHwError+0x4cf
0xffff820b16570458 : 0xfffff806469bc14f : nt!WheaReportHwError+0x4cf
0xffff820b165704d8 : 0xfffff806426c10a4 : PSHED!PshedRetrieveErrorInfo+0x94
0xffff820b165704e8 : 0xfffff806466395f9 : nt!EtwWriteEx+0x119
0xffff820b165704f8 : 0xfffff806469bca99 : nt!WheaHwErrorReportSetSeverityDeviceDriver+0x9
0xffff820b16570520 : 0xfffff80648669930 : storport!WheaErrorData
0xffff820b16570528 : 0xfffff806469bcbb9 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
0xffff820b16570540 : 0xffffa2827a4b7070 :  Trap @ ffff820b16570540
0xffff820b16570558 : 0xfffff806469bccd5 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
0xffff820b165705b8 : 0xfffff80648643711 : storport!StorpWheaReportError+0x9d
0xffff820b16570608 : 0xfffff80648662350 : storport!g_StorpSourceGuid
0xffff820b16570618 : 0xfffff806486435c0 : storport!StorpPopulateErrorData+0x120
0xffff820b16570648 : 0xfffff8064863caf0 : storport!StorpMarkDeviceFailed+0x358
0xffff820b165706a8 : 0xfffff8064663c5d9 : nt!KiInsertQueueDpc+0x289
0xffff820b16570718 : 0xfffff806485f1750 :  !du ""Controller Reset failed due to surprise remove""
0xffff820b16570750 : 0xffffa2827a4f69c8 :  !du "stornvme"
0xffff820b165707d0 : 0xfffff806486690ff : storport!SrbShimHooks+0xf
0xffff820b165707e8 : 0xfffff806486388c1 : storport!StorEtwMiniportLogError+0x255
0xffff820b16570820 : 0xffffa2827a4f69c8 :  !du "stornvme"
0xffff820b16570858 : 0xfffff806485f1000 :  !du ""Controller Fatal Status is set""
0xffff820b16570878 : 0xfffff806485f1000 :  !du ""Controller Fatal Status is set""
0xffff820b16570888 : 0xfffff806485f1000 :  !du ""Controller Fatal Status is set""
0xffff820b165708a0 : 0xfffff80647125440 : nt!ExNode0
0xffff820b165708d8 : 0xfffff8064860f0cc : storport!StorPortNotification+0x91c
0xffff820b165708e0 : 0xfffff80648669000 : storport!WPP_GLOBAL_Control
0xffff820b16570900 : 0xfffff806485f1750 :  !du ""Controller Reset failed due to surprise remove""
0xffff820b16570908 : 0xfffff80648610000 : storport!StorPortExtendedFunction+0x980
0xffff820b16570918 : 0xfffff806485d0000 : "stornvme!NVMeIsAllowedWithinThrottleLimit <PERF> (stornvme+0x0)"
0xffff820b16570958 : 0xfffff806485e0b46 : stornvme!NVMeRequestComplete+0x96
0xffff820b16570968 : 0xfffff80647125440 : nt!ExNode0
0xffff820b165709a8 : 0xfffff806485db57d : stornvme!ControllerReset+0x1a1
0xffff820b165709d8 : 0xfffff806485f1750 :  !du ""Controller Reset failed due to surprise remove""
0xffff820b16570a28 : 0xfffff806485de78e : stornvme!NVMeControllerReset+0x10a
0xffff820b16570a58 : 0xfffff806485dd6ef : stornvme!NVMeControllerAsyncResetWorker+0x3f
0xffff820b16570a88 : 0xfffff8064863a1c5 : storport!StorPortWorkItemRoutine+0x45
0xffff820b16570ab0 : 0xfffff8064863a180 : storport!StorPortWorkItemRoutine
0xffff820b16570ab8 : 0xfffff806466dde15 : nt!IopProcessWorkItem+0x135
0xffff820b16570ad8 : 0xfffff80675467050 : usbaudio!USBCaptureRequeueWorker
0xffff820b16570ae8 : 0xfffff806466ddce0 : nt!IopProcessWorkItem
0xffff820b16570b28 : 0xfffff806466489d5 : nt!ExpWorkerThread+0x105
0xffff820b16570b40 : 0xfffff806466ddce0 : nt!IopProcessWorkItem
0xffff820b16570b68 : 0xffffa28276672630 : 0xffffa282766b75e0 : 0xfffff80647050c00 : nt!MiSystemPartition
0xffff820b16570bb0 : 0xfffff806466488d0 : nt!ExpWorkerThread
0xffff820b16570bc8 : 0xfffff806467347d5 : nt!PspSystemThreadStartup+0x55
0xffff820b16570c18 : 0xfffff80646806f38 : nt!KiStartSystemThread+0x28
0xffff820b16570c30 : 0xfffff80646734780 : nt!PspSystemThreadStartup
Check the SMART data of your NVMe drive(s).
Click to expand...
1745412980629.webp1745413256410.webp

This is the boot nvme which runs very hot, it's health has deteriorated from 95% a couple months ago to now, and it was 88% just last month. The excel log is from GIGABYTE's own SSD tool. Does the errors you pointed out mean the drive is failing?
 
It might. A drive shouldn't deteriorate that fast. Itis really not possible to interpret any of those raw values, they are always vendor and drive dependent. Is your E: drive an NVMe, that one does seem to be having problems...!
 
ubuysa said:
It might. A drive shouldn't deteriorate that fast. Itis really not possible to interpret any of those raw values, they are always vendor and drive dependent. Is your E: drive an NVMe, that one does seem to be having problems...!
Click to expand...
The E: Drive is a 10year old shucked drive from an old PC, looking to replace it soon. I seem to have isolated the issue to the C: Drive, the GIGABYTE nvme, it crashes windows upon large file transfers/under load, with temps sitting at 80+C, even under crystaldiskmark it crashes, will try and get it warrantied.
 
What I typically do to better interpret the raw values in CrystalDiskInfo: Function > advanced features > Raw values > 10 dec, this changes the values to decimal values making them interpretable to us humans.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top