ASUS x99 Deluxe + 5930k. Massive underclock

[Aceman.au]

Results from my latest PC. Check the clocks. Its sitting @ 2300mhz when running the test and the RAM is underclocking itself.

http://www.3dmark.com/fs/3856120

Something is seriously broken in my BIOS and I'm not sure what. The overclocks aren't kicking in and the RAM is supposed to be @ 2800mhz.

Old CPU and Mobo. Same Graphics cards.

http://www.3dmark.com/fs/2357879

 

[The N]

lol not a very noticeable performance difference in physics between them. there might be any power issue that bottlecking in performance.and what about GPU's score it is way drowned then ivy's setup.

if there is BIOS problem then did you tried updating the BIOS ?

 

[Aceman.au]

I adjusted some settings and got a much better result. Still pretty poor. http://www.3dmark.com/fs/3856316

The RAM wants to sit a low speed for some reason I can't figure out. I adjusted it to its speed in the BIOS but it refuses to go up.

Can't be a power issue. 1300w PSU

 

[Aceman.au]

This BIOS is too complicated for me. I'll start a new thread in 24 hours and start from square 1.

 

[WaterKewl]

You should be able to set XMP for 2800MHz target on the memory and call it a day.
A basic stock configuration shouldn't be giving you this much trouble. I think you should try updating the BIOS. If a BIOS update doesn't exist, flash and start from stock settings, read the manual and ASUS forums, and contact ASUS tech support. Asking questions here is fine, but you're not giving us a whole lot of information.

 

[cadaveca]

Working fine here:

http://www.3dmark.com/fs/3838024

 

[sneekypeet]

Hey @cadaveca does that 47 million MHz memory profile boot (XMP-0)?

 

[Aceman.au]

You should be able to set XMP for 2800MHz target on the memory and call it a day.
A basic stock configuration shouldn't be giving you this much trouble. I think you should try updating the BIOS. If a BIOS update doesn't exist, flash and start from stock settings, read the manual and ASUS forums, and contact ASUS tech support. Asking questions here is fine, but you're not giving us a whole lot of information.

I did that. Caused BSOD loops on startup. There's a profile for 3000mhz should I try that?

 

[Aceman.au]

Ok ran the 3000mhz XMP profile after updating the BIOS. Bumped up the multiplier. Got it stable @ 4.5ghz. Also I didn't realise the DRAM frequency is supposed to be doubled to get the actual frequency. I was wondering why it was sitting at half my set speed. Ran FS again got just under 7000. I dunno why I can't pull a result like the 12k on my 3930k, but I guess Ill have to live with it.

 

[Aquinus]

Ok ran the 3000mhz XMP profile after updating the BIOS. Bumped up the multiplier. Got it stable @ 4.5ghz. Also I didn't realise the DRAM frequency is supposed to be doubled to get the actual frequency. I was wondering why it was sitting at half my set speed. Ran FS again got just under 7000. I dunno why I can't pull a result like the 12k on my 3930k, but I guess Ill have to live with it.

Double? Why yes. That is what the first D in DDR stands for (Double Data Rate) which is because it sends data on every rising/falling clock edge, as a result the "effective clock speed" or "transfer rate" which I would consider the more proper term to use, would be double the actual clock rate itself. As a result, my memory running at 2133 "Mhz" (really should be MT/s) has a clock speed of ~1066Mhz.

With respect to your overclock, are you certain it's boosting on all cores? I know my P9X79 Deluxe will let me set individual boost multipliers for different cores and by default, it doesn't boost all of them unless I tell it to do all cores.

 

[WaterKewl]

Ok ran the 3000mhz XMP profile after updating the BIOS. Bumped up the multiplier. Got it stable @ 4.5ghz. Also I didn't realise the DRAM frequency is supposed to be doubled to get the actual frequency. I was wondering why it was sitting at half my set speed. Ran FS again got just under 7000. I dunno why I can't pull a result like the 12k on my 3930k, but I guess Ill have to live with it.

