Question Help needed! New build crashes. Over thousands of errors in OCCT CPU test.

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
I've got a question regarding the memtest86+: the ram sticks fail within first hour of test if I enable SMP option, but without SMP enabled they were running for 10 hours with 4 passes and no errors.

Why do they pass tests with SMP disabled?
I ran Prime95 with Large FFTs option and it reported the following errors
Code:
[Fri Mar  5 13:01:51 2021]
FATAL ERROR: Rounding was 0.4991662188, expected less than 0.4
Hardware failure detected, consult stress.txt file.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
If I run Prime95 with the Small FFTs options then no problems are found:
 
Last edited:

Vic 40

Titan
Ambassador
Might be that xmp messes up the timings somehow, already said to try and set them manually, speed as well.

Maybe the memory controller on the cpu isn't great, maybe the motherboards bios isn't great or the motherboard itself.

No way of testing with another kit?
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Might be that xmp messes up the timings somehow, already said to try and set them manually, speed as well.

Maybe the memory controller on the cpu isn't great, maybe the motherboards bios isn't great or the motherboard itself.

No way of testing with another kit?
I set them manually, both speed and timings.
I wish I had another RAM stick just to test if it's the RAM issue.
What surprises me is that Memtest doesn't recognize memory type and chipset. It says "Unknown" for both of them. Speccy doesn't recognize memory type either. Is that common?
 
Last edited:

Vic 40

Titan
Ambassador
When? now or earlier on already? And how is that working? If it is not working think about either returning this kit or sell it and get a more compatibel kit. Think it's just some compatibility problem.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
When? now or earlier on already? And how is that working? If it is not working think about either returning this kit or sell it and get a more compatibel kit. Think it's just some compatibility problem.
I set them manually right before testing with Prime95.
It hasn't crashed for last 2 days, but I think It will crash later or sooner. It's been like this before: it didn't crash for a while, so I thought the problem has gone, but then suddenly started crashing again. I remember tweaking with timings and speed settings even before you suggested doing so. I did so many things in order to fix the issue, I've lost the count.
 
Last edited:

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Well you can just continue with this kit at stock settings or take my advice and test with another.
I'd love to test with another RAM, but I don't have that option. I'll probably buy another RAM kit later, when i get such opportunity. Thank you for your input.
 

Vic 40

Titan
Ambassador
You're welcome. Is hard to say more without having another kit to test other than maybe add voltage to the memory controller. Might be Vcore NB ofset voltage, see if you can go +0.05, see if that helps. Could also be the VDDP/SOC voltage, if finding that could try 1.1V, not going over 1.2V. These voltage should you find in the OC Tweaker.

If your German is adequate could you watch this, but maybe that the keywords and vid itself can be helpfull,

View: https://www.youtube.com/watch?v=ygUFGF_FiuA
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Might be good to get another kit to test with.
I bought a new pair of new RAM sticks. Crucial 8GB DDR4-2666 UDIMM CT8G4DFRA266
OCCT and memtest still find errors

I also noticed that no matter what ram stick I have installed the Failing Address is almost the same. If you look at my old post with previous RAM sticks installed it had almost identical Failing Address list. The Err-Bits, Bad and CPU columns also match, no matter what RAM sticks I have installed.
 
Last edited:
Apparently, you bought two supposedly identical ram sticks.
They are not identical.
Ram is sold in kits for a reason.
Proper operation is only assured for a single kit.

A motherboard must manage all the ram using the same specs of voltage, cas and speed.
The internal workings are designed for the capacity of the kit.
Ram from the same vendor and part number can be made up of differing manufacturing components over time.
Some motherboards, can be very sensitive to this.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Apparently, you bought two supposedly identical ram sticks.
They are not identical.
Ram is sold in kits for a reason.
Proper operation is only assured for a single kit.

A motherboard must manage all the ram using the same specs of voltage, cas and speed.
The internal workings are designed for the capacity of the kit.
Ram from the same vendor and part number can be made up of differing manufacturing components over time.
Some motherboards, can be very sensitive to this.
IDK, I did some research before buying sticks and It was said as long as two ram sticks have the same speed, voltage, latency etc. they should work fine. With the previous kit I tested each stick at a time and still had the same results.
Here cpu-z report for both of the sticks
 
The operative word is "supposedly"
Most of the time, disparate sticks with the same specs work just fine.
Particularly with intel motherboards.
Ryzen, on the other hand is very tightly tied to ram for performance and functionality.
You may have other underlying issues that are causing you problem.

Since the ram failed memtest, I would try to return it in favor of a kit that is explicitly supported for your motherboard on the ram QVL list.
There are different versions, depending on the processor used; pick the right list.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
Since the ram failed memtest, I would try to return it in favor of a kit that is explicitly supported for your motherboard on the ram QVL list.
I have only one question. What if they retest the ram sticks on their side and they won't fail, they might refuse me to replace those sticks with different ones? If I bought the wrong sticks then it's my problem, they won't exchange them for different ones.
 

Herr B

