First things first - hello to everyone on the forum that was the most helpful one during my trip with PCs, laptops and such. Now I come to ask my own question, since I can't really find an answer anywhere on the Internet.
Specs:
- 7700k @ stock for now
- Gigabyte GA-Z270X-Ultra Gaming
- G.Skill Ripjaws V 2x8GB 3200MHz (currently XMP disabled, so 1,2v and 2133MHz)
- Palit Jetstream GTX1080
- Corsair RM650X
- Some M.2 SSD and 2 HDDs (not important regarding this issue)
So...
For a couple of days I've tried to lower the temps by adjusting Vcore, and so testing began as I made my trip from 1,165v to 1,19v, which seemed stable under load (AIDA stress test, didn't try Prime95). It was all nice and dandy, but today I got another bluescreen signaling instability during Dishonored 2 play session (CLOCK_WATCHDOG_TIMEOUT). So, things needed to be done - I went to bios and changed Vcore to 1,195v and went straight to Windows to test it yet again, I fired up HWMonitor, then AIDA, aaaand that's where I noticed absolutely crazy (to me) voltage of 1,512v. Absolute panic, return to bios, check if voltages are set correctly, and they were. Now it shows 1,5v everywhere, it seems I can't control it whatsoever. It even showed 1.6v when I fired PC up after a while (~1hrs)
Things I tried:
- Change Vcore to multiple different values - no effect
- Reset bios via defaults and battery reseating - no effect
- Flash bios (from F4 to F8) - no effect
- Reseating CPU - no effect
- Change Vcore with Gigabyte utility - no effect
- Change other voltages to check if they have any effect - none
- Launch stress test to see if it's a sensor issue - instant BSoD (CLOCK_WATCHDOG_TIMEOUT)
Temperatures seem to be fine while idle (~40*C on package with 1.215v is nothing new to me with this build), but I'm not able to do anything other than firing up browser and praying that it holds up somehow.
An interesting thing: when it showed 1.6v I did observe voltage gradually dropping over time back to 1.5v in bios. No idea if this helps with diagnosing.
I'm unable to get spare parts for testing, so I'm down to what I have here. All I could do is try another motherboard in a week or two, but I need this PC working as of now.
Specs:
- 7700k @ stock for now
- Gigabyte GA-Z270X-Ultra Gaming
- G.Skill Ripjaws V 2x8GB 3200MHz (currently XMP disabled, so 1,2v and 2133MHz)
- Palit Jetstream GTX1080
- Corsair RM650X
- Some M.2 SSD and 2 HDDs (not important regarding this issue)
So...
For a couple of days I've tried to lower the temps by adjusting Vcore, and so testing began as I made my trip from 1,165v to 1,19v, which seemed stable under load (AIDA stress test, didn't try Prime95). It was all nice and dandy, but today I got another bluescreen signaling instability during Dishonored 2 play session (CLOCK_WATCHDOG_TIMEOUT). So, things needed to be done - I went to bios and changed Vcore to 1,195v and went straight to Windows to test it yet again, I fired up HWMonitor, then AIDA, aaaand that's where I noticed absolutely crazy (to me) voltage of 1,512v. Absolute panic, return to bios, check if voltages are set correctly, and they were. Now it shows 1,5v everywhere, it seems I can't control it whatsoever. It even showed 1.6v when I fired PC up after a while (~1hrs)
Things I tried:
- Change Vcore to multiple different values - no effect
- Reset bios via defaults and battery reseating - no effect
- Flash bios (from F4 to F8) - no effect
- Reseating CPU - no effect
- Change Vcore with Gigabyte utility - no effect
- Change other voltages to check if they have any effect - none
- Launch stress test to see if it's a sensor issue - instant BSoD (CLOCK_WATCHDOG_TIMEOUT)
Temperatures seem to be fine while idle (~40*C on package with 1.215v is nothing new to me with this build), but I'm not able to do anything other than firing up browser and praying that it holds up somehow.
An interesting thing: when it showed 1.6v I did observe voltage gradually dropping over time back to 1.5v in bios. No idea if this helps with diagnosing.
I'm unable to get spare parts for testing, so I'm down to what I have here. All I could do is try another motherboard in a week or two, but I need this PC working as of now.