Getting random and multiple BSOD's....

R

Raedwald

Member
Joined
Feb 14, 2024
Posts
9
Hi,
Started getting random BSOD's around the middle of January of this year. I had written them down, but lost the note...sad. Tried SFC, chkdsk and windows mem test, got nowhere. I'd fix one and then another would pop up.

  • A brief description of your problem (but you can also include the steps you tried) See above.
  • System Manufacturer? Self-built.
  • Laptop or Desktop? Desktop.
  • Exact model number (if laptop, check label on bottom) Self-built.
  • OS ? (Windows 11, 10, 8.1, 8, 7, Vista) Win 10.
  • x86 (32bit) or x64 (64bit)? X64.
  • (Only for Vista, Windows 7) Service pack? N/A
  • What was original installed OS on system? Win 10.
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full retail Version.
  • Age of system? (hardware) About 3 years.
  • Age of OS installation? Same.
  • Have you re-installed the OS? No.
  • CPU AMD Ryzen 3
  • RAM (brand, EXACT model, what slots are you using?) Crucial 16GB. 1 and 3
  • Video Card GeForce GTX 1050 Ti 4GB
  • MotherBoard - (if NOT a laptop) Gigabyte B450M DS3H-Cf (AM4)
  • Power Supply - brand & wattage (if laptop, skip this one) 500 watt
  • Is driver verifier enabled or disabled? Unknown
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth) Windows Defender
  • Are you using proxy, vpn, ipfilters or similar software? No
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software) No
  • Are you currently under/overclocking? Are there overclocking software installed on your system? No

http://speccy.piriform.com/results/4q3UALGuPZCjrk2BpHjxeTD

I hope you can help.

Regards,
Raedwald
 

Attachments

I made an error on my ram: it Should be G.Skill Ripjaws V DDR4 Model: F4 3200C16D-16GVRB

Power supply: Cooler Master PS 500PCAR-D3

Raed
 
Hmm, have you tried updating your Nvidia driver(s) using DDU and then making sure that you only install those drivers?
 
I used DDUI to clean my Nvidia drivers and reinstalled the most recent ones. After 5 mins. the system froze. Rebooted and froze again after 20mins. So there is still something going on that I can't see. I did do the Memtest86. Attached are the results. It passed.
 

Attachments

Im certainly not going to argue with @x BlueRobot, he's way more advanced at this that I, but from the earlier dumps this looks very much like a RAM problem to me, that or a CPU issue. I don't recognise that Memtest86 output you posted?

My reasoning is that, although you have Driver Verifier enabled (with just the standard tests rather than those recommended here), none of these BSODs are Driver Verifier generated and that in itself is a good indication of a hardware cause. In addition, I don't see any third-party drivers referenced in these dumps, another good indicator of a hardware issue.

Two of the dumps are 0x3B bugchecks with non-canonical (garbage) memory address references and hence 0xC0000005 exceptions (invalid memory access), one of these also has a misaligned instruction pointer flagged. One dump is a 0x50 with an invalid memory reference, another is a 0x139 for a corrupted memory data structure, neither showing any third-party driver references - another good indication of a probable hardware cause. The fifth dump is a 0x101, which we can only fully debug with a kernel dump, but sadly that's already been overwritten. This bugcheck indicates a CPU hang and that's generally a CPU problem, which is why I mentioned CPU above.

In addition, in your System log, I can see the crashes with no indication of any error that might have caused them - another indicator of a probably hardware cause. In your Application log there are a number of application error messages with either 0xC0000005 exception codes (invalid memory reference) or 0x0000374 exception codes (heap corruption) - these point at a potential RAM issue.

I do know that AMD processors like fast RAM and you seem to have your 3200MHz RAM clocked at the stock frequency of 2133MHz. I don't hold out much hope but you could try running your RAM at the 3200MHz design speed?

You have two 8GB RAM sticks so you could also try removing one stick at a time and see whether it's BSODing on only one.

I've also seen a few AMD CPUs that were a tad unstable at low power C-States, so if you can, try disabling C-States in the BIOS and see whether that stops the BSODs.
 
Generally we recommend running Memtest86 twice, so you run 8 iterations, but if you can, pulling one RAM stick for a while is guaranteed to identify a flaky stick.

If you want to test your CPU we usually suggest running Prime95, but be aware that this WILL make your CPU run very hot, so you need to be sure your CPU (and your rig) is being properly cooled...
  1. Download Prime95 and a temperature monitoring tool (CoreTemp is sufficient).
  2. Run each of the three Prime 95 tests (small FFTs, large FFTs, and Blend) for an hour each test, if you can.
  3. If Prime95 throws errors, if the system crashes/freezes/BSODs, or if the CPU temperature exceeds 90°C (TjMax for your CPU is 95°C) then stop Prime95 and let us know what happened.
Note that a stable and properly cooled CPU should be able to run each Prime95 tests pretty much indefinitely.
 
At the large FFT stress test 2 of the workers threw out Fatal errors:

FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected running 224K FFT size, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected running 224K FFT size, consult stress.txt file.

I stopped the test.

Raed
 
The large FFT test puts an increased load on RAM, so if Prime95 passes small FFTs and fails only on large FFTs that might indicate that the problem may be more RAM than CPU. What you should do now is ensure that there are NO overclocks applied anywhere, not on the CPU, not on RAM (via XMP for example), and not on your GPU either. Also disable any undervolting you may be doing to try and control temperatures. EVERYTHING must be running at stock voltages and frequencies.

When everything is running at stock, try Prime95 again. Run only the large FFTs test and see whether there is any difference. If it still fails then remove one stick of RAM and run Prime95 large FFTs testing again. If it runs for an hour then swap RAM sticks and try the large FFTs test on just the other RAM stick (or vice-versa).

If the large FFTs test fails on both RAM sticks independently then check whether your RAM is on the QVL for your motherboard. Not being on the QVL doesn't mean that the RAM won't work, but it does mean that it's not been tested and verified as compatible - that's always a worry when you see a problem like this.

If your RAM is on the QVL and the large FFTs test fails on each stick independently then I would suspect that CPU I'm afraid.
 
It seems that my ram is not on the QVL list. I have made sure that nothing is over-clocked and that they are running at the correct voltage. I ran the test again and had the same error as before. So I took one stick out and ran the test again. After a few minutes, the same error occurs. So I removed that ram and put the other stick in it's place and the test ran fine for an hour. So it looks like one of my ram sticks is faulty. I will look into getting the proper ram and see if this corrects my problem. Thanks too all of you for your help.

I'll let you know how the new ram performs.

Raed
 
Buy the new RAM as a matched pair of sticks, not as individual sticks. I very much suggest yous stick to RAM that's on the QVL.
 

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

Back
Top