Upped FSB to 150 and can't get SETI Client to run

[Greg M]

I loaded the BIOS for overclocking. I'm running with FSB at 150 and everything seems to be working great...except for the SETI Client. Anybody else see anything like this?

My 1.4 TB is running at 51C under load. How hot is 'too hot'?

 

[Greg M]

I'm such a moron :-(

Never mind. I do this stuff for a living and forgot to reset the clock after the BIOS update. Now I can't make fun of anybody for lUser error or PEBKAC for a while.

Problem resolved.

...and ultimately had to roll back to 138. IBM 60GXP couldn't cut it at 150.

 

[PDL]

Re: I'm such a moron :-(

Never mind. I do this stuff for a living and forgot to reset the clock after the BIOS update. Now I can't make fun of anybody for lUser error or PEBKAC for a while.

Problem resolved.

...and ultimately had to roll back to 138. IBM 60GXP couldn't cut it at 150.

Greg, if I may ask!
When you say your HDD couldn't cut it at 150 FSB, what did it do that lead you to that conclusion? What were the problems?
I was running at 150 several times and after about 2 days I would get various error messages that seemed to be data read errors. When I went back to 138, thay all went away and there was no reinstalls of any software.
Thanks for the input.

 

[Greg M]

Sorry it took so long to get back to you. I was having BSOD's with paging faults. That combined with having drive errors on another MB with a different chipset using the same make and model drive when approaching 150mhz FSB kind of sealed the deal for me. Going to 138 relieved the errors, but running at 1450mhz instead of 1400mhz wasn't very exciting. I also was able to note that it wasn't buying me any performance increases, so I went back to stock.

 

[Greg M]

Maybe not...

I could be wrong. I played around with the memory settings, running fast instead of ultra, and now have been running for a little while at 150fsb without a BSOD (time will tell). My 1.4 is running at 1.6, no appreciable heat increase according to MBM.

 

[Greg M]

Blew chunks today while I was at work. I couldn't even get XP to load. Reloaded Win2K Pro and so far so good. I noticed W2K seemed to be less affected by overclocking than XP when I was playing with my 1Ghz system. If this works out, I may dump XP on it also and increase the fsb on it, too.

Keeping my fingers crossed.

G-Man

 

[Greg M]

Nope. Back at 133. May have to try another board or build another system. It's no wonder ECS doesn't provide overclocking in their BIOS.