Link to home
Start Free TrialLog in
Avatar of stretchr

asked on

XP reboots on Stop error following hardware upgrade

Hi folks,

Just upgraded some components of my home PC, new mobo, CPU and graphics.

Went from a Gigabyte mobo with Intel chipset and 2.8Ghz P4 CPU with Radeon 9600 to a new Asus A8MVP deluxe with crossfire chipset, Athlon 64 X2 4200+ CPU and Radeon X1600.
NIC is now onboard rather than a separate PCI card, but other than that, all hardware is the same.
I'm running XP Pro SP2 with all the latest patches.

I've done searches here and found stuff that is similar to, but not quite the same as my problem.

When the machine boots, the windows splash screen appears, then just about at the point it would normally move on from there, the splash screen freezes for about half a second (ie the running bar stops moving) and then I get a BSOD with a stop error that flashes up for a brief millisecond, just enough to determine that it is a stop error but not to get any other detail, then the machine reboots. If I just left it, it would do this endlessly.

I have managed to boot into safe mode, and windows appeared to finish loading all the drivers for the new mobo bits n pieces, and the drivers for the X1600 as well, but on a restart, the same thing happens as above.

So I went back into safe mode, managed to get online, and read somewhere on this site to try doing a repair install of windows, so it can rebuild the kernel or something like that. I loaded up the windows CD and booted off it, started off the repair install. After copying the files to disk, it has to restart. And on restart I get the BSOD and rebooting as first described, so now windows is stuck in the middle of Setup with nowhere to go, if I boot into Safe Mode I am told that Setup cant run in safe mode and I cant do anything except reboot. It's a never ending loop.

So I suspect I am going to have to do something in the Recovery Console, but I have no idea what, as at this point in time I have absolutely no idea what is causing the stop error.

I have pulled out all extraneous hardware and USB devices, all I have left plugged into the mobo are the graphics card, network cable, mouse, USB keyboard, one SATA connected HD that I boot from, a SATA connected LS120 drive that the BIOS doesn't appear to recognise, DVD drive and CD drive, and USB connector for extra rear USB ports.

As it's my only home machine, I want to get it up and running again ASAP without having to throw all my old hardware back in.

Any help or pointers most appreciated.

Avatar of LeeTutor
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of stretchr


Do I possibly have to force the HAL to something different as per now that I'm running a dual core CPU?

I'll try that when I next get back to my computer, I've been using the advanced options menu to get back into Safe Mode, didn't ever notice an option to disable the automatic restart though, maybe wasn't looking hard enough!

Will post back here if that works and I can see what the STOP error is.
As to your question on forcing the HAL, I am not a hardware expert at all, but after reading the MSKB article, I think it likely that you would have to follow that.
Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
venom if you read my post correctly, I'm in the middle of doing a repair install, and after setup finishes copying the files across, it has to reboot to continue the setup procedure, it's at that point that I'm still getting the stop error. I was hoping the repair install would have fixed it but it hasn't.
If you have a second partition, I would do a fresh install so that you have a dual boot system, onto the second partition.

If this does NOT work, then you may have bad hardware somewhere.

Remember that you may need to load SATA or other drivers as part of the install process.

I hope this helps !
Is it possible that during the restart, it needs to boot to the cdrom.
Have you adjusted your bios so that the cd is the first boot device?
here's what i did for that exact problem after moving from an soyo k7vme to an asus a8v, i booted into safe mode->
1)  went into devmgmt.msc & removed all old devices related to the old mobo, then i went into add/remove software & removed anything soyo related - including.
2) rebooted back into safe mode, then put in the driver cd from asus & manually navigated to the appropriate inf file for any driver that xp tried to install & ran the 4in1 via update tool
3) was able to boot into normal mode without rebooting, then continued to load the driver software for the ati radeon card & other asus tools - never had to repair or do an in-place reinstall.
Ok well here's what happened over lunchtime.

I actually had an old install of XP on another hard disk (IDE not SATA), it's from a year or more ago, just still sitting around, the reason I dumped it was that I couldn't get XP SP2 to install on it. So I booted it up and it worked beautifully, booted into XP, found all the new hardware, installed drivers for it, rebooted, windows started again no probs at all.

