G.skill sniper 1866 speed

[minix69]

I recently bought some g.skill sniper 1866 mhz ram but it only runs at 1600 via cpuz, how can I get this to full speed.
System
Phenom IIx6 1100t
asus m4a89td pro usb 3.o
CF 5870's
samsung spinpoint 7200 rpm 500gb hard drive
650w xfx modular psu
windows 7 pro

My timings are set to factory 9,10,9,28

 

[minix69]

I'll try that and Got my ram cooler installed today as well. Get right back to you.

 

[minix69]

ok so I set all that and stil get errors at exactly test 7? No matter how I set it up its errors at test 7. but while usuing the pc with any of those settings it seems stable. I'm gonna try auto which sets it to 1600 by defualt and see where the errors start, any more suggestions in the mean time?

 

[jaquith]

Your best bet is to use one of the JEDEC speeds; so if there's a JEDEC 800 MHz {1600} manually set the CAS Timings and DRAM Voltage to match.

FAQ Test 7 -> http://www.memtest86.com/tech.html
Errors from this test are not used to calculate BadRAM patterns.

Some memory related errors are discovered and often a BIOS update addresses the problem. IMO use BIOS 2001.

Q - What version of BIOS is running?

 

[minix69]

OK so I ran this ram everyway I can, auto 1600, errors a test 7! I OC to 2000mhz 7 errors b4 test 7 then all errors after, and put it back to your settings originally and no errors till test 7. I'll check out that link but I think i'm just gonna let it ride as I have no probs with my pc so far, your opinion?

 

[minix69]

I read my problem in that and it is block move errors, not sure how to correct this but any ideas?

 

[jaquith]

On a similar thread a GSKILL Administrator suggested to ignore Test 7 errors. You are exceeding the AMD CPU's IMC limits running 1600 MHz DDR3 and faster; as stated test 7 is not a RAM test as such "Errors from this test are not used to calculate BadRAM patterns."

Therefore to test the IMC Load Defaults in the BIOS and re-run the tests.

Next, I assume that you are running the latest non-Beta BIOS version 2001.

Lastly, you might want to report it to ASUS so they can look into a BIOS upgrade to correct the issue.

 

[nikorr]

This topic has been closed by Nikorr