F5F Stay Refreshed Power Users Overclocking Who bears the responsibility? The issue lies with Windows 10 or the overclocking?

Who bears the responsibility? The issue lies with Windows 10 or the overclocking?

Who bears the responsibility? The issue lies with Windows 10 or the overclocking?

Pages (3): 1 2 3 Next
T
theicefrenzy
Member
65
08-06-2016, 10:04 AM
#1
Windows 10 is operating smoothly on my system now, but a recurring issue still happens. Occasionally, during high CPU usage (such as gaming), the system shuts down unexpectedly. Is a stable overclock in Windows 8.1 indicative of stability in Windows 10?
T
theicefrenzy
08-06-2016, 10:04 AM #1

Windows 10 is operating smoothly on my system now, but a recurring issue still happens. Occasionally, during high CPU usage (such as gaming), the system shuts down unexpectedly. Is a stable overclock in Windows 8.1 indicative of stability in Windows 10?

W
WildCandy
Senior Member
675
08-09-2016, 08:33 PM
#2
I would revert the overclock and simply save the settings. If another crash occurs, it could indicate a hardware issue or a problem with Windows 10. I would avoid raising the voltage since it might not clarify whether the clock instability exists or if there are compatibility problems with the operating system.
W
WildCandy
08-09-2016, 08:33 PM #2

I would revert the overclock and simply save the settings. If another crash occurs, it could indicate a hardware issue or a problem with Windows 10. I would avoid raising the voltage since it might not clarify whether the clock instability exists or if there are compatibility problems with the operating system.

F
173
08-10-2016, 10:39 AM
#3
It should remain a reliable clock for as long as it was consistently stable in Windows 8.1 initially. When I moved from Windows 7 to Windows 8, there were significant problems with my custom hardware that hadn't been properly secured yet. I advise you to revert your overclocking until Windows 10 offers better stability. If the issue persists, file a ticket with Microsoft and revert to Windows 8.1.
F
firebuckler123
08-10-2016, 10:39 AM #3

It should remain a reliable clock for as long as it was consistently stable in Windows 8.1 initially. When I moved from Windows 7 to Windows 8, there were significant problems with my custom hardware that hadn't been properly secured yet. I advise you to revert your overclocking until Windows 10 offers better stability. If the issue persists, file a ticket with Microsoft and revert to Windows 8.1.

K
Kaymary10
Member
152
08-25-2016, 02:56 PM
#4
It should function reliably for a long time as long as it was stable in Windows 8.1 initially. When I moved from Windows 7 to 8, there were significant problems with my custom hardware that hadn't been properly secured yet. I suggest you revert your overclocking until Windows 10 offers better stability. If the issue persists, contact Microsoft and revert to Windows 8.1.
K
Kaymary10
08-25-2016, 02:56 PM #4

It should function reliably for a long time as long as it was stable in Windows 8.1 initially. When I moved from Windows 7 to 8, there were significant problems with my custom hardware that hadn't been properly secured yet. I suggest you revert your overclocking until Windows 10 offers better stability. If the issue persists, contact Microsoft and revert to Windows 8.1.

K
kitty_345
Member
59
08-26-2016, 01:15 AM
#5
I would revert the overclock and simply save the settings. If another crash occurs, it could indicate a hardware issue or a problem with Windows 10. I would avoid raising the voltage since it might not clarify whether the clock instability exists or if there are compatibility problems with the operating system.
K
kitty_345
08-26-2016, 01:15 AM #5

I would revert the overclock and simply save the settings. If another crash occurs, it could indicate a hardware issue or a problem with Windows 10. I would avoid raising the voltage since it might not clarify whether the clock instability exists or if there are compatibility problems with the operating system.

X
xFqtal_
Senior Member
670
09-08-2016, 07:16 PM
#6
I would revert the overclock and simply save the settings. If another crash occurs, it could indicate a different hardware issue or that Windows 10 is involved. I wouldn't raise the voltage, as it might not clarify whether the clock instability or OS compatibility problems are at play.
X
xFqtal_
09-08-2016, 07:16 PM #6

