F5F Stay Refreshed Hardware Desktop PC freezing regularly every few days can be frustrating.

PC freezing regularly every few days can be frustrating.

PC freezing regularly every few days can be frustrating.

Pages (2): 1 2 Next
F
fwkenxz
Member
64
10-07-2020, 12:31 PM
#1
I've been assisting a colleague with his PC troubles for roughly two weeks. Even with my tech expertise and extra troubleshooting steps, we haven't managed to resolve the problem.

Background: The computer is new, purchased from Origin PC. It functioned well initially but began freezing recently. We performed a fresh OS installation after several consistent issues (repeated BSODs, failed updates). We suspected an external drive was the cause but those were removed and freezing continued. We swapped out an old mouse and headset, excluded those drives, but the issue remains.

After a recent OS upgrade (Windows 10 from Origin flash), BIOS was updated to the latest version. All drivers and hardware (SSDs, CPU, GPU, RAM) were verified through Samsung Magician software. Windows Event Viewer and Task Scheduler logs showed no critical errors until the freezes started. We disabled unused audio devices, turned off Wi-Fi, and checked for sleep settings—no sleep or hibernation issues detected.

Despite these efforts, a hard freeze occurs every 2–3 days, usually between 4–9 AM. The freezes seem to happen after inactivity but don’t align with typical sleep cycles. The PC never enters sleep mode, and display lights remain on even when idle.

Current specs: AMD Ryzen 9 5950X, Gigabyte X570, 64GB RAM, NVIDIA RTX 3070, 500GB SSD. No RAID drives or external storage detected.

What’s happening? It feels like a delay after inactivity, but that doesn’t match the timing. I’m not sure if the watchdog violation has been resolved or if it persists in another form. Any suggestions would be greatly appreciated.

Updates: The system froze at 5 AM and again at 8 AM today, after two days without freezing. This pattern seems linked to early morning use. The WATCHDOG VIOLATION code disappeared since there were no BSODs, but it’s unclear if the fix worked.

Please share any leads that could help us get this resolved!
F
fwkenxz
10-07-2020, 12:31 PM #1

I've been assisting a colleague with his PC troubles for roughly two weeks. Even with my tech expertise and extra troubleshooting steps, we haven't managed to resolve the problem.

Background: The computer is new, purchased from Origin PC. It functioned well initially but began freezing recently. We performed a fresh OS installation after several consistent issues (repeated BSODs, failed updates). We suspected an external drive was the cause but those were removed and freezing continued. We swapped out an old mouse and headset, excluded those drives, but the issue remains.

After a recent OS upgrade (Windows 10 from Origin flash), BIOS was updated to the latest version. All drivers and hardware (SSDs, CPU, GPU, RAM) were verified through Samsung Magician software. Windows Event Viewer and Task Scheduler logs showed no critical errors until the freezes started. We disabled unused audio devices, turned off Wi-Fi, and checked for sleep settings—no sleep or hibernation issues detected.

Despite these efforts, a hard freeze occurs every 2–3 days, usually between 4–9 AM. The freezes seem to happen after inactivity but don’t align with typical sleep cycles. The PC never enters sleep mode, and display lights remain on even when idle.

Current specs: AMD Ryzen 9 5950X, Gigabyte X570, 64GB RAM, NVIDIA RTX 3070, 500GB SSD. No RAID drives or external storage detected.

What’s happening? It feels like a delay after inactivity, but that doesn’t match the timing. I’m not sure if the watchdog violation has been resolved or if it persists in another form. Any suggestions would be greatly appreciated.

Updates: The system froze at 5 AM and again at 8 AM today, after two days without freezing. This pattern seems linked to early morning use. The WATCHDOG VIOLATION code disappeared since there were no BSODs, but it’s unclear if the fix worked.

Please share any leads that could help us get this resolved!

T
teuntjaaah
Junior Member
41
10-13-2020, 04:12 AM
#2
I missed including the details about your specifications.
T
teuntjaaah
10-13-2020, 04:12 AM #2

I missed including the details about your specifications.

L
levoyageur92
Posting Freak
807
10-17-2020, 02:59 PM
#3
Event viewer displays the same messages right before and after freezing. PBO is enabled by default; ensure it remains active. RAM frequency exceeds 3200MHz, so apply the DOCP/XMP profile and set it to auto. Clarify the behavior of the WD 14tb external disk and why the PC froze upon its connection.
L
levoyageur92
10-17-2020, 02:59 PM #3

Event viewer displays the same messages right before and after freezing. PBO is enabled by default; ensure it remains active. RAM frequency exceeds 3200MHz, so apply the DOCP/XMP profile and set it to auto. Clarify the behavior of the WD 14tb external disk and why the PC froze upon its connection.

N
Nubynent
Junior Member
7
10-17-2020, 10:19 PM
#4
Corrected the information in DxDiag.
N
Nubynent
10-17-2020, 10:19 PM #4

Corrected the information in DxDiag.

S
SpinnSky
Member
73
10-18-2020, 12:13 AM
#5
I begin by taking it out first, then run a memtest. Do you have any options for an OC?
S
SpinnSky
10-18-2020, 12:13 AM #5

