Hi All,
I had my brand new 6700K on an Asus Z170-WS running at 4.6GHz using Offset vcore mode. I was actually lowering voltage via offset mode: At the time of the CPU's demise, it was running offset -0.070 which was resulting in a vcore display of 1.328 in BIOS, an HWMonitor reading of 1.248v at idle, and a load value of 1.360v. Nothing scary at all. Temps while running RealBench were chilly at 55/59/53/55 (Corsair H115i).
Nothing else fancy in the BIOS. Just XMP enabled for my 3200MHz Corsairs, and pretty much everything else (the exception being offset vcore of -0.070) left at auto as recommended most places for Skylake.
I walked away from this system to run an 8 hour RealBench validation run (to confirm it was stable), and when I came back for a check-in around 90 minutes in. . . the screen was frozen, and yet I could still see HWMonitor reporting a vcore of. . .. wait for it. . . 1.984v.
one, point, nine, eight, four. w. t. f.
The CPU is toast. Won't boot into Windows. Even moved it into another computer and it misbehaves there too (while a swapped core i5 6500 works okay in mine).
So, my question: Would you chalk that 1.984v showing as vcore on the frozen screen as an anomaly due to the CPU dying at that moment. . . or rather would you look at it as the cause and perhaps suspect the motherboard? I have no reason to suspect the PSU. It has served me well in my Haswell rig and it's a Seasonic X-series 1250.
Just a dud CPU. . . or would you swap out the motherboard too? I love most things about this motherboard but I'm not sure I can trust it.
Also, any thoughts on how likely this was to have taken other components with it? I'm thinking vcore is pretty isolated, but would hate to have zapped my Titan X (old) or other components!
--H
I had my brand new 6700K on an Asus Z170-WS running at 4.6GHz using Offset vcore mode. I was actually lowering voltage via offset mode: At the time of the CPU's demise, it was running offset -0.070 which was resulting in a vcore display of 1.328 in BIOS, an HWMonitor reading of 1.248v at idle, and a load value of 1.360v. Nothing scary at all. Temps while running RealBench were chilly at 55/59/53/55 (Corsair H115i).
Nothing else fancy in the BIOS. Just XMP enabled for my 3200MHz Corsairs, and pretty much everything else (the exception being offset vcore of -0.070) left at auto as recommended most places for Skylake.
I walked away from this system to run an 8 hour RealBench validation run (to confirm it was stable), and when I came back for a check-in around 90 minutes in. . . the screen was frozen, and yet I could still see HWMonitor reporting a vcore of. . .. wait for it. . . 1.984v.
one, point, nine, eight, four. w. t. f.
The CPU is toast. Won't boot into Windows. Even moved it into another computer and it misbehaves there too (while a swapped core i5 6500 works okay in mine).
So, my question: Would you chalk that 1.984v showing as vcore on the frozen screen as an anomaly due to the CPU dying at that moment. . . or rather would you look at it as the cause and perhaps suspect the motherboard? I have no reason to suspect the PSU. It has served me well in my Haswell rig and it's a Seasonic X-series 1250.
Just a dud CPU. . . or would you swap out the motherboard too? I love most things about this motherboard but I'm not sure I can trust it.
Also, any thoughts on how likely this was to have taken other components with it? I'm thinking vcore is pretty isolated, but would hate to have zapped my Titan X (old) or other components!
--H