ASUS X99 Motherboard Series - Official Support Thread

Sycraft said:
....The WS is nice on account of the higher grade components (completely overkill, but still neat) and the PLX chip meaning all 16x PCIe all the time for all the slots :D.
Click to expand...

WS has 7 PCI-e 3.0 x16 slots but when all are in use (with 40-lane processor) only one of them is operating in x16 mode, others are x8. Which is still more than enough for practical applications. WS is ideal for high-end workstation packed with cards, it accepts up to 128 GB of RAM:

http://www.asus.com/Commercial_Servers_Workstations/X99E_WS/specifications/
 
what is CPU Power Thermal Control in bios?
at default it stays at 120, is 120c or 120 fahrenheit?
 
I've got the 40 to AA LED bug. Running the 904 BIOS and it's still there. Anyone know of any fixes or hope that the next BIOS is going to address this?
 
Weeth said:
I've got the 40 to AA LED bug. Running the 904 BIOS and it's still there. Anyone know of any fixes or hope that the next BIOS is going to address this?
Click to expand...

Code 40 is normal depending on how the machine was shutdown by Windows. There is no bug to patch.
 
Raja@ASUS said:
Code 40 is normal depending on how the machine was shutdown by Windows. There is no bug to patch.
Click to expand...

Code 40 crashes and reboots my system 9 times out of 10. When I get a 40 I reboot and get an AA and it's rock solid.
 
Then your system is unstable coming out or sleep/hibernation. Could be a number of things from instability with memory or CPU OC to drivers.
 
Last edited:
I have a more serious problem now. This is my config Raja:
5960X, RVE, G.Skill Ripjaws 4 F4-3000C15Q-16GRR, Corsair H110 with Noctua NF-A14-FLX, MSI 780Ti Gaming 3G with GOP BIOS, PSU is Corsair 1200.

When reset to "optimized defaults" it is fine, but if I apply XMP profile (the only one) to make it run at 1.35 and 3000, I get freezes on reboot. Sometimes it is a "db" code, sometimes "CE", sometimes it just sits there with A2 or AA or A6... with no picture of BIOS on. And really, those codes don't help that much...

Also, after updating BIOS of the MBO to 0706, my BIOS screen flickers, like something is wrong with the VGA or cable or monitor (it is not when connected to other PC).

I've tried following an Asus ROG guide for overclocking too, but the very first try at 1.3V and multiplier to 45 (as per instructions) caused a freeze in desktop and totally messed the machine so I had to reflash BIOS with BIOS2...
 
Last edited:
Raja@ASUS said:
Then your system is unstable coming out or sleep/hibernation. Could be a number of things from instability with memory or CPU OC to drivers.
Click to expand...

Thanks for your info, Raja. I've brought the Octocore back to factory spec speed and all the drivers are updated. As far as I can tell there is no problem with the memory, but I'd appreciate if you can let me know what diagnostics I should run to try and isolate this problem.
 
What's the part number of the memory kit? Suspecting you have combined memory kits - and that is your issue.
 
toncij said:
I have a more serious problem now. This is my config Raja:
5960X, RVE, G.Skill Ripjaws 4 F4-3000C15Q-16GRR, Corsair H110 with Noctua NF-A14-FLX, MSI 780Ti Gaming 3G with GOP BIOS, PSU is Corsair 1200.

When reset to "optimized defaults" it is fine, but if I apply XMP profile (the only one) to make it run at 1.35 and 3000, I get freezes on reboot. Sometimes it is a "db" code, sometimes "CE", sometimes it just sits there with A2 or AA or A6... with no picture of BIOS on. And really, those codes don't help that much...

Also, after updating BIOS of the MBO to 0706, my BIOS screen flickers, like something is wrong with the VGA or cable or monitor (it is not when connected to other PC).

I've tried following an Asus ROG guide for overclocking too, but the very first try at 1.3V and multiplier to 45 (as per instructions) caused a freeze in desktop and totally messed the machine so I had to reflash BIOS with BIOS2...
Click to expand...




1) Was the machine ever stable at stock? Did you check that before overclocking the CPU? Following the guide as stated would not mess up the BIOS unless some kind of serious issue exists.

2) I suspect you tried to push too hard too soon. Work on memory only first. No point in overclocking the CPU and making things hard for yourself before getting the memory stable. DDR4-3000 can need VCCSA adjustments and some other things to be tuned.

