PC locks up; Kernel-Power Event ID 41, Task 63; RAM suspected as cause

Please provide more information so that the cause of your problem may be diagnosed.

Please restart your computer and allow 20 minutes for the system to run before uploading information required to help me investigate your problem. When examining Event Viewer log files many, not all, problems show in the period immediately after the computer has been booted.

Please provide a copy of your System Information file. To access your System Information file select the keyboard shortcut Win+R, type msinfo32 and click OK . Place the cursor on System Summary. Select File, Export and give the file a name noting where it is located. Click Save. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here. If the report is in a language other than English, please state the language.

Please upload to your OneDrive and share with everyone a copy of your System log file from your Event Viewer and post a link here. Please remove any earlier copies of the logs from your OneDrive.

To access the System log select the keyboard shortcut Win+R, type eventvwr.msc and press the ENTER key. From the list in the left side of the window select Windows Logs and System. Place the cursor on System, select Action from the Menu and Save All Events as (the default evtx file type) and give the file a name. Do not provide filtered files. Do not place the cursor in the list of reports before selecting Action from the menu. Do not clear logs whilst you have a continuing problem.

Please download Speccy and upload a copy of the report it produces to OneDrive. To obtain a report select File, Save as Text file. It helps to obtain the report at a time when the system is under pressure and temperatures may be higher than normal:
http://www.piriform.com/docs/speccy/using-speccy

For help with OneDrive see paragraph 9.3:

http://www.gerryscomputertips.co.uk/MicrosoftCommunity1.htm

It would be helpful to me if in the future you broke down those instructions into numbered steps. I.e.:

Step 1: Press Win+R and enter in msinfo32

Step 2: Etc etc.

Here is the link to the MSInfo file.
https://1drv.ms/t/s!AnVJiqu_y0kghXsjGFLpVWg5Vm4U

Here is the link to the Event Viewer log.

https://1drv.ms/u/s!AnVJiqu_y0kghXw9-mwhIu5A02e6

Here is the link to the Speccy report.

https://1drv.ms/t/s!AnVJiqu_y0kghX1caXUAkRKhehh8

Update the Realtek LAN Driver to version 10.1.505.2015:

http://dlcdnet.asus.com/pub/ASUS/lan/Realtek_LAN_Win7-81-10_V792-838-101.zip?_ga=1.187474477.420918933.1468246909

Update the Intel(R) Gigabit Ethernet Driver to version 20.5.150.0:

http://dlcdnet.asus.com/pub/ASUS/lan/Intel_Gigabit_Ethernet_Win7-81_V205510_Win10_V205150.zip?_ga=1.178348833.420918933.1468246909

You were having problems with the Nvidia Graphics driver and this caused blue screen errors. You have recently updated the driver and it is not clear whether any of the crashes occurred after the updated driver was installed. If you experience any further crashes please let me know.

Update the Realtek LAN Driver to version 10.1.505.2015:

http://dlcdnet.asus.com/pub/ASUS/lan/Realtek_LAN_Win7-81-10_V792-838-101.zip?_ga=1.187474477.420918933.1468246909

Update the Intel(R) Gigabit Ethernet Driver to version 20.5.150.0:

http://dlcdnet.asus.com/pub/ASUS/lan/Intel_Gigabit_Ethernet_Win7-81_V205510_Win10_V205150.zip?_ga=1.178348833.420918933.1468246909

You were having problems with the Nvidia Graphics driver and this caused blue screen errors. You have recently updated the driver and it is not clear whether any of the crashes occurred after the updated driver was installed. If you experience any further crashes please let me know.

How are outdated LAN drivers causing lockups? I will try your solution, but I would like you to connect the line between these lockups and my network adapter.

 

We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here

If you have any questions about the procedure please ask

There are no DMP files. The crashes are not BSODs. There were no dumps recorded.

Sorry but you are incorrect  If a bug check code is created you did indeed blue screen

<Data Name="BugcheckCode">0</Data>
    <Data Name="BugcheckParameter1">0x0</Data>
    <Data Name="BugcheckParameter2">0x0</Data>
    <Data Name="BugcheckParameter3">0x0</Data>
    <Data Name="BugcheckParameter4">0x0</Data>
    <Data Name="SleepInProgress">0</Data>
    <Data Name="PowerButtonTimestamp">131126581207117100</Data>
    <Data Name="BootAppStatus">0</Data>

If there are no dump files your machine may not be configured to enable them.  Check the wiki for the correct configuration

Killian

ZigZag is correct.

You have had blue screen errors as listed below:

Error 09/07/2016 15:48:57 BugCheck 1001 None
Error 08/07/2016 00:27:20 BugCheck 1001 None
Error 09/06/2016 18:03:31 BugCheck 1001 None

You may not have dump files and if you do not have we need to find out why.

A good place to start checking. Please open cCleaner and uncheck the box before Memory Dumps. It is the fourth item in the System section on the Windows tab. 

Killian

ZigZag is correct.

You have had blue screen errors as listed below:

Error 09/07/2016 15:48:57 BugCheck 1001 None
Error 08/07/2016 00:27:20 BugCheck 1001 None
Error 09/06/2016 18:03:31 BugCheck 1001 None

You may not have dump files and if you do not have we need to find out why.

A good place to start checking. Please open cCleaner and uncheck the box before Memory Dumps. It is the fourth item in the System section on the Windows tab. 

This would be the culprit, would seem. Automatic cleaning was also enabled, and so was probably cleaning the dumps before I could copy them, as you say. I have disabled both. If further crashes happen, and dumps are collected, I will post them here. Thank you.

I've also been informed that the WILLIAMETTE service is related to the Intel Driver Update Utility, and have been advised to uninstall it. I have done so.

Things were running smoothly for a few days after updating the network adapter drivers and disabling the one network adapter not in use. However, as before, after extended use with multiple applications open at once, the system responsiveness very quickly slows to a crawl (takes about ten seconds or so before the Numlock key no longer makes the LED blink and the mouse cursor won't move anymore) before rebooting. And, as before, no DMP files were saved to C:\Windows or Windows\Minidump. The Bugchecks may indicate a Blue Screen error, but I haven't seen any blue screen nor was the time between lockup and auto-reboot sufficient for any dump info to be collected. The wiki explaining how to make sure dumps are enabled also speaks of the page file. I've looked at my page file settings and see that instead of the recommended 2900MB, it's been set to 200MB. I would increase this, to the recommended settings, but I don't know how this would affect the lifetime of the SSD disk.

Event Viewer shows only the same Kernel-Power event ID, with no additional information.

Here are the refreshed logs.

Event Viewer:

https://1drv.ms/u/s!AnVJiqu_y0kghgDEiESDUOSyoY0Q

MSInfo32:

https://1drv.ms/t/s!AnVJiqu_y0kghX-u2GJ-lFnB1kuL

Speccy:

https://1drv.ms/t/s!AnVJiqu_y0kghX4P2-rrgQf8LNrb