Author Topic: Win2k / WinXP Stop Error ? (Read 338 times)

Vermillion · « **on:** July 02, 2002, 01:30:06 PM »

As some of you know from my other thread, I fried my motherboard on Sunday afternoon.

Got the new motherboard in today, installed it, and I've got it up and running.

When I started this, I had one SCSI 4Gb drive with Win98 on it, an older IDE 2Gb drive with Win2k, and a brand new drive 80Gb drive with WinXP on it.

If I boot from the SCSI drive into Win98 , no problem and thats how I'm posting here.

If I try to boot into either IDE drive and either 2K or XP operating system it won't boot correctly. I've tried both as master, slave, and solo, with the exact same results.

In BIOS it reads both IDE drives correct, and the SMART IDE function reports both drives as "OK"

In 2k it goes thru the monochrome "loading windows" screen, and then goes into the colored splash Win2k loading screen and the progress bar at the bottom proceeds all the way across the screen and then I get a blue screen stop error.

STOP ERROR _ INACCESSIBLE BOOT DRIVE. And it tells me to run chkdsk /f

Any Ideas? Same error, two physically different drives (on same cable when system blew) with two seperately installed operating systems.

Is it possible I fried both IDE drives as well as my motherboard, or is this just an error in NT I haven't seen before?

Wanker · « **Reply #1 on:** July 02, 2002, 01:49:32 PM »

It doesn't sound good, Verm. Did you update the BIOS on the motherboard to the latest by chance? If not, I'd at least try that.

You are using all new cables that came with the new motherboard, correct?

It doesn't sound good.

Tumor · « **Reply #2 on:** July 05, 2002, 08:47:56 PM »

Verm? Can you see the other drives when in Win98? I had a problem similar to this once (long time ago). If you can see the other drives in Win98, I hate to tell ya but, I ended up having to reinstall W2K (didn't have XP then). Real pain in the butt. If you cannot see the other drives in Win98.. I'd say it doesn't look good. If you can't, try booting up with a Win98 bootdisk and seeing what fdisk has to say about the other drives.

maddog · « **Reply #3 on:** July 06, 2002, 10:17:23 AM »

Unfortunately in w2k or xp changing a motherboard "forces" you to reinstall everything..... been there, done that.... no way around it...... (had same problem)(same error).... have to reinstall OS from scratch...... sorry....

SKurj · « **Reply #4 on:** July 06, 2002, 01:28:49 PM »

i changed a mobo under XP pro and had to do absolutely nothing!

XP recognized the changes and did everything for me... surprised the hell outta me...

good luck Verm

SKurj

AKDejaVu · « **Reply #5 on:** July 06, 2002, 01:34:13 PM »

I've heard that Win2k and XP are different as far as the MoBo change goes. XP may not require a re-install, but Win2k will.

We do need to get one of the pros in here on this one though... I know there are quirks with installing Win2k on SCSI+IDE systems. I had a friend that had some issues... but I don't recall what they were.

AKDejaVu

AKIron · « **Reply #6 on:** July 06, 2002, 03:05:00 PM »

Both Win2K and XP have a boot.ini file at the root of their boot drive. This file tells the system from which partition to boot.

It's possible that the new mother board has somehow assigned different priorities to the drives. If your using NTFS on the drives then you'll need a repair disk to alter them, FAT32 and you won't.

You might also try swapping cables, including the cdrom drive and removing the scsi controller.

AKIron · « **Reply #7 on:** July 06, 2002, 03:36:14 PM »

FYI, WinXP will require reauthentication if significant hardware, i.e., motherboard, hard drive, etc... is changed. I've heard, but can't verify, that you can authenticate once every 120 days automatically (either by Internet or phone). If you have to reauthenticate more often than that you will have to call and explain why. This last one I can verify as I've had to do that several times now.

bloom25 · « **Reply #8 on:** July 06, 2002, 04:38:00 PM »

Did you remember to hit F6 right at the start of Win2k install and install your raid drivers off a floppy disk? Typically though, even if you don't the raid controller (if it's a Highpoint at least) will work as a regular IDE controller but lack raid functionality. You might try just hooking up the drive with Win2k/XP on it alone as the primary master (single) and seeing if the system boots.

Vermillion · « **Reply #9 on:** July 06, 2002, 10:24:36 PM »

Wasn't a Raid system.

The Win98 can't read the drives because they're NTFS.

Took both the IDE drives (NTFS drives, 1 w/Win2k, 1 w/WinXP) to my office and hooked them up to my Win2K system there as the last resort suggested for that particular stop error (error 7B) in the "Getting Started" manual.

Then ran the chkdsk /f as suggest and no errors were reported. Strange I could access both drives with no problem, but evidently both drives had the boot sectors corrupted, as neither would still not boot.

Bascially I got the important data off the new 80Gb drive, and just did a fresh install of Win2k. A pain in the rear, but only way I could get it to run. Took a whole day to get it all setup.

Then believe it or not, somehow in all the installs and updates to all my software, I caught the Frodo.Fish.6 virus, even though I had Norton Antivirus installed, which corrupted my nice new fresh Win2k install and the next day I had to wipe the drive and start all over again.

Oh well, its all fixed now. Thanks guys.