F5F Stay Refreshed Hardware Desktop Check your motherboard and CPU first.

Check your motherboard and CPU first.

Check your motherboard and CPU first.

A
ashton555
Member
57
11-09-2017, 12:58 AM
#1
Hey everyone, thanks for your support. I've been putting in a lot of effort on this project. It seems the PC has been acting up since not using it for quite some time. By September 1, 2022, the system began locking down heavily with intense CPU usage. After resetting the power, the motherboard—something I’ve dealt with before—wouldn’t recognize my NVMe boot device. There were two BSODs linked to DCP Watchdog violations, but the machine keeps locking even when errors appear or not. Sometimes it powers back up and finishes booting. Mem tests came back clean, showing no memory issues. Samsung Magician passed all checks without errors. Windows File Check found a corrupted file, though I think that’s probably from the crashes themselves since nothing changed. Norton ran multiple scans with no threats detected. I tried checking drives and updating as much as possible before it froze again. Personally, I’m worried about my CPU overheating after overclocking, and the motherboard has been struggling with heat for a while. Here’s what I have:

- Windows 10 64-bit
- AMD Ryzen 5 1600 (14nm) 3.2 GHz, 6 cores (OC 3.9)
- Corsair H100i 77 CFM liquid cooler
- Gigabyte GA-AB350-GAMING 3 ATX AM4 board
- Corsair Vengeance LPX 8 GB & 16 GB DDR4
- Samsung 970 Evo Plus M.2 NVME (Windows boot)
- Samsung 870 Evo 500 GB M.2 NVME
- Samsung 850 Evo 250 GB M.2 NVME
- Seagate BarraCuda 2 TB 3.5" HDD
- Corsair RM850 850W, 80+ Gold certified

Specs: 2023 update, January 10.
A
ashton555
11-09-2017, 12:58 AM #1

Hey everyone, thanks for your support. I've been putting in a lot of effort on this project. It seems the PC has been acting up since not using it for quite some time. By September 1, 2022, the system began locking down heavily with intense CPU usage. After resetting the power, the motherboard—something I’ve dealt with before—wouldn’t recognize my NVMe boot device. There were two BSODs linked to DCP Watchdog violations, but the machine keeps locking even when errors appear or not. Sometimes it powers back up and finishes booting. Mem tests came back clean, showing no memory issues. Samsung Magician passed all checks without errors. Windows File Check found a corrupted file, though I think that’s probably from the crashes themselves since nothing changed. Norton ran multiple scans with no threats detected. I tried checking drives and updating as much as possible before it froze again. Personally, I’m worried about my CPU overheating after overclocking, and the motherboard has been struggling with heat for a while. Here’s what I have:

- Windows 10 64-bit
- AMD Ryzen 5 1600 (14nm) 3.2 GHz, 6 cores (OC 3.9)
- Corsair H100i 77 CFM liquid cooler
- Gigabyte GA-AB350-GAMING 3 ATX AM4 board
- Corsair Vengeance LPX 8 GB & 16 GB DDR4
- Samsung 970 Evo Plus M.2 NVME (Windows boot)
- Samsung 870 Evo 500 GB M.2 NVME
- Samsung 850 Evo 250 GB M.2 NVME
- Seagate BarraCuda 2 TB 3.5" HDD
- Corsair RM850 850W, 80+ Gold certified

Specs: 2023 update, January 10.

K
KanayOne
Member
212
11-12-2017, 10:52 AM
#2
Have you experimented with a single RAM module? Combining two distinct RAM sets is usually discouraged because of variations in the integrated circuits and clock speeds.
K
KanayOne
11-12-2017, 10:52 AM #2

Have you experimented with a single RAM module? Combining two distinct RAM sets is usually discouraged because of variations in the integrated circuits and clock speeds.

M
MiverGames
Junior Member
28
11-12-2017, 12:39 PM
#3
I suggest testing a single RAM module first. As @CommanderAlex mentioned, combining various types can lead to problems since they operate differently. Even though they’re from the same brand, they might not be identical models.
M
MiverGames
11-12-2017, 12:39 PM #3

I suggest testing a single RAM module first. As @CommanderAlex mentioned, combining various types can lead to problems since they operate differently. Even though they’re from the same brand, they might not be identical models.

R
Robater
Member
86
11-17-2017, 12:27 PM
#4
I've considered it, but the mixed RAM kit has been functioning well over the years. It matches the exact speed and clock speed to address mixed problems. Please let me know if you'd like a moment to pick a pair.
R
Robater
11-17-2017, 12:27 PM #4

I've considered it, but the mixed RAM kit has been functioning well over the years. It matches the exact speed and clock speed to address mixed problems. Please let me know if you'd like a moment to pick a pair.

R
Rosario17_
Posting Freak
897
11-25-2017, 06:22 AM
#5
I removed the smaller ram kit and it seems to have improved stability. Still, I keep encountering issues with motherboard failure to reliably detect the NVMe drive after restarts. I suspect a GLCKIO2.sys might be malware, but I can't locate it or confirm its activity because it keeps failing to start. I'll attempt to reload my old BIOS settings to see if restoring fewer RAM parameters brings me back to the original configuration.
R
Rosario17_
11-25-2017, 06:22 AM #5

I removed the smaller ram kit and it seems to have improved stability. Still, I keep encountering issues with motherboard failure to reliably detect the NVMe drive after restarts. I suspect a GLCKIO2.sys might be malware, but I can't locate it or confirm its activity because it keeps failing to start. I'll attempt to reload my old BIOS settings to see if restoring fewer RAM parameters brings me back to the original configuration.

M
MM_BOSE
Member
56
11-25-2017, 08:12 AM
#6
I managed to revert to the original BIOS configuration and overclocked the CPU once more. The system remains stable, but I still sense something isn’t quite right. I’m updating my recovery software since outdated versions might have contributed to the problem. Once I run some tests, I’ll check if the NVMe drive experiences any issues again and perform a crash stress test. I’m puzzled by the RAM—despite passing memory tests and being in use for years, it seems to be the cause of this instability.
M
MM_BOSE
11-25-2017, 08:12 AM #6

I managed to revert to the original BIOS configuration and overclocked the CPU once more. The system remains stable, but I still sense something isn’t quite right. I’m updating my recovery software since outdated versions might have contributed to the problem. Once I run some tests, I’ll check if the NVMe drive experiences any issues again and perform a crash stress test. I’m puzzled by the RAM—despite passing memory tests and being in use for years, it seems to be the cause of this instability.

H
Hingodu
Member
56
11-25-2017, 02:11 PM
#7
GLCKIO2.sys seems to be a legitimate Windows component, likely a driver. It appears safe since the issue isn’t affecting other drives. Removing the problematic RAM module seems to have restored stability.
H
Hingodu
11-25-2017, 02:11 PM #7

GLCKIO2.sys seems to be a legitimate Windows component, likely a driver. It appears safe since the issue isn’t affecting other drives. Removing the problematic RAM module seems to have restored stability.