Windows 10: Critical Error - PC Shutdown & Reboot

Hi,


I seem to be having an issue where my PC Randomly shuts down & reboots, only while playing games - from new to old. This is always at random, sometimes a few minutes in or maybe even hours. I am fairly confident in saying it is not a hardware issue, I use my desktop for very intensive 3D rendering for hours sometimes days in length & never any issues.


Here is a log on the event viewer -


- File System Filter 'FileInfo' (10.0, ‎2041‎-‎01‎-‎31T08:18:31.000000000Z) has successfully loaded and registered with Filter Manager.

- File System Filter 'Wof' (10.0, ‎2098‎-‎02‎-‎02T18:47:11.000000000Z) has successfully loaded and registered with Filter Manager.

- Volume C: (\Device\HarddiskVolume6) is healthy. No action is needed.

- File System Filter 'aswSP' (10.0, ‎2019‎-‎09‎-‎26T13:45:52.000000000Z) has successfully loaded and registered with Filter Manager.

- File System Filter 'aswSnx' (10.0, ‎2019‎-‎09‎-‎26T12:43:54.000000000Z) has successfully loaded and registered with Filter Manager.

- File System Filter 'FileCrypt' (10.0, ‎2034‎-‎08‎-‎13T15:30:12.000000000Z) has successfully loaded and registered with Filter Manager.

- File System Filter 'npsvctrig' (10.0, ‎2037‎-‎02‎-‎23T07:11:04.000000000Z) has successfully loaded and registered with Filter Manager.

- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.



Here is a view of the events with time and event ID's.

https://gyazo.com/7586f0c3409f5f38a8c5f78fdf9d6501


Kind Regards,

Sam

:)

 

Critical error messages in event viewer after each shutdown


I'm getting a trio of critical error messages in event viewer after each shutdown:

- "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."

- "Windows failed fast startup with error status 0xC00000D4."

- "The previous system shutdown was unexpected."

The PC starts up fine and seems to shut down very fast - within 10-12 seconds, and there seems to be no issues with startup or shutdown. But when I stumbled onto these critical messages in event viewer I got concerned. What could be triggering this? How do I troubleshoot this? They are logged in event viewer after each shutdown/reboot.

 

PC reboots (no BSOD) on CPU stress

Hi fellow TPU members,

not too long ago, the box my gf's PC was transported in gave way on the stairs. Yes, you got it right, that sent a PC tumbling down a flight of steps alright.

Stuff broke. Also, stuff remained intact somehow.

I bought her a new case, new CPU cooler and we removed the floppy drive, so far so good. But the PC started crashing for no apparent reason, without a BSOD.

I tested:

• Memtest86+, left overnight, 0 errors
• Scanned the HDD for errors, nothing there
• Left FurMark burning up the GFX card and drawing some power, no problems there
• Ran Ubuntu from a Live CD doing nothing special, didn't crash
• Ran OCCT, Linpack, Prime95, all 3 caused reboots within minutes
• Oh, and I disabled "Restart on error" so I'm sure it's not a BSOD.

Now, I can still try and test something CPU intensive on Ubuntu, but my guess is the CPU didn't survive.
Before I do anything drastic like whippin' out the magic wallet and get her a new AMD quad, is there anything I didn't see?
I'm guessing the motherboard could be borkered as well, but can I check that other than replacing the CPU with a working one?
Any suggestions on which proggies I can use from an Ubuntu Live CD to stress the CPU?

 

Critical error Event ID 41 after every shutdown and bootup.


I have done what you said, and I still receive the same error. It can happen once a day, once a week, or several times in the same day.

The computer only lists the error after shutdown, My PC does not loose power during normal usage. From a bystander`s
perspective everything is ok.

What I am asking is this: Does windows lists the error as a false positive ? Or does the PC actually somehow looses power during shutdown ?