F5F Stay Refreshed Hardware Desktop PC shutting down, restarting and resetting time, launching default Windows desktop upon login

PC shutting down, restarting and resetting time, launching default Windows desktop upon login

PC shutting down, restarting and resetting time, launching default Windows desktop upon login

X
Xenoram
Member
Find
82
06-05-2023, 02:23 PM
#1
I'm unsure where this would lead because there isn't a dedicated "troubleshooting" forum. What's occurred is that recently, every time I switched my system, it would restart within ten seconds and then log in. After logging in, I'd see the time since the last shutdown without any automatic adjustment. It usually worked when left on, and it didn't cause issues in sleep mode. I thought the motherboard battery might be the issue, especially since the clock behavior seemed affected.

This issue didn't seem to happen much before I updated the motherboard's BIOS to the latest version. It stopped for a few days until it rebooted shortly after loading Windows. The reboot was followed by the monitor flickering and the screen displaying garbled text. I noticed this problem also appeared last year, along with other artifacts. I attributed it to GPU sag after moving the system into a new case, which removed the anti-sag support I had before. I've since replaced the anti-sag bracket and updated the GPU drivers, but nothing has changed yet.

I'm hoping the problem is resolved by replacing the motherboard battery or by fixing the new GPU drivers. Anyone have suggestions?

Specs
B760 Tomahawk DDR4
32GB Kingston Fury Beast 3200MHz
12700KF running stock
Fractal Lumen S24 (planned upgrade)
Thermaltake GF-3 1650
TUF 3080
Reply
Reply
X
Xenoram
06-05-2023, 02:23 PM #1

I'm unsure where this would lead because there isn't a dedicated "troubleshooting" forum. What's occurred is that recently, every time I switched my system, it would restart within ten seconds and then log in. After logging in, I'd see the time since the last shutdown without any automatic adjustment. It usually worked when left on, and it didn't cause issues in sleep mode. I thought the motherboard battery might be the issue, especially since the clock behavior seemed affected.

This issue didn't seem to happen much before I updated the motherboard's BIOS to the latest version. It stopped for a few days until it rebooted shortly after loading Windows. The reboot was followed by the monitor flickering and the screen displaying garbled text. I noticed this problem also appeared last year, along with other artifacts. I attributed it to GPU sag after moving the system into a new case, which removed the anti-sag support I had before. I've since replaced the anti-sag bracket and updated the GPU drivers, but nothing has changed yet.

I'm hoping the problem is resolved by replacing the motherboard battery or by fixing the new GPU drivers. Anyone have suggestions?

Specs
B760 Tomahawk DDR4
32GB Kingston Fury Beast 3200MHz
12700KF running stock
Fractal Lumen S24 (planned upgrade)
Thermaltake GF-3 1650
TUF 3080

Reply
Reply
R
Raptowulf
Junior Member
Find
6
06-13-2023, 11:55 PM
#2
Check the Reliability History/Monitor and Event Viewer for any error codes, warnings, or informational events recorded around the times of the issues.
= = = =
Begin by changing the CMOS battery using the Motherboards User Guide/Manual.
Make sure the system is receiving accurate date and time data from a reliable source.
If swapping the battery resolves the issue, everything should work fine.
If the problems persist, proceed with additional troubleshooting steps.
For example:
Execute the built-in Windows Troubleshooters; they might identify and resolve the problem.
Run "dism" and "sfc /scannow" to detect and repair corrupted files.
Also confirm that all critical data is backed up at least twice in separate locations away from the affected computer.
Double-check that these backups are accessible and readable.
Just in case...
Reply
Reply
R
Raptowulf
06-13-2023, 11:55 PM #2

Check the Reliability History/Monitor and Event Viewer for any error codes, warnings, or informational events recorded around the times of the issues.
= = = =
Begin by changing the CMOS battery using the Motherboards User Guide/Manual.
Make sure the system is receiving accurate date and time data from a reliable source.
If swapping the battery resolves the issue, everything should work fine.
If the problems persist, proceed with additional troubleshooting steps.
For example:
Execute the built-in Windows Troubleshooters; they might identify and resolve the problem.
Run "dism" and "sfc /scannow" to detect and repair corrupted files.
Also confirm that all critical data is backed up at least twice in separate locations away from the affected computer.
Double-check that these backups are accessible and readable.
Just in case...

Reply
Reply
B
berke1010
Member
Find
147
06-18-2023, 12:22 AM
#3
Didn't realize reliability history existed. I'm recalling the 30th of May. A consistent pattern appears from that date: LEDKeeper2 stopped functioning, Windows updates triggered warnings (which also verify successful updates in event logs). Many instances of "windows was not properly shut down" despite always closing normally when I choose shutdown from power settings. Currently, I notice two hardware errors in critical events, a BAD_DUMPFILE, and "LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere". None of these signatures make sense to me since I'm not a coder.
Reply
Reply
B
berke1010
06-18-2023, 12:22 AM #3

Didn't realize reliability history existed. I'm recalling the 30th of May. A consistent pattern appears from that date: LEDKeeper2 stopped functioning, Windows updates triggered warnings (which also verify successful updates in event logs). Many instances of "windows was not properly shut down" despite always closing normally when I choose shutdown from power settings. Currently, I notice two hardware errors in critical events, a BAD_DUMPFILE, and "LKD_0x117_Tdr:A_IMAGE_nvlddmkm.sys_Ampere". None of these signatures make sense to me since I'm not a coder.

Reply
Reply