BSOD

DanCarter194

Bronze Level Poster
I messaged tech support about this but haven't heard back and discovered this forum so thought I'd post here as well and see if anyone can help me.

My new PC arrived yesterday and I've been installing software and setting it up. A couple of times I've had a BSOD. The second time it happened I was able to note down the error code `MEMORY_MANAGEMENT`.

Please see below links to relevant files:
If it helps, I'm currently running Windows 10 Home 2004, and there is an OS update available (to 20H2).

Below are the tech specs of my PC:

Case
CORSAIR 175R RGB MID TOWER GAMING CASE
Processor (CPU)
AMD Ryzen 5 3600 Six Core CPU (3.6GHz-4.2GHz/36MB CACHE/AM4)
Motherboard
ASUS® PRIME B550-PLUS (DDR4, USB 3.2, 6Gb/s) - ARGB Ready!
Memory (RAM)
16GB Corsair VENGEANCE DDR4 3200MHz (2 x 8GB)
Graphics Card
4GB NVIDIA GEFORCE GTX 1050 Ti - DVI, HDMI, DP
1st M.2 SSD Drive
500GB SAMSUNG 970 EVO PLUS M.2, PCIe NVMe (up to 3500MB/R, 3200MB/W)
Power Supply
CORSAIR 650W TXm SERIES™ SEMI-MODULAR 80 PLUS® GOLD, ULTRA QUIET
Power Cable
1 x 1 Metre UK Power Cable (Kettle Lead)
Processor Cooling
STANDARD AMD CPU COOLER
Thermal Paste
STANDARD THERMAL PASTE FOR SUFFICIENT COOLING
Extra Case Fans
2x 120mm Black Case Fan (configured to extract from rear/roof)
Sound Card
ONBOARD 6 CHANNEL (5.1) HIGH DEF AUDIO (AS STANDARD)
Network Card
10/100/1000 GIGABIT LAN PORT (Wi-Fi NOT INCLUDED)
Wireless Network Card
WIRELESS 802.11N 300Mbps/2.4GHz PCI-E CARD
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
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 Standard Warranty (1 Month Collect & Return, 1 Year Parts, 3 Year Labour)
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
 

Martinr36

MOST VALUED CONTRIBUTOR
Whip the side off and make sure all the memory and graphic card are properly seated, stuff can come loose in transit
 

DanCarter194

Bronze Level Poster
Yesterday evening I got another BSOD.

This time the error code was `IRQL_NOT_LESS_OR_EQUAL`.

Based on a quick google search it seems that this error can happen when the OS or drivers are out of date. There's a Windows update available, so I'll try installing that.

See below for links to relevant information:
I still haven't heard back from tech support (I logged into the website > Tech Support > New Message). Have I done the right thing or should I be using another channel to speak to PCSpecialist?
 

ubuysa

The BSOD Doctor
Yesterday evening I got another BSOD.

This time the error code was `IRQL_NOT_LESS_OR_EQUAL`.

Based on a quick google search it seems that this error can happen when the OS or drivers are out of date. There's a Windows update available, so I'll try installing that.

See below for links to relevant information:
I still haven't heard back from tech support (I logged into the website > Tech Support > New Message). Have I done the right thing or should I be using another channel to speak to PCSpecialist?
I'll look at both kernel dumps when they've downloaded. The best way to contact PCS is by phone - there will be a long waiting time but at least you'll get to talk to someone.
 

DanCarter194

Bronze Level Poster
Thanks for the response. It's just happened again with the same code, `IRQL_NOT_LESS_OR_EQUAL`. I can get the memory dump if needed, although it's potentially the same problem.
 

ubuysa

The BSOD Doctor
The first kernel dump (the MEMORY_MANAGEMENT one) was a RAM issue. The failure was an out of sync page table and that's almost always a RAM hardware issue.

The second kernel dump (the classic IRQL_NOT_LESS_OR_EQUAL) and after you'd reseated the RAM I think(?) was most likely caused by the Nvidia graphics driver nvlddmkm.sys. In the list of driver calls for the active thread there is a clear error for it...

Code:
ffff8281`5cf8a808  fffff806`25be052d Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvrfi.inf_amd64_0da9e25cd8a1ccb0\nvlddmkm.sys, Win32 error 0n2
 nvlddmkm+0x1c052d

BUT....

The stack trace of the active thread just before the bug check shows several system function calls related to memory management and manipulation (copying virtual storage pages, locking pages, etc.), so it's entirely possible there is still a RAM issue there and the Nvidia graphics driver failure was possibly a RAM issue.

The common denominator between these two dumps is RAM, so I think I would download Memtest, use the extracted tool to make a bootable USB stick containing Memtest, and then boot that USB stick. Memtest will start running. Let it complete all four iterations of the 13 individual tests. Even one error is a failure.

Do please upload the new kernel dump, it would be very useful to see the active thread's stack trace in there too. :)
 

DanCarter194

Bronze Level Poster
OK, so I ran Memtest, and the results I got seem to indicate that the RAM is working fine. I ran it for two and a half hours - should I have left it running longer? If so I'll do it overnight.

Here is the results file from it: https://drive.google.com/file/d/1hcdcvE1kXocZa3jGaci14IlJcy_aN_bm/view?usp=sharing

Below are two "screenshots" of the results.
I guess the next step is to investigate the Nvidia graphics driver? How do I do that?

Thanks in advance.
 

ubuysa

The BSOD Doctor
Did it finish the 4th pass? That screenshot above looks like it was in the middle of running it? You really want to run the entire 4 run set...it may be it is fine for the first 3 and then flags an error in the 4th
Absolutely. The key with testing RAM is to run as many iterations of the tests as you can. The free version only does 4 and that's just about enough, ideally you want to run 8 iterations. The paid for version will do up to 15.

