The file header checksum does match the computer checksum

[Big Jim]

Dell Optiplex
4th gen I5
1 x 8GB Stick RAM
480GB Intel SSD
W10 Pro (Domain machine)

Google suggests this could be a bad stick of ram, however we are currently on about pass 25 with no errors on memtest
SSD has no bad sectors, and SMART data shows a working drive.
Checkdisk found nothing, neithr did SFC
PRIME 95 ran for over an hour without issue


The computer has apparently crashed and come up with this error a couple of times but a quick reboot had it working again.
It also does it sometimes on boot, before it arrived the error came up and rebooting did not resolve the issue.
Customer brought it to me and it booted fine here when it arrived,


Any ideas ?

 

[Sky-Knight]

Defective SSD, if RAM passes then the SSD must be the culprit. When they fail, they fail like RAM does, and often don't fail actual tests. RMA and support nightmare to be honest, eventually it'll just up and die and you'll know. But between here and there is potentially years of random BSOD.

 

[Big Jim]

its hardly had any use though, is it still a likely culprit ?

 

[wavey]

I would clone the SSD, see what happens.

 

[Sky-Knight]

I've had this happen twice, it's not a common thing. But, in both cases the machines randomly BSOD'd from the time they were brand new. Months, if not years later the SSD finally just up and died, replaced it under warranty in both cases and both units were perfect from then on.

Both machines were also Intel SSDs annoyingly enough, reddit seems to say they have a reputation for this. Perhaps Intel had some bad controllers?

But yeah the only way to test is to clone the SSD to a new one, and let it ride to see if the issue resolves.

 

[Big Jim]

I've had this happen twice, it's not a common thing. But, in both cases the machines randomly BSOD'd from the time they were brand new. Months, if not years later the SSD finally just up and died, replaced it under warranty in both cases and both units were perfect from then on.

Both machines were also Intel SSDs annoyingly enough, reddit seems to say they have a reputation for this. Perhaps Intel had some bad controllers?

But yeah the only way to test is to clone the SSD to a new one, and let it ride to see if the issue resolves.

I assume in this case the original drive not much use for anything ?

 

[Sky-Knight]

If you slap a new SSD in there and the problem is gone, then yes the original drive is defective. Anything stored on it is at extreme risk, and any OS on it will have problems. RMA the thing if possible.

 

[Big Jim]

If you slap a new SSD in there and the problem is gone, then yes the original drive is defective. Anything stored on it is at extreme risk, and any OS on it will have problems. RMA the thing if possible.

This is a refurbished PC (still under our warranty) that i sold to them with a 2nd hand SSD in it
I'll happily replace it with another drive, I was just trying to get as good an idea as possible what was wrong so I don't end up endlessly spending money on it and replacing things that don't need replacing.

I have found a semi-decent brand of SSDs that arent silly expensive that i plan to use in all of our future refurbs meaning that 2nd hand SSDs are pretty much pointless for me now. as the cost of any brand like Crucial/Samsung/Intel/Sandisk 2nd hand is the price I pay for a patriot Burst brand new.

 

[Sky-Knight]

Interesting, well I have to point out once again my two units that did this were brand spanking new when the symptoms first manifested. But, if you got used parts who knows... perhaps the donor machine was tossed because the drive was bad and it went undiagnosed.