3) How is the GPU connected to the monitor? What kind of interface is being used (DVI, HDMI etc).
 
Last edited:
Raja@ASUS said:
1) Was the machine ever stable at stock? Did you check that before overclocking the CPU? Following the guide as stated would not mess up the BIOS unless some kind of serious issue exists.

2) I suspect you tried to push too hard too soon. Work on memory only first. No point in overclocking the CPU and making things hard for yourself before getting the memory stable. DDR4-3000 can need VCCSA adjustments and some other things to be tuned.

3) How is the GPU connected to the monitor? What kind of interface is being used (DVI, HDMI etc).
Click to expand...

1. No. I mean, on BIOS defaults, yes, but not with XMP. The machine becomes very strange when I apply XMP (only). For example, after saving, it just goes to max fans speed and no boot to BIOS.

2. Was 100Hz x 45. Even memory was stock without XMP. But, yes, thx.

3. Display Port and monitor is in 1.2 mode (LG 3440x1440 UC97 model).
 
Last edited:
toncij said:
1. No. I mean, on BIOS defaults, yes, but not with XMP. The machine becomes very strange when I apply XMP (only). For example, after saving, it just goes to max fans speed and no boot to BIOS.

2. Was 100Hz x 45. Even memory was stock without XMP. But, yes, thx.

3. Display Port and monitor is in 1.2 mode (LG 3440x1440 UC97 model).
Click to expand...

1) Likely VCCSA needs tuning for the CPU. Update to 0801 UEFI (in the first post and start from there).

2) Okay - take it easy this time

3) That DP cable might be leaking DC back into the board. There are a lot of non compliant DP cables out there that connect pin 20 when they should not. If that is the case, 3.3V will be fed back into the board via the GPU causing all sorts of issues. The board power seequencing and most ICs need that rail to be pulled down during power cycle. When it is present due to a non coompliant cable, the onboard devices don't restart or initialize properly. Hopefully that isnt the case here - but something about a flickering display and all manner of instability make me think it could be. This is exactly why I asked you how the monitor is connected (suspected DP cable).

The only other thing it could be is an issue with the monitor handling 1280X1024 res (the output res of UEFI).

-Raja
 
toncij said:
Is there a way to test that leakage with a voltmeter maybe?
Click to expand...

If you can get to the pins connect one end to the monitor with it powered and carefully check for any DC on pin 20.


http://hackipedia.org/Hardware/video/connectors/DisplayPort/VESA DisplayPort Standard v1.1a.pdf

Page 196

See footnotes

Notes:
1) Pins 13 and 14 must be connected to ground through a pull-down device. External devices and cable
assemblies must be designed to not rely on a low impedance ground path from these pins.
2) Pin 20, PWR Out, must provide +3.3 volts ± 10% with a maximum current of 500 mA and a
minimum power capability of 1.5 watts.

Figure 4-14 shows the wiring of an external cable connector assembly. The standard external cable connector assembly must not have a wire on pin 20, DP_PWR.
 
Raja@ASUS said:
If you can get to the pins connect one end to the monitor with it powered and carefully check for any DC on pin 20.


http://hackipedia.org/Hardware/video/connectors/DisplayPort/VESA DisplayPort Standard v1.1a.pdf

Page 196

See footnotes

Notes:
1) Pins 13 and 14 must be connected to ground through a pull-down device. External devices and cable
assemblies must be designed to not rely on a low impedance ground path from these pins.
2) Pin 20, PWR Out, must provide +3.3 volts ± 10% with a maximum current of 500 mA and a
minimum power capability of 1.5 watts.

Figure 4-14 shows the wiring of an external cable connector assembly. The standard external cable connector assembly must not have a wire on pin 20, DP_PWR.
Click to expand...


Cheap DP cables are especially prone to this.

You might find it easier to try a different monitor or connection method to debug this than measuring for DC.
 
I've solved this now with monitor in 1.1 mode, instead of 1.2. Works fine now.

Still, have problems clocking it. Even in BIOS, CPU temp is 36-38 C on 125x32 (XMP applied).

Stock + XMP works fine now, but temps are insane. Could be a bad setup of H110 (pull on top, radiator below fans, fans and radiator below top).
 
