Safe to say a RAM problem?

[DiscoDave]

So i've been getting some radom errors and such, came shortly after my PC kept restarting due to oveheating. Here are some screenies.

These two come up on startup on a fresh XP install




and this one in CS : S



Quite frequently.

Is it safe to say its a RAM problem? I dont want to replace it and find it its actually a MOBO problem or something.

I've tried lowering the timings, upping the voltage etc but its not working.

Thanks

David

[killie99]

definately NOT safe to assume it's a RAM problem. It could easily be a cache problem, in which case it's the CPU. I think it's unlikely to be the mobo, but until you try swapping bits you can't tell.

[demonwolf]

Thos are the sort of errrors I get when I overclock too far and the system isnt stable if i go too far then its BSOD time. But before that..I get those sort of errors.

Might want to downclock your system even if its at stock settings to see if thats the problem

[yardbird]

If you suspect memory errors, get a floppy disk and run Memtest for one or two passes.

[mike_w]

Those error messages could be lots of things... as said, you can try Memtest, as well as swapping out components and underclocking. When I got similar messages, a quick reformat did the trick for me.

[Dav0s]

i got same errors, run ram at 2T ddr333. my prob is cpu mem controler

[Pdog]

Did you get any odd error messages appear when you Installed XP?

I also recommened starting with Memtest, but would leave it running longer than two passes. if it passes ok it maybe the CPU that is damaged. Trial and error dude.