[SOLVED] Windows 10 isn't logging WHEA errors

[sunset_boulevard3]

I have a new Ryzen 9 5900X running at stock settings and DOCP at 3200Mhz with manufacturer provided timings. I'm getting constant WHEA BSOD's while gaming in specific titles. Now from my research the chip looks like it's faulty, however for the RMA process I need to be able to provide at least some proof that CPU is the cause. Since windows cannot write a dump in this case, my only option is the Event Viewer, which doesn't record WHEA events at all. From what I've seen it should be able to, as users with the same exact problem got their logs, but I cannot for the life of me make it work. However I'm getting a few "PerfDiag" related errors that indicate the log file size is full? Can that be the reason?

 

[Colif]

WHEA errors are normally recorded in the Memory.dump file that is on the root of C drive. The size of the dump file is only restricted by your page file size on C drive, so if you didn't change it or touch it, it should be around the same size as your ram, but that can depend on usage.

If you want to test CPU, I would run Prime 95
download: https://www.guru3d.com/files-details/prime95-download.html
Prime 95 how to Guide: http://www.playtool.com/pages/prime95/prime95.html

Its best we have since AMD don't have a tool to test their CPU with.

WHEA errors can be any hardware, its an error called by CPU but not necessarily caused by it. I have seen other causes before, sometimes it can be drivers.

 

[sunset_boulevard3]

WHEA errors are normally recorded in the Memory.dump file that is on the root of C drive. The size of the dump file is only restricted by your page file size on C drive, so if you didn't change it or touch it, it should be around the same size as your ram, but that can depend on usage.

If you want to test CPU, I would run Prime 95
download: https://www.guru3d.com/files-details/prime95-download.html
Prime 95 how to Guide: http://www.playtool.com/pages/prime95/prime95.html

Its best we have since AMD don't have a tool to test their CPU with.

WHEA errors can be any hardware, its an error called by CPU but not necessarily caused by it. I have seen other causes before, sometimes it can be drivers.

Solved temporarily by setting SOC to 1.1v, CCD to 0.900v, and IOD .950v. Will be asking for a refund, the chip is definitely defective.