toncij said:
I have a more serious problem now. This is my config Raja:
5960X, RVE, G.Skill Ripjaws 4 F4-3000C15Q-16GRR, Corsair H110 with Noctua NF-A14-FLX, MSI 780Ti Gaming 3G with GOP BIOS, PSU is Corsair 1200.

When reset to "optimized defaults" it is fine, but if I apply XMP profile (the only one) to make it run at 1.35 and 3000, I get freezes on reboot. Sometimes it is a "db" code, sometimes "CE", sometimes it just sits there with A2 or AA or A6... with no picture of BIOS on. And really, those codes don't help that much...

Also, after updating BIOS of the MBO to 0706, my BIOS screen flickers, like something is wrong with the VGA or cable or monitor (it is not when connected to other PC).

I've tried following an Asus ROG guide for overclocking too, but the very first try at 1.3V and multiplier to 45 (as per instructions) caused a freeze in desktop and totally messed the machine so I had to reflash BIOS with BIOS2...
Click to expand...

There are tons of users who have problem using XMP 2800 or 3000.
Tons of bd error. This platform is borned bad.
Never had problem with XMP before.

Don't know if it is motherboard, CPU or ram problem, the fact is that this platform is really buggy all the way.
 
sblantipodi said:
There are tons of users who have problem using XMP 2800 or 3000.
Tons of bd error. This platform is borned bad.
Never had problem with XMP before.

Don't know if it is motherboard, CPU or ram problem, the fact is that this platform is really buggy all the way.
Click to expand...

So, going down to 2666 should solve the problem? Did that help?

ATM I have XMP running and CPU x30 to 3,75GHz, but the temperature is in idle desktop around 37-38 ℃.
 
toncij said:
So, going down to 2666 should solve the problem? Did that help?

ATM I have XMP running and CPU x30 to 3,75GHz, but the temperature is in idle desktop around 37-38 ℃.
Click to expand...

It should help but this is clearly a problem of the platform that is not able to achieve what it is advertised to do.
 
toncij said:
I've solved this now with monitor in 1.1 mode, instead of 1.2. Works fine now.

Still, have problems clocking it. Even in BIOS, CPU temp is 36-38 C on 125x32 (XMP applied).

Stock + XMP works fine now, but temps are insane. Could be a bad setup of H110 (pull on top, radiator below fans, fans and radiator below top).
Click to expand...


Glad it works - yes, check the pump speed etc.
 
toncij said:
Pump is 1488-1497 now. :)
Click to expand...


Whats its full speed? Set the header it is connected to at full speed.

Also get that cable checked if you can - any DC leaking back into the board is not good (if that was the case).

Those temps seem normal btw for a H110 on an 8 core CPU.
 
Raja@ASUS said:
Whats its full speed? Set the header it is connected to at full speed.

Also get that cable checked if you can - any DC leaking back into the board is not good (if that was the case).

Those temps seem normal btw for a H110 on an 8 core CPU.
Click to expand...

Is there a better cooler? Because, here the result is way better:

http://www.digitalstormonline.com/u...-review-and-overclocking-benchmarks-idnum324/

Seems that 0801 BIOS made it far more stable. I'm now running XMP 125 x33 at 1.2V at 34℃ in BIOS. Seems pretty good according to your comment. I'm not using any custom cooling for VRM, but I have 2 120mm NF-F12 PWMs on the side of the case blowing into MBO so it may help a little.
Not sure how would I put a cooler on VRM tho, I see no space for that and it is already pretty much crowded around it...
 
Last edited:
toncij said:
Is there a better cooler? Because, here the result is way better:

http://www.digitalstormonline.com/u...-review-and-overclocking-benchmarks-idnum324/

Seems that 0801 BIOS made it far more stable. I'm now running XMP 125 x33 at 1.2V at 34℃ in BIOS. Seems pretty good according to your comment. I'm not using any custom cooling for VRM, but I have 2 120mm NF-F12 PWMs on the side of the case blowing into MBO so it may help a little.
Not sure how would I put a cooler on VRM tho, I see no space for that and it is already pretty much crowded around it...
Click to expand...

same here, asus suggest to actively cool the VRM on low vcore too.
they never saied how to cool that and why we need to cool that on low vcore too.

1.3V is a low vcore, can't understand why a 350€+ board should be actively cooled for such a low vcore.
 
toncij said:
Is there a better cooler? Because, here the result is way better:

http://www.digitalstormonline.com/u...-review-and-overclocking-benchmarks-idnum324/

