[SOLVED] No issues for weeks then random BSOD's every few minutes or hours

[cloner23]

So i had no issues after upgrading my system a few weeks ago. Ran great!
Previous system specs:
GTX 1080ti
Gigabyte Auros x570 elite
corsair 3000mhz ( cancelled the overclock for now, so it's 2133mhz ) 8gbx2
750W Thermaltake RGB Tough power
CPU Ryzen 3600
Water cooled AIO

Upgraded components:
RTX 3080 MSI ventus
Same motherboard
Gskill Trident Z rgb 3600mhz 8gb x2
Same Power supply ( 750W should be sweet spot )
Ryzen 5800x ( got it for a great deal at local online retailer )
Water cooler has been upped to a corsair H115i RGB Platinum
NVME is a samsung 960 evo 250gb as my main , secondary is a 500gb SSD

Everything was fine, no issues, great gaming times, fps at 1440p was a blast, then one day, BSOD.

I started checking why and what, updated all my driver to make sure, no difference.
Ran memtest, no issues, changed them over into the other slots as well.
Component reseating was followed shortly after that.

CMD commands were run to check for faults with no problems picked up. The BSOD's started to become more frequent and everyone of them had a different error displayed.

I could play a game like warzone of battlefield or dota with no problems. Once i idle in the menu or on the desktop browsing chrome, BSOD! Chrome made it worse somehow, firefox seems to be less aggressive at this stage.

I've done so much searching and troubleshooting that i just can't find the issue. Ram is fine, temps are fine, ram was swapped with another kit, ssd was swapped in to check the nvme for issues.

I've placed my dumps in this we transfer link, pleas please someone assist!! I can't work or play anymore.

https://wetransfer.com/downloads/bcb557004fc47066754420262b00275b20210201181945/f9fe8a

I hope you all can see something i dont.

FYI, pc has been restarted 6 times now, everytime a different model like 1904, 1909, 20H etc etc. All do the same! I've checked my network drivers, as i saw that peaked an interest in my event viewer. No change after upgrading.

Your help would be greatly appreciated!

 

[cloner23]

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Mon 2021/02/01 19:53:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minid\020121-6796-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x3D (0xFFFFF806632756D8, 0xFFFFF80663274F20, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2021/02/01 19:09:13 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minid\020121-9468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x50 (0xFFFFF38052E98C50, 0x0, 0xFFFFF80175BECB8E, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2021/02/01 18:59:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minid\020121-14078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80319077E19, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2021/02/01 16:32:45 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minid\020121-7187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8005BA23589, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2021/02/01 14:51:20 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minid\020121-6515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1220)
Bugcheck code: 0x50 (0xFFFFBC075B94FAD3, 0x10, 0xFFFFBC075B94FAD3, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

[Colif]

who crashed always shows NTOSKRNL as the cause. It is what crashed but only as it was the victim.

I will ask a friend to convert the dumps, we see what might really be cause.

 

[Ds_Tech]

Have you updated bios check for bios update dont install beta bios.
Try installing F32 bios for your motherboard.

 

[cloner23]

Have you updated bios check for bios update dont install beta bios.
Try installing F32 bios for your motherboard.

Hi,

Did that already, tested the F30 as well, tested them all on every format i've done.

I've replaced my ram with my wife's corsair but no change, swaped to a2 and b2 slots, same thing still.

 

[cloner23]

who crashed always shows NTOSKRNL as the cause. It is what crashed but only as it was the victim.

I will ask a friend to convert the dumps, we see what might really be cause.

I didn't know that, good to know!

Thank you! Would be greatly appreciated, been stuck on this for a while now!

 

[Ds_Tech]

Do you tried your old ryzen3600 cpu and gpu try that one by one.
If that also give prob then may be motherboard.

 

[cloner23]

Do you tried your old ryzen3600 cpu and gpu try that one by one.
If that also give prob then may be motherboard.

Those are sold to a friend.

I don't have someone with a spare gpu. Wife's got a ryzen 3 3200g though..but that won't help much seeing that the gpu is integrated

 

[cloner23]

Hopefully, the dump files from Colif can give me more direction on where to look into.

 

[Ds_Tech]

Those are sold to a friend.

I don't have someone with a spare gpu. Wife's got a ryzen 3 3200g though..but that won't help much seeing that the gpu is integrated

Try that 3200g no issue if had integrated graphics install your rtx 3080 with it try it. To check what causes prob.

 

[cloner23]

Try that 3200g no issue if had integrated graphics install your rtx 3080 with it try it. To check what causes prob.

Wife using it quite often, will see when i can steal it out
If not the dump files will hopefully show something.

 

[Ds_Tech]

Wife using it quite often, will see when i can steal it out
If not the dump files will hopefully show something.

Which motherboard your wife pc have if its b520 or above you can try mixing cpu and can check.

 

[cloner23]

Which motherboard your wife pc have if its b520 or above you can try mixing cpu and can check.

GA-A320M-S2H

Won't work

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/njgfz5bd/show 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.

Spoiler: Dump File Results

File information:	020121-9468-01.dmp (Feb 1 2021 - 12:09:13)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: Origin.exe)
Uptime:	0 Day(s), 0 Hour(s), 08 Min(s), and 19 Sec(s)

File information:	020121-7187-01.dmp (Feb 1 2021 - 09:32:45)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 46 Min(s), and 08 Sec(s)

File information:	020121-6796-01.dmp (Feb 1 2021 - 12:53:13)
Bugcheck:	INTERRUPT_EXCEPTION_NOT_HANDLED (3D)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 39 Min(s), and 15 Sec(s)

File information:	020121-6515-01.dmp (Feb 1 2021 - 07:51:20)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: MemCompression)
Uptime:	0 Day(s), 0 Hour(s), 17 Min(s), and 18 Sec(s)

File information:	020121-14078-01.dmp (Feb 1 2021 - 11:59:49)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: chrome.exe)
Uptime:	0 Day(s), 2 Hour(s), 25 Min(s), and 12 Sec(s)