Proper
May 29, 2020
165
33
190
10
I have had many BSOD experiences with tools such Driver easy. BSODS most of the times hint to driver issues.

  1. Load stock settings in Bios (to evade all possibly incorrect settings here)
  2. Fresh windows install formatting the harddrive (to evade all possibly corrupt driver installations - removing old drivers does not always work)
  3. Get drivers from Oem website and install them
That's the first steps I'd do as an IT technician in order to make sure all drivers are set up properly and I do not have to deal with any faulty residue from previous experiments.

Most oems webpages are having the very same navigation leading to the drivers:
Manufacturers Webpage -> support -> Drivers and downloads

Once you did that you can be fairly sure there is a hardware issue.

If possible, send link to minidump file. Minidump contains the basic bsod information. Its normally located in C:\Windows\minidump
 
Last edited:
I have only one question. What if they retest the ram sticks on their side and they won't fail, they might refuse me to replace those sticks with different ones? If I bought the wrong sticks then it's my problem, they won't exchange them for different ones.
If you bought directly from crucial, they might well test the sticks and find them good individually.
They would be returned to you and you could sell them yourself.
If you bought from a retailer, the defective return policy will be in effect and the retailer should refund your money. They will not have the means to test every return.
A retailer is likely to look favorably if you offer to buy a replacement kit.

All of this assumes that your problems are not rooted elsewhere.
 
Reactions: Herr B

Herr B

Proper
May 29, 2020
165
33
190
10
Agree. Vendors usually do that whithout any questions.
By the fact that you bought different sticks already kind of rules that error out to me. The fact that the two sticks should not match well can be easily ruled out by just testing one stick at a time.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
By the fact that you bought different sticks already kind of rules that error out to me.
They are actually the same sticks; the same part number, frequency, timings. etc. They are identical sticks, just weren't being sold as a single kit. Before buying those sticks I had the same problems with another kit of ram sticks.
 

Herr B

Proper
May 29, 2020
165
33
190
10
I have had many BSOD experiences with tools such Driver easy. BSODS most of the times hint to driver issues.

  1. Load stock settings in Bios (to evade all possibly incorrect settings here)
  2. Fresh windows install formatting the harddrive (to evade all possibly corrupt driver installations - removing old drivers does not always work)
  3. Get drivers from Oem website and install them
That's the first steps I'd do as an IT technician in order to make sure all drivers are set up properly and I do not have to deal with any faulty residue from previous experiments.

Most oems webpages are having the very same navigation leading to the drivers:
Manufacturers Webpage -> support -> Drivers and downloads

Once you did that you can be fairly sure there is a hardware issue.

If possible, send link to minidump file. Minidump contains the basic bsod information. Its normally located in C:\Windows\minidump
 

Vic 40

Titan
Ambassador
Your motherboard requires a bios update to level P2.0 to support your processor.
https://www.asrock.com/mb/AMD/B450M Pro4-F/#CPU
'Something odd about this, it seems to be necessary to update to at least 2.00 to make the 1600 12nm work, but at the same time they say not to update to it when using pinnacle ridge which the 1600 12nm is .....

Maybe OP should ask support of Asrock what the hell that means. Don't know if he has upgrade the bios above this 2.00 which likely should be better for ram compatibility.

Could also be that the motehrboard just doesn't work right or even the memory controller on the cpu when having faults in memtest86. Although even memtest itself can get it wrong. You tested the sticks without overclock/ XMP enabled?


I set voltage to 1.3v and it made the system even more unstable.
Sure that was Dram voltage? Should be fine upt to 1.35V and even 1.4V should work.
 

blablaalb

Commendable
Sep 29, 2018
51
0
1,530
0
'Something odd about this, it seems to be necessary to update to at least 2.00 to make the 1600 12nm work, but at the same time they say not to update to it when using pinnacle ridge which the 1600 12nm is .....

Maybe OP should ask support of Asrock what the hell that means. Don't know if he has upgrade the bios above this 2.00 which likely should be better for ram compatibility.

Could also be that the motehrboard just doesn't work right or even the memory controller on the cpu when having faults in memtest86. Although even memtest itself can get it wrong. You tested the sticks without overclock/ XMP enabled?



Sure that was Dram voltage? Should be fine upt to 1.35V and even 1.4V should work.
I also was confused by it. Since I already had problems with system stability I updated the BIOS to the latest version, but then downgraded it to the p2.0. The new ram sticks I bought don't have XMP profile.
I'm pretty sure it was DRAM voltage. The VCore option is above ram options and was set to automatic and hadn't touched it. A few days ago I set the VCore Offset to -50 since it was 1.35-1.40v even when system was idle.

It seems like something is wrong with the Ryzen's SMT. With SMT disabled system seems to be more stable. Also the memtest: it doesn' find any errors even with the old ram sticks unless I enable the multithreading. The old ram sticks were tested with memtest for 9 and half hours without multithreading enabled and no errors were found, but if enable the multithreading option (F2) in the memtest then it finds errors within the first hour of running, sometimes within few minutes. I disabled the SMT option in the BIOS and let the memtest run for 2 complete passes with multithreading enabled (F2). It utilized all 6 physical cores and didn't find any errors.
 
Last edited:

ASK THE COMMUNITY

TRENDING THREADS