Shutdown & backup problems

[John Stetson]

I have a couple of problems I need help with. After 3
hard drive failures in a year I decided to upgrade my
motherboard/CPU (Biostar M7MKA/AMD Athlon K700/Award > ECS
L4VXA2/Intel Celeron 2.5 GHz/Award) and replace my power
supply while replacing the drive.

After doing so, I can't shut down, hibernate, standby, or
restart. Initiating any of those things from either the
keyboard or taskbar results in a blue screen/GPF condition.

The BIOS is current as of 11/03. I'm running W2K
5.00.2195, service pack 4. I have 512MB RAM installed.

I've disconnected the power to the drive and the power and
reset buttons on the front panel operate normally. But
when I come up in windows, the GPF problems occur.

All else functions normally. Except that when I tried to
back up the new drive to an older physical drive running
in both configurations (in anticipation of troubleshooting
this problem), I get a "not enough disk space" error
trying to complete an MS backup. The analysis says it
will need 1.1 GB. The drive has 11.1 GB space available.
But still I get the not enough space error.

 

[Chris Knapp]

You didn't state whether you reinstalled Windows after swapping the mobo. Or
did you just stick the old HD's onto the new mobo without reinstalling?

 

[John Stetson]

The whole purpose of the exercise was because a drive had
failed (or was failing) as I stated. Consequently, the
boot drive was replaced. I didn't reinstall windows. I
used the Maxtor disk copy utility and copied the OS from
the failing drive. Then I installed all the latest
updates from MS.

 

[Chris Knapp]

Well, that's most likely your problem. You shouldn't expect to take the boot
drive out of a server & place it into another without problems. Replacing
the mobo is basically a whole new system. Windows uses the concept of a HAL
(Hardware Abstraction Layer) to translate windows commands to actions the
hardware can understand. The HAL is initially created at OS install, and is
adjusted at every boot to account for new hardware (within reason.) A new
NIC or graphics card is 1 thing, but the all the basic IO & system resources
that are part of device manager have to get rebuilt when you switch mobos.
Its almost NEVER recommended to go the route you did. You seem to have
gotten lucky. Many report no problems but I would never take the chance on a
production system. I recommend you do a complete backup of what you can (to
tape preferably) and reinstall windows from scratch. You may have to stick
the old drives back onto the old mobo in order to get a good backup. You
could also stick the drives into another system as purely data drives and
then backup the data off them.

However, if you don't wish to do any of these things, you can check your
motherboard manufacturer's website to see if they have an INF that will help
the system enumerate all the new IO devices & system resources on your new
motherboard.

Good luck.

 

[Guest]

This is not helpful. Anybody else? One of the MVP's
perhaps.

 

[Chris Knapp]

Maybe you should pay to have a qualified Network Administrator take a look
at your setup. It is obviously beyond your capabilities.