I begin by taking it out first, then run a memtest. Do you have any options for an OC?

A
Awesomater14
Member
192
10-20-2020, 07:20 AM
#6
No overclocks were made, XMP was actually off; I turned it on to 3200Mhz, though I thought we’d already adjusted it after the BIOS update. It’s worth mentioning this wasn’t active during the problems, and I’m unsure if it was enabled by default when Origin delivered it. I remember it had a V30 BIOS, about two years ago—so who knows? Regarding disabling PBO, it was set to Auto and is now off. The external WD drives (14TB and 12TB) were suspected for the WATCHDOG VIOLATION BSOD, since no other devices seemed involved, though this was mostly based on logic. Both drives have been taken out of consideration for testing now, as they’re no longer part of the investigation. The only peripherals still in use are a C920 webcam and a blue Yeti mic—both common models, and I’m using both on an AMD system (5900x). We’ll replace them just to be safe, but we’re still hoping for a quicker resolution since waiting 4–6 days to test them feels too long.
A
Awesomater14
10-20-2020, 07:20 AM #6

No overclocks were made, XMP was actually off; I turned it on to 3200Mhz, though I thought we’d already adjusted it after the BIOS update. It’s worth mentioning this wasn’t active during the problems, and I’m unsure if it was enabled by default when Origin delivered it. I remember it had a V30 BIOS, about two years ago—so who knows? Regarding disabling PBO, it was set to Auto and is now off. The external WD drives (14TB and 12TB) were suspected for the WATCHDOG VIOLATION BSOD, since no other devices seemed involved, though this was mostly based on logic. Both drives have been taken out of consideration for testing now, as they’re no longer part of the investigation. The only peripherals still in use are a C920 webcam and a blue Yeti mic—both common models, and I’m using both on an AMD system (5900x). We’ll replace them just to be safe, but we’re still hoping for a quicker resolution since waiting 4–6 days to test them feels too long.

L
Logarion
Member
202
10-27-2020, 05:34 PM
#7
I’ve got some unusual suggestions. Have you considered updating the monitor firmware? I faced some frustrating problems that were fixed by that. The DPC issue appears to be software-based, so a clean Windows install without the extra bloat might help. Also, running chkdsk, sfc, and dismis could be useful if the drive is failing. DDU just in case.
L
Logarion
10-27-2020, 05:34 PM #7

I’ve got some unusual suggestions. Have you considered updating the monitor firmware? I faced some frustrating problems that were fixed by that. The DPC issue appears to be software-based, so a clean Windows install without the extra bloat might help. Also, running chkdsk, sfc, and dismis could be useful if the drive is failing. DDU just in case.

P
PetqPqn
Member
68
10-27-2020, 10:59 PM
#8
I reviewed the monitor model on the BenQ website and found no available options—they don’t provide plug-and-play monitors. I’m looking for a detailed software guide to compare. I ran SFC and chkdsk, and the Samsung Magician checks came back clean. I thought about using DDU, but since we performed a clean install and updated drivers via GeForce Experience, it seems unlikely DDU would assist further.
P
PetqPqn
10-27-2020, 10:59 PM #8

I reviewed the monitor model on the BenQ website and found no available options—they don’t provide plug-and-play monitors. I’m looking for a detailed software guide to compare. I ran SFC and chkdsk, and the Samsung Magician checks came back clean. I thought about using DDU, but since we performed a clean install and updated drivers via GeForce Experience, it seems unlikely DDU would assist further.

Y
yJaaoxD
Member
203
10-28-2020, 05:17 AM
#9
This typically comes with the standard Windows generic display drivers, which can lead to problems. Playing Whackamole feels like a possible red flag, but honestly, I find it really annoying—I’ve never used any DDU software before.
Y
yJaaoxD
10-28-2020, 05:17 AM #9

This typically comes with the standard Windows generic display drivers, which can lead to problems. Playing Whackamole feels like a possible red flag, but honestly, I find it really annoying—I’ve never used any DDU software before.

C
Cathomir
Member
64
10-29-2020, 06:20 PM
#10
I've experienced this before switching from a temporary R9 390 to my current build (originally from a laptop without a GPU for some time). It wasn't difficult, just a bit time-consuming. I'll note it as something we might consider. We've already run chkdsk, sfc, and dismis, all passing without issues. Even with Origin software that heavily used CPU and RAM for 30 minutes, we plan to run Memtest86 overnight or soon, since he has 64GB and it's likely a bad sector within that size can take some time, especially when using only 16-20GB, which is usually for video editing.
C
Cathomir
10-29-2020, 06:20 PM #10

I've experienced this before switching from a temporary R9 390 to my current build (originally from a laptop without a GPU for some time). It wasn't difficult, just a bit time-consuming. I'll note it as something we might consider. We've already run chkdsk, sfc, and dismis, all passing without issues. Even with Origin software that heavily used CPU and RAM for 30 minutes, we plan to run Memtest86 overnight or soon, since he has 64GB and it's likely a bad sector within that size can take some time, especially when using only 16-20GB, which is usually for video editing.

Pages (2): 1 2 Next