F5F Stay Refreshed Hardware Desktop The system freezes unexpectedly, but restarting resolves the problem temporarily.

The system freezes unexpectedly, but restarting resolves the problem temporarily.

The system freezes unexpectedly, but restarting resolves the problem temporarily.

Pages (3): 1 2 3 Next
C
CounterStrikeZ
Junior Member
23
08-18-2022, 05:14 AM
#1
Hello everyone, I’ve encountered this relatively rare problem with my PC where it tends to lock itself in a soft state. The only solution seems to be restarting the system. I’d appreciate any advice you might have on how to fix this, thank you. (Sorry for the lengthy update.)

My hardware details are: CPU – AMD Ryzen 7 3700X, Motherboard – Asus X570 - E Gaming; RAM – 32GB Corsair Vengeance RBG Pro (4x8GB); GPU – Strix 1070 with latest drivers; M.2 drive for storage; several SSDs for games; additional fans and cooling components from Corsair.

I believe the problem started after upgrading from GPU Tweak 2 to GPU Tweak 3, and I installed Armoury Crate by mistake. From what I observed, my PC would suddenly lock itself. Visually, the RGB fan patterns would revert to their default colors before launching Windows. The taskbar clock would freeze, but I could still close applications or shut out of Steam. Only a restart via the start menu would bring it back, sometimes for weeks.

I tried uninstalling through the standard method, which didn’t resolve it. Using the portable Revo tool helped more, but the issue persisted. I also noticed the RGB on my RAM would behave erratically—sometimes not lighting up at all or stuck on partial colors. In Corsair iCUE, it alerts me that “iCUE has stopped receiving data from DRAM. Please restart or power cycle your system to fix this.”

I’ve reinstalled iCUE several times, so I’m not certain the software is the root cause. However, I saw videos suggesting Armoury Crate might be involved. I ran into a problem with a folder named PHISON inside it, which I couldn’t delete. A file called Phison_x86.dll was removed, but Phison_x64.dll remains. I’m unsure if deleting the PHISON folder helped, especially since its DLL has an older date (25/06/2021). Could removing it have caused trouble?

I’m open to any suggestions and happy to share more details if needed. Thanks in advance.
C
CounterStrikeZ
08-18-2022, 05:14 AM #1

Hello everyone, I’ve encountered this relatively rare problem with my PC where it tends to lock itself in a soft state. The only solution seems to be restarting the system. I’d appreciate any advice you might have on how to fix this, thank you. (Sorry for the lengthy update.)

My hardware details are: CPU – AMD Ryzen 7 3700X, Motherboard – Asus X570 - E Gaming; RAM – 32GB Corsair Vengeance RBG Pro (4x8GB); GPU – Strix 1070 with latest drivers; M.2 drive for storage; several SSDs for games; additional fans and cooling components from Corsair.

I believe the problem started after upgrading from GPU Tweak 2 to GPU Tweak 3, and I installed Armoury Crate by mistake. From what I observed, my PC would suddenly lock itself. Visually, the RGB fan patterns would revert to their default colors before launching Windows. The taskbar clock would freeze, but I could still close applications or shut out of Steam. Only a restart via the start menu would bring it back, sometimes for weeks.

I tried uninstalling through the standard method, which didn’t resolve it. Using the portable Revo tool helped more, but the issue persisted. I also noticed the RGB on my RAM would behave erratically—sometimes not lighting up at all or stuck on partial colors. In Corsair iCUE, it alerts me that “iCUE has stopped receiving data from DRAM. Please restart or power cycle your system to fix this.”

I’ve reinstalled iCUE several times, so I’m not certain the software is the root cause. However, I saw videos suggesting Armoury Crate might be involved. I ran into a problem with a folder named PHISON inside it, which I couldn’t delete. A file called Phison_x86.dll was removed, but Phison_x64.dll remains. I’m unsure if deleting the PHISON folder helped, especially since its DLL has an older date (25/06/2021). Could removing it have caused trouble?

I’m open to any suggestions and happy to share more details if needed. Thanks in advance.

T
Thuthur
Member
191
08-18-2022, 05:14 AM
#2
You can access the official Asus utility to delete the Armory Crate. It's included with the downloads for your motherboard. Make sure you're using the most recent BIOS and have the latest AMD chipset drivers installed.
T
Thuthur
08-18-2022, 05:14 AM #2

