corsair vengance

Associate
Joined
3 Nov 2011
Posts
15
i have 2x4gb corsair vengance 1866 on a m5a99xevo with a phenom 1100t(stock speed).my memory is reading at 1333mhz.if i up it to 1600 and leave everything else on AUTO it wont reboot.the VGA led light on the mobo lights up and it just hangs(no fault on graphics card,tested in another system) To get it to reboot i have to clear the Cmos.ideas or help to get my memory running at 1866 would be appreciated.
 
What other settings have you changed - have you checked that the voltage, timings and command rate are correct for 1600Mhz? (9-9-9-24 at 1600MHz, 1.50V)

Also, have you tried each stick on its own?
 
Last edited:
What other settings have you changed - have you checked that the voltage, timings and command rate are correct for 1600Mhz? (9-9-9-24 at 1600MHz, 1.50V)

Also, have you tried each stick on its own?

yes tried each stick seperately to same result.only setting changed is from 1333 to 1600(no option for 1866).all other settings are on auto.voltage is at 1.5v...just thinking of buying 1600mhz and cutting loses but unsure if will have same prob.
 
Have you got the latest BIOS release for you motherboard?

Quite often the releases resolve memory compatibilty issues.
 
Is your system clocked at all? If it is revert everything to stock.

I would also try clearing the CMOS and loading optimised defaults and then save and exit.

Then try manually inputing all the memory's spec for 1600Mhz settings:

  • Frequency -1600Mhz
  • Timings - 9 9 9 24 (although i would consider slacker timing if it fails to boot 10 10 10 27)
  • Command Rate - 2T
  • Voltage - 1.5V
 
Is your system clocked at all? If it is revert everything to stock.

I would also try clearing the CMOS and loading optimised defaults and then save and exit.

Then try manually inputing all the memory's spec for 1600Mhz settings:

  • Frequency -1600Mhz
  • Timings - 9 9 9 24 (although i would consider slacker timing if it fails to boot 10 10 10 27)
  • Command Rate - 2T
  • Voltage - 1.5V
done that and now it will boot up to windows,the only problem now is that i cant do a restart(hangs with vga led on)if i turn computer off and leave for 5 mins it will boot up no probs,only seem to be able to do a cold restart..thanx for your help Plec
 
I would do a cold restart and make the DVD the first bootable device and then memtest for a few hrs form a bootable ISO - link.

Or if it's reverted back to form I would do the above procedure again but this time instead of going into windows go straight to the BIOS and then run memtest.

It may not be a memory related problem but it would help to try and rule it out.
 
ran memtest and no errors,ran windows mem diag-no errors.so decided to strip comp down and then put it all back together-runnin fine and restarting no problem now.memory runnin at 1600.thanx for your help PLEC was appreciated.
 
No worries - glad you seem to have cured the problem.

It's amazing how often a re-build coupled with a CMOS reset will sometimes cure a niggly problem.
 
never speak to soon :-( after several restarts with no problems the problem of comp hanging has returned (started after computer had been on for several hours)just wont rebootas before :-(
 
Sorry to read that.

Try running memtest now - without doing a cmos reset or reseating connections etc....

The reason i suggest this is sometimes a CMOS reset or reseating can sometimes disguise a memory problem, whether it's the stick themsleves or the MCH on the motherboard (AMD).

It could well prove to be someting else but again it would be handy to rule out.

If that fails it may pay to do a paper clip test on the PSU using a voltmeter and then, if possible, swapping out components.

If you don't have any spare parts to hand you may have to consider running a skeleton setup outside of the case and slowly add parts until it buckles. Although each stage may take time to test given how long the problem took to re-appear
 
thanx to those for giving there opinions and help:).after much testing and having a repair shop look and test my comp it comes down to a faulty mobo after all :( and not the memory
 
Glad you've finally isolated the problem - troubleshooting an unknown memory controller problem on a MB without spare memory was always going to be tough to diagnose. (It's a bit of a sod that it's the MB causing the problem rather than the memory.)

Are you still within the retailers warranty or have you got to go through Asus? If it's the latter you have my sympathies.

Best of luck.
 
Last edited:
Back
Top Bottom