02-20-2017 03:52 PM - last edited on 03-06-2024 08:49 PM by ROGBot
12-21-2018 09:06 AM
12-27-2018 10:06 AM
Arne Saknussemm wrote:
Hi autoturk
Sorry I had Haswell in my post but we're talking Haswell E X99...different platform...
1.3 VCCSA on that platform is at the high end of safe I think...though too much can be as bad as not enough sometimes
Maybe start a new thread?
12-21-2018 03:38 PM
12-21-2018 11:13 PM
12-22-2018 07:13 AM
Arne Saknussemm wrote:
Keep under 1.2 VCCSA 1.1 is fine...just bump to 1.0v and then 1.05.....1.1...
01-16-2019 09:12 AM
02-02-2019 09:54 AM
GoatHumper wrote:
After a few relapses, I've noticed that the LED display shows "E1" which according to the manual corresponds to "S3 Boot Script execution" ... I wonder if there's a means for debugging what instruction it's hanging on...
Also, there's a blinking yellow light right by the LED, from the PCI Express I think... I'm afraid I didn't check to see which slot it was. I have a 1080 TI on PCIE_X16_1, NVME drives on both PCIE_X16/X8_3 and PCIE_X8_4, with a PCIE x1 sound card (old but gold SB X-Fi Titanium Fatal1ty) on PCIE_X4_1. I'll be more mindful the next time it happens to identify which device might be causing issues. At this point, my money is on the sound card since it's the older device.
Cheers!
02-02-2019 10:12 AM
badmojout wrote:
When you see the E1 code, how did you wake the computer? *By moving the mouse or kitting a key? *If so, try this the next time. *Wake up your computer and when everything starts up but you get a black screen, just wait. *Make yourself a sandwich, grab a drink but just wait it out. *I suspect it’ll eventually resume and load into Windows. *Give it a good 15-30 minutes before you think of doing a hard reset or power off. *If my hunch is correct, it should boot into Windows well before the 15 minute mark. *
02-02-2019 11:11 AM
GoatHumper wrote:
Arne? You still there?
02-02-2019 12:05 PM
Arne Saknussemm wrote:
Sort of :o...sorry..seem to have missed some posts...
Waking from sleep problems are often RAM related so my first thought is more of the same...either relax timings or bump voltage(s) a bit
If the RAM is unstable and you are getting BSODs or having to hard reset you might also run into OS corruption which feeds back to greater instability
Maybe run "sfc /scannow" in cmd as admin to check OS is OK