Then I started up regedit, and followed the steps in , loaded the hive of the XP install that wasn't booting, (hmm I'll have to double check that tonight but I'm pretty sure I had the right one) and changed the autoreboot value to 0, unloaded the hive and restarted.

Booting the problematic drive then had absolutely the same problem as before, and that's all I had time for. At least I have a working installation that I can use to help troubleshoot.

Sysexpert, if I had to load SATA drivers it wouldn't have found my current installation in the install process, so that's not the problem.

If anyone can tell me how to tell windows that its not in the middle of a setup process, then I could go back into safe mode and try some of the stuff that friartuk did. I did actually remove all the software related to the old mobo when I went into Safe Mode the first time, before I started the repair install.
Did you manage to boot with the " disable automatic restart on system failure" feature?

my advanced options boot menu doesn't have an item called "disable automatic restart on system failure"
Are you definitely booting from an SP2 CD?  If ti's an SP1 cd, then you'll have to slipstream it with SP2:

no, it's an SP1 cd, but I thought that I would be able to repair from the SP1 and then reapply SP2. Anyway, I'll create the slipstreamed CD and then give that a go, but I'm not optimistic at this stage. I already half got ready to do a slipstream CD before but didn't finish it.

I just checked, and I have got the automatic restart on system failure disabled in the system hive on the problem install, so there must be another reason why the BSOD is flashing so quickly. When I say quickly, I barely get to see the blue on screen before it disappears.
when I get them, I normally record it with my camera phone, then go back through the frames and I can see what the message was ;)
hmmm, good idea, might drag out my camera and see if it can get it
did you have a look at the links i posted? can help
well, recording at 30fps I cant even catch the whole of the stop error screen, I don't think it's even drawing the whole thing. The last paragraph I can see on the screen reads " Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing. If you  need to use safe mode to remove or disable components, restart your computer, press .... " and thats where it ends .. top half of screen only.

Well, now to try my slipstreamed XP-SP2 cd.
nobus, thanks but they weren't any help at all, already covered that ground
On my PDA, I record, and then play it and then pause it at the right spot and I seem to get it.. Have to do it a few times to pause it at the right spot but it does the job.

Have you tried to boot to the cd and try the recoveyr console doing.

chdsk /f

I had a computer recently that did the same thing but with a slipstreamed version of xp with the drivers inside, so it makes me wonder if it does have something to do with the driver as SysExpert said.. maybe as a last resort, you could try loading the driver again (with F6 during windows cd boot install)  just incase the system one is corrupted for whatever reason.

I've got a canon Ixus 800IS and I can play back the movie recorded frame by frame, that's why I'm telling you like the whole blue screen showed for like 1/10th of a second

Anyway, I've run setup with the slipstream CD, and now at least the boot is halting on the stop error screen

Tech info reads:

STOP: 0x0000007E (0xc0000005, 0xF77EC750, 0xF79FB42c, 0xF79FB128)

nothing else

I might try updating the BIOS next
according to this article, it can be ba
Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Well it's unlikely to be the ram, I have two sticks and tried each of them separately, no joy
well, did you test them? use memtest86+ from :      
and did you update the video driver?
there functioning fine for me in this install of XP on a different HD ... as mentioned, without SP2 ... and I cant update the video driver because it's still in the middle of setup
chkdsk and fixboot in recovery console didnt make any difference. wasn't willing to risk fixmbr taking out my partitions

back to a dead end *sigh*
Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
yeah have plenty of HD space ... 7.5Gb free on an 18Gb partition
well moving all the files out of the Drivers folder hasn't worked so far .... but I'm thinking I may have taken too many out, it's now telling me it can't start because the fastfat.sys file is missing, so I think the line about all files with a creation date of 8/13/2001 is incorrect, it doesn't take into account SP2 files, which by looking at my machine here at work, would have a creation date of 4/08/2004 (or 8/04/2004 for you folks across the ocean). I think when I get home again I'll try putting everything back except the files which have a very recent creation date, of which there are a number.
Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok I'll give that a try tonight. My working installation is now doing the same thing as the problem one used to, quick flash of stop error on bootup then reboot. So I think I'm going to have to do a fresh install on that system just so I've got something to work with. Repair console will just take forever to put the driver files back because you cant use wildcards.

