So i have an Asus A7N8X nforce2 board that is upgraded to the latest bios (1010) and has the latest PCB (2.0). Everything on Asus's site says my new athlon 3200+ barton 400FSB should work on this motherboard. I popped out my old 2500+ barton, stuck the new one in, upped the FSB from 333 to 400 and poof, computer crashes when loading windows. When i clock it back down to 333 FSB it runs fine, but the computer thinks i have a 2500+ barton in here, not a 3200 cause it's running at a 2500+ clockspeed. What the hell is causing it to crash when i load windows? As far as i can tell cooling isn't a problem as the bios never shows my CPU above 40 degrees after a crash (and crashes don't normaly happen till 60?). I've got a nice $40 heatsink on the processor that kept my 2500+ at 44 or below most of the time, figure it should work for this one too. So what is the problem? I increased the CPU multiplyer to 12.5 and now my compute thinks it's a 2600+. It seems the CPU can clock higher but the board doesn't like going to 400 FSB? Is there something else i have to change to make it work with 400 FSB? Last hint is that when windows starts up again after the crash, it says something has been cause by a device driver, which is probably BS, since i have the latest mobo drivers as well. Any help would be apreciated. I'd hate to think i spent $100 on a CPU upgrade only to have it work the same as my old CPU.
well you're CPU runs at 333mhz fsb. Not 400. This has nothing to do with your motherboard. If your computer thinks it's a 2500+ at 333mhz and multiplier is set right then you infact do have a 2500+ not a 3200+. Where did you get your processor? The crashing is being caused by errors in your ram of it's incapability to run at the set speed.
I got it at partspc.com, everything i can tell from the outside says it's a 3200. Multiplyer is set at 11x and at 333 it thinks it's a 2500+. If i change the multiplyer to 12.5x (highest it will go) it thinks it's a 2600+. Think i got ripped off?
I don't know what RAM you have, but if you're running it in sync with the FSB and the RAM can't run at that speed and/or the timings for it are too tight, that might be causing a problem. I'd download [google]Memtest[/google] to check that part out.
I'm not running my Ram in sync. I had it setup to run at 333 while my FSB was at 400. Perhaps the timings were screwed up because of that. I'll have to get some 400 ram maybe :\
