Replies

It is worth looking at Thunderbird bug 1577548, which , I believe, I opened.  The fix was included in Thunderbird around November, 2021.  The problem was that Thunderbird, during a POP3 attempt at downloading new mail, received a “-ERR [SYS/TEMP] Server error – Please try again later.”  message, which Thunderbird did not parse correctly.  This caused Thunderbird to stop checking for new mail until Thunderbird was stopped and restarted.  I had this problem for many years,  and everyone online told me that the mail server must have been down until (magically) I restarted Thunderbird.  I knew that the problem would vanish when I restarted Thunderbird, whether it was one minute or 24 hours since the failure.  I do not have the version of Thunderbird that contained the fix, as I was running at that time the Daily build to test new fixes.

This topic has migrated to the AskWoody thread “BSOD VIDEO_TDR_FAILURE (116)“.

In response to four 116 BSODs in one hour (cause not resolved, but not repeated), I re-seated the two memory sticks (actually interchanged them) and checked the power connections to the motherboard.  My last auto-reboot was 07/23/2022 08:17, before I shut down to do the re-seating.  See what I have posted there.

OHM says that the max temp for each core is 212 degrees F.

My last auto-reboot was 07/23/2022 08:17, before I shut down to re-seat the memory and check the power connections to the motherboard.  I just ran a full Defender scan, which took 29 minutes (09:44 – 10:13) and got all six CPU cores to over 150 degrees F.   For most of the time all six cores were running at 100%.  I have attached the OHM log file; the temps logged are in Celsius.

My short memory test was done ONLY to ensure that I had properly re-inserted the two sticks of memory in their slots.  I was assuming, maybe incorrectly, that if the memory stick had not been installed properly, then memtest would fail almost immediately.  I do not know if there is any memory test during boot, so I do not know if incorrectly installed memory would cause a failure.  I assume that the Windows 10 operating system, which needs memory, would fail at some point while starting.  On July 3 I ran memtest for 4.0 hours without a problem.  It was in pass 2 of 4 when I terminated to reboot back into Windows 10.

I installed the July updates this morning to Windows 10 64-bit 21H2.

KB890830 Malicious Software Removal Tool (Jul 2022) MRT.exe
KB5015730 2022-07 Cumulative Preview Update .NET 3.5 & 4.3 for Win 10 21H2
KB5015807 2022-07 Cumulative Update for Win 10 v21H2 x64

The Win 10 21H2 preview was optional, but the .NET preview was NOT optional, so I had to install it.  I have no idea why Microsoft put this preview patch as required.

1 user thanked author for this post.

Coldheart9020

On another forum someone suggested checking the power connections.  After I installed the July updates this morning,  I checked the power connections on the motherboard.  I will see if I experience any m ore auto-reboots.

I had two auto-reboots today.  The first at 04:48, when I was asleep (or maybe listening to weather alerts on my radio).  I got to my machine around 8:10, and after I logged in and while I was starting the applications needed for a Zoom session, at 08:17 there was another auto-reboot.  I did not have time to do anything then, so at 21:10 this evening, (after the failed TPM settings test above), I shut down.  I interchanged the two memory sticks, and I rebooted into memtest to test the memory for 2.5 minutes.  Then I rebooted into Windows 10.  The machine did not auto-reboot between 8:17AM and the time I did the memory exchange at 21:10.

I was logging OHM every two minutes, and I have attached a copy of the log for today.  I did not see any temperature spike at the end, but I have not reviewed the log in detail.  I have changed the logging from 2-minute intervals to one-minute.  But I cannot tell from the System Event Log exactly when the auto-reboot occurred. 04:39:22 is the timestamp of the first entry after the reboot, but EventID 6008 says, “The previous system shutdown at 4:02:09 AM on ‎7/‎23/‎2022 was unexpected.”  And I know that if the reboot was at 04:02, the restart would have put the machine in the login screen within a minute.  So I have no idea from where the time in the 6008 Event Log record was retrieved.  And the last entry in the OHM log is 4:38:23.

 

“What I will do (at the next reboot): Run Settings > Update & Security > Recovery and select Restart now under Advanced startup.
From the next screen, select Troubleshoot > Advanced options > UEFI Firmware Settings > Restart to make changes.”

I tried, and, (as I might have expected), these instructions did not work.  Maybe they are wrong or written for a different level of Windows 10.  I tried the first line, and when I came to “Restart now”, the compute4r started a reboot.  I did not get into the “next” screen.  So, at this point I have no idea what to try next.

I have not manually shutdown to re-seat power cables and the two memory sticks, as I assumed that the machine would reboot on its own, and then I could shutdown to do the “maintenance”.   If I run a few weeks without an auto-reboot, then I will power-down and do the maintenance, including the TPM stuff, above.

Maybe my CPU chip has ESP and knows that the temps are being monitored and logged 🙂
I have not had an outage since I started logging, but I have gone this long without an auto-reboot before, as per my reboot log:

