Saturday, October 07, 2006 11:12 PMJust downloaded RC2 today and burned it to dvd. It installed fine on my ancient laptop with no internet so I know the image burned correctly. However when I try and install it on my HP I get this message after the initial "Windows is loading files" progress bar:
"Stop: 0x0000005c (0x0000010b, 0x00000003, 0x00000000, 0x00000000)"
That's it. I have to reboot. My computer is a HP with a 250gig hard drive, 1gig DDR2 ram and a Xpress200 ATI graphics card. My hard drive is partioned with a EXT3 (Ubuntu), Swap (for ubuntu), NTFS (Current windows installation) and a FAT32 storage partition. What do you suppose the issue could be?
Update: I launched the ISO through damien tools and it initially installed quite ok but as soon as the PC went through the first restart I got the same error screen. It also happened after another restart.
What could be going on here?
Saturday, October 07, 2006 11:31 PM***, just went googling for this issue. It seems many, many others are having this issue but there is absolutely no solution. Can anyone confirm this? Any updates when the Vista team will have this fixed?
Saturday, October 14, 2006 8:21 PM
Same error here. I called into Support Line and it gives the option for Vista RC1 support. The rep told me that only customers who are slected can get free support. That's funny cause we're all trying to help Microsoft troubleshoot the bugs and it seems that this one has no fix. Any help from someone would be VERY appreciated.
I've now tried loading Vista RC1 32-bit from:
1. Fresh XP SP2 with all updates, Tried to upgrade to vista and migrade settings. - Same error code.
2. Fresh XP SP2 with all updates,tried to install Full Vista over XP and same error. I loaded the SATA-Raid drivers while the fresh Vista install was going on. Very nice interface to load drivers but the rest of the install has to work for me to like it. Same error code.
3. Load from boot device. CD-DVD ROM. Gets to loading the files and finished the horizontal bar load and then bang "Blue Screen with error code.
4. Tried going into Safe mode- Same error.
5. Safe mode - low res 640x480 - Same error.
6. Fresh XP SP2 install with all updates, tried to install Full Vista over XP, after uninstalling all the video drivers. Now all I get is the Vista compatbility program telling me that I won't be able to use the Aero interface. - Same error.
Vista RC1 64-bit from:
1. Load from boot device. CD-DVD ROM. Gets to loading the files and finished the horizontal bar load and then bang "Blue Screen with error code.
Im still able to get to the XP install but have to quickly select the previous XP install from the menu. This isn't a primary PC but it's still frustrating as others have described. I'm only trying to load Vista on 1 hard drive no RAID.
I got an error message that told me the installation had failed and go to the upgrade advisor from microsoft. I had run that before doing the install and the only issues that it mentioned were the display driver. That seems to be a common problem among beta testers. It only mentioned that I might have trouble with the video drivers and that they may not work as expected. As above mentions I tried to install without the video drivers that vista says will be a slight problen. The scan came clean and even after loading all the files during the installation and then expanding some (i think 20% or so) it says it needs to restart, then "Blue screen" with error code.
PC is a:
Pentium D 945
160GB WD Hard Drive
ATI Raden Express 200
Thanks ahead of time for any help.
Saturday, October 14, 2006 8:32 PMI am also using the ATI Radeon Xpress200 video card. That is the only common hardware between our two machines. I heard somewhere that the ATI drivers may be causing the conflict but I got the same error even after a fresh format. Otherwise the steps you outlined above are exactly the same steps i tried. Exactly
Saturday, October 14, 2006 8:37 PM
Glad to hear I'm not alone in this frustrating circle of restarts.
I found a post on another website related to this issue but not on the MS site.
Hope it's ok to post this. Thanks ahead of time to the other website.
If the link doesn't work, basically it may be related to the ECS motherboard. Did you get yours at Fry's with a special sale? That's where this one is from. Good cheap machine for the price. Just using it as a file server/web/ventrilo/general.
I will keep looking for a solution and post here. I'm running memory tests but I doubt they will find anything. It's been running in XP for days at a time with no restarts.
Saturday, October 14, 2006 9:00 PMI actually got mine at CompUSA. It is a HP Pavillion a1420n. Interesting post you linked. I may have to see if there is a BIOS upgrade available.
I've ran Win98, WinXP and even Ubuntu with no issues on this machine. I will have to check out any BIOS upgrades available.
My memory tests came out fine and the MS advisor gave me the green light for Vista compatability as well.
Thursday, October 19, 2006 12:49 AM
I've given up as of 3 days ago on this version of Vista for the PC i have.
No luck with the RC1 after more than 6 hours of work. I ended up trying to load Vista with 5 different SATA/IDE drivers just to see if there was some possibility of a driver conflict with the SATA controller. No luck. Same error no matter what driver I loaded.
I gave the copy to someone else to try it on their test bed. I will try to update the post with the results.What sucks is I paid MS to do all this work and they won't even hear my feedback.
Wednesday, March 28, 2007 5:32 AM
yeea im having the same problem here too... i let my friend test it out.. and it works for him.. >.>
Pentium D 940
and using this new SATA dvd drive i just got..
Thursday, October 04, 2007 5:22 PMI had a stable vista system for about a year, now I get this error.
Caused by Windows update?
Full error is Stop 0x0000005c (0x0000010B, 0x00000003, 0x00000000, 0x00000000)
Any help appreciated.
Friday, October 05, 2007 4:38 AM
So after a load of reading on-line this is what happened for me.
I learned that the error is to do with a hardware abstraction layer.
I found that for some people it's to do with the power saving settings (set them to ASPI).
For others it's simply a BIOS that does not support Vista. (not my issue)
For others still it's due to a RAM voltage being a smidge too low. (not my issue)
So for me, it seems to be that Windows Update - that installed last night - killed my machine. I finally got the machine to boot in safe mode (I fiddled with ASPI, DIMM Volyages, and generally fiddled in the BIOS), and once it did, was able to perform a resore point roll-back to before the last windows update.
Apart from my USB keyboard also giving up the ghost at the same time, I would be comfortable with my diagnosis. As I had to plug in a PS2 keyboard, I can't really say the machine is 100%... But EVERYTHING else I have tried seems to be working...
Good luck all who suffer from the BSOD.
I will post more if I learn more. (using another machine as necessary!)
Thursday, November 20, 2008 8:04 PMI found a resolution to this with HP Server gear. There is an advanced BIOS setting for Linux HPET. If you disable this, it works. If enabled, you get the bsod stop message.
HPET is a hardware timer: http://en.wikipedia.org/wiki/HPET
- Proposed As Answer by Reddy Surendar Wednesday, November 11, 2009 7:48 PM
Thursday, September 24, 2009 10:18 AM
Thanx for the solution
Saturday, December 26, 2009 5:13 AMHey,
The correction to this problem is easier than you think. The problem is you need at least 2gigs of ram in order to install the operating system. If you do not have 2 gigs the system does not have enough temp space to store the install files and you get the dam "stop blue screen. Remember the the minimal system requirements for Vista and 7 is at least 2 gigs of ram. Since you only have one, well that's the problem. Add more ram and good luck.
Friday, January 01, 2010 10:14 PMIt is so annoying that neither Microsoft or Acer (7520G) just sit on things and absolutely do nothing about to fix the issue. It is like Adobe doesn't seem to be busy at all to fix stuttering Flash problems although the net is full of experience that no matter the models of computers people use, the stuttering problems keep on going.
Friday, March 26, 2010 8:39 PM
Hi! I've had this exact same HP Pavilion computer you're talking about at home for repairing. The guy asked me for a Windows 7 upgrade at the same time. MylesKelvin was right: That computers' BIOS is what is causing this error, preventing the Windows 7 installation from booting the computer properly!
Find the BIOS update for your specific HP Pavilion model (mine here is "Pavilion a1320n"). It's available on HP's website, in their "Customer Care" section! This update could be executed from my Windows XP installation.
Then I rebooted and, voilà! The STOP message didn't appear anymore. I hope these were clear instructions! Have a nice day.
Wednesday, April 28, 2010 4:12 AM
You all are good...updated bios and now win 7 is installing (Pavilion a1320n)
Friday, June 18, 2010 7:43 PM
Thank you for everyone's previous posts. i was trying to install windows home server on my wife's old compaq presario SR1705uk machine which i have added RAM to to make it 2 Ghz and had install server Win2K3. this error kept coming up. after reading previous posts i downloaded a BIOS updated. tried to install Home server again and TWOK (Tested Working OK) fantastic!
Thanks again for everyone's posts
Computer Mong that i am
Monday, June 21, 2010 10:03 AM
Sometimes the stop 0x0000005C error appears on the screen of your computer at the time you attempt to setup the Windows XP operating system on the computer. The error message is most of the times displayed at the moment you try to restart the PC during the installation process or immediately after the completion of it.
There are several reasons for the stop 0x0000005C error to occur on your computer. Some of the most common are:
- There is not enough free space on the drive where you try to install Windows XP
- Some of the BIOS settings are no longer compatible with the new operation system.
- You have an outdated, faulty or incompatible third party device driver installed on your system.
The outdated system files and drivers as well as a full hard disk are the main causes for the computer errors. In addition to that, the spyware infections and the bloated windows registry increase the number of problems you may experience with your PC. With some preventive maintenance and an increased level of vigilance, you can avoid this sort of problems like the stop 0x0000005C error. Just use the registry cleaner software regularly and your system will be just fine.
This is the easiest way to eliminate the stop 0x0000005C errors.The majority of these programs are offered in a freeware version but some of them will offer you more complex features and you will need to pay for them. Of course, there are free trials and with their help you will be able to test before buying.
It is recommended just to download a copy of these registry cleaner programs instead of spending time online to document about the manual resolve of the stop 0x0000005C error. The software find and fix the error in no time and you will not need to worry anymore about this. You should not miss the opportunity of the wide range of software that will offer both the free computer scan and the free repair of the problems that are found during the scan which these programs perform. They will also update regularly, so you will have a complete working program at your disposal all the time.
Click here for more info.
Friday, July 23, 2010 3:41 PMSolved thanks to your indication!!! My board is an MSI G31TM-P21 with the same issue. I changed the hpet parameter to enable and now Windows 7 installs perfectly!!!
- Proposed As Answer by Baris Eris Thursday, October 06, 2011 12:09 AM
Monday, January 24, 2011 8:58 PM
Hello: I also had this issue in a gateway 2.4 dual core running win7 pro. I was adding a internal drive to the system. All was going as planned, saw it, configed it, formated it and then. I ran a disc scan on the new drive and in the process system crashed. Then on reboot got missing tables message and the blue screen 0x0000005C . I tried the install disc but could not get to the repair screen or when i did it started to load and then went to the blue screen. So, I made the new drive the primary and same thing happened. I then installed a new drive and it also would not install from the disc. So then I remembered I had something similar before in another machine.
I removed one ram stick and guess what happened. It loaded from the original drive, repaired with a 24 hour roll back and machine appears to be functioning normal. Conclussion, ram held the defect tables when it crashed, boot bio's up looks at nvram, it must load whats held in memory and once it was removed machine loaded normal. Reinstalled the one ram and guess what , machine started normal, all functiions test perfect. In the past I have had many machines not load for bad ram so was reason I went that avenue. try removing one ram at a time and see if it helps.
- Proposed As Answer by maxineis Monday, January 24, 2011 10:35 PM
Thursday, December 08, 2011 8:55 PMWow, thanks for this, Gifto. I was just having this problem while setting up one of my Proliant servers and although I had seen that BIOS setting it never occurred to me there might be a connection. You saved me a lot of swearing and hair-tearing.
- Edited by CUPressIT Thursday, December 08, 2011 9:04 PM
Wednesday, May 23, 2012 4:29 PM
In my case... I have a Desktop Board "Asrock G41M-VS3" i had reseted de bios, Updated it (Instant Flash inside de BIOS setup with a USB Flash Drive), changed Ramm Sticks, Hard Disks... Without Success.
I was found inside de Bios a option in the ACPI Settings called: ACPI HPET Table (It was disabled by default)... I changed it to "Enabled" and problem solved.
Thanks to all u guys!.
Wednesday, July 18, 2012 7:40 AM
just saying thanks for this thread.
had issues with installing Windows 7, got the same error.
it's an eMachines T3516A so i updated the BIOS from " RC410-M V1.02 " to the latest available of version 2.00 : http://support.gateway.com/us/en/emac/product/default.aspx?modelId=1575
and it installed fine thereafter. :)
note1: because it had that error and i had wiped my drive prior to the install of Win7, i had to reinstall XP and then flash the BIOS under that environment......it went smoothly....i then formatted the drive and installed Win7 with no probs. :)
note2: always make sure you only flash what is correct for your system!
hope my experience helps someone googling too. :)
- Edited by richtv Wednesday, July 18, 2012 7:47 AM