Strange Ubuntu Problem, Hardware?

[markyb]

Ok heres was my Linux Box rig...

AMD Sempron 2800+
Winfast NF3 MB
2x Kingston Hyper X 333mhz Ram (1Gb)
ATi 9700 Pro AGP Graphics Card
1x 60Gb HD 1x 20Gb HD
Antec 350w PSU

Just recently I was running Ubuntu 7.04 on the above which worked perfectly. No problems what so ever.

Ive just upgraded the processor to a AMD A64 3000+ and having some problems.

If I boot Ubuntu from either the HD or CD-ROM live disc, It locks. Hard locks. I have to turn off and turn on again.

So I took one of the sticks of ram out. Works perfectly again. The moment I put either one in, it crashes again.

I brought another 512mb Kingston Value Ram 400mhz and put it in with the existing ram and Ubuntu this time boots up perfectly fine and I can use it off the live disc, however If I go to install it locks again.

I know its got to be maybe the fact that the sticks are 333mhz and the processor runs @ 400mhz bus speed. But with all the sticks works perfectly in Windows XP Home. It runs Orthos for 1 hour + with no problems with the 1Gb of ram.

Any ideas?

 

[fumbles]

memtest?

I've run my X2 3800+ with DDR333 with no problems..

 

[markyb]

Mem test runs with no errors at all. Ive left it run for 2 passes.

 

[brummie]

Had a similar problem here, turned out to be my wireless PCI card.

 

[LizardKing]

Have you tried booting with the -noapic command?
Will it boot to the CLI?

 

[mattyrigby00]

i had that once turned out it was a corrupted cd

 

[markyb]

Have you tried booting with the -noapic command?
Will it boot to the CLI?

Ill give that a try thanks.

i had that once turned out it was a corrupted cd

Its been working perfectly before I upgraded the Processor and works without a problem when I take the Kingston 2700 memory out.

**Update**

Ive now ripped out all the ram apart from the DDR400 Kingston 512mb Stick and its working perfectly. I put one stick back in and within 30mins the PC hard locks.

 

[richardbirks]

Maybe a CPU/memory controller microcode problem. If you haven't already done so, bring the BIOS on the motherboard up to date.

--
Richard
Signature Under Construction

 

[markyb]

Maybe a CPU/memory controller microcode problem. If you haven't already done so, bring the BIOS on the motherboard up to date.

--
Richard
Signature Under Construction

But it works perfectly on Windows XP, without a hitch. Just recently updated the Bios before I had this problem