Random shutdowns, sfc /scannow returns corrupted files, fresh install

Egomachina · 01 Aug 2019

Hello everyone, yet again another sfc /scannow thread...

This one comes with random computer shutdowns, no matter what I'm doing or what processes are launched (game, windows explorer or web browser).

When the computer crashes, it just shuts down, like if the power cable was removed, generating no bsod logs.
I have tested the temperatures and stress tested the cg, processor and memory but to no avail.

Tried updating every driver to no avail, also tried reinstalling the system, cleaned the hard drive it was installed on, installed the latest drivers for my hardware and uninstalled the basic windows amd drivers with DDU, still random shutdowns.

The only info I can find about this is a 6008 error in the event viewer, nothing else is provided.

Maybe there is some information in the CBS.log file, I have trouble differentiating which lines are actually causing an error from the ones about fonts... The latest crash occured at 18h52 if it can help.

I tried everything I could think about, please help me

Sorry about the .7z attachment, its size is over 2MB so I couldn't just post it. Cheers :)

Edit : I now realize I may have posted this in the wrong forum category... Sorry about that

jdc1 · 01 Aug 2019

Shutdowns without error messages usually signify a hardware problem.
Continued problems after a clean install of W10 also usually suggest a hardware problem.

Start with these:
1) Memtest86 (not 86+): MemTest86 - MemTest86 - Official Site of the x86 Memory Testing Tool

2) SeaGate SeaTools for Windows (test ALL hard drives - HDD/SSD/USB/etc): How to use SeaTools for Windows | Seagate Support US

3) Intel Processor Diagnostic Tool: Download Intel(R) Processor Diagnostic Tool
Disregard if not using an Intel processor

4) Furmark stress test for GPU: FurMark > Downloads
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

5) OCCT: OCBASE / OCCT
Read the instructions carefully and watch your system when testing.
If it starts spitting out problems and you can't shut it down - simply turn the system off/unplug it from the wall

If these hardware tests don't find anything, then you'll have to start troubleshooting by removing parts. Here's a page that describes this: Hardware Stripdown Troubleshooting
Although it's old, it's still relevant in these situations.

Good luck!

Egomachina · 01 Aug 2019

I suspect a hardware malfunction too :).

I will try those tests, thank you very much !

- - - Updated - - -

None of the tests found any error, I guess it's hardware related then. Off to tests parts then.
Thank you for your help jdc1, it is very appreciated. :)

I'm closing the thread