bios settings help please

Status
Not open for further replies.
Joined
Jul 22, 2003
Messages
1
Reaction score
0
I got P4 3.0 800 Mhz HT
With Corsair XMS 3500 434 Mhz 2X256 MB...
Abit IC7-G

please tell me what do make it faster? i try different stuff in bios but then it wont boot:-(( regards Tommy
 
In message <WvgTa.17294$>, "--((T.F))--"
writes
I got P4 3.0 800 Mhz HT
With Corsair XMS 3500 434 Mhz 2X256 MB...
Abit IC7-G

please tell me what do make it faster? i try different stuff in bios but then it wont boot:-(( regards Tommy
Mine is worse than not booting. I've got a 2.4C 800Mhz HT proc in an IC7-G with the latest v15 BIOS, along with Corsair 3200 memory in dual DDR mode. Any attempt to alter the memory timings, or to set the "Game Accelerator" settings to anything other than Auto, result in a BIOS corruption requiring a reflash of the BIOS.

NASTY !!

Anyone else had this problem ?
 
I have not had to reflash but with the fsb I am running and the ram timings at 2, 5, 2, 2, if I try anything other than Auto on the game acceleration I don't get a boot at all.
 
In message <JalTa.17784$zd4.8576@lakeread02>, TomG
writes
I have not had to reflash but with the fsb I am running and the ram timings at 2, 5, 2, 2, if I try anything other than Auto on the game acceleration I don't get a boot at all.
Well mine starts to boot, but then promptly emits a loud series of beeps and demands a BIOS image on a floppy. I too was trying a 2, 5, 2, 2 config, and using either it, or setting the "Game Accelerator" settings to anything other than Auto result in the same problem.

My current thinking is that the v15 BIOS is flaky. Setting your memory timings aggressively and then saving the settings, should not result in having to reflash the BIOS. There is some possibility that my Corsair 3200 memory is at its limits already, but trying to stretch it a bit, should not result in the sort of issue I am seeing. I don't suppose that I will get to the bottom of this until I either get a matched pair of 3700's or better in the board, or v16 of the BIOS appears.
 
"FatHippy" <{$spamtrap$}@fathippy.net> wrote:

In message <JalTa.17784$zd4.8576@lakeread02>, TomG
writes
I have not had to reflash but with the fsb I am running and the ram timings at 2, 5, 2, 2, if I try anything other than Auto on the game acceleration I don't get a boot at all.

Well mine starts to boot, but then promptly emits a loud series of beeps and demands a BIOS image on a floppy. I too was trying a 2, 5, 2, 2 config, and using either it, or setting the "Game Accelerator" settings to anything other than Auto result in the same problem.

My current thinking is that the v15 BIOS is flaky. Setting your memory timings aggressively and then saving the settings, should not result in having to reflash the BIOS. There is some possibility that my Corsair 3200 memory is at its limits already, but trying to stretch it a bit, should not result in the sort of issue I am seeing. I don't suppose that ...

You may be interested in this:
http://www.hexus.co.uk/review.php?review=404&page=6
regards
@ndrew
 
In message , "@ndrew"
<andrewrattpg.no_spamcom.au@?.?.invalid> writes
"FatHippy" <{$spamtrap$}@fathippy.net> wrote:

In message <JalTa.17784$zd4.8576@lakeread02>, TomG
writes
I have not had to reflash but with the fsb I am running and the ram timings at 2, 5, 2, 2, if I try anything other than Auto on the game acceleration I don't get a boot at all.

Well mine starts to boot, but then promptly emits a loud series of beeps and demands a BIOS image on a floppy. I too was trying a 2, 5, 2, 2 ...
That is extremely useful. Thanks very much. I am off to have a fiddle and see if I can stabilise things any. I will report back in a few days. Thanks again Andrew.
 
you probably do not really need to flash the bios but I could be wrong. you could try either clearing the CMOS or holding Insert down during the power on sequence. of course, flashing the bios may be easier than getting into the system to clear the CMOS but keep in mind that you are really supposed to be clearing the CMOS after a flash anyway.
 
In message <QkCTa.18481$zd4.11207@lakeread02>, TomG
writes
you probably do not really need to flash the bios but I could be wrong. you could try either clearing the CMOS or holding Insert down during the power on sequence. of course, flashing the bios may be easier than getting into the system to clear the CMOS but keep in mind that you are really supposed to be clearing the CMOS after a flash anyway.

I absolutely take your point, I clear the CMOS as a matter of course, but I will try the insert key method next time it happens.

The last couple of days have manifested another development. Every once in a while, sometimes with 8 hours or more between incidents, my PC just resets itself, even on standard settings. I am leaning more and more towards the Corsair memory being at its limits on standard settings in the dual DDR configuration I am running. I bought the Corsair memory specifically because I knew that I was going to need quality memory, but I did not buy the TWINX matched pair, the ones I have are the CAS2, 3200 256MB Platinum modules. With the benefit of hindsight, I probably should have pushed the boat out for a TWINX matched pair, or indeed 3700 memory, but both of those are a small fortune.

I have upped the voltage on the memory to 2.8v tonight, still on standard timings other than that, so I'll see if that results in a lack of reboots, and if it does, then it looks like that is my problem.

I shall report back here anyway, and hopefully save someone else from learning the hard way like I may have done.
 
what CPU are you running? I found that my ram was happier if I manually configured the system and overclocked the FSB. In the end, the ram was running a little slower than default configuration with everything on user define but stability is rock solid and the system is MUCH faster.

2.8c at 244 FSB with NB at 4:5. ram at 390 or so and at 2, 5, 2, 2. DDR at 2.65v and cpu at stock voltage.
 
In message <C2FTa.18606$zd4.13580@lakeread02>, TomG
writes
what CPU are you running? I found that my ram was happier if I manually configured the system and overclocked the FSB. In the end, the ram was running a little slower than default configuration with everything on user define but stability is rock solid and the system is MUCH faster.

2.8c at 244 FSB with NB at 4:5. ram at 390 or so and at 2, 5, 2, 2. DDR at
2.65v and cpu at stock voltage.
Running a 2.4c (which is reporting 1.525v on its standard settings, so probably some overclockability, voltage wise in it) on an IC7-G. All at standard settings other than the current 2.8v being supplied to the memory. As I said, 2,5,2,2 on 2.65v results in a "Please insert Boot Floppy".

Your comments are interesting however. I am going to run at 2.8v for a few days to see if that is solid enough, before tweaking, but I welcome suggested settings from yourself (and indeed anyone else) for this Processor and RAM setup.

Are you running the same memory modules as me, or did you do the sensible thing and buy the TWINX variant ? :-)
 
mine are just good old Corsair XMS3500. I don't have to run at 2.8 volts, as I pointed out. I'd bet that you wont even have to raise your core voltage to be able to overclock significantly...
 
In message <iqGTa.18613$zd4.2065@lakeread02>, TomG writes
mine are just good old Corsair XMS3500. I don't have to run at 2.8 volts, as I pointed out. I'd bet that you wont even have to raise your core voltage to be able to overclock significantly...
I look forward to trying.
And probably swearing a lot. :-)
 
In message <GWXTa.20588$zd4.13996@lakeread02>, TomG
writes
as I said, 2, 5, 2, 2 works fine for me.
You have 3500 modules though, and I have 3200 modules. According to Corsair's website, the preset timimgsand tolerances of them are quite different, and certainly the SPD setting will pick them up differently and any attempt to use the "Game Accelerator" function will affect them differently.

I currently have them at 2,6,3,3 and 2.8v, and all so far (here's hoping !) is rock solid stable.

If it stays like that, then the next thing I will try, is backing off the voltage to 2.7v, and if still stable, changing to 2,5,2,2.

Although all that being said, there are considerably larger gains to be made by my o'clocking the frontside bus, and using far more relaxed memory timings, compared to using very tight memory timings but not being able to overclock much. :-)

I very much appreciate everyones advice here by the way, so my thanks to you all. Being able to benefit from everyone elses practical experiences on this issue, is of considerable help and worth. So, thanks again to everyone who is providing input.
 
ah, I didn't catch that we were using different modules. I don't run by SPD, obviously, just like I don't run the NB in "by CPU".
 
In message <uaZTa.21089$zd4.14483@lakeread02>, TomG
writes
ah, I didn't catch that we were using different modules. I don't run by SPD, obviously, just like I don't run the NB in "by CPU".
Well I'm not running it by SPD either anymore. :-)
I've still got some poking and prodding to do, but all seems stable at the moment.

For the benefit of others that may be reading, I also found this article to be very useful. Particularly the chart on page 4.

http://www.xbitlabs.com/articles/cpu/display/p4-2400c-oc.html
 
In message <z4jUa.22629$zd4.3110@lakeread02>, TomG writes
Neat article.
I thought so too. Rather better written than they normally are, with quite a lot of inormation.
 
In message <uQAJWSEZazH$>, FatHippy
<{$spamtrap$}@fathippy.net> writes
In message <iqGTa.18613$zd4.2065@lakeread02>, TomG
writes
mine are just good old Corsair XMS3500. I don't have to run at 2.8 volts, as I pointed out. I'd bet that you wont even have to raise your core voltage to be able to overclock significantly...

I look forward to trying.
And probably swearing a lot. :-)

And following up my own post, which I know is bad form, but I said I'd report back.

Most stable I can get it, is 2.5, 7, 3, 3 @ 2,8v. It still reboots itself at random, once every 24-48 hours of running, but this is definately an improvement on where I was.

Also tested the memory fully, using memtestx86 and it shows up as 100% OK.

Going forward, with the intention of overclocking, I shall save up and get a matched pair of PC3700's I think.
 
Status
Not open for further replies.
Back
Top