- Restart SW,
- Changing SATA power cable,
- Looking at condensators in power supply
Jump to content
Posted 19 May 2016 - 10:17 AM
Posted 19 May 2016 - 10:38 AM
Check the event logs and it should show if there was a power interruption or if something else may be causing it.
Posted 19 May 2016 - 10:42 AM
With every reboots, event logs shows:
Critical Kernel-Power 41
Warning Kernel-PnP 219 The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000.
Posted 19 May 2016 - 10:55 AM
It's possible your power supply may be failing. I input your specs into a power supply calculator and was getting 400W minimum and you have a 600W so you should be covered on power needs. I would recommend taking canned air to it if you haven't done maintenance in a while and also try reseating the power connections on the MB and other devices. If the issue continues I would recommend swapping out the power supply and if that doesn't resolve the issue you may have a malfunctioning motherboard.
Posted 19 May 2016 - 11:13 AM
Did reseating, will try canned air. I'll have access to voltage meter and another ps in june.
Posted 21 May 2016 - 04:33 AM
Wait for the next random reboot, then get back into Windows and let's try looking at these 2 sets of reports:
1) Please run this report collecting tool (even though you may not be reporting BSOD's) so we can provide a complete analysis: http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location.
By default it'll be a .zip file located on your Desktop
Simply upload the .zip file with your next post and we'll move on from there.
If it doesn't work for you, then please try this: http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/
2) Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).
FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here: http://support.microsoft.com/kb/2028504
While waiting for a reply, please continue to monitor your temps (although the system doesn't appear to have temperature issues from your screenshot)
Posted 22 May 2016 - 04:39 AM
Unfortunately it appears that the system has pirated software.
Please get a legitimate copy installed and we'll be glad to help.
Here's suggestions on how to ensure that your version is legitimate: http://windows.microsoft.com/en-us/windows/genuine
Please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.
As a courtesy, I will offer an analysis of your issues using the reports you provided.
I will not answer any questions about the analysis until the system is made legitimate.
If you do make it legitimate, please submit a new set of reports for us to check.
The Admin logfile doesn't show much of anything in the events prior to the unexpected shutdown.
Usually this is a sign of a hardware problem - but can also be due to compatibility issues or low-level drivers
Please start with these free hardware diagnostics: http://www.carrona.org/hwdiag.html
There may be a pattern relating to the "The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000." warning message - but I'm uncertain about it.
This error usually refers to a portable device attached to the system - so I'd disconnect any connected devices (such as USB/Firewire/etc)
Your UEFI/BIOS (version F8f) dates from 2013. Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system. If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it. WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
Only 7 Windows Update hotfixes installed. Most build 10586 (TH2/1511) systems have more than this. Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important. Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.
AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows systems.
NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program.
Please note that I stated "video stuff", as some integrated processors may have the graphics chip built in (which may involve the chipset software).
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://www.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: http://www.sysnative.com/forums/showthread.php/668-ATI-video-cards-DRIVER-ONLY-installation-procedure
If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.
If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.
0 members, 0 guests, 0 anonymous users