05-03-2016
12:38 AM
- last edited on
03-06-2024
02:22 AM
by
ROGBot
05-03-2016 02:21 AM
05-03-2016 02:49 AM
brkkab123 wrote:
I have the same case & motherboard. Are you using the case's fans hooked up to the case like it came or did you plug them into the motherboard ? Either way try setting them to medium or high and see what happens.
Also were the new parts added after the original Windows install ? If so, a clean install may help.
Is your ram on the mobo's QVL ? http://www.asus.com/us/Motherboards/MAXIMUS-VIII-HERO/HelpDesk_QVL/
Also Nvidia put out new video card drivers yesterday. http://www.nvidia.com/Download/index.aspx?lang=en-us They're now version 365.10
05-03-2016 04:45 AM
05-03-2016 04:46 AM
05-04-2016 02:15 AM
Eric_F wrote:
A few thoughts:
Be sure you're running the latest BIOS -- It's version 1601 currently for your board. If you need to update it, remember to clear the CMOS after flashing with the "Clear CMOS" button on the mobo, then when you first go into the BIOS, use the "Load Optimized Defaults" option and then start making settings.
Fans - Try at least medium speed on your case fans if you want to leave them connected to the control in the case. I personally prefer to use the mobo controller. If you plug them into the mobo. use the Q-Fan control settings in BIOS to set the baseline performance. Then fine-tune in Fan Xpert. (Using Fan Xpert, I like to set the fan curves to come on a little more aggressively than what the auto-tuning sets, and I disable auto-off for any fans so they always run, but stay quiet most of the time.
Sometimes timing issues cause odd things with Skylake processors and Windows 10; it can be trickier when overclocked, but there are also plenty of reports of issues on stock speed and high-performance systems. A lot of folks have good results with locking the timer source to the HPET output (High Precision Event Timer). Open a command prompt with "Run as Administrator" option and type this: "bcdedit /set useplatformclock true" (Without quotes) To un-do it if you want, open the command prompt the same way and type "bcdedit /deletevalue useplatformclock" (Without quotes again). Having HPET explicitly enabled as the primary timer source seems to reduce some of the wake/sleep/shutdown problems on a lot of Skylake platforms -- but it isn't the cure-all.
The monitors' color change + lockup behavior could also be related to the video card and drivers. What version of the Nvidia driver are you using? Windows loads an old driver, which may not be optimal. There's been some problems reported with the 364.xx series, so if you updated it in the past few days, you may have 364.72. Lots of people say that staying slightly behind on 362.00 has been the most stable. (Nvidia just released 365.10 yesterday, but I haven't had time to gather info on it yet to tell if it's worth updating.)
The anti-surge protection on the mobo can be oversensitive and cause reboots, especially when overclocking the CPU and/or memory. Try turning it off. (Invest in a high-quality surge protector for your whole system instead.)
I see you're using OC'd memory. First try running the RAM at stock DDR4 speeds (1600 MHZ / BIOS default). Then see if the system is stable. If it is, then try bringing the speed up. Maintaining 3200 MHz takes more than stock voltage to RAM and the System Agent. Try setting the default XMP profile for your memory first. Turn OFF the "ASUS Multicore Enhancement" for the CPU, and turn ON "Maximus Tweak 1" in your memory settings. Increase "DRAM Current Capability" to 120% or 130%. Put Core/Cache voltage in "Adaptive" mode. If you still have stability issues, try carefully increasing DRAM voltage and System Agent voltage. (1.35 is typical DRAM voltage for 3000 MHZ and above.) System agent voltage might have to be raised between 1.25 and 1.3 for memory stability, but you shouldn't need to go above that. High speed memory puts more load on the memory controller -- so you might have to compensate a little bit.
In general, it's best to use stock memory speed (underclock the RAM you have) until you know the CPU configuration is stable, and then OC the CPU first. After that, bring up the DRAM speed with the XMP profile as the basis.
The Maximus boards might be a little intimidating with all the fine-tuning involved, but keep with it. It's worth it! :cool:
05-04-2016 08:26 AM
05-04-2016 02:51 PM
Chino wrote:
Does the problem occur with your system at stock speed?
05-05-2016 04:00 AM
05-05-2016 04:30 AM
Eric_F wrote:
Latest 365.10 Nvidia driver is getting a lot of positive feedback now. I upgraded and have had no problems with it. The "Gamer" OC profile is a good start toward a stable OC for everyday use. It will push the settings in the direction of what I already described (Which are ones I learned from reading these forums :)) plus others geared toward good support for overclocking the CPU. Once you're sure the system is stable, you may want to try the XMP setting that corresponds to your memory and continue tweaking from there.
Personally, I get the best results by making all settings in the BIOS, rather than using AISuite. I mostly use AISuite for the advanced fan control in FanXpert -- it lets me adjust the fan response curve as well as add a delay in the response particularly for stepping down (It holds higher speed for longer to ensure good cooling). It also offers variable speed for my compatible water pump, which the BIOS QFan control doesn't seem to offer.