F5F Stay Refreshed Hardware Desktop Severe freezing issues reported across the state.

Severe freezing issues reported across the state.

Severe freezing issues reported across the state.

A
Agusz_XD
Junior Member
42
07-27-2021, 02:43 PM
#1
Hey there. I also had to create a temporary account since my desktop finally started working properly without freezing. The setup includes an AMD 5950x processor, Asus Dark Hero VIII with 128GB RAM, and a 3080ti GPU running Windows 11 Pro. A few weeks back my computer began freezing unexpectedly, without any BSOD. Over the last couple of days it got worse—after rebooting it would freeze almost immediately when I reached my desktop. Earlier, checking the Event Viewer showed no unusual activity. Recently, after disabling C-State in the BIOS (as I found online helpful), I’ve had no problems and managed to install Windows successfully. Now I’m planning to download a fresh ISO and start over, hoping to resolve everything. Can anyone explain what might be causing this issue and why disabling Global C State seems to help?
A
Agusz_XD
07-27-2021, 02:43 PM #1

Hey there. I also had to create a temporary account since my desktop finally started working properly without freezing. The setup includes an AMD 5950x processor, Asus Dark Hero VIII with 128GB RAM, and a 3080ti GPU running Windows 11 Pro. A few weeks back my computer began freezing unexpectedly, without any BSOD. Over the last couple of days it got worse—after rebooting it would freeze almost immediately when I reached my desktop. Earlier, checking the Event Viewer showed no unusual activity. Recently, after disabling C-State in the BIOS (as I found online helpful), I’ve had no problems and managed to install Windows successfully. Now I’m planning to download a fresh ISO and start over, hoping to resolve everything. Can anyone explain what might be causing this issue and why disabling Global C State seems to help?

M
Milobest2000
Member
99
07-27-2021, 03:13 PM
#2
On desktops, c-states are often disabled by default in the BIOS. You might need to install additional drivers, such as those from the Intel chipset or AMD support tools, before they function properly. Consider adding AMD's chipset driver to test if c-states operate correctly.
M
Milobest2000
07-27-2021, 03:13 PM #2

On desktops, c-states are often disabled by default in the BIOS. You might need to install additional drivers, such as those from the Intel chipset or AMD support tools, before they function properly. Consider adding AMD's chipset driver to test if c-states operate correctly.

_
_ObitoUchiha
Junior Member
2
07-27-2021, 03:32 PM
#3
No, I don't use a curve optimizer.
_
_ObitoUchiha
07-27-2021, 03:32 PM #3

No, I don't use a curve optimizer.

B
bishopboys68
Posting Freak
899
07-28-2021, 03:50 PM
#4
We've encountered several problems with the 5000 series concerning voltage settings. It seems this issue has become more common over the past few years, though it wasn't always a frequent occurrence. Most cases involve shutdowns or restarts rather than just freezing. Check your Event Viewer for any WHEA events. Navigate to Windows Logs → System, choose Filter Current Log, and select WHEA-logger from the Event Sources menu. If applicable, highlight it and right-click to save. You may want to share the .evtx file if someone needs to review it. It could also stem from an outdated BIOS or chipset driver. The only factors I've identified that might stabilize the system are disabling C-States. If you see WHEA events, consider adjusting voltage settings that have worked well on similar hardware (assuming the issue relates to CPU memory controller). Alternatively, set a static voltage of 1.3v for the Core and 1.1v for the SoC. If your board uses voltage increments, aim closely to those values; you can't use both simultaneously. The first suggestion applies broadly to 5000 series when CPU memory controller errors appear, while the second has proven effective for higher-end models like 5800x, 5900x, and 5950x during various crashes.
B
bishopboys68
07-28-2021, 03:50 PM #4

We've encountered several problems with the 5000 series concerning voltage settings. It seems this issue has become more common over the past few years, though it wasn't always a frequent occurrence. Most cases involve shutdowns or restarts rather than just freezing. Check your Event Viewer for any WHEA events. Navigate to Windows Logs → System, choose Filter Current Log, and select WHEA-logger from the Event Sources menu. If applicable, highlight it and right-click to save. You may want to share the .evtx file if someone needs to review it. It could also stem from an outdated BIOS or chipset driver. The only factors I've identified that might stabilize the system are disabling C-States. If you see WHEA events, consider adjusting voltage settings that have worked well on similar hardware (assuming the issue relates to CPU memory controller). Alternatively, set a static voltage of 1.3v for the Core and 1.1v for the SoC. If your board uses voltage increments, aim closely to those values; you can't use both simultaneously. The first suggestion applies broadly to 5000 series when CPU memory controller errors appear, while the second has proven effective for higher-end models like 5800x, 5900x, and 5950x during various crashes.