Seems that 0801 BIOS made it far more stable. I'm now running XMP 125 x33 at 1.2V at 34℃ in BIOS. Seems pretty good according to your comment. I'm not using any custom cooling for VRM, but I have 2 120mm NF-F12 PWMs on the side of the case blowing into MBO so it may help a little.
Not sure how would I put a cooler on VRM tho, I see no space for that and it is already pretty much crowded around it...
Click to expand...

Yes that is fine - UEFI actually places a partial load on the CPU - it does not idle in there. Stay on UEFI 0801.

I usually balance a fan near the VRM heatsink in a case. On an 8 core CPU, the current draw can be in excess of 300W during encodes.

When comparing temps one needs to bear in mind the differences between ambient temps on different setups.
 
Last edited:
Raja@ASUS said:
Yes that is fine - UEFI actually places a partial load on the CPU - it does not idle in there. Stay on UEFI 0801.

I usually balance a fan near the VRM heatsink in a case. On an 8 core CPU, the current draw can be in excess of 300W during encodes.

When comparing temps one needs to bear in mind the differences between ambient temps on different setups.
Click to expand...

I was too happy too early - "idling" in desktop at 25℃ room temp, get me a fixed 38℃ for XMP 3000 @ 125Hz x 33 and 4.125Ghz @ 1.2V (followed 'easy guide for 4.2'). Haven't tried load yet. Is this OK?

Also, Prime95 small test is not recommended I presume?
 
toncij said:
I was too happy too early - "idling" in desktop at 25℃ room temp, get me a fixed 38℃ for XMP 3000 @ 125Hz x 33 and 4.125Ghz @ 1.2V (followed 'easy guide for 4.2'). Haven't tried load yet. Is this OK?

Also, Prime95 small test is not recommended I presume?
Click to expand...

1) Again this is fine for idle temps. Your load temps in the applications you will run daily are the most important factor.

2) Stay away from small FFTs of Prime95 version 27.9 and 28.5. They can pull over 400W of power through an 8 core CPU at 1.30V

-Raja
 
Raja@ASUS said:
What's the part number of the memory kit? Suspecting you have combined memory kits - and that is your issue.
Click to expand...

G.SKILL Ripjaws 4 series 32GB (4 x 8GB) F4-2400C15Q-32GRR. I ordered two in black but one came in black and the other in red, so I sent back the second red kit and haven't yet received it. So that's all that has ever been installed in the rig.
 
Weeth said:
G.SKILL Ripjaws 4 series 32GB (4 x 8GB) F4-2400C15Q-32GRR. I ordered two in black but one came in black and the other in red, so I sent back the second red kit and haven't yet received it. So that's all that has ever been installed in the rig.
Click to expand...

I was going by your sig mentioning 64GB which it still does (was all I had to go on at the time).


Reset the system to stock if you have not already (again your sig mentions an overclock) and chase out the cause from there.
 
Last edited:
Raja@ASUS said:
I was going by your sig mentioning 64GB which it still does (was all I had to go on at the time).


Reset the system to stock if you have not already (again your sig mentions an overclock) and chase out the cause from there.
Click to expand...

Yup, system is absolutely stock default in every way and has been for days. I've tried several restarts during that time and have always had a random reboot within about the first 30 minutes of operation when the LED reads 40 and none with AA. It's not a scientific sampling but it's reflective of my experience with this board so far.
 
Weeth said:
have always had a random reboot within about the first 30 minutes of operation when the LED reads 40 and none with AA
Click to expand...

Hello

Sounds as if there is some type memory instability as resuming from S3/S4 is susceptible to these type of errors. Disable Fast Start in Win8.1 and the board will always boot showing AA on the Q-Code.
 
I got a question guys. In the manual it say which pci-e ports it recommends to use for two gpus in SLI. Now, I bought the nvidia branded LED bridge (actually by mistake i bought one of each for two way SLI, the "spaced" version and the shorter one). I ask because it recommends you use ports 1 and 3 for two way SLI in the user manual, but this is odd spacing and neither bridge will work properly if I use 1 & 3. Is it okay to use ports 1 & 2, or 1 & 4 as the either bridge will work respectively if I use one of those options instead. Will I be forced into a 16x and 8x situation if I don't use 1 & 3?

Any advice would be greatly appreciated.
 
You must log in or register to reply here.
Back
Top