Sign in with
Sign up | Sign in
Your question

P3 733 won't do over 683

Last response: in CPUs
Share
August 27, 2002 11:57:49 PM

I'm currently running my Pentium 3 733 at 683 because everytime Windows XP boots up I get the infamous:

"Windows could not start because the following file is missing or corrupt:

\WINDOWS\SYSTEM32\CONFIG\SYSTEM"

Now if I drop the cpu down from 5.5x @ 133 to 5.5x @124 it runs perfect. In fact I've been running it at 124 for a year cause I didn't think 50Mhz makes a huge difference. Well I have decided its enough for me to look into fixing it. :) 

Motherboard: Abit VA6.
RAM: 320 MB PC133
Graphics: GeForce 2 GTS 32MB
Network: Linkysys 10/100
Sound Card: Old SB64 just broke, SB Live on the way
Hard Drive: Maxtor 20GB 5400rpm

Alittle history on this problem. I had Windows 98 on this box for a year or two and decided I wanted to put Win 2K on about a year and a half ago. Well, everytime during install it would freak out and die. So I stuck with 98 for another 6 months and got XP. Tried installing, exact same problem as 2K. I put some time into it and found that if I drop the bus from 133 to 124 it would install and run perfect. So its not a recent thing and my hardware seems good cause I had 98 on here for a long time. Just a conflict with 2K and XP. I've also tried swapping hardware out incase there is some conflict and nothing has work. I've tried swapping out sound card, video card, ram, and network card. Nothing. I also have the latest BIOS from Abit and have every update downloaded for XP. Anyone have any ideas on this very strange problem?

Thanks,
Kevin




<P ID="edit"><FONT SIZE=-1><EM>Edited by kbrad on 08/27/02 08:02 PM.</EM></FONT></P>

More about : 733 683

August 28, 2002 12:45:48 AM

could be a ram problem... can test that with MEMTEST86
could be a fsb problem... that motherboard is certified for 133fsb operation right?
could even be a power problem.

<b>Due to Customer Complaints this sig has been withdrawn from public use. Thankyou. :lol:  </b>
August 28, 2002 12:53:44 AM

the thing that troubles me is the windows error message. why would that have to do anything with kevin increasing or decreasing his fsb...weird ? if lhgboopaa's solution doesnt work, i would suggest stayin on 124... 50mhz is really not a lot at all....

real philosophy of life: "do onto others what you dont want them do onto you"
Related resources
August 28, 2002 2:59:31 PM

Thanks for the ideas lhgpOObAA. I ran MEMTEST86 last night and everything checked out fine. I figured it would, because I had been running this thing at 133fsb with this ram for a long time. And yes, this motherboard is certified for 133fsb and I had it running at it for 1-2 years actually.

The power issue... it is possible I guess. But I have a 300 watt power supply, and don't think I even come close to using it. In fact when I was trying to trouble shoot this problem I took out most of my cards (sound, network), unplugged all of my CD Drives and it still died.

grassapa:
You're right, 50mhz isn't a big deal. But I was hoping if I could solve this problem I could upgraded to a 1.0 or 1.1 Ghz P3. But I don't want to do that until I get this damn problem solved.

Thanks for the ideas guys! Any others?

Kevin
August 28, 2002 3:13:32 PM

It may sound stupid, but take a can of compressed air and blow the ever loving crap out of the mobo, making sure to also hit the CPU and RAM sockets.

<pre><A HREF="http://www.nuklearpower.com/comic/186.htm" target="_new"><font color=red>It's all relative...</font color=red></A></pre><p>
!