900mhz ram showing up as ddr2 800 on boot up?


Recommended Posts

Does it say 800MHz or PC6400?

When I'm OCing i need to tune "down" the speed since the memory speed follows the FSB. This results in that PC5300 or PC4300 shows up at startup, eventhough the RAM is running at say 800MHz.

Regarding another matter: I hope it also states Dual channel?

*edit*

I saw on Asus.com that your board only supports (original) speeds up to 800MHz.

  Quote
Dual channel memory architecture

4 x DIMM, max. 8GB, DDR2-800/667/533, ECC and non-ECC, un-buffered memory

I guess you have to "OC" the rest of the way.

What's your system specs'?

I know because of my OC the system shows mine running at 266Mhz even though it's actually at 400Mhz. But is is probably also the fact that the board only supports up to 800Mhz on the board. You aren't goinmg to get 900Mhz out of it without overclocking.

The system specs are:

550w PSU

AMD Athlon X2 5000+

2GB (2x 1gb) OCZ 900mhz ddr2 ram

asus m2n32 sli deluxe

320gb sata2 hard drive

How would I even go about overclocking the ram? Will it cause the temps to shoot up? Will it cause the ram any harm?

cheers

unlink the ram and push it to 450MHz (900MHz effective outcome) your board won't set 900MHz itself as it will only accept 533 667 800 and 1066 to get 900 1000 or similar speeds from these non-conforming dimms you need to set the parameters yourself.

You will most likely need to set the Voltage aswell as many 800MHz modules use 1.8v while the 900+ use 1.9v to 2.2v (Check which your RAM requires).

Temps will never shoot up... maybe 3 degrees hotter then before... if they already can go on 900 mhz why care with overclocking..

but then again maybe ur mobo wont allow it cuz of the processor

You don't need to OC your CPU if your multiplier is unlocked. Tune up the FSB and the RAM will follow, at the same time lower your multiplier so your core won't be OC. For example: [FSB]*[Multi], 250*12 = 3000MHz, "same as" 300*10 = 3000MHz but your bus has been OC 50MHz --> 100MHz OC of your memory. No need for changing the vcore, only vdimm. Make sure you lock you PCI-slots though (PCIE to 100MHz, PCI to 33,33MHz)

Hmmm i've set the dram voltage to 2.1v (the voltage it says on the OCZ site), i'm not sure about the FSB etc and don't want to balls it all up so i'll probably leave it at that (if just changing the voltage will make any difference?)

  randomnut said:

Hmmm i've set the dram voltage to 2.1v (the voltage it says on the OCZ site), i'm not sure about the FSB etc and don't want to balls it all up so i'll probably leave it at that (if just changing the voltage will make any difference?)

Altering the voltage won't make any performance difference. It may only help you overclock a bit further in terms of stability.

It's difficult for me to help you as I don't have an AMD system here and I've not used an AMD DDR2 system as yet.

on my Intel system I would unlink the DDR2 RAM from the FSB and set the RAM myself to 900MHz Effective, I would also set the voltage to 2.1V and set the timings to C2.

I don't know how it's done on AMD platforms as they don't even have a Front Side Bus due to the integrated memory controller. I think maybe you have to up your HT to overclock the RAM.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Amarok 3.3 Beta 2 replaces Phonon API with GStreamer by David Uzondu Audio players come and go, but one of the long-standing pack leaders is Amarok, a KDE project that has been around since 2003. This player was an essential application for anyone who ran a KDE 3 system, mostly because its interface was simple and did not get in your way. After spending some time in hibernation following the 2.x series, development has picked up again. Now we have version 3.3 Beta 2, bringing some changes under the hood. The most important of which is a complete overhaul of the audio engine. The developers have ditched the old Phonon multimedia framework on Qt6 and reworked everything to use GStreamer instead. The developers have also partially restored CUE sheet support, which is fantastic news for anyone who keeps albums as single audio files. ReplayGain logic has been improved to apply a default fallback value for tracks without loudness data, helping to even out the volume. Some work was also done to prevent potential database issues that could happen during library scans. This release also finalizes some major changes that were introduced in the first beta, as outlined below: Dropping support for Qt5 and KDE Frameworks 5 entirely. It is Qt6 from here on out. Updating the database character set to allow full UTF-8 values, which is great for international music collections. Fixing a year 2038 bug for dates stored in the database. Removing TagLib extras support, which affects RealMedia and Audible files. Now, before you rush off to install it, there are a couple of things to know. Because the first beta updated the database schema, downgrading from this beta back to an older version is not really possible unless you manually backed up your music library first. Also, if you are a big Last.fm user, its official library has not caught up with the Qt6 world yet. You will need a specific build from a repository like this one to get those features working for now. If you are feeling adventurous and want to try the new beta, you will probably have to build it yourself. For that, you can check out the project on GitLab for the source code and guidance. Some Linux distributions might also package the beta in their testing or unstable repositories, so it is worth a look there, too. You can grab the latest stable version of Amarok on Linux via FlatHub.
    • Yeah, stable and consistent data-harvesting to secure you and your 801 partners bottom line...thanks but no thanks.
    • The ethical thing for MS to do (a foreign concept) would be to continue full support for WIndows-10; until WIndows-11 is stable and mature enough to be considered reliable. Give users the ability to get decent use out of hardware they have bought, that MS decided are no longer able to run WIndows-11.
    • Why should users give up using a relatively stable OS (after almost a decade from its initial release) and move to a Beta+ level OS? Maybe in four or five more years, when it finally becomes more stable. Oh, and we have finally gotten fair use out of the hardware we bought, only to have MS say "toss it."
  • Recent Achievements

    • Rising Star
      Phillip0web went up a rank
      Rising Star
    • One Month Later
      Epaminombas earned a badge
      One Month Later
    • One Year In
      Bert Fershner earned a badge
      One Year In
    • Reacting Well
      ChrisOdinUK earned a badge
      Reacting Well
    • One Year In
      Steviant earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      545
    2. 2
      ATLien_0
      205
    3. 3
      +FloatingFatMan
      170
    4. 4
      Michael Scrip
      150
    5. 5
      Som
      131
  • Tell a friend

    Love Neowin? Tell a friend!