|Topic Review (Newest First)|
|01-28-2019 05:22 AM|
Yeah I've read some that say adaptive isn't all that great on haswell-e
For cache I've use offset of +0.175 for like 3+ years and it maxes out at 1.122v for 38
I've used adaptive for core voltage I think it works okay
But like I said past bios 2101 vccio pch and vccio cpu needs to be manually set to 1.05v for their standard voltage otherwise vccio cpu gets really zapped to 1.25v+- instead of 1.05+- which has also been said to be cooking voltage.
|01-27-2019 07:17 PM|
|OFDM||Cache was at 4gHz on adaptive with a max of 1.15v. As mentioned before all the problems started when I reset to defaults, and now those problems have persisted on the new board. I disabled XMP on the Strix via the physical switch, which allowed it to POST, but it crashes immediately upon entering the desktop. It doesn't seem to want to load correct defaults for the chip. For whatever reason anytime I reset to default with the Strix it tries to set a 125 mHz BCLK. That is the case with or without XMP. So I'm leaning toward the CPU. I feel RAM has been sufficiently tested, and the same circumstances persist whether the m2 is installed or not, won't load an OS with a thumb drive either.|
|01-27-2019 03:16 PM|
Yeah you could try 4 sticks and see how it goes.
What cache oc'ing were you doing exactly voltage offset... ?
|01-27-2019 02:29 PM|
So I had changed all the various boot settings and cleared secure keys to no avail. Always resulted in freezing at the OS load point. So my new ROG Strix X99 showed up and worked for about 2 weeks before the system started failing to POST intermittently, usually in conjunction with any BIOS changes. It too has frozen on OS load a few times as well. Now I can only get it to POST one out of every 3 or 4 attempts and it goes to 'failed overclock press f1' even though there is no OC applied, default settings are loaded.
So it's entirely possible the Sabertooth is fine, and it's either the 5820k or one of 8 DIMMS. Thing is, these failures seem to coincide with overclock attempts, particularly any changes to the cache multiplier. I ran a cache overclock for years and may have damaged something on the CPU just enough for it to intermittently fail like this. I checked each DIMM independently with the Sabertooth and it always did the same thing, so I'm leaning towards the 5820k. Power supply is new and an older one resulted in the same behavior on the sabertooth. So now I'm debating between a new i9 board and a 9900k or saving a few hundred and looking for a deal on a 6800k or the like.
|01-15-2019 11:57 AM|
Just disabling fast start and clearing secure boot keys which will disable secure boot.
Select Other OS as OS Type rather than uefi only boot it would be rare if that changed.
|01-15-2019 12:32 AM|
|AndiWandi||There may be USB incompatibilities preventing the board to boot (usually a PS4 controller). Also try disabling CSM as that too was causing the spinning dots to stop.|
|01-14-2019 01:45 PM|
I believe my sabertooth just died after simply setting the BIOS back to defaults. It's been stable for 4 years with a 5820K running at 4.5 with 1.2v on water. Reset the BIOS to default in anticipation of flashing a newer release. After the reset the machine will not load an OS, it freezes a few seconds after the circle timer appears. Occasionally the machine simply powers off after the circle timer freezes, other times it restarts, but most times it just permanently freezes. Removed the M.2 drive and attempted with a newly created windows installation USB drive, same thing. Haven't tried Linux yet, but I might.
I can get into and change the BIOS fine, but occasionally the machine doesn't even post. I tried to reload the previous OC profile and the BIOS just freezes when that is attempted.
I was able to flash the new BIOS but the same condition persists. Reset the BIOS via jumper, removed the battery, still the same. Used Tuf detective from the phone to clear BIOS, still the same.
Tested all the RAM independently. I'm at a loss and I don't see any other possibility than a permanently corrupted BIOS or HW failure somewhere on the board. In the meantime I've ordered a ROG strix x99 as I wasn't really looking to build a whole new rig just yet. I may try flashing back to the older firmware but I don't see the point. It was simply setting defaults that created the condition.
This board has been a bit flaky for a while with respect to boots, every once in a while it's required a couple attempts to get it to POST, particularly after changing something in the BIOS. Whatever was creeping up seems to have finally arrived. Any final tricks I should try? Thanks.
|01-03-2019 06:43 AM|
About all I got off the manual compatible versions
Assuming you had secure boot on with the other install you probably would of had to turn it off and clear existing secure boot keys before installing the m.2
|01-02-2019 06:17 PM|
Hey all. I was going to refresh my PC with an upgrade with an M.2 Samsung 970 Evo NVMe drive. I checked the key and size and it looks like the board can hold it. I removed most all the USB connections except the keyboard and mouse and unplugged all internal drives. I installed the M.2 and booted with a Windows USB ready to go. Well, I got the BOOT_DEVICE red LED and my board is stuck on the POST image. I can't get into the BIOS, the computer is frozen. I have tried removing the M.2 and booting but the problem remains the same. I have tried resetting the CMOS with the jumper, as well as BIOS Flashback to the latest BIOS and one version back. No luck, it still does the same thing. I will probably have to warranty the board unless anyone can think of something else I can try to fix it.
Setup is as follows:
32GB Corsair Vengeance LPX 8x4GB
Some SSDs and HDDs (currently unplugged)
|09-26-2018 02:15 AM|
|brotherscro1||Hello I just got Samsung 860 EVO SSD currently I have 850 EVO without any issues so I was wondering if anyone has 860 EVO on this motherboard are there any issues or anything|
|This thread has more than 10 replies. Click here to review the whole thread.|