F5F Stay Refreshed Power Users Overclocking Unable to achieve a consistent OC at 3770K

Unable to achieve a consistent OC at 3770K

Unable to achieve a consistent OC at 3770K

Pages (2): Previous 1 2
C
Crazy_Ken
Member
57
06-07-2016, 12:00 PM
#11
I know the core differences are due to a bad mount, but I won't remount until I get the conductonaut, since the way I see it, as long as the hottest cores aren't too hot there shouldn't be a problem right?
The nail polish thing, where and how much do I apply it? Do I just cover the whole chip around the die? Is there any specific nail polish I should use or will any do?
I have tried putting in 4.2GHz and leaving voltage on auto and it crashes as well, 124 error according to BlueScreenView.
EDIT: The auto voltage put it to ~1.3V when I was testing 4.2 with auto voltage.
Funny thing. I don't actually get a BSOD, the screen goes all fuzzy like on old TV's when there's no channel, then reboots. I have to check the BSOD codes with BlueScreenView. Majority of my codes are mostly vcore related from what I can tell.
Well, something new happened. I just got a crash on default settings...... d1 error code
Here's my BSW screenshot
https://imgur.com/a/7SIAbIK
View: https://imgur.com/a/7SIAbIK
I guess it could be my RAM going bad, since I had occasional crashes on my old 2500K setup, but I bumped vcore and it stopped. I guess it might have been a placeebo?
C
Crazy_Ken
06-07-2016, 12:00 PM #11

I know the core differences are due to a bad mount, but I won't remount until I get the conductonaut, since the way I see it, as long as the hottest cores aren't too hot there shouldn't be a problem right?
The nail polish thing, where and how much do I apply it? Do I just cover the whole chip around the die? Is there any specific nail polish I should use or will any do?
I have tried putting in 4.2GHz and leaving voltage on auto and it crashes as well, 124 error according to BlueScreenView.
EDIT: The auto voltage put it to ~1.3V when I was testing 4.2 with auto voltage.
Funny thing. I don't actually get a BSOD, the screen goes all fuzzy like on old TV's when there's no channel, then reboots. I have to check the BSOD codes with BlueScreenView. Majority of my codes are mostly vcore related from what I can tell.
Well, something new happened. I just got a crash on default settings...... d1 error code
Here's my BSW screenshot
https://imgur.com/a/7SIAbIK
View: https://imgur.com/a/7SIAbIK
I guess it could be my RAM going bad, since I had occasional crashes on my old 2500K setup, but I bumped vcore and it stopped. I guess it might have been a placeebo?

C
CriticalFrost
Member
61
06-14-2016, 04:55 PM
#12
Conductonaut is a liquid metal, which makes it somewhat conductive electrically. When examining the PCB, you'll notice small gold dots around the die. To protect against any Tim flows escaping the die, it's advisable to coat the entire surrounding PCB area with nail polish. This creates a barrier between the die and the PCB if needed.
C
CriticalFrost
06-14-2016, 04:55 PM #12

Conductonaut is a liquid metal, which makes it somewhat conductive electrically. When examining the PCB, you'll notice small gold dots around the die. To protect against any Tim flows escaping the die, it's advisable to coat the entire surrounding PCB area with nail polish. This creates a barrier between the die and the PCB if needed.

N
Naane
Junior Member
5
07-01-2016, 12:43 PM
#13
I think it might be memory issues, I have a HyperX Fury DDR3 1866MHz 1.5V. It was stable yesterday when I manually adjusted the RAM settings. I plan to run a memtest soon, then wait for conductonaut, update the BIOS, and try again—maybe even reinstall the BIOS. The last D1 BSOD likely happened because I had network drivers installed for revision 1.0, but I checked and upgraded to revision 1.1.
I hope it’s not memory-related, these sticks are more expensive than DDR4 3600 modules.
N
Naane
07-01-2016, 12:43 PM #13

I think it might be memory issues, I have a HyperX Fury DDR3 1866MHz 1.5V. It was stable yesterday when I manually adjusted the RAM settings. I plan to run a memtest soon, then wait for conductonaut, update the BIOS, and try again—maybe even reinstall the BIOS. The last D1 BSOD likely happened because I had network drivers installed for revision 1.0, but I checked and upgraded to revision 1.1.
I hope it’s not memory-related, these sticks are more expensive than DDR4 3600 modules.

Pages (2): Previous 1 2