• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Computer constantly crashing at 333Mhz FSB, help please.

T

tmar89

Junior Member
I have an ASUS A7N8X Deluxe MB. 1 PC2700 DDR333 RAM module and I just went from an Athlon Thunderbird 1.4Mhz to an Athlon XP 2500+ Barton core (socket A). My mainboard supports up to 400Mhz FSB and I originally had it set to 200Mhz with the 1.4Mhz Athlon. After updating my BIOS to the most recent version, I can run the system and have it stable at 200Mhz FSB and 266Mhz FSB but when I push it up to 333Mhz FSB, it randomly reboots when in Windows XP. I am running at Optimized settings for my memory (7,3,3,2.5T). I also tried changing the settings to 9,3,3,3T but it still reboots. The temperature for both the MB and CPU are about 100 degrees F and well below the limits. I wasn't sure how to debug this and was looking for some help.
 
sounds like my problem (see thread titled "CPU upgrade problems"). My first thought was power, and that has more or less been confirmed.

 
So you replaced your PS and it works now? I'm running an Athlon rated 450W PS so I think I do have enough power but I suppose it is an idea. I can check voltage levels so what should I be looking for?
 
o you replaced your PS and it works now?
Click to expand...

not yet, but I put the FSB back down to 133 (from 166) and so far I haven't had any crashes.
I will tweak it up for now if things still look good.

You can check the voltage on the MB connector (just stick the probes in the top of the connector).

This link has more info.

Though, a good 450W supply should be fine (I have a 250W).

 
Good idea. I already downloaded the program and I plan on doing it tonight. Thanks for the tips.

Here is SiSoftware Sandra's probe of the memory:
I have 1 Samsung 512MB 16x(32Mx8) DDR-SDRAM PC2700-2533-700 (CL2.5 up to 167MHz) (CL2 up to 133MHz)
 
Anything else I can try? I'm thinking 2 steps ahead because hypothetically, say the memtest86 passes and there are no problems, what else is there?
 
Ok, so I ran memtest86 for FSB 333Mhz for 9 hours and I got 243 errors on test #8. I am not sure what this all means but I suppose I should run this same test at FSB 266Mhz and see if I get the same errors.
 
Ok, so I kicked the speed back to 266Mhz and ran memtest and there were no errors over 8 hours. So obviously, there was an issue with my memory running at 333Mhz even though it is DDR333. Is there anything I can do about this such as changing options in the BIOS for latencies, etc?
 
Isn't that very risky to bump up the memory voltage?

My board is set to 3-3-2CL for FSB 266Mhz and I tried 3-3-2.5CL for FSB 333Mhz. Recommendations for getting this stable at 333Mhz before increasing the voltage?
 
I have a similar problem with my Soyo Dragon Ultra Platinum board. I cannot run my memory at 333Mhz and be 100% stable. (more like 97% stable). If I run at 266 (2100 speeds) it is 99.99% stable. (rough guess..)
I have swapped motherboards and memory. Still acts the same. I attribute it to bad motherboard design. The MB is supposed to support 400Mhz memory too! scary.

I have 2700 memory from Crucial. I originally had 2700 Kingston, but Newegg took it back (they rule)... and I hoped that Crucial memory would be my saviour... but NOPE.


 
I had this problem with a Soltek KT333 board, after banging my head enough times, I noticed that 2 of the CAPACITORS near the CPU were starting to Bulge.......

Heck I changed all components on it, upto 266FSB it was stable, going to 333FSB, system would be completely unstable, had to clock the CRUCIAL 512MB PC2700 down to PC2100 and the CPU to 266FSB to get it to work.

Needless to say, that board isnt being used anymore.
 
Well, I boosted the DIMM voltage up from 2.6 to 2.7, changed the latencies and still, errors in memtest86. Oh well.. I kept my CPU at 333 but dropped down the memory speed and its stable. Thanks for the help
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top