SmOKeY89
New Member
- Joined
- Mar 24, 2018
Hello guyz. I experienced a very unusual situation with my last build.
It's my second custom build. My first was back in 2011 with the legendary i5-2500k which is still running flawlessly.
(Still overclocked to 4.2, with offset voltage.)
However I thought that it's time for an upgrade after all these years.
So I started to look up after parts, and after a lot of study, I decided to pick up the following components:
Motherboard: Asus Maximus X Hero (no wi-fi)
CPU: Intel i7-8700k
Cooler: Noctua NH-D15
RAM: GSkill TridentZ RGB 16GB DDR4 3200MHz, CL14 (2x8GB, dual channel)
HDD: Seagate FireCuda SSHD 2TB SATA3 7200rpm
PSU: Seasonic Focus+, 750W, 80+ Platinum
Case: Sharkoon DG7000-G
Components moved from my old PC:
HDD: Seagate 2TB ST2000DM001, SATA3
SSD: Kingston HyperX Savage 480GB, SATA3
VGA Card: ASUS GTX760-DC2OC-2GD5, 256bit, 2GB (I haven't upgraded 'cuz of these insanely high prices nowadays, damn you miners)
So, I happily assembled my new system, it worked after pressing Start button for the first time. (usually this is rare hehe)
At start I thought not to owerclock, just let's see how it works.
I kept using it for about a week, measuring temps, then I started to mess around in bios to try overclocking the system.
(also updated to the latest v1003 Bios)
My main reason was not the +200,300Mhz gain, but the thing that I noticed some high voltages with stock mobo owerclock.
(sometimes hitting past 1.4 volts, at 4.7Ghz).
So, like I did with my last build, I tried to use offset owerclock, because I like to keep it on low voltages while
my system is not on heavy loads. (tried adaptive first but I didn't really got the desired voltages, 'cuz while heavy load,
the system always worked past the voltages that I have set in bios). I found my system stable at 4.8Ghz at around 1.28v,
with likeable temperatures around 80C while running Prime95 no AVX, and AVX hitting 85-86C. (this was manual, all time at same voltage setup).
Then I tried adaptive voltages, didn't liked it. Moved on to offset. Now I know that I messed it up by giving too much + offset,
ending up killing my CPU. (Mobo was showing Q-Code 00 all the time, and below where the Leds are, my CPU led was red).
No problem, I have warranty, so I sent it back for replace.
Got my new i7 after a week, so I started to mess around again in bios, to set a stable owerclock.
Again I found a sweet spot around 1.26-1.28v, but now for 4.9Ghz. I've set a -30 offset. It worked great while testing.
I forgot to mention that in the first case I had XMP profile set up for my RAM, to be able to run it at supposed speed, 3200Mhz.
With the replaced CPU I left alone XMP and just entered manually the settings (DDR4-3200MHz, 14-14-34, 1.35v, even lowered the
VCCIO voltage to 1v and the System Agent voltage to 1.1v, because i thought that auto is giving too much.)
So I went happily to sleep after all day messing around with owerclocking, thinking that finally my system is stable.
Then in the morning when I woke up, I started my PC. It started with double boot and it restarted like 3 times, no post,
ending up killing my CPU again. (from what I think). Now I've got "0d" in my Q-Code display, and the same red CPU Led under.
So I've sent it back again, and I'm waiting for the new one again.
I've decided to write this because I am left without any more ideas.
Killing 2 CPUs in a month is kind of rare I think.
I haven't bought this i7 to not be able to owerclock it, especially when stock voltages are insanely high,
and I know that by manually settings i can go a lot lower, at even higher core speeds.
What am I doing wrong? 1.28v isn't supposed to kill my CPU.
Again with my second owerclock i haven't passed 85C in tests.
What I am thinking of it's maybe my RAM is killing it? Maybe I have to stay bethween the safe maximum speed (it's 2666Mhz for this i7).
I really don't know what to do anymore. I am open to anny suggestion.
Thanks for reading this "book" I wrote. And have a nice day.
(sorry if I'm ain't writing gramatically correct, I am not an english speaking person)
It's my second custom build. My first was back in 2011 with the legendary i5-2500k which is still running flawlessly.
(Still overclocked to 4.2, with offset voltage.)
However I thought that it's time for an upgrade after all these years.
So I started to look up after parts, and after a lot of study, I decided to pick up the following components:
Motherboard: Asus Maximus X Hero (no wi-fi)
CPU: Intel i7-8700k
Cooler: Noctua NH-D15
RAM: GSkill TridentZ RGB 16GB DDR4 3200MHz, CL14 (2x8GB, dual channel)
HDD: Seagate FireCuda SSHD 2TB SATA3 7200rpm
PSU: Seasonic Focus+, 750W, 80+ Platinum
Case: Sharkoon DG7000-G
Components moved from my old PC:
HDD: Seagate 2TB ST2000DM001, SATA3
SSD: Kingston HyperX Savage 480GB, SATA3
VGA Card: ASUS GTX760-DC2OC-2GD5, 256bit, 2GB (I haven't upgraded 'cuz of these insanely high prices nowadays, damn you miners)
So, I happily assembled my new system, it worked after pressing Start button for the first time. (usually this is rare hehe)
At start I thought not to owerclock, just let's see how it works.
I kept using it for about a week, measuring temps, then I started to mess around in bios to try overclocking the system.
(also updated to the latest v1003 Bios)
My main reason was not the +200,300Mhz gain, but the thing that I noticed some high voltages with stock mobo owerclock.
(sometimes hitting past 1.4 volts, at 4.7Ghz).
So, like I did with my last build, I tried to use offset owerclock, because I like to keep it on low voltages while
my system is not on heavy loads. (tried adaptive first but I didn't really got the desired voltages, 'cuz while heavy load,
the system always worked past the voltages that I have set in bios). I found my system stable at 4.8Ghz at around 1.28v,
with likeable temperatures around 80C while running Prime95 no AVX, and AVX hitting 85-86C. (this was manual, all time at same voltage setup).
Then I tried adaptive voltages, didn't liked it. Moved on to offset. Now I know that I messed it up by giving too much + offset,
ending up killing my CPU. (Mobo was showing Q-Code 00 all the time, and below where the Leds are, my CPU led was red).
No problem, I have warranty, so I sent it back for replace.
Got my new i7 after a week, so I started to mess around again in bios, to set a stable owerclock.
Again I found a sweet spot around 1.26-1.28v, but now for 4.9Ghz. I've set a -30 offset. It worked great while testing.
I forgot to mention that in the first case I had XMP profile set up for my RAM, to be able to run it at supposed speed, 3200Mhz.
With the replaced CPU I left alone XMP and just entered manually the settings (DDR4-3200MHz, 14-14-34, 1.35v, even lowered the
VCCIO voltage to 1v and the System Agent voltage to 1.1v, because i thought that auto is giving too much.)
So I went happily to sleep after all day messing around with owerclocking, thinking that finally my system is stable.
Then in the morning when I woke up, I started my PC. It started with double boot and it restarted like 3 times, no post,
ending up killing my CPU again. (from what I think). Now I've got "0d" in my Q-Code display, and the same red CPU Led under.
So I've sent it back again, and I'm waiting for the new one again.
I've decided to write this because I am left without any more ideas.
Killing 2 CPUs in a month is kind of rare I think.
I haven't bought this i7 to not be able to owerclock it, especially when stock voltages are insanely high,
and I know that by manually settings i can go a lot lower, at even higher core speeds.
What am I doing wrong? 1.28v isn't supposed to kill my CPU.
Again with my second owerclock i haven't passed 85C in tests.
What I am thinking of it's maybe my RAM is killing it? Maybe I have to stay bethween the safe maximum speed (it's 2666Mhz for this i7).
I really don't know what to do anymore. I am open to anny suggestion.
Thanks for reading this "book" I wrote. And have a nice day.
(sorry if I'm ain't writing gramatically correct, I am not an english speaking person)