(Solved) Parity-check found errors

[Arkadin55]

Can someone please take a look at my diagnostics and help me interpret what's going on? Parity check found two errors. Also received message about raw read error rates for one drive and then another message that the rates were returned to normal. The drive with the errors is connected to a controller card and is my most recently added drive. I have also recently installed additional ram. I have done at least one parity-check since installing the drive on the controller and it was fine. I have not had any unclean shutdowns. I plan on checking the cables attached to the problem drive and the seating of the controller card, but was wondering what else I may need to be checking.

 

xanadu-diagnostics-20190118-0937.zip

[trurl]

24 minutes ago, Arkadin55 said:

recently installed additional ram.

Did you do a memtest?

[Arkadin55]

I was planning to but have not yet done so. Should that be my next step?

[trurl]

Well it may be unlikely but bad memory will make everything else bad. Once you get that verified then you can go on to the other things,

[JorgeB]

Is your RAM overclocked? There's been more than one user with ryzen and overclocked memory getting a few sync errors, despite no errors detected on memtest.

 

[Arkadin55]

I had enabled D.O.C.P. and set it at the rated speed for my ram and motherboard on my original ram and never had any problems. I did recently return it to auto after reading in this forum about potential problems other were having. I'm wondering if I should remove the new ram I installed since it's the only thing that's changed since my last successful parity-check. If I do that, should I still run a memtest or should I do another parity-check?

[JorgeB]

You should respect the max non overclock speeds depending on your config:

 

 

Then run another parity check.

[Arkadin55]

Yes, I have returned the ram to non overlock speeds.  I will do a memtest and then post my results. Seems like 24 hours is a commonly recommended amount of time to allow the test to run.

[JorgeB]

33 minutes ago, Arkadin55 said:

Yes, I have returned the ram to non overlock speeds.

I would forgo the memtest for now, run another non correcting check, if still errors see if they are in the same sectors.

[Arkadin55]

Will do. Thanks.

[Arkadin55]

Parity-check just completed with 2 errors on the same sectors as before.

 

 

xanadu-diagnostics-20190119-1039.zip

[JorgeB]

Since they are the same sectors will need to run a correcting check, keep RAM at standard clocks, then run another non correct check in a week or so and hopefully no more errors.

[Arkadin55]

Will do. Thanks for your assistance and prompt replies.

[Arkadin55]

Just wanted to come back and mark this as solved. My most recent parity-check came back with no errors.

 

It seems pretty certain to me that the problem was I forgot to change the ram clock speed after I added an additional 2 dimms. The recommended speeds differ depending on the number of dimms being used. This is a good example of why it's probably just better in most cases to leave your ram at stock speeds.

 

Thanks again @johnnie.black and @trurl for your quick and helpful responses!