The computer crashed and generated a BSOD on 12 July 2017
The System log from Event Viewer shows these Event ID 41 "Critical" errors:
16 July x 2
15 July x 3
11 July x 2
10 July x 4
Event ID 41 is Windows saying it doesn't know why the system shut down (more info on it here: http://support.microsoft.com/kb/2028504 )
It occurs after the reboot, so searching the times prior to the reboot is where you might find evidence of why it crashed.
In these cases tho', lack of that evidence is usually indicative of a hardware problem (if Windows crashes, it usually knows enough to leave traces of the crash in the error logs - but with hardware crashes the effects of the bad hardware may cause the OS to crash before it can generate an error).
I don't scan any deeper with the text versions of the Event Viewer logs as it's very labor intensive. I usually ask for a copy of the Admin log so that I can sort the errors in the MMC Event Viewer
Here's my canned speech for that:
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 monitor your temps with this free utility:
SpeedFan v. 4.5.1 and later (free from here: http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:
You may not need to log temps. If uncertain, please ask.
NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.
To make it work (log the temps to a file) you have to do BOTH of the below:
1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.
2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.
The log will be located at C:\Program Files (x86)\SpeedFan
Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.
Notes: whenever you change the options related with logging, SpeedFan starts a new log file.
How do you know that the STOP 0x101 BSOD was due to overclocking? Although I haven't seen it recently, there was an application called TurboBoost (for Intel processors) that would automatically overclock the processor. It was a mild overclock and generally conformed to the specs put forth by Intel for this purpose. I had never seen it cause a problem (but I suppose that it was possible).
I don't scan of overclocking as a part of my analysis. If the CPU is marked as being overclocked in some of the reports, then I'll mention it. If it's not, I generally only look for certain programs that are suggestive of overclocking (AMD Overdrive, MSI Afterburner, Riva Tuner, etc).
As for the customer lying to you - it is possible, but it's not very common and is extremely unlikely.
Who would have the money to do this, and would also want to lose their computer while you have it?
IMO the most likely thing here is a hardware problem (and I don't see any hard evidence of a software problem).
Another option is to have them run the Speedfan log (from my canned speech above) and then look to see if it's an overheating problem.
How about making a house call? That'd serve to put the issue of crashes at home to rest.
Maybe try another computer at home - to see if that one crashes also?
My thoughts here revolve around the fact that it does not crash at your shop - yet the customer claims that it crashes in a few minutes.
The Event Viewer crashes tends to support this thought pattern (with the number of Event ID 41 crashes).
As such, it's most likely something environmental.
Just another thought, maybe there's a loose cord/wire between the PC and the wall plug.
Accidentally nudging it with a toe or chair leg could cause the power to be interrupted - thereby causing the system to crash.
1) Test the cord that the owner uses to plug it in.
2) Then have them use a different surge protector and a different wall socket to plug the computer in.
And see if that helps.
Another test would be to move the computer to another room in the house and see if it has problems there.