Frequent BSOD Errors

M

MagicTurtleeee

Member
Hey all, I have had this PC for almost a year now and recently I have been getting BSOD errors whenever I use the PC. It happened a few times a number of weeks ago and seemed to occur more frequently when idle. The last week or so it they have been occurring very frequently (usually within 15 minutes of starting the PC) and it rebooted multiple times while I was trying to obtain the log and dump files.

The errors seem to vary but these are the ones I have noted down over the last few days:
PAGE_FAULT_IN_NONPAGED_AREA
REFERENCE_BY_POINTER
KERNEL_SECURITY_CHECK_FAILURE
IRQL_NOT_LESS_OR_EQUAL
SYSTEM_SERVICE_EXCEPTION
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE

Windows is up to date and I have been through and updated my driver list as well. As I had more errors while trying to get the dump files I saved three of them (dont know if that's useful). Any help/advice much appreciated!

BSOD files – Google Drive

drive.google.com drive.google.com

Case
NZXT H511 MID-TOWER GAMING CASE (WHITE)
Processor (CPU)
AMD Ryzen 5 3600 Six Core CPU (3.6GHz-4.2GHz/36MB CACHE/AM4)
Motherboard
ASUS® PRIME B450-PLUS (DDR4, USB 3.1, 6Gb/s) - RGB Ready!
Memory (RAM)
16GB Corsair VENGEANCE DDR4 3600MHz (2 x 8GB)
Graphics Card
6GB NVIDIA GEFORCE RTX 2060 - HDMI, DP - VR Ready!
1st Storage Drive
2TB SEAGATE BARRACUDA SATA-III 3.5" HDD, 6GB/s, 7200RPM, 256MB CACHE
1st M.2 SSD Drive
500GB SAMSUNG 970 EVO PLUS M.2, PCIe NVMe (up to 3500MB/R, 3200MB/W)
Power Supply
CORSAIR 550W TXm SERIES™ SEMI-MODULAR 80 PLUS® GOLD, ULTRA QUIET
Power Cable
1 x 1 Metre UK Power Cable (Kettle Lead)
Processor Cooling
CoolerMaster MasterLiquid Lite 120 High Performance Liquid Cooler
Thermal Paste
STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Extra Case Fans
1x 120mm Black Case Fan (configured to extract from rear/roof)
Sound Card
ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Wireless Network Card
WIRELESS INTEL® Wi-Fi 6 AX200 2,400Mbps/5GHz, 300Mbps/2.4GHz PCI-E CARD + BT 5.0
USB/Thunderbolt Options
MIN. 2 x USB 3.0 & 2 x USB 2.0 PORTS @ BACK PANEL + MIN. 2 FRONT PORTS
Operating System
Windows 10 Home 64 Bit - inc. Single Licence [KK3-00002]
Operating System Language
United Kingdom - English Language
Windows Recovery Media
Windows 10 Multi-Language Recovery Image - Unlimited Downloads from Online Account
Office Software
FREE 30 Day Trial of Microsoft 365® (Operating System Required)
Anti-Virus
BullGuard™ Internet Security - Free 90 Day License inc. Gamer Mode
Browser
Google Chrome™
Warranty
3 Year Silver Warranty (1 Year Collect & Return, 1 Year Parts, 3 Year Labour)
Insurance
Simplesurance Purchase Protection inc. Accidental Damage & Theft
Delivery
STANDARD INSURED DELIVERY TO UK MAINLAND (MON-FRI)
Build Time
Standard Build - Approximately 12 to 15 working days
Welcome Book
PCSpecialist Welcome Book - United Kingdom & Republic of Ireland
Logo Branding
PCSpecialist Logo
 
M

MagicTurtleeee

Member
I used Windows device manager and searched for driver updates for each device listed. I didn't use a driver optimiser, are there any you would recommend?

The GPU drivers are up to date through NVIDIA GeForce Experience.

I'll try installing that chipset driver in the meantime, thanks for your help!
 
SpyderTracks

SpyderTracks

We love you Ukraine
MagicTurtleeee said:
I used Windows device manager and searched for driver updates for each device listed. I didn't use a driver optimiser, are there any you would recommend?

The GPU drivers are up to date through NVIDIA GeForce Experience.

I'll try installing that chipset driver in the meantime, thanks for your help!
Click to expand...
No, on the driver updater, just checking, they're always bad news for any system and should never be used, you've done it the correct way.

Fingers crossed it's the chipset driver, it's been fairly common in recent months.

But @ubuysa will take a look at the dump files if that doesn't resolve it which will give more conclusive areas to focus on.
 
ubuysa

ubuysa

The BSOD Doctor
I'm downloading the dumps etc. but all those stop codes could well be the result of bad chipset drivers. I will take a look at the dumps and stuff though. :)
 
ubuysa

ubuysa

The BSOD Doctor
There's nothing of special interest in the Application log and the System log contains nothing of interest beyond the various bug checks.

Dump1 is unreadable, it's clearly corrupted somehow. Bad chipset drivers could easily be responsible for that - but so could a RAM error, a paging file error, or even a drive error.

Dump 2 is a classic IRQL_NOT_LESS_OR_EQUAL, which means that an attempt was made to access memory that was invalid (not allocated or paged out) whilst running at an elevated IRQL (when accessing invalid memory is not permitted). Microsoft code doesn't make these kinds of mistakes so it's always a third party driver that's the cause of these BSODs.

The active thread was the Idle thread - this is dispatched when there is no work for this CPU to do. The stack trace suggests that the bug check happened as the CPU was exiting the idle loop and resuming a clock timer, but it's pretty clear that the problem was not related to anything that this thread was doing.

The list of driver calls for the active thread shows a lot of activity by amdppm.sys immediately following a nt!KeResumeClockTimerFromIdle function call, and that immediately precedes the bug check in the stack trace. The amdppm.sys driver is an AMD chipset driver of course.

There is an error from our old friend nvlddmkm.sys (the Nvidia graphics driver) and there is a lot of nvlddmkm.sys activity in the list of driver calls.
Code: 
ffff8189`f9ab2018  fffff803`3eb2df42 Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7d91b2ed40558a26\nvlddmkm.sys, Win32 error 0n2
 nvlddmkm+0x17df42

It's clear that although this CPU was executing the idle thread at the time of the bug check, the graphics card was busy communicating with its driver and this is likely the cause of the BSOD. However, I've seen many dumps before where nvlddmkm.sys failed because of a problem with the AMD chipset drivers.

Hopefully updating the chipset drivers has solved the problem. If it doesn't then upload the latest dump(s). :)
 
M

MagicTurtleeee

Member
I updated the chipset drivers as per Spyder's recommendation and it has been running without incident for over an hour now (which would have been unthinkable before).

If it happens again I'll come back and upload more dumps for you to have a look at.

Thanks both for your help! :)
 
You must log in or register to reply here.
Top