ntoskrnl.exe error

[johnathan142]

Hey guys I recently started getting a BSOD, something about ntoskrnl.exe. I've updated windows to the latest windows update, reinstalled by graphics drivers with DDU, I'm thinking it might be an issue with my GPU or RAM, but i have no spare parts so I wanted your advice before I start the rma process. I've attached some screenshots from bluescreenview and whocrashed. I'll update if any more information is needed.

 

Roughly a year old build
Windows version: Windows 10 , 10.0, build: 19041 x64 
GPU: MSI GeForce GTX 1660 GAMING X 6G
Motherboard: MSI B450 TOMAHAWK AMD AM4 ATX Gaming Motherboard
CPU: AMD Ryzen 5 3600 3.60 GHz
RAM: G.Skill Trident Z RGB 16GB (2x8GB) 3200MHz DDR4

PSU: EVGA SuperNOVA 750 G2 750W 80 Plus Gold Modular Power Supply

 

 

 

 

[TehDwonz]

Just now, johnathan142 said:

Hey guys I recently started getting a BSOD, something about ntoskrnl.exe. I've updated windows to the latest windows update, reinstalled by graphics drivers with DDU, I'm thinking it might be an issue with my GPU or RAM, but i have no spare parts so I wanted your advice before I start the rma process. I've attached some screenshots from bluescreenview and whocrashed. I'll update if any more information is needed.

 

Roughly a year old build
Windows version: Windows 10 , 10.0, build: 19041 x64 
GPU: MSI GeForce GTX 1660 GAMING X 6G
Motherboard: MSI B450 TOMAHAWK AMD AM4 ATX Gaming Motherboard
CPU: AMD Ryzen 5 3600 3.60 GHz
RAM: G.Skill Trident Z RGB 16GB (2x8GB) 3200MHz DDR4

PSU: EVGA SuperNOVA 750 G2 750W 80 Plus Gold Modular Power Supply

 

Is anything overclocked? If not, re-seat your RAM and GPU, then in an admin cmd prompt:

SFC /SCANNOW
DISM /ONLINE /CLEANUP-IMAGE /RESTOREHEALTH

If either one gives an indication of corruption or errors, re-run the other.

[johnathan142]

I've finished reseating the RAM and GPU and ran the commands, doesn't indicate anything was broken, there's no overclock on the system, and a couple hours after i ran the commands my computer has blue screened again, the nature of this crash was the same as the crash on the 6/10/2020, being KMODE_EXCEPTION_NOT_HANDLED