Glad to hear your not BSODing.

Looking at the two different scores, the issue is with your GPUs, not the proc. You Physics score in FS went UP. Your GPU score is in the shitter.
Gotta figure out why.
Make sure you have the PCIe lanes set up properly in the BIOS. Keep in mind that Auto doesn't always work right.
Try disabling crossfire, and testing one card at a time.
I don't understand why a crossfire 290 setup would be getting such a low score unless the drivers were jacked up, or the PCI config in the BIOS was holding the card down to 2 lanes or something. Worst case one of your cards ate shit at some point during the CPU swap. Check to make sure your power connections are all secure too.

 

[Aceman.au]

Double? Why yes. That is what the first D in DDR stands for (Double Data Rate) which is because it sends data on every rising/falling clock edge, as a result the "effective clock speed" or "transfer rate" which I would consider the more proper term to use, would be double the actual clock rate itself. As a result, my memory running at 2133 "Mhz" (really should be MT/s) has a clock speed of ~1066Mhz.

With respect to your overclock, are you certain it's boosting on all cores? I know my P9X79 Deluxe will let me set individual boost multipliers for different cores and by default, it doesn't boost all of them unless I tell it to do all cores.

The CPU is set to sync all cores to the same multiplier. I can set each core to a different speed but I just sync it to prevent issues.

 

[Aceman.au]

Glad to hear your not BSODing.

Looking at the two different scores, the issue is with your GPUs, not the proc. You Physics score in FS went UP. Your GPU score is in the shitter.
Gotta figure out why.
Make sure you have the PCIe lanes set up properly in the BIOS. Keep in mind that Auto doesn't always work right.
Try disabling crossfire, and testing one card at a time.
I don't understand why a crossfire 290 setup would be getting such a low score unless the drivers were jacked up, or the PCI config in the BIOS was holding the card down to 2 lanes or something. Worst case one of your cards ate shit at some point during the CPU swap. Check to make sure your power connections are all secure too.

Ok what should I be looking for in the BIOS when checking my lanes out. This is unexplored territory for me. Also Im using the latest driver 14.12 Omega

Games seem to run fine so I doubt I've cooked the GPU(s). Checking power connections now.

 

[Aceman.au]

Power connections all appear fine. I'll log some data from GPU-Z and post it.

Update:

I ran the render test and it went up to x16 3.0 in the bus interface on both cards.

They are seated in slot 0 and 2

 

[OneMoar]

id hardly call 2133 a massive under clock
set the timings and voltages manually and see what happens

 

[Aceman.au]

GPU-Z data from about 2 minutes gameplay in Diablo 3. The clock on my GPU is 975/1250mhz. Factory overclocked.

Single 290: http://www.3dmark.com/3dm/5626580?

 

[Aceman.au]

id hardly call 2133 a massive under clock
set the timings and voltages manually and see what happens

I fixed the CPU/ram problem. Now we're trying to figure out why my FS score is so low. Thanks for the input though

 

[OneMoar]

I fixed the CPU/ram problem. Now we're trying to figure out why my FS score is so low. Thanks for the input though

welcome to owning a crossfire setup enjoy your stay ...
drivers aren't scaling there is nothing you are gonna do about that other then wait for AMD to fix it
its nothing to be concerned with its only a benchmark

 

[Aceman.au]

F***ING NAILED IT GUYS.

http://www.3dmark.com/3dm/5660561?

GPU was throtling self to reach the Target temp set in CCC and underclocking to lower heat. I bumped the target temp up to 75c from 60c and it stopped throtling (didn't even reach 75c either). Massive result too and I even brought the clock down to 4.1ghz (4.5ghz was crashing, but I will bring it up again later).

Wow I'm just outside of the top 100 for Firestrike. Not that amazing, but as an amatuer Im stoked!

 

[WaterKewl]

Thank you for actually posting the result of your troubleshooting. It's so frustrating when people don't do this. Sorry I haven't been around for a few days. Glad it worked out!