I would revert the overclock and simply save the settings. If another crash occurs, it could indicate a different hardware issue or that Windows 10 is involved. I wouldn't raise the voltage, as it might not clarify whether the clock instability or OS compatibility problems are at play.

M
Mr_Cookie13
Junior Member
31
09-10-2016, 03:21 AM
#7
Just returned to the stock. On the first start, Windows 10 would remain idle at the login screen after entering the password, until I pressed Ctrl+Alt+Del and restarted the computer. The second boot is now working properly. I'll follow up if any problems arise.
M
Mr_Cookie13
09-10-2016, 03:21 AM #7

Just returned to the stock. On the first start, Windows 10 would remain idle at the login screen after entering the password, until I pressed Ctrl+Alt+Del and restarted the computer. The second boot is now working properly. I'll follow up if any problems arise.

T
Thomasvegetta
Junior Member
8
09-10-2016, 11:18 AM
#8
TechyInAZ just returned to the stock. On first launch, Windows 10 would remain idle at login after entering the password, requiring a Ctrl+Alt+Del restart. The second boot is now fine. I'll follow up if any problems arise.
Windows 10 has some minor issues, but these are typical for early users. Most functions work well, though I've had to reduce my GPU overclock by 50Mhz in Win 10. It might be driver-related, but I'm hopeful. I occasionally experience random game freezes, but not too often. With more updates and driver patches, things should improve. I still prefer Windows 10 overall.
T
Thomasvegetta
09-10-2016, 11:18 AM #8

TechyInAZ just returned to the stock. On first launch, Windows 10 would remain idle at login after entering the password, requiring a Ctrl+Alt+Del restart. The second boot is now fine. I'll follow up if any problems arise.
Windows 10 has some minor issues, but these are typical for early users. Most functions work well, though I've had to reduce my GPU overclock by 50Mhz in Win 10. It might be driver-related, but I'm hopeful. I occasionally experience random game freezes, but not too often. With more updates and driver patches, things should improve. I still prefer Windows 10 overall.

J
Jdyy
Member
64
09-10-2016, 12:07 PM
#9
Reaper_7799:
I recently switched back to the stock version. On first launch, Windows 10 would remain idle at login after entering my password, requiring me to press Ctrl+Alt+Del and restart the system. The second boot is now smooth. I'll follow up if any problems arise.

Windows 10 has some quirks, but it's normal for this version. Most of my setup works well, and games run without major issues. I had to reduce my GPU overclock by 50Mhz in Windows 10, possibly due to driver concerns. Occasional game freezes occur, but not too frequent. With more updates and drivers, things should improve. I generally prefer Windows 10, though I anticipate some instability when moving from 8.1 to 10, similar to past upgrades. As long as it gets better, I'm okay.
J
Jdyy
09-10-2016, 12:07 PM #9

Reaper_7799:
I recently switched back to the stock version. On first launch, Windows 10 would remain idle at login after entering my password, requiring me to press Ctrl+Alt+Del and restart the system. The second boot is now smooth. I'll follow up if any problems arise.

Windows 10 has some quirks, but it's normal for this version. Most of my setup works well, and games run without major issues. I had to reduce my GPU overclock by 50Mhz in Windows 10, possibly due to driver concerns. Occasional game freezes occur, but not too frequent. With more updates and drivers, things should improve. I generally prefer Windows 10, though I anticipate some instability when moving from 8.1 to 10, similar to past upgrades. As long as it gets better, I'm okay.

L
lexaroo123456
Junior Member
14
09-25-2016, 03:47 AM
#10
It just reverted the XMP profile, now operating at 1333mhz instead of 2400mhz.
L
lexaroo123456
09-25-2016, 03:47 AM #10

It just reverted the XMP profile, now operating at 1333mhz instead of 2400mhz.

Pages (3): 1 2 3 Next