no joy with those links. mind you, I couldn't find the CurrentControlSet as mentioned on, only ControlSet001, maybe it's in a different hive located somewhere else.

I've installed a fresh copy of windows on my old drive, and all working well so far. I have taken all the freshest files out of system32\drivers, including video card drivers, and now the stop error is giving me some more info. After the STOP 0x0000007E line, there's now a line that says imapi.sys
Strange.... try and delete that driver and/or disconnect the cd drive completely from the PC.

When exactly did you upgrade to SP2, or have you been running it all along..
hmm, can't remember when I upgraded to SP2 .... definitely over a year ago, possibly 18 months or more .... I installed SP2 as soon as I got the new HD and ghosted the old install across to it. will try deleting the driver and try the drive thing too.
neither deleting the driver or detaching the drives made any difference

i'm about ready to give up here and just to a fresh install, and grit my teeth for the days ahead of configuring and reinstalling software ...
yes, reinstalling is time consuming. If you like to return to a clean system every few months, i suggest install all your applications, and settings; let it run for a few days to check if you haven't forgotten anything, and make an image.
you can use xxcopy, ghost, or Acronis drive image for it.
Then, in 20 minutes, you set the image back.
I've got Acronis, thats how I imaged across from the old drive to the new one. But yes, at least with a reinstall I will have a nice clean system.
well - I admire your patience for sticking in this long - when I had a problem of this degree for about the 50th time, I switched to Linux and never looked back ;)

I'll keep looking around for a solution - let me know what you decide.
well its the first time i've had a problem this big. I'd probably have switched to Linux too if I didn't have a number of programs that only run on windows and no Linux alternative. Matter of fact, I just burned a Linspire Live cd today at work just in case I couldn't get Windows going again, so I would at least have something at home to access the internet for research.

Time to bite the bullet .... wish me luck.
heh yeh - the programs that I need to access in windows, I still do, using an emulated copy with the free vmware server.. works lik ea charm, and plus, if you don't need internet access you can lock it down so no viruses get in just like a standalone PC.  It'd run sweet on your system, i've only got an Athlon 64 3400+ single core.

Good Luck! ;)
hmmm might have to look into that, didn't know there was a free version of vmware
Ok well thanks for all your help. Further on Linux, I've been playing with it on and off for oh probably 8-9 years or so ... various incarnations of redhat, lindows, xandros and others.
thanks for the grade - although i'm sorry we couldn't fully fix your problem!
I ran into this recently... rarely mentioned is the fact that if something perchance trashes your iastor and/or other related drivers that are responsible for allowing the operating system to recognize attached SATA drives, then you will run into this problem of auto-restart, specifically...

1) you can boot as far as being able to go to the (F8) Advanced options menu

2) you can continue thru the boot logo, i.e., if you were not displaying the boot logo you would observe the drivers list loading

3) if you are observing that list you may observe the very last driver listed as the 'ACPI' something or other (to do with your system's ACPI Controller driver), or if you are not observing the list it will appear as if you are leaving the Boot-Logo and just about to be handed the Logon screen...
....when suddenly you get BSOD, but its too fast to observe.

4) and you cannot log into Safe Mode Either.

Describes your problem?  Then go into your MotherBoard's BIOS and switch your Device confirguration for the Hard Drives ...turning SATA to Disabled.

You should then be able to boot and log into Windows.
IF you can, then the next stage of recovery is to (after backing up of course) download and reinstall the ACPI/SATA drivers for your motherboard model & operating system version.

Took me forever to find (googling)  that this symptom is a classic issue pertaining to trashed ACPI/SATA driver, or an ACPI Controller issue.  Mine happened after simply plugging in a Logitech Mouse Transceiver... when it went to load its new driver my system hung.  Took me a cople days to find out the issue, but, due to other ramifications, it then took me three weeks to recover my system.

Nightmare...  hope sharing this is helpful to any other poor soul facing this.

Cheers, TwohHawks