I have this exact same motherboard. I had no problems with it until I
went to do a RAM upgrade.
Of course, I purchased the fastest RAM that the manual said I could
PC3200 - DDR-400!
And immediately I was getting blue screens!
I put the old RAM in, and NO problem. So I went to the web site!
Lo and behold! BIOS UPDATE!
The latest BIOS is:
AV49PS06
Checksum: 46D0H Date: 02/05/2004
1.Audio ID from 1106 4161 to 1297 C405.
2.Support AV49 PCB 1.5
3.Fixed 133 FSB with DDR400 compatibility problem.
Note item #3 here??? As soon as I flashed to this BIOS, the board
worked fine with the DDR400 RAM. I will caution you though, it takes a
LONG time to boot with this BIOS version! So BE PATIENT. The system
takes longer to boot, but it is stable - and that is a good thing!
Here is a lint to the Shuttle web site for the downloads:
http://global.shuttle.com/Download/Download_File.asp?Item=AV49P/N
Did you happen to notice or record the BIOS versions of the two
motherboards you have?
This is about the only thing I think could cause the problem.
Oh, and of course, you let the motherboard determine the RAM speed
timing by itself! If you manually set these settings, then you would
have to make sure that the settings were transfered into the BIOS on
the new motherboard as well.
Let me know how it goes!
hth
On Sun, 5 Nov 2006 20:02:45 -0600, "kazikmazik"
<kazhatespam RemoveThis @wideopenwest.com> wrote:
>My son recently got this MB on eBay to replace the same MB he was running
>which had a broken SATA connector. The first AV49P/N was running perfectly
>for almost a year until he wanted to add another SATA drive. After swapping
>everything, WinXP booted just fine but shortly thereafter kept giving
>bluescreens. He ran memtest and would get errors right away. He put the same
>memory sticks in another computer and got no errors after 12 hours. These
>were the same memory sticks from the previous AV49P/N. The CPU that came
>with the MB was so hard to remove from the socket that one pin of the CPU
>pulled out! It was a ground pin so that CPU is still good.When he pulled his
>original CPU out of the new MB, it was also very difficult to remove, but
>fortunately no broken pins this time. Any ideas what can be wrong with this
>board or the CPU socket. The seller won't respond to emails, so I guess
>we're stuck with it. He put everything back on the original MB and it's
>running perfectly (except for the broken SATA connector).
>