CPU causing memory problems.

Jun 18, 2004
196
0
0
I did a minor upgrade to one of my machines. Upgraded the Atholn 1ghz to an AMD Palomino 2000+. The motherboard is an Asus A7V133-c which can support this processor with the board revision # and the Bios that I am using. Got it running at 1667 mhz, but when installing a program I got some memory errors. Ran memtest and got all sorts of errors on test 5 running my PC133 SDRAM at 133mhz. I backed down the system to 1250 mhz which is one of the default settings and then started moving up the FSB/Memory settings to just before where I would get errors. Ran fine for a while, then had occasional hang at startup.

Today, it hung at startup and when I restarted I would not post. After checking all of my connections and resetting the CMOS I finally changed the processor back to the Athlon 1000 and it started right up.

Set the ram speed at 133, the FSB at 100 and the processor at 1000. Runs memtest fine where the other processor caused errors.

It seems pretty evident that the processor was causing these problems or at least is a major factor contributing to the problems..

I just want to confirm that a processor could cause these types of memory problems and the processor I bought 3 weeks ago is the problem.
 

masshass81

Senior member
Sep 4, 2004
627
0
0
I'm pretty sure its your old memory. The Athlon XP 2000+ runs at 266FSB, although ram at 133mhz would run this cpu, you need DDR memory, not SDRAM. So you need at least PC-2100 (DDR-266) to run that cpu.
 
Jun 18, 2004
196
0
0
When I bought this processor it was because Asus's website said it would work with my mobo and ram. Now, I know that there are sometimes conflicts with particular setups, but I assumed it would work.

What is interesting is that when I first installed it, the computer booted right up. Later I found it was running at 1250 mhz. I bumped it up to 1667 and it ran fine. then I was installing a program and got some memory errors so I tweaked it around a little and had it running at about 1500 mhz. The other day it hung during startup, tehn I could not even get it to post. I know there are a lot of variable which could have caused it, but when I went back to my old processor the computer started up and ran fine.

I may have to spring for a new motherboard and upgrade the ram to see. If it turns out to be the CPU, then it it is only a few $'s more to buy a new CPU that is even faster. I was hoping that this 2000+ would hold this computer until Socket 939 components came down in price and were more reasonable.
 

Delorian

Senior member
Mar 10, 2004
590
0
0
I ran my 1800+ with PC133 for awhile after my ECS mobo's ddr slots fried. You might check your ram timings and relax them a little bit. I don't know much about the timings myself but by tweaking them you can get better peformance/stability with higher FSBs.
 
Jun 18, 2004
196
0
0
They are running at 3-3-3. I really just wanted the Palomino 2000+ to run at stock speed, but it doesn't seem to be in the cards.
 

jtnik

Junior Member
Aug 16, 2004
13
0
0
Maybe temp related. My palomino 2100 would hit 70c, had all kinds of problems. Reseated heatsink installed a case fan and cut out case grills. Down to 50c with a room temp of about 31c (88f).
 

mrweirdo

Senior member
Dec 1, 2002
706
0
0
My palomino 2100 allways seems to run hot as well before when I used the retail heatsink in my case that stays around 31-32C and CPU idel temp of 50- 52C. It would easily overheat going up to around 62C whenever i didnt a processor heavy task then my computer would just automaticly reset.

I just recently upgraded to a speeze cooler that seemed to knock about 5C off the temps so it just keeps it out of a system reset.

I have had a friend tell me that palomino cores are complete worthless garbage. I can see why since they seem to overheat so easily and performance probably isnt all that great compared to a newer core at a similar speeds. I wonder if it would be worth it to replace this chip with a Thoroughbred core based cpu at the same speed 2100+ 1.73ghz.
 
Jun 18, 2004
196
0
0
It might be. I was hoping to just keep this system for about another year, but I might have to bite the bullet and upgrade sooner.
 

jtnik

Junior Member
Aug 16, 2004
13
0
0
Know how you feel, tried to upgrade to a 2100 palomino on my kt133 board, it did not work. Had to purchase a new motherboard and ddr memory.