[no2pencil]

I've been working on this customers machine for about 3 days now, & I'm getting no where ... fast.

The customer jammed a foreign object into the usb drive, shorting out the usb chain. So when the new motherboard arrived, I figured since this was a set in stone, no options motherboard (Gateway eMachine el1200) that it would be a simple part swap.

From the getgo, the original install of Windows XP (Home) throws a BSOD at boot with the 0x0007B error, indicating it has trouble communicating with the Boot partition. This is odd because I see a quick blip of the Windows XP logo. This also indicates that the Hard drive is seen by Bios, before anyone asks.

So no matter which option that I choose, safe mode, command prompt, or regular mode, it would BSOD. After some lengthy research, I found 3 possible solutions, & the following infromation.

The reason for the error is that the chipset is somehow different, between the motherboards, & the instillation of Windows needs updated drivers to access the chipset. This makes sense. So after visiting Gateways website for the motherboard drivers (here), & installing every available option (on the pre-existing motherboard), I am at the same resolve.

1. ) Disable the ACPI option in bios. After doing this, the BSOD goes away, however the machine simply reboots, without the slight blip of the Windows XP logo

2. ) Perform a fresh install of Windows XP. I wasn't keen on this option, but I thought an OS repair might be in order. I get the same BSOD error off both Home & Pro boot disks.

3.) Flash the BIOS with the newest release (found here). Though I don't much like the idea of going "all in" with flashing the BIOS, my options are looking pretty limited.

After reading the following, how on Earth would I be able to flash the BIOS if I can't get access to the OS, &/or is this even the right approach? WTF is Windows rebooting, with no BSOD?!

Thank you...

[Sethro117]

Hmm, could it have possible done something to the PSU as well? I wouldnt think a PSU issue would cause a BSOD but after disabling ACPI and the BSOD going away but still not booting properly it might be worth to check out if you have an extra PSU that will work on that machine laying around.

When you got the BSOD would it stay powered on until you rebooted it or flash then start to reboot?

[no2pencil]

With the BSOD it stays powered on until I shut it down by holding the power switch.

Assuming that PSU = Power Supply Unit, the entire rig works fine with the original motherboard. Except for the damaged USB ports & USB chain (bus?). It boots, I can get on the network, access user accounts, everything that a normal XP install should do. However, changing the motherboard & the OS craps out.

[Sethro117]

Cant you flash from a Floppy or USB drive? I read up on the BSOD error and came across the IDE controller being different. I sure you read it to but that makes sense, since its new motherboard. Ive never flashed a BIOS in Windows all the ones Ive flashed have been old and the update was able to be put on a Floppy and booted from.

[no2pencil]

I didn't think about using a USB drive. Even so, the bios image provided by Gateway comes in an exe file. Without being able to boot Windows (from CD/DVD or the Hard drive), how can I run an exe?

How can I access the floppy or USB outside of Windows?

[Sethro117]

Just the WinFlash utility is the EXE to run from within Windows. You can use regedit and stuff in DOS mode cant you? Isnt that like running an exe? Im probably taking a shot in the dark there, I havent messed with hardware for awhile so Im proably wrong.

Im *thinking* you could boot from usb then just run AWDFlash.

[no2pencil]

Sethro117, on 10 Dec, 2009 - 10:30 PM, said:

Just the WinFlash utility is the EXE to run from within Windows.

Please see above where it can't boot to Windows.

Quote

You can use regedit and stuff in DOS mode cant you?

Please see above where I can't boot to DOS.

Quote

Im probably taking a shot in the dark there, I havent messed with hardware for awhile so Im proably wrong.

It isn't that you are wrong, it's that I must have not made myself clear.

The hard drive obviously works fine, as it boots with the old (blown USB) motherboard. When I swap motherboards, it doesn't do jack. The only difference that I can make is that with ACPI enabled, I get BSOD, with ACPI disabled, it reboots. It will not boot off the hard drive in any mode nor can I boot off a Windows XP Home or Professional setup disk to use the repair console. I can not operate in an OS to any degree (that I know of) using this motherboard, so how can I run the flash utility?

Quote

Im *thinking* you could boot from usb then just run AWDFlash.

Is AWDFlash a mini OS, or does it require to be ran inside of an OS? I'll check out AWDFlash & see what I can find out.

[Sethro117]

No sorry. I figured the AWDFlash is what contained the BIOS Update in that file download you posted in the first post. I looked at it and the WinFlash is just for those who want a GUI to do it so youd have to be in Windows. I was meaning since you cant get into Windows you could try maybe putting like a win98 boot disk on the USB and booting to that then that should be able to get you to a DOS prompt then just run the AWDFlash.exe which should update the BIOS. I dont know, Im just offering ideas. lol

[danny_kay1710]

no2pencil, on 11 Dec, 2009 - 03:09 AM, said:

I didn't think about using a USB drive. Even so, the bios image provided by Gateway comes in an exe file. Without being able to boot Windows (from CD/DVD or the Hard drive), how can I run an exe?

How can I access the floppy or USB outside of Windows?

Use BartPE or you could boot into a vista install disk and get to the startup recovery command prompt and try running it from there. I don't know what is stripped from either of these though so there is a chance it might need a section of the Windows API that could be missing from either version.


When you disable ACPI you are changing the HAL of the computer. I would be more surprised if it didn't reboot almost instantly. The chances are it is BSOD'ing just it's instantly rebooting.

It could also be a safety mechanism if the OS makes an unsupported power feature request or similar. (Just a guess)

I would try two things:

1) Try sysprepping the windows installation using the old mobo use the -pnp and the -clean command line arguments to force driver re-detection and clean the Mass Storage driver database. make sure that you use the new mobo when it reboots though. (I would try this first as the next one to me is a last resort before reformatting.)

2) Force windows to use a different HAL when up and running on the old mobo.

To do this goto Device Manager. Under the computer section there will be something like ACPI compliant uni/multi processor PC or similar it can be a few different things. Update this driver and tell it you want to choose from a list of drivers. You should see an option called Standard PC

This is the most compatible BUT can have side effects e.g. it may prevent it from auto-powering down, COULD have performance issues AND IS NON REVERSIBLE WITHOUT A FULL RE-INSTALL. The HAL is the most vital part of your system so changing it could lead to all sorts of weird and wonderful things. I have done it in the past form most compatibility on imaging but there are querks.

When it first reboots it will re-install a whole load of drivers for a crap load of things. It may be best to allow it to do this on the new motherboard if it gets into the OS, if not try doing it on the old one then using the new mobo.

I hope this helps but I must re-iterate that the last option COULD backfire, at best it has annoying and stupid side-effects and at worse it breaks OS on both mobo's. Do this at your own risk.

This post has been edited by danny_kay1710: 12 December 2009 - 04:04 PM

[no2pencil]

An update on this issue. I received an answer to my email with the supplier of this motherboard. They were able to replicate the issue, & they are going to swap out the board for a proper replacement for the chipset.

So there is no way I'm flashing the bios. Though I've performed a BIOS flash before, I'm certain this wouldn't fix the issue.

[Mr.Janson]

Does the computer have a sata drive? if so try changing the sata operation in the bios to raid auto detect/ATA or raid auto detect /AHCI or vice versa not sure this will help but its worth a try.