Need help, system shuts down after exactly 30 minutes.

[I Love Huskies]

What happens
I start up my system and then it runs for exactly 30 minutes every time before it stops without any warning, there is no blue-screen it just cuts power and shuts off. It does not turn itself back on after, but i am able to turn it on immediately by pressing the power button. The power supply i am using is about 6-7 years old and it could be that, but the time which the computer turns off is exactly 30 minutes, so it makes me think it could be a motherboard problem.

Information i find Relative

My Powersupply
I do not know exactly what power-supply i have because it is a old one from my brothers first PC, it has been working for me just fine for several months and is around 6-7 years old.

My Motherboard
MSI Z87 Mpower

Windows System Logs, on the left is the error and on the right is the description of the error.

HWMonitor Details

Things i have tried

Updating motherboard bios.
Turning off Turbo Boost.
Leaving system off overnight.

I will be checking back every few minutes for replies, thanks.

 

[cin19]

From the system logs, for the error kernel-pnp or other error, those are related to the driver for the device, do you try to update all the drivers for your hardware, like keyboard, add-on card, intel chipset driver, etc.

 

[I Love Huskies]

From the system logs, for the error kernel-pnp or other error, those are related to the driver for the device, do you try to update all the drivers for your hardware, like keyboard, add-on card, intel chipset driver, etc.

I don't think the drivers are what is causing my system to shutdown because it still shuts down even if i leave it in the bios.

 

[cin19]

From the system logs, for the error kernel-pnp or other error, those are related to the driver for the device, do you try to update all the drivers for your hardware, like keyboard, add-on card, intel chipset driver, etc.

I don't think the drivers are what is causing my system to shutdown because it still shuts down even if i leave it in the bios.

When you look at the windows system logs, 8/24/2014 11:50:06 PM warning: "The driver \Driver\WUDFRd failed to load for the device"

So I google the Wudfrd and I found the similar problem like you, if you use the Logitech keyboards/mice, and problem may from them. Try the same method from the link to see you can solve the problem or not. http://chinbim.blogspot.com/2013/02/event-id-219-driver-driverwudfrd-failed.html

 

[I Love Huskies]

From the system logs, for the error kernel-pnp or other error, those are related to the driver for the device, do you try to update all the drivers for your hardware, like keyboard, add-on card, intel chipset driver, etc.

I don't think the drivers are what is causing my system to shutdown because it still shuts down even if i leave it in the bios.

When you look at the windows system logs, 8/24/2014 11:50:06 PM warning: "The driver \Driver\WUDFRd failed to load for the device"

So I google the Wudfrd and I found the similar problem like you, if you use the Logitech keyboards/mice, and problem may from them. Try the same method from the link to see you can solve the problem or not. http://chinbim.blogspot.com/2013/02/event-id-219-driver-driverwudfrd-failed.html

I have done that and the same error still shows up in my Event Viewer. Could this be causing my system to shutdown?

 

[carlo_bigtunes]

it can be overheating hardware...check gpu, cpu, mb temp..
to minimize malfuntion of hardware coz of heat, motherboard shut off automatic without any warning.

 

[I Love Huskies]

it can be overheating hardware...check gpu, cpu, mb temp..
to minimize malfuntion of hardware coz of heat, motherboard shut off automatic without any warning.

I doubt it is heat, my GPU/CPU/MB temps all hover around 30-45c, also it happens EXACTLY 30 minutes after i start up the system whether i am idle in bios, or playing a game in windows.

 

[quantumdogma]

By any chance had you "recently" upgraded your CPU?
I've been having the same issue after upgrading from a Pentium to an i7.
After I switched back to the original CPU the problem stopped.
I've been doing a lot of research and it seems that the issue is actually with the Intel Management Engine.
If you've never heard of it, don't be surprised, neither had I.
It's a subsystem on the newer (2008+) processors that performs tasks during boot-up, while the computer is running, and while it is asleep.
In 2016, the me_cleaner project found that the ME's integrity verification is broken. The ME is supposed to detect that it has been tampered with, and, if this is the case, shut down the PC forcefully after 30 minutes. This prevents a compromised system from running undetected, yet allows the owner to fix the issue by flashing a valid version of the ME firmware during the grace period.
The Electronic Frontier Foundation (EFF) and security expert Damien Zammit accuse the ME of being a backdoor and a privacy concern.
Personally, I have yet to find a way to correct this issue, but I haven't tried flasing a valid version of the ME firmware, but I am still looking. I hope this helps point you in the right direction.

https://en.wikipedia.org/wiki/Intel_Management_Engine
https://hackaday.com/2016/11/28/neutralizing-intels-management-engine/

 

[cin19]

Necro post. Closed.