My new computer is OC'd... Mobile 2400+ w/ NF7-s at 2.4 right now... need help. - Tilted Forum Project Discussion Community

cheesemoney · 02-23-2004, 07:24 PM

W/ apologies, some of this was taken from another thread because I didn't wanna write it all 2x but could use yous' guys' advice.

I wanna take it higher.
I'm still trying a run at prime 95. I've just upped the vcore to 1.8 because it crashed after running at 1.775 w/ prime 95 and 3dmark 2001 se.

Damn 2 sticks of geil ram
pc3200, golden dragon, 2.5 rated. I think I'm running them on optimal right now. THey were at 2-2-2-6 I believe at 3200+ speed.

Damnit.... so far, I'm "only" able to hit 2.4 ghz with my mobile 2400+ and my abit nf7-s.

It will load windows at 203 but then fuck up, won't even post at 204.

Its funny, but upping ram voltage seemed to do nothing, nor did upping chipset voltage.

This chip ran at "stock" <1.5 vcore at 11*200 fsb, btw, w/ no voltage mods whatsoever.

I'm very happy with the processor. I was hoping for a little more outta my ram, but I had to cut a few costs, and ram ended up being second tier instead of first. Its not crappy--Geil Golden Dragon 3200, rated at 2.5, and I'm pretty sure it was doing 2-2-2-6 at 3200+ speed, but I could be mistaken.

Freakin' 204 fsb kills it though. DAMNIT! Won't post, and I'm alot friendlier with cmos than I ever wanted to get.

I've heard that these things sometimes take time, so I'm gonna keep runnin' prime 95 like i've been--right now it kept finding errors after 10 mins or so in prime, which is why I've upped the voltage on the vcore to 1.8. I'm afraid to go too much over that, but thankfully the cpu full load has never taken me over 40 degrees.

Thank you thermalright. Unfortunately, that wonderful vantec tornado fan sounds like a freakin' hurricane instead.

I can hear it downstairs w/ my door closed.

Any advice on v-core/chipset/vdimm settings much appreciated. To increase my fsb.

Also, what do I do now if I can't increase fsb anymore.

I'm at 200fsb/12 multiplier (2.4ghz). What do I try for--200/12.5?

For the record, I havn't flashed the bios in my nf7-s rev 2.0. I'm afraid of it, and don't know if I really need to or not.

yakimushi · 02-23-2004, 09:57 PM

I've been having some problems with my NF7-S as well (rev 2.0).

I think its my chip, but something keeps flaking out at 185FSB and up. I don't think its my RAM, which is PC3200 running at default timings.

I'm starting to think its the northbridge, these NForce chips get toasty and the stock cooler just looks weak. I'm going to upgrade to a Zalman and see if that helps any.

cheesemoney · 02-23-2004, 10:59 PM

Hmm... I have it at 1.8v @ 2500 mhz and battlefileld 1942 keeps crashing to desktop. Mem timings are now 2.5-4-4-8 (not really good), so apparently I have a lot of tweaking left to do.

At 2.5 I idle at 32 degrees and max out at 40, so heat doesn't seem to be the issue, unless my abit nf7-s isn't remotely accurate (not that likely).

Lasereth · 02-24-2004, 05:51 AM

cheesemoney, Battlefield 1942 crashes to desktop on basically every computer ever made.

EA's tech support has an entire section devoted to the "crashing to desktop" problem, so I doubt it's your OC that's making it happen. OC'ing problems usually cause the game to freeze up or the entire PC to reset back into POST while playing. Crashing to desktop is usually driver problems.

-Lasereth

sailor · 02-24-2004, 07:05 AM

Quote:

Originally posted by Lasereth
cheesemoney, Battlefield 1942 crashes to desktop on basically every computer ever made. EA's tech support has an entire section devoted to the "crashing to desktop" problem, so I doubt it's your OC that's making it happen. OC'ing problems usually cause the game to freeze up or the entire PC to reset back into POST while playing. Crashing to desktop is usually driver problems.

-Lasereth

Haha, he speaks the truth. I have never seen a game with so many problems.

As for the overclocking, every system eventually hits a ceiling, and how high this ceiling is is largely determined by luck. If you have played around and cant get it to go any further, it is likely that you have just hit the maximum that your machine wants to run at. Sorry... Overclocking is largely based on luck.

Lasereth · 02-24-2004, 08:24 AM

Quote:

