Xp bsod on startup after ram upgrade

by Blaine   Last Updated May 16, 2019 01:01 AM

I just upgraded my hp dv6426us from 1gb of ram (512x2) to 4 gb (2x2). I have a vista 32 bit and xp 32 bit dual boot os configuration.

Now when I boot up xp gives me a bsod right after showing the spalsh screen. It does this in safe mode too. However, Vista works fine. The bios shows 4096mb of ram. Vista System information shows: Installed physical memory (RAM): 4.00 GB Total physical memory: 2.99 GB

I would like to be able to use xp with 4 gb of ram, or at least the 3 gb it cuts it down to (if it does.) I would not like to go back to using 1 gb. Any suggestions? Thanks!

EDIT: the bsod shows:

A problem has been detected and windows has been shut down to prevent damage to your computer. If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check for viruses on your computer. Remove any newly installed hard drives or hard drive contollers. Check your hard drive to make sure it is proberley configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer

Technical information:

*** STOP: 0x0000007B (0xBA4CF524,0xC0000034,0X00000000,0x00000000)

also, memtest86 results are no errors

Answers 3

STOP 0x0000007B normally means "INACCESSIBLE_BOOT_DEVICE", which means that the crash on XP happens very early in the boot process.

This stop-code actually means : Something prevented protected-mode (meaning XP boot) from connecting to the device that the real-mode (meaning BIOS) passed on to protected-mode. Said device is most probably the hard disk.

One guess to the problem could be that it has to do with the BIOS seeing your additional RAM but somehow later miscommunicating with the XP boot process.

In that case, I suggest as a first step to update your BIOS from the page HP Pavilion dv6040us Notebook PC Drivers, then try again to boot. Ensure that your computer model is exactly the same as described on that page and that your BIOS is not already of that version (so as not to take this risk for nothing). Stop on the least doubt or error message, since a botched BIOS update can brick your computer.

If this doesn't help, start XP with 1 GB and fully patch it using Windows Update, including optional updates. Check in the above HP download page if any drivers are more recent than the ones Windows suggested, with special attention to the chipset and storage drivers.

If this doesn't help, setup the computer with 4 GB and try to do a Repair Installation for XP. This requires an XP boot CD, but read well on all the requirements in this article.

All backups need to be done before starting, as this kind of operations could result in a total reinstallation of all operating systems.

February 10, 2014 15:02 PM

Ok, this fix was originally suggested in a comment by gladiator2345. I am now posting it as the answer since he did not.

gladiator2345 said:

Could you check if SATA mode in BIOS is set to AHCI. To boot xp it should be set to ATA

When I was changing the ram, I disconnected the cmos battery just to be safe. This must have reset the bios changing back to sata enabled mode that I forgot I had disabled to allow xp to run.
It's just like me to forget the most obvious things :P Xp sys information even recognizes 4gb of ram (although it only shows 2.64 as "available" and task manager says 3gb total. Whatever the case, performance is now stunningly better.

Thank you once again gladiator2345

April 26, 2014 04:11 AM

I just wanted to say that I had a similar problem, found this by Google search, and my BIOS was strangely set to AHCI. Setting it to Compatibility fixed it. I was about to wipe my entire partition and try to reinstall XP. You saved me precious files and hours of troubleshooting. I love you, gladiator2345!!!!!!!!!!!!!!!!!!!!

May 16, 2019 00:36 AM

Related Questions

Updated September 18, 2017 20:01 PM

Updated June 10, 2015 16:00 PM

Updated May 13, 2017 09:01 AM

Updated March 01, 2016 08:00 AM

Updated December 21, 2018 14:01 PM