Did you get Dell paperwork? Maybe in there?
I kept the box and paperwork for about 30 days, then tossed it. I donāt think Iāll be able to tear down the PC until this weekend.
Some (not many)bios display the serial number of the CPU, might be worth checking.
Got to take the cooler off.
Thatās the only place itās usually located unless dell printed/stored it on somewhere else aswell.
It should start with 9R6 and then xxxxxxx numbers.
Seeking a little clarity here. I tried the kill-ryzen.sh script (on Ubuntu 17.04) you posted a couple of days ago to test for the Ryzen segfault bug. It ran for about an hour and a half without crashing, and normally trips within 5 minutes or so. @catsay that makes me doubt that it really is your early adopter bug. I bought this PC in Jan 2018.
Another difference between my problem and the SEGV bug is that bug occurs under heavy load, whereas my crash always occurs when the system is idle, or being prodded out of idle by a mouse click. I thought it might be @noenkenās bug, but mine is not a PCIe error, but an MCE crash.
So Iām not really sure Iāve found the root of the problem. There have been a few theories about problems with PSUs not supporting C6, but that seems far-fetched. The system also came with a single 16GB stick. I bought a āsystem compatibleā stick from Kingston (same as the OEM stick) with the same timings, but Iām starting to suspect it too.
Perhaps I should try Windows for a few days and see if I experience any crashes. If it truly is hardware, I should also see problems with Windows, which I just havenāt used much.
Does it only occur when you have alot of ram in use?
I can tell you I have 32G DDR4 with real nice lean timings and I have experienced a couple weird hardware crashes when Iām at 25+GB of memory in use.
I only use windows 10 soā¦ it could be ram also but I have a R7 1700x and its not my OC or anything.
But I havenāt been able to accurately reproduce it, and now as of recent I have a very weird bug where running any website that contains flash (even if flash is disabled) in any browser instantly takes down the entire system.
Many where affected by a number of issues.
SEGV is just the big one.
There where also:
Freezes - Instant lockups
Hard resets
Memory & Cache corruption issues leading to MCE events
These where caused by
Number of C-state issues in silicon
Cache memory defects
Branch prediction problems
FMA3 load induced voltage drops
I have now tested many Ryzen systems under linux and of all those about 5% had C-state issues as a result of hardware defects resolved only by an RMA.
Some chips that where not affected by the SEGV issue may still encounter the MCE events. The very second chip I had behaved exactly like yours. No MCEās under testing but would randomly at idle hard reset or freeze.
You can try increasing SoC voltage, disabling C6, limiting to C1 max. But in all honesty none of this should be necessary.
Perhaps your mainboard also just needs a bios update?
How the story ended. I have same problem.
Windows never had a problem with the CPU, so I took Linux off the machine. Six months or so later I put it back on, and no problem. Iāve been running the CPU overclocked for the past year or so. Recently I had to reinstate it as my main gaming rig. Doing nicely with a 2070 Super in both OSās.
Mustāve been a bug. Either the kernel code was corrected, or they wrote around a firmware/microcode bug. Very stable now.