Hardware

Ask something
Discussion Locked

how to underclock memory - please help

0 helpful
13 replies

by white owl 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I need some help here. I'm trying to lower the memory frequency from 400 to 333 (where there is more stability, meaning no shutdowns and restarts). In Bios the settings won't allow it to go lower than 400. It used to be set at 333 and was fine. (It's a long story how it got changed to 400 - which is the memory frequency). Now I'm crashing every 25 minutes or so.

I have a Gigabyte Titan 4 GA-8S648FX-L motherboard, P4 2.6 Ghz hyperthreading cpu, with a gig of memory. It's possible that the problem is with having memory from two different manufacturers. The memory originally there is a different brand (Premium?) than the 512 Kingston I added. Do you think this could be the source of my instability and the reason why I seem to need to underclock memory?

In addition I'm noticing possible overheating. I have so many fans going in there, about five or so. What should the temp be? I have the Gigabyte Easy Tune software to check the temp and it seems high, running around 98 with the Chieftek side door open (opened it to see if that would help.)

The Easy Tune software enables easy adjustments and additional adjustments that through Bios are not evident, but I am unable to take the memory frequency down to 333. It won't go below 401.

I had it at 333, so this is mysterious to me.

Please, feedback!

Thank you so much.

Layne in California

13 replies

by white owl

Thank you for the url for the manual, but I have the manual, and no, it does not discuss my problem. As I said, in the startup Bios settings and in the Gigabyte accompanying software (Easy Tune4), I am unable to lower the frequency. It only goes as low as 400 or 401. However, I did have it set at 333 at one time...and it was through the startup Bios!

Is there any other way to access this setting?

Thank you,
Layne

by thechas

In order to have a slower memory speed, you need to lower the Front Side Bus speed on your CPU.

Or at least change how the CPU FSB is derived.

Then, you should have the slower memory speed option back.

While I have no experience with under-clocking Pentium 4 CPUs, I can attest that AMD Athlon CPUs do NOT like to be under-clocked at all!

Did you originally change the FSB and memory speed for a new CPU?
If so, the correct answer may be to get faster RAM.

Chas

by don christner

Originally you could set the speed to 333MHz; so what's changed? The Kingston memory? Remove the Kingston memory and go back to the original memory. Then, before you lower the speed, run for a day or two and see if your crashes go away. If you still get crashes, try lowering the speed.

I haven't heard of anyone having to lower speeds since the 386 days.

Don

by white owl

Thank you for your feedback, both of you....

I didn't need to change the bus before. It's 800 by the way.

When I lowered the speed to 333 it was right after putting in the second memory, the Kingston. The original 512 of memory was at 400, but when we put in the Kingston, I found the computer unstable, lots of BSOD's. So I lowered the speed to 333 - the Bios setup let me do it! It totally solved the issue. We figured either the original memory actual speed was not listed correctly - maybe 400 was an overclocking speed - or the two types of memory weren't compatible??? Anyway, it worked to lower it.

Since the total crash of XP last week (described above), and subsequent installation of XP on a new partition etc., I am getting these mini crashes where it just shuts off and restarts in the middle of working on the computer. Now when I try to set the memory to 333 it won't let me! Why is it different - I have no idea!

One other thing. In reinstalling all my apps I installed DirectX 9 which was on the Gigabyte driver and software CD. I don't know it I had it on the computer before?? Is it possible that there is a problem with DirectX 9? And should I upgrade it? I have read awful stories of crashing with DirectX.

Also...what about this heat issue? What temp should my cpu and memory be at? It's running around 98 with the side door panel open.

I'm trying to think of everything here!

Thanks so much....

Layne

by white owl

Sorry, my comments should have been added with the comments button...but I didn't see it anywhere on the page I was on.... Now I see that button.... I think it was a different view. See my additional comments below in the thread. Also, I'm new here, and I didn't understand about the points program. Please accept my apologies. -L

by white owl

Don and igruhler, thanks. I have been leaning toward getting 512 more of the Kingston - or maybe I should get a gig of a totally new brand, like Crucial? I think these two brands of ram have never liked each other and XP hasn't liked them either. :)

Do you think I could go with the Kingston if it's all the same? I thought Kingston was one of the decent ones. Feedback please!

Layne

by jgruhler

I agree with DON
Sounds like the Kingston RAM could be the problem. Kingston makes good RAM but they also make some thats not so good. Also if you are mixing the 2 types of RAM in the system this in it self can be the problem. Some motherboards can auto detect and manage different types and speeds of RAM but most can not. Try removing the Kingston and test as Don said if this works go a step farther. Try removing the original RAM and run with the Kingston only. if this works great. The system is stable with the faster RAM so add in more of the same and leave the original RAM in the drawer.

by jgruhler

I misunderstood. Thought your original ram was 333. Still sounds like incompatability to me. Generic grade ram even if it is name branded will continually corrupt XP or any NTFS system. XP may or may not install OK but then errors will begin to show up and get continually worse until total disaster. Best to used Registered grade RAM with XP.

by ozi eagle

Hi Layne,

I had a similar problem when I installed a second memory stick.
Problem turned out to be the CAS latency setting in BIOS. Both sticks had a nominal CAS latency of 2.5, however, for some reason bios was set to 2. Original memory OK with this but second stick couldn't run. Resetting CAS latency to 2.5 solved problem.

by white owl

I appreciate all the posts to this question. All have helped me through my thinking process on this.

I decided my temp was okay and I didn't need to worry about that. Back to the memory. I took out the original evidently generic memory with blue heat spreaders - I took off the heat spreaders to see what the heck was there. It is Elixir memory. I think it was incompatible with the first motherboard that came in this custom built computer, and then when I added the new Gigabyte motherboard I believe it was incompatible with that too - not to mention possibly incompatible with the Kingston I added when I put in the Gigabyte P4 Titan and the new hyperthreading 2.6 GHz P4 cpu.

Okay...so I've removed this memory and guess what. No more crashes of any kind for two days now. This is a very good sign!

So now I'm adding more Kingston memory to get to my desired 1 gig of memory. Since the Kingston I have in there is in a 512 kit...I may remove one of those and put in a new 1 gig kit in the first two slots so I can take advantage of dual channel capabilities that I believe I have. It's been hard to discern this for certain. I'm learning so many details as I go through this situation.

I've been studying memory and have learned some things about dual channel and placement of memory, etc.

Anyway, the memory that was causing problems since the beginning is out and I have no more crashes. When I was able to underclock memory to 333 it wasn't a problem, but since I can no longer do that, ouch! But it was never right - I should be able to run at 400. So now all will be as it should be. :)

Thank you all for your help!

Layne

This discussion is closed to new replies.