Originally posted by sailor
As for the overclocking, every system eventually hits a ceiling, and how high this ceiling is is largely determined by luck. If you have played around and cant get it to go any further, it is likely that you have just hit the maximum that your machine wants to run at. Sorry... Overclocking is largely based on luck.

Yep. People want to believe that OC'ing is a standard 100% informational process, but it's not. Even the tiniest of differences in systems can cause maximums to fall short of other systems. Sometimes you get lucky and get a freak machine (my friend with his 9500 Pro and Athlon XP 1700+ getting over 15,000 on 3d Mark 2001 with simple OC'ing), and sometimes you get a lesser-than average machine (my 5900 Ultra and Barton 2500+ with 1 GB of PC2700 got 13,300 on 3d Mark 2001).

You can always try different settings, but in the end, you can't push a system past its max.

-Lasereth

JStrider · 02-24-2004, 11:35 AM

one thing... instead of raising the multiplier... try lowering it one notch... and continue increasing the fsb...

its better to have a slightly slower cpu and a faster fsb since fsb overclocks the whole system, not just the processor...

cheesemoney · 02-24-2004, 03:11 PM

I know... i can't get the fsb to 205 with a multiplier of 5.

Arghhh!

And shit... just failed prime 95 after 10 hours at 2.5 ghz 200 fsb x 12.5 multiplier.

Looks like I'm gonna settle for 2.4 ghz for now since its not really my machine anyway. When it starts to get old you can always knock up that vcore and turn it up!

Vanquish · 02-24-2004, 03:36 PM

What is the Vcore at right now? Anything under 1.95 shouldn't hurt the system MUCH, I have mine running at 1.95 and its been there for 1.5-2 years now.

cheesemoney · 02-24-2004, 03:51 PM

1.85. Still no change at 1.85. I don't know what to set the vdimm at. Geil I've heard can take some decent voltage, but with the original bios installed I can't up it more than 2.9--right now I'm running 2.8.
Earlier I tried 2.9 and it didn't get to windows at 203.

Vanquish · 02-24-2004, 08:23 PM

k Try and up your Chipset voltage a bit, maby .1 - .2 it might be that your northbridge isn't allowing you to go farther. But still 2.5ghz at 10hrs PRIME is considered stable by the mass OC market, and is not a number to sniff at

cheesemoney · 02-25-2004, 07:38 PM

Yeah. I'm happy with the cpu, just not stoked at only getting 202 mhz with the ram. Stoked that my little 2400+ mobile can get up to 2.5 on 1.85 volts though. I decided I'm gonna turn it over to my bro at stock voltage and 2.21 ghz, and then in a year or so crank the voltage up to 2, put the tornado back on (jet engines are quieter), and see if it can play catch up to these new cpu's.

02-23-2004, 07:24 PM	#1 (permalink)
cheesemoney Loser Location: Paradise	My new computer is OC'd... Mobile 2400+ w/ NF7-s at 2.4 right now... need help. W/ apologies, some of this was taken from another thread because I didn't wanna write it all 2x but could use yous' guys' advice. I wanna take it higher. I'm still trying a run at prime 95. I've just upped the vcore to 1.8 because it crashed after running at 1.775 w/ prime 95 and 3dmark 2001 se. Damn 2 sticks of geil ram pc3200, golden dragon, 2.5 rated. I think I'm running them on optimal right now. THey were at 2-2-2-6 I believe at 3200+ speed. Damnit.... so far, I'm "only" able to hit 2.4 ghz with my mobile 2400+ and my abit nf7-s. It will load windows at 203 but then fuck up, won't even post at 204. Its funny, but upping ram voltage seemed to do nothing, nor did upping chipset voltage. This chip ran at "stock" <1.5 vcore at 11*200 fsb, btw, w/ no voltage mods whatsoever. I'm very happy with the processor. I was hoping for a little more outta my ram, but I had to cut a few costs, and ram ended up being second tier instead of first. Its not crappy--Geil Golden Dragon 3200, rated at 2.5, and I'm pretty sure it was doing 2-2-2-6 at 3200+ speed, but I could be mistaken. Freakin' 204 fsb kills it though. DAMNIT! Won't post, and I'm alot friendlier with cmos than I ever wanted to get. I've heard that these things sometimes take time, so I'm gonna keep runnin' prime 95 like i've been--right now it kept finding errors after 10 mins or so in prime, which is why I've upped the voltage on the vcore to 1.8. I'm afraid to go too much over that, but thankfully the cpu full load has never taken me over 40 degrees. Thank you thermalright. Unfortunately, that wonderful vantec tornado fan sounds like a freakin' hurricane instead. I can hear it downstairs w/ my door closed. Any advice on v-core/chipset/vdimm settings much appreciated. To increase my fsb. Also, what do I do now if I can't increase fsb anymore. I'm at 200fsb/12 multiplier (2.4ghz). What do I try for--200/12.5? For the record, I havn't flashed the bios in my nf7-s rev 2.0. I'm afraid of it, and don't know if I really need to or not.

02-24-2004, 05:51 AM	#4 (permalink)
Lasereth Knight of the Old Republic Location: Winston-Salem, NC	cheesemoney, Battlefield 1942 crashes to desktop on basically every computer ever made. EA's tech support has an entire section devoted to the "crashing to desktop" problem, so I doubt it's your OC that's making it happen. OC'ing problems usually cause the game to freeze up or the entire PC to reset back into POST while playing. Crashing to desktop is usually driver problems. -Lasereth __________________ "A Darwinian attacks his theory, seeking to find flaws. An ID believer defends his theory, seeking to conceal flaws." -Roger Ebert

02-24-2004, 11:35 AM	#7 (permalink)
JStrider Poo-tee-weet? Location: The Woodlands, TX	one thing... instead of raising the multiplier... try lowering it one notch... and continue increasing the fsb... its better to have a slightly slower cpu and a faster fsb since fsb overclocks the whole system, not just the processor... __________________ -=JStrider=- ~Clatto Verata Nicto

02-23-2004, 09:57 PM	#2 (permalink)
yakimushi Addict	I've been having some problems with my NF7-S as well (rev 2.0). I think its my chip, but something keeps flaking out at 185FSB and up. I don't think its my RAM, which is PC3200 running at default timings. I'm starting to think its the northbridge, these NForce chips get toasty and the stock cooler just looks weak. I'm going to upgrade to a Zalman and see if that helps any.

02-23-2004, 10:59 PM	#3 (permalink)
cheesemoney Loser Location: Paradise	Hmm... I have it at 1.8v @ 2500 mhz and battlefileld 1942 keeps crashing to desktop. Mem timings are now 2.5-4-4-8 (not really good), so apparently I have a lot of tweaking left to do. At 2.5 I idle at 32 degrees and max out at 40, so heat doesn't seem to be the issue, unless my abit nf7-s isn't remotely accurate (not that likely).

02-24-2004, 03:11 PM	#8 (permalink)
cheesemoney Loser Location: Paradise	I know... i can't get the fsb to 205 with a multiplier of 5. Arghhh! And shit... just failed prime 95 after 10 hours at 2.5 ghz 200 fsb x 12.5 multiplier. Looks like I'm gonna settle for 2.4 ghz for now since its not really my machine anyway. When it starts to get old you can always knock up that vcore and turn it up!

02-24-2004, 03:36 PM	#9 (permalink)
Vanquish Insane Location: Truro, Nova Scotia	What is the Vcore at right now? Anything under 1.95 shouldn't hurt the system MUCH, I have mine running at 1.95 and its been there for 1.5-2 years now.

02-24-2004, 03:51 PM	#10 (permalink)
cheesemoney Loser Location: Paradise	1.85. Still no change at 1.85. I don't know what to set the vdimm at. Geil I've heard can take some decent voltage, but with the original bios installed I can't up it more than 2.9--right now I'm running 2.8. Earlier I tried 2.9 and it didn't get to windows at 203.

02-24-2004, 08:23 PM	#11 (permalink)
Vanquish Insane Location: Truro, Nova Scotia	k Try and up your Chipset voltage a bit, maby .1 - .2 it might be that your northbridge isn't allowing you to go farther. But still 2.5ghz at 10hrs PRIME is considered stable by the mass OC market, and is not a number to sniff at

02-25-2004, 07:38 PM	#12 (permalink)
cheesemoney Loser Location: Paradise	Yeah. I'm happy with the cpu, just not stoked at only getting 202 mhz with the ram. Stoked that my little 2400+ mobile can get up to 2.5 on 1.85 volts though. I decided I'm gonna turn it over to my bro at stock voltage and 2.21 ghz, and then in a year or so crank the voltage up to 2, put the tornado back on (jet engines are quieter), and see if it can play catch up to these new cpu's.