F5F Stay Refreshed Power Users Overclocking What have I done?!

What have I done?!

What have I done?!

Y
YoungAriesArt
Member
192
09-03-2017, 02:17 AM
#1
I'm struggling and need assistance, I don't understand what's happening.
I recently attempted to overclock my 1060 with 6GB RAM using MSI afterburner. I increased the core clock slowly, but the system became unstable and crashed.
After powering it back up, it wouldn't boot into Windows, showing a kernel error and suggesting recovery.
Recovery failed to load, then restarted after 20 minutes and successfully booted into Windows again.
I used it for several hours, turned it off, and when I tried it later, the kernel problem appeared.
My specs are as follows:
Motherboard: MSI B350 Tomahawk
CPU: Ryzen 1600x
RAM: 16GB Corsair Ven. 2666 c15
GPU: Palit 1060 6GB Dual
I'm confused about how a GPU overclock failure could affect the kernel, especially since Windows booted normally after a CMOS reset (settings are default).
Did I make a mistake? Please help!
Y
YoungAriesArt
09-03-2017, 02:17 AM #1

I'm struggling and need assistance, I don't understand what's happening.
I recently attempted to overclock my 1060 with 6GB RAM using MSI afterburner. I increased the core clock slowly, but the system became unstable and crashed.
After powering it back up, it wouldn't boot into Windows, showing a kernel error and suggesting recovery.
Recovery failed to load, then restarted after 20 minutes and successfully booted into Windows again.
I used it for several hours, turned it off, and when I tried it later, the kernel problem appeared.
My specs are as follows:
Motherboard: MSI B350 Tomahawk
CPU: Ryzen 1600x
RAM: 16GB Corsair Ven. 2666 c15
GPU: Palit 1060 6GB Dual
I'm confused about how a GPU overclock failure could affect the kernel, especially since Windows booted normally after a CMOS reset (settings are default).
Did I make a mistake? Please help!

C
Crockyy
Member
58
09-15-2017, 01:50 PM
#2
Kernel issues usually arise from hardware problems. When overclocking, many things can go wrong. What PSU do you have? A low-quality one might have damaged the motherboard, which could explain why a CMOS clear sometimes works. It may be worth trying to replace parts to identify the faulty hardware.
C
Crockyy
09-15-2017, 01:50 PM #2

Kernel issues usually arise from hardware problems. When overclocking, many things can go wrong. What PSU do you have? A low-quality one might have damaged the motherboard, which could explain why a CMOS clear sometimes works. It may be worth trying to replace parts to identify the faulty hardware.

K
56
09-15-2017, 03:35 PM
#3
I can initiate safe mode and the utility you employed for the update was [insert utility name]. You mentioned you'd remove it as well and reinstall drivers.
K
KoolaidMan_154
09-15-2017, 03:35 PM #3

I can initiate safe mode and the utility you employed for the update was [insert utility name]. You mentioned you'd remove it as well and reinstall drivers.

P
PinneyGelvin
Member
52
09-16-2017, 06:27 PM
#4
The CPU isn't the GPU, so resetting the BIOS won't be very effective. You'll need to remove the GPU overclocking by returning to Afterburner and reversing the changes made.
P
PinneyGelvin
09-16-2017, 06:27 PM #4

The CPU isn't the GPU, so resetting the BIOS won't be very effective. You'll need to remove the GPU overclocking by returning to Afterburner and reversing the changes made.

S
Sopanda59
Member
115
09-16-2017, 06:56 PM
#5
I mentioned in the original message that I used MSI Afterburner to apply the OC. As soon as I logged back into Windows, I deleted the saved OC and went back to the defaults. That means the OC is no longer being applied. But it still occurs.
S
Sopanda59
09-16-2017, 06:56 PM #5

I mentioned in the original message that I used MSI Afterburner to apply the OC. As soon as I logged back into Windows, I deleted the saved OC and went back to the defaults. That means the OC is no longer being applied. But it still occurs.

N
ninty99
Member
107
09-19-2017, 12:50 AM
#6
I understand the CPU isn't the GPU, though I'm sure resetting the BIOS should definitely help. This happened seven times in a row, and it seems to be working somewhat. The OC was removed right after I started using Windows again. The problem isn't with the overclock settings; everything is back to normal but still causing issues. Since it does boot into Windows occasionally, I don’t think it’s an OS-related problem. The boot drive is a new 120GB SSD and shouldn’t be failing, so there’s probably another cause. I can’t think of anything else right now, but I’ll probably do a full OS reinstall to see if that fixes it, though I’d rather try something else.
N
ninty99
09-19-2017, 12:50 AM #6

I understand the CPU isn't the GPU, though I'm sure resetting the BIOS should definitely help. This happened seven times in a row, and it seems to be working somewhat. The OC was removed right after I started using Windows again. The problem isn't with the overclock settings; everything is back to normal but still causing issues. Since it does boot into Windows occasionally, I don’t think it’s an OS-related problem. The boot drive is a new 120GB SSD and shouldn’t be failing, so there’s probably another cause. I can’t think of anything else right now, but I’ll probably do a full OS reinstall to see if that fixes it, though I’d rather try something else.

A
AbsolFangz
Junior Member
49
09-23-2017, 06:42 AM
#7
Kernel issues usually arise from hardware problems. When overclocking, many things can go wrong. What PSU do you have? A low-quality one might have damaged the motherboard, which could explain why a CMOS clear sometimes works. It may be worth trying to replace parts to identify the faulty hardware.
A
AbsolFangz
09-23-2017, 06:42 AM #7

Kernel issues usually arise from hardware problems. When overclocking, many things can go wrong. What PSU do you have? A low-quality one might have damaged the motherboard, which could explain why a CMOS clear sometimes works. It may be worth trying to replace parts to identify the faulty hardware.

L
lavaZX
Junior Member
1
09-30-2017, 03:05 AM
#8
Thank you, that clarifies things a bit. I can easily change the hardware except for the MOBO at the moment; though it's the intermittent issue that's tricky to identify. I restarted and shut down six times today and always booted normally, but then it stopped afterward.
I'll return to the basics using an older GPU and one stick of RAM and will get back to you.
L
lavaZX
09-30-2017, 03:05 AM #8

Thank you, that clarifies things a bit. I can easily change the hardware except for the MOBO at the moment; though it's the intermittent issue that's tricky to identify. I restarted and shut down six times today and always booted normally, but then it stopped afterward.
I'll return to the basics using an older GPU and one stick of RAM and will get back to you.

B
BAPEHbE
Junior Member
47
10-14-2017, 02:31 AM
#9
It's conceivable that the initial crash led to corruption in a driver. Although uncommon, it does occur. I would attempt a fresh installation of the GPU drivers (custom install not available, but clean install is available), then start from the boot menu, open CMD with administrative privileges, and enter
SFC /SCANNOW
to scan and repair all system files.
B
BAPEHbE
10-14-2017, 02:31 AM #9

It's conceivable that the initial crash led to corruption in a driver. Although uncommon, it does occur. I would attempt a fresh installation of the GPU drivers (custom install not available, but clean install is available), then start from the boot menu, open CMD with administrative privileges, and enter
SFC /SCANNOW
to scan and repair all system files.