04/02/2022 04:17 Auto-reboot
04/02/2022 16:55 Auto-reboot
04/03/2022 20:58 Auto-reboot
04/03/2022 22:53 Auto-reboot
04/04/2022 08:04 Auto-reboot
04/04/2022 08:09 Auto-reboot
04/09/2022 04:21 Auto-reboot
04/17/2022 14:58 Auto-reboot
04/17/2022 16:56 Auto-reboot
04/18/2022 09:19 Auto-reboot
04/19/2022 11:22 Auto-reboot
04/20/2022 16:49 Auto-reboot
06/26/2022 10:46 Auto-reboot
06/26/2022 16:07 Auto-reboot (during full Defender scan)
06/28/2022 09:56 Auto-reboot (while connecting blue Passport disk)
06/28/2022 11:27 Auto-reboot (while closing front panel)
06/28/2022 14:51 Auto-reboot
06/28/2022 15:02 Auto-reboot
07/02/2022 01:59 Auto-reboot
07/02/2022 08:34 Auto-reboot
07/03/2022 11:08 Auto-reboot
07/03/2022 11:23 Auto-reboot
07/03/2022 11:31 Auto-reboot
07/04/2022 09:39 Auto-reboot (while connecting blue Passport disk)
07/10/2022 00:09 Auto-reboot
07/11/2022 09:11 Auto-reboot (while connecting yellow Passport disk)
07/11/2022 18:35 Auto-reboot
07/13/2022 10:26 Auto-reboot
07/14/2022 04:09 Auto-reboot
07/14/2022 18:33 Auto-reboot
07/15/2022 04:38 Auto-reboot
07/15/2022 08:21 Auto-reboot
07/16/2022 11:00 Auto-reboot
07/17/2022 03:01 Auto-reboot
07/17/2022 10:01 Auto-reboot

01) System Log EventID 15 – TPM (10:02:07AM)
The device driver for the Trusted Platform Module (TPM) encountered
a non-recoverable error in the TPM hardware, which prevents TPM
services (such as data encryption) from being used. For further help,
please contact the computer manufacturer.
locationCode 0x1c0004f3

02) System Log EventID 1282 – TPM-WMI (10:02:23AM)
The TBS device identifier has been generated.

03) System Log EventID 1282 – TPM-WMI (10:02:23AM)
The Trusted Platform Module (TPM) hardware on this computer cannot be
provisioned for use automatically. To set up the TPM interactively
use the TPM management console (Start->tpm.msc) and use the action to
make the TPM ready.

Error: The operation completed successfully.
Additional Information: 0x80000

04) tpm.msc
Status +
The TPM is ready for use.

05) PC Health Check:
“This PC must support Secure Boot”

It appears that some of these statements are contradictory.  What I will do (at the next reboot): Run Settings > Update & Security > Recovery and select Restart now under Advanced startup.
From the next screen, select Troubleshoot > Advanced options > UEFI Firmware Settings > Restart to make changes.

1 user thanked author for this post.

satrow

I am now logging temps with OHM every two minutes.  When I get another reboot, I will check the log and re-seat the memory.  When I have been at my computer during auto-reboots, there is nothing CPU-intensive happening, as far as I can tell.  I also will check the TPM setting in the BIOS, as I am getting conflicting info on the status of my TPM.

“I hope that you can find out whether Zoom is the problem causing software, it could be searching only Zoom’s forums again shows complaints but perhaps no solutions.

“The USB driver may be fine as is, it might not cause harm to update them as the drivers cover a range of chip set models. Although wait until the Zoom issue get resolved before introducing another potential issue. Intel’s utility should tell you if a driver needs replacement although sometimes you will need to search for driver manually.

“Has this different Passport drive caused other computer to auto-reset (spontaneous reboot?) or only this one?”

My replies: I have used Zoom a number of times since, and I have not experienced any further 116 BSOD outages.

Intel(R) Driver & Support Assistant reports, “No supported driver or software updates are available for your system.”

I have two Passport drives that I use once a week for backups.  I have had outages with both, but I have never had outages with both on the same day.

These two external hard drives are used ONLY on this computer; I do not use them on the Win 8,1 laptop that I manage.

One further question.  I am assuming that the auto-reboots are initiated by the CPU chip, which may be sensing overheating.  These are not Windows-initiated BSODs, as there is no mi minidump produced and no traditional BSOD screen from Windows stating that a problem has occurred.  Is there any other hardware that would cause these auto-reboots?  My brother suggested that, since the 116 BSOD minidumps point to memory corruption, that I re-seat the memory and/or interchange the two sticks in the slots.  Could memory cause these reboots?  I do not see how, but I am not an expert in PC hardware.  Thanks.

If I were to open the case and look at the existing thermal paste, how can I tell if what I have is adequate for the surface area of the CPU chip?  One of my brothers thinks that I need a new case with better cooling.  The temperatures now are 100-104 degrees F.  But this morning at 4:09 the machine reset (while I was sleeping), and I have no idea what the temperatures were at that time.