F5F Stay Refreshed Hardware Desktop Error or crash occurs when opening the Winrar folder.

Error or crash occurs when opening the Winrar folder.

Error or crash occurs when opening the Winrar folder.

K
KablooieKablam
Posting Freak
908
04-23-2016, 03:56 PM
#1
I verified temperatures, ran memory tests and stress checks. I can run long hours with demanding games on both GPU and CPU. The system scans and drives worked without problems. However, when opening a WinRAR folder (around 2.5GB) the computer freezes about eight times out of ten, sometimes triggering a crash. I suspected an SSD failure after checking with native tools—no issues found, replaced the drive and switched to NVMe. Restarted the OS. The problem persists. What further actions should be taken or tested?
K
KablooieKablam
04-23-2016, 03:56 PM #1

I verified temperatures, ran memory tests and stress checks. I can run long hours with demanding games on both GPU and CPU. The system scans and drives worked without problems. However, when opening a WinRAR folder (around 2.5GB) the computer freezes about eight times out of ten, sometimes triggering a crash. I suspected an SSD failure after checking with native tools—no issues found, replaced the drive and switched to NVMe. Restarted the OS. The problem persists. What further actions should be taken or tested?

C
casanuva
Member
61
05-11-2016, 10:08 PM
#2
What's the BSOD error code?
C
casanuva
05-11-2016, 10:08 PM #2

What's the BSOD error code?

C
CuzImJuli
Member
204
05-16-2016, 01:01 PM
#3
Usually it freezes, rarely restarts completely. Crash screens are uncommon, most often a full system reset occurs. Error messages like "WHEA_UNCORRECTABLE_ERROR" appear infrequently.
C
CuzImJuli
05-16-2016, 01:01 PM #3

Usually it freezes, rarely restarts completely. Crash screens are uncommon, most often a full system reset occurs. Error messages like "WHEA_UNCORRECTABLE_ERROR" appear infrequently.

G
GenjiBear
Junior Member
1
05-16-2016, 09:36 PM
#4
No, I didn't solve the issue. It's the exact same problem again.
G
GenjiBear
05-16-2016, 09:36 PM #4

No, I didn't solve the issue. It's the exact same problem again.