Please run Memtest again overnight and allow it to do all 4 iterations.
 

ubuysa

The BSOD Doctor
OK, so I ran Memtest, and the results I got seem to indicate that the RAM is working fine. I ran it for two and a half hours - should I have left it running longer? If so I'll do it overnight.

Here is the results file from it: https://drive.google.com/file/d/1hcdcvE1kXocZa3jGaci14IlJcy_aN_bm/view?usp=sharing

Below are two "screenshots" of the results.
I guess the next step is to investigate the Nvidia graphics driver? How do I do that?

Thanks in advance.
This latest dump is also an IRQL_NOT_LESS_OR_EQUAL. This stop code happens because some kernel mode code (which are not allowed to take page faults - ie. referencing memory which is not valid, meaning paged out or not allocated) ran into a page fault - hence the BSOD. Although Windows code could contain a bug that causes this invalid situation, the whole world would know if it did. Hence these sorts of errors come from the only other code allowed to run in kernel mode - device drivers. That's why this stop code can be confidently laid at the door of a device driver.

Before we get to the driver in this dump, the stack trace of the active thread this time does not show memory manipulation function calls. This time they show the thread starting an I/O operation and the dispatcher being called to schedule a new thread on the CPU. This BSOD then does not appear to be RAM related.

However, the driver at error is (again) the Nvidia graphics driver nvlddmkm.sys...

Code:
ffffa98b`1f0d5038  fffff804`68f5052d Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvrfi.inf_amd64_0da9e25cd8a1ccb0\nvlddmkm.sys, Win32 error 0n2 nvlddmkm+0x1c052d

....so this would appear to be the Nvidia graphics driver at fault - as in the last IRQL_NOT_LESS_OR_EQUAL failure.
 

DanCarter194

Bronze Level Poster
OK, thanks for investigating.

So it sounds like it's the graphics driver at fault. Is there a way I can fix this? Does it need updating and if so how do I do that? Using Device Manager under "display adaptors" my graphics card is listed, and using "update driver" it says that the best drivers are installed. The installed driver is version 27.21.14.6140, released 2021-01-22. Looking at the NVIDIA website, there is one release 2021-01-26 which I guess is an update - do I want to install that one? https://www.nvidia.co.uk/Download/driverResults.aspx/170461/en-uk

I'll run Memtest overnight anyway to be sure it's not RAM related.
 

SpyderTracks

We love you Ukraine
OK, thanks for investigating.

So it sounds like it's the graphics driver at fault. Is there a way I can fix this? Does it need updating and if so how do I do that? Using Device Manager under "display adaptors" my graphics card is listed, and using "update driver" it says that the best drivers are installed. The installed driver is version 27.21.14.6140, released 2021-01-22. Looking at the NVIDIA website, there is one release 2021-01-26 which I guess is an update - do I want to install that one? https://www.nvidia.co.uk/Download/driverResults.aspx/170461/en-uk

I'll run Memtest overnight anyway to be sure it's not RAM related.
Yes, you'll want to keep the display drivers up to date and always direct from nvidia.

Also, whenever updating the display driver, always select a custom install and leave out the HDAudio component as that's known to cause issues at the moment.
 

DanCarter194

Bronze Level Poster
According to Device Manager the driver I have installed is 27.21.14.6140, released 2021-01-22. However NVIDIA GeForce Experience tells me I have the latest driver, which is version 461.40, released 2021-01-26 (which matches the link above).

I'll try reinstalling and making sure to leave out the HDAudio component.
 

SpyderTracks

We love you Ukraine
According to Device Manager the driver I have installed is 27.21.14.6140, released 2021-01-22. However NVIDIA GeForce Experience tells me I have the latest driver, which is version 461.40, released 2021-01-26 (which matches the link above).

I'll try reinstalling and making sure to leave out the HDAudio component.
If reinstalling, it's best to use Display Driver uninstaller first, that will completely wipe the current driver.

 

DanCarter194

Bronze Level Poster
Had a look at DDU but there were loads of options and enough warnings about knowing exactly what you're doing that I didn't feel comfortable running it. I don't want my new PC to become unusable because I didn't choose the right options.

I reinstalled the driver using NVIDIA GeForce Experience, but Device Manager is still reporting the older version. Maybe I need to bite the bullet and run DDU anyway. What settings should I use for it? Do I need to do a backup of some kind before running it?
 

SpyderTracks

We love you Ukraine
Had a look at DDU but there were loads of options and enough warnings about knowing exactly what you're doing that I didn't feel comfortable running it. I don't want my new PC to become unusable because I didn't choose the right options.

I reinstalled the driver using NVIDIA GeForce Experience, but Device Manager is still reporting the older version. Maybe I need to bite the bullet and run DDU anyway. What settings should I use for it? Do I need to do a backup of some kind before running it?
The only thing you need to do is check all the boxes for nvidia including PhysX which will be unticked by default, then leave the rest as they are:

1613944426789.png


Then in the main program window, in the right hand side "select device type" select graphics, then underneath, select the nvidia card, then click "Clean and Restart" in the top left:

1613944568302.png


It may flash up a warning about being in safe mode at the start, personally, I've never used it in safe mode and never had an issue.
 

DanCarter194

Bronze Level Poster
Thanks for your help. I used DDU and then installed the driver again. Device Manager is still reporting the older version of the driver so I don't know if that is a problem. The difference is that now I know I don't have HDAudio, so that might fix the problem. I'll see how it goes for a few days and report back if the BSOD happens again.
 
Top