Many BSOD after installing new ram, but still getting them when old ram is in.

None of those BSODs were generated by Driver Verifier and they fail during different operations and for largely different reasons, so your BSODs are extremely unlikely to be caused by a flaky third-party driver. That means that this is a hardware issue.

Normally I'd suggest you start with a RAM test, but since you've had BSODs with two different sets of RAM it's unlikely to be flaky RAM. I would suggest you download and run Prime95 to stress test your CPU and (in certain tests) your RAM. This will cause your CPU to run hot, so you also need to run some temperature monitoring software (like CoreTemp) to watch your CPU temperature.

Run all three Prime95 tests (small FFTs, large FFTs, and Blend) one at a time for at least 2 hours (each test). If Prime95 flags errors, if the system BSODs or crashes, or if your CPU runs too hot (according to this the max operating temp for your CPU is 95°C), then stop Prime95 and let us know what happened.
 
None of those BSODs were generated by Driver Verifier and they fail during different operations and for largely different reasons, so your BSODs are extremely unlikely to be caused by a flaky third-party driver. That means that this is a hardware issue.

Normally I'd suggest you start with a RAM test, but since you've had BSODs with two different sets of RAM it's unlikely to be flaky RAM. I would suggest you download and run Prime95 to stress test your CPU and (in certain tests) your RAM. This will cause your CPU to run hot, so you also need to run some temperature monitoring software (like CoreTemp) to watch your CPU temperature.

Run all three Prime95 tests (small FFTs, large FFTs, and Blend) one at a time for at least 2 hours (each test). If Prime95 flags errors, if the system BSODs or crashes, or if your CPU runs too hot (according to this the max operating temp for your CPU is 95°C), then stop Prime95 and let us know what happened.
Well that was quick lol. It ran at 95c and came up with an error on worker 4

[Jul 18 13:31] Worker starting
[Jul 18 13:31] Beginning a continuous torture test on your computer.
[Jul 18 13:31] Please read stress.txt. Choose Test/Stop to end this test.
[Jul 18 13:31] Test 1 (thread 2 of 2), 7000000 Lucas-Lehmer in-place iterations of M83839 using FMA3 FFT length 4K.
[Jul 18 13:31] Test 1 (thread 1 of 2), 7000000 Lucas-Lehmer in-place iterations of M83839 using FMA3 FFT length 4K.
[Jul 18 13:33] Test 2 (thread 2 of 2), 7000000 Lucas-Lehmer in-place iterations of M82031 using FMA3 FFT length 4K.
[Jul 18 13:33] Test 2 (thread 1 of 2), 7000000 Lucas-Lehmer in-place iterations of M82031 using FMA3 FFT length 4K.
[Jul 18 13:33] FATAL ERROR: Rounding was 1.812232929e+11, expected less than 0.4
[Jul 18 13:33] Hardware failure detected running 4K FFT size, consult stress.txt file.
[Jul 18 13:34] FATAL ERROR: Rounding was 0.4985351563, expected less than 0.4
[Jul 18 13:34] Hardware failure detected running 4K FFT size, consult stress.txt file.
[Jul 18 13:34] Torture Test completed 2 tests in 3 minutes - 2 errors, 0 warnings.
[Jul 18 13:34] Worker stopped.
 
I would probably still remove the fan clean off the old thermal paste (coffee filter and alcohol work great), remove and reinstall the CPU, new thermal paste and see if that makes a difference.
> http://www.arcticsilver.com/PDF/appmeth/amd/vl/amd_app_method_vl_1.3.pdf

I kind of don't want to touch anything in my computer much anymore lol. Specially not the cpu or cooler.
Last time I did so many years ago, I ended up messing something up and had to get a new mobo.
Only thing I've really changed in a computer are the hard drives/ssds and the gpu.
Apparently me touching anything else leads to computer problems.
 
This does seem to be a CPU issue, you aren't going to fail a Prime95 test because of the GPU or SSD. It isn't designed to test those.

You've tried two different sets of RAM, which means like @ubuysa said, that isn't likely to be the issue but you could run MemTest86 for further confirmation.

You only really have one option: get a new CPU to test with and ideally ensure that your RAM is on the QvL.
 
This does seem to be a CPU issue, you aren't going to fail a Prime95 test because of the GPU or SSD. It isn't designed to test those.

You've tried two different sets of RAM, which means like @ubuysa said, that isn't likely to be the issue but you could run MemTest86 for further confirmation.

You only really have one option: get a new CPU to test with and ideally ensure that your RAM is on the QvL.

I might be stuck then. Don't really have the money to go out and buy a new cpu, don't have one spare, and really don't have the confidence to change a cpu honestly.

I did run memtest86 on the new ram as one of the first troubleshoot things my friend suggested. Came back clean. So you're probably right about it being cpu.

Honestly didn't know changing ram around could cause the cpu to have problems. Seems strange lol. At least I know in the future.
 
It isn't because you've changed the RAM, your CPU is defective and will need to be replaced.
 
It isn't because you've changed the RAM, your CPU is defective and will need to be replaced.

I'm not saying you're wrong. You're the expert. Just that's the only thing that I've changed.
My computer was working fine before I changed the ram. Computer starts to bsod after changing to new ram. Changed back to old ram and computer continues to bsod.
You can see how I'm a little confused and can think that the ram change caused the cpu to become defective.
 
It would seem coincidental to me, hardware failures are often unpredictable unfortunately and can happen at any time.
 
It would seem coincidental to me, hardware failures are often unpredictable unfortunately and can happen at any time.

Fair. Guess I'm stuck then. Was kind of hoping it was something like bios settings or something. But probably is just cpu like everyone's said.

Thanks for trying to help.
 

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

Back
Top