CalVic
Member
I nearly fried my AMD FX 8350 Last night... Twice infact!
So, I was a little bored and decided I'd have a play with my Overclock, I wasn't really concentrating at the values I was entering in the UEFI for my vCore, I ended up shoving 1.88 into my chip. Luckily I caught it before the system rebooted and rushed for the power lead that was right next to me (You could say it was a mad dash a hacker would do in a rush to fry his HDDs before the police *knock* on the door.).
If that wasn't enough, after I reset the UEFI and entered the menu to re-apply the settings that I use, I rebooted the system to Windows to find I was running 1.7v on the CPU/NB... Again, I shut the system down and reset the UEFI.
Fuckin' ell' I said to myself. Never done that before - Let alone twice.
So I left it alone and went bed! LOL.
I guess moral of the story is... check over the values before hitting the shortcut to save and exit, and not do it when concentration is lacking.
=00=
So, I was a little bored and decided I'd have a play with my Overclock, I wasn't really concentrating at the values I was entering in the UEFI for my vCore, I ended up shoving 1.88 into my chip. Luckily I caught it before the system rebooted and rushed for the power lead that was right next to me (You could say it was a mad dash a hacker would do in a rush to fry his HDDs before the police *knock* on the door.).
If that wasn't enough, after I reset the UEFI and entered the menu to re-apply the settings that I use, I rebooted the system to Windows to find I was running 1.7v on the CPU/NB... Again, I shut the system down and reset the UEFI.
Fuckin' ell' I said to myself. Never done that before - Let alone twice.
So I left it alone and went bed! LOL.
I guess moral of the story is... check over the values before hitting the shortcut to save and exit, and not do it when concentration is lacking.
=00=