You can access the official Asus utility to delete the Armory Crate. It's included with the downloads for your motherboard. Make sure you're using the most recent BIOS and have the latest AMD chipset drivers installed.

W
WolfEH117
Member
180
08-18-2022, 05:14 AM
#3
Hello, the uninstall tool has cleared some files for you. Regarding the BIOS, you're using version 1407, while the latest from Asus is 4403—upgrading could be beneficial. Updating might be worth considering. As for chipset drivers, you haven't changed them since building the PC a few years ago.
W
WolfEH117
08-18-2022, 05:14 AM #3

Hello, the uninstall tool has cleared some files for you. Regarding the BIOS, you're using version 1407, while the latest from Asus is 4403—upgrading could be beneficial. Updating might be worth considering. As for chipset drivers, you haven't changed them since building the PC a few years ago.

D
DapperMD
Member
153
08-18-2022, 05:14 AM
#4
Your system is experiencing issues due to being two years behind in stability and compatibility fixes, as well as performance gains from BIOS updates. Update your BIOS and review the details for each version. Also, download the newest chipset drivers from AMD directly.
D
DapperMD
08-18-2022, 05:14 AM #4

Your system is experiencing issues due to being two years behind in stability and compatibility fixes, as well as performance gains from BIOS updates. Update your BIOS and review the details for each version. Also, download the newest chipset drivers from AMD directly.

I
IpSenKo
Member
61
08-18-2022, 05:14 AM
#5
Installed the newest chipset drivers. Will handle the bios setup. Drive is ready to use.
I
IpSenKo
08-18-2022, 05:14 AM #5

Installed the newest chipset drivers. Will handle the bios setup. Drive is ready to use.

H
Hades666201
Member
175
08-18-2022, 05:14 AM
#6
So I've gone ahead and installed the bios update via the drive. The code led has changed a few times, but for the last 10 minutes it's been stuck on code 64. Before that, it was on 02 (I think) for a few minutes before changing to code 64. Am I to leave this to sort its checks out, or can I remove the USB/press the restart button? No login page showing on the screen.
H
Hades666201
08-18-2022, 05:14 AM #6

So I've gone ahead and installed the bios update via the drive. The code led has changed a few times, but for the last 10 minutes it's been stuck on code 64. Before that, it was on 02 (I think) for a few minutes before changing to code 64. Am I to leave this to sort its checks out, or can I remove the USB/press the restart button? No login page showing on the screen.

D
DA_Red_Gamer
Member
225
08-18-2022, 05:14 AM
#7
I used the USB flashback method.
D
DA_Red_Gamer
08-18-2022, 05:14 AM #7

I used the USB flashback method.

S
SolitudeFX
Member
131
08-18-2022, 05:14 AM
#8
I connected the USB using the newest bios into the port marked BIOS. Next, I opened the bios and executed the update tool. After a few minutes, the progress indicator finished.
S
SolitudeFX
08-18-2022, 05:14 AM #8

I connected the USB using the newest bios into the port marked BIOS. Next, I opened the bios and executed the update tool. After a few minutes, the progress indicator finished.

L
LaxShooter19
Junior Member
21
08-18-2022, 05:14 AM
#9
It has restarted and now appears on an error code. The manual states that pages 84, 85, and 86 explain that Q code 64 is part of the CPU initialization sequence. If the device is stuck, after the flashing finishes, you can attempt a system reset. Clearing the BIOS (reloading CMOS) may also help.
L
LaxShooter19
08-18-2022, 05:14 AM #9

It has restarted and now appears on an error code. The manual states that pages 84, 85, and 86 explain that Q code 64 is part of the CPU initialization sequence. If the device is stuck, after the flashing finishes, you can attempt a system reset. Clearing the BIOS (reloading CMOS) may also help.

M
mousse2006
Member
157
08-18-2022, 05:14 AM
#10
Sure, I understand. I can simply press the restart button to check if that resolves the issue.
M
mousse2006
08-18-2022, 05:14 AM #10

Sure, I understand. I can simply press the restart button to check if that resolves the issue.

Pages (3): 1 2 3 Next