1 of the 5 crashes was caused by nvlddmkm.sys. The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/X570-AORUS-ELITE-rev-10#kf
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.

 

[cloner23]

Thanks for this!
I'll wait for someone to see what the other 4 dumps could have been

 

[Colif]

Thanks for this!
I'll wait for someone to see what the other 4 dumps could have been

i can play this game...
its easy when you know Nvidia is bad...
Crash 1 looks like GPU drivers
Crash 2 isn't so obvious but lets see, you have old chipset drivers and newest bios - try updating them - https://www.gigabyte.com/au/Motherboard/X570-AORUS-ELITE-rev-10/support#support-dl-driver-chipset
Crash 3 mentions Nvidia so its too easy
Crash 4 is odd
Crash 5 is unclear

gigabyte are slow updating your lan drivers, so I would run this and see what Intel think - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html

 

[cloner23]

I'll check this out and update when i sit down at the system.

 

[cloner23]

Oky I've updated system drivers, nvidia is updated.

Everything is up to date.

I'll monitor and report back.

 

[cloner23]

BSOD

New dumps
https://we.tl/t-ZgF9QjleQs

Will start checking what's changed in the last day

 

[cloner23]

- System

- Provider

[ Name] Microsoft-Windows-WER-SystemErrorReporting
[ Guid] {ABCE23E7-DE45-4366-8631-84FA6C525952}
[ EventSourceName] BugCheck

- EventID 1001

[ Qualifiers] 16384

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2021-02-04T13:20:10.7887000Z

EventRecordID 2386

Correlation

- Execution

[ ProcessID] 0
[ ThreadID] 0

Channel System

Computer DESKTOP-3UHDVDQ

Security


- EventData

param1 0x0000007e (0xffffffffc0000005, 0xfffff8066a039aa5, 0xffffe805dbd5a788, 0xffffe805dbd59fc0)
param2 C:\Windows\MEMORY.DMP
param3 32b0d584-50d3-4ffa-8eb3-4a47e24245dc

All that's changed is the nvidia driver ( they were updated to the latest ) Rolled them back to the 460.89 version.

 

[Colif]

cam you copy paste results as plain text? it will strip the formatting and maybe make it easier to read

 

[cloner23]

https://imgur.com/a/5nvyuUk

View: https://imgur.com/a/5nvyuUk

 

[cloner23]

I have since disabled my boost on the cpu, it's running at base 3.8ghz.

Saw a few people complain about bsod on the 5800x

 

[Colif]

all of those events are after the restart, you need to look before 15:43:30 on that page.

I am glad I don't have to deal with that nerf fix. Hate to buy new CPU and not be able to run it at full speed. I don't know if mine ever done max speed but its been close . your base is same as mine, you just have 2 more cores.

hope they fix it soon. Not sure who is aware of it.

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/6d7phjbe/show 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.

Spoiler: Dump File Results

File information:	020421-18140-01.dmp (Feb 4 2021 - 08:19:11)
Bugcheck:	SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)
Probably caused by:	memory_corruption (Process: conhost.exe)
Uptime:	0 Day(s), 8 Hour(s), 10 Min(s), and 08 Sec(s)

File information:	020321-17359-01.dmp (Feb 3 2021 - 13:37:12)
Bugcheck:	KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:	memory_corruption (Process: Discord.exe)
Uptime:	0 Day(s), 0 Hour(s), 54 Min(s), and 23 Sec(s)

File information:	020321-16453-01.dmp (Feb 3 2021 - 08:26:13)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: MemCompression)
Uptime:	0 Day(s), 0 Hour(s), 01 Min(s), and 18 Sec(s)

File information:	020321-15890-01.dmp (Feb 3 2021 - 09:42:59)
Bugcheck:	PAGE_FAULT_IN_NONPAGED_AREA (50)
Probably caused by:	memory_corruption (Process: MemCompression)
Uptime:	0 Day(s), 1 Hour(s), 16 Min(s), and 19 Sec(s)

File information:	020321-15406-01.dmp (Feb 3 2021 - 09:53:37)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 0 Hour(s), 10 Min(s), and 12 Sec(s)

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