:Stop error in win2kpro after p3v4x installation

[pX1138]

Finally got to use my new 550E on the p3v4x i got in the mail today, but every time I try to boot into win2000pro I get a stop error:

STOP: 0x0000007B (0x81825690, 0xC0000032, 0x00000000, 0x00000000)
INACCESSIBLE_BOOT_DEVICE

Then it goes on to say a bunch of stuff like;
Remove any newly installed hard drives or controllers... make sure hard drives are configured properly, etc.

I've got win98se on another partition on the same HD, and it runs fine. So far I've tried taking pci/isa cards out, disabling the USB(possible IRQ conflict?), and running CHKDSK /p /r in the recovery console of win2k, nothing has worked, still get the same error.

Anyone have any ideas?


pX1138

 

[pX1138]

come on, i need some help guyz!

 

[medic]

Look here for information:

http://support.microsoft.com/support/kb/articles/Q122/9/26.ASP

 

[LXi]

Did you install the 4.22 4-in-1s, and 4.03 AGP drivers?

 

[pX1138]

LXi> I cant even get into 2000. I just got the mobo today and can't get it into 2000.

CRV> So far I've tried several of the things outline in the link you gave, non have did jack. But I have two questions, in ont method it says

<< If you recently added new hardware, remove the new hardware or re-configure it so it does not conflict with the resources of any other installed controllers. >>


How would i &quot;re-configure&quot; my new hardware, thru the bios? what exactly could I do? I have disable all serial, USB and parallel ports, and set my PCI to 'NA' which i assume disables them. (all of that in effort to perhaps free up an IRQ that may be in conflict).

any other suggestions? what about the MBR, should i try something with it?

any suggestions would really help.

thanks for the help thus far,


pX1138

 

[medic]

I would try removing any extra cards except the video card

and set my PCI to 'NA' which i assume disables them
Are you talking about the bios choice for video? Usually AGP or PCI? I would leave that at AGP if your video card is an AGP card.

Has this dual boot of yours ever worked? Or only before the M.B. swap?
Did you use to get the Bootloader on startup?

 

[pX1138]

i meant in the &quot;PCI config&quot; part of the BIOS, you can manually set the IRQ, i had set them all to NA....

the dual boot I have running has worked great for around 6 monthes, I'm just using the bootloader that install with win2k. and like I said my win98 partition work great, im using it right now. i switched out mobos today, i had an old aopen ax6b.

as far as the bootloader goes, it works fine. the error is on up when win2k is almost all the way loaded, toward the end of the first 'color' screen upon bootup.

i guess i could switch back to my old mobo and see if it still works there but i am fairly sure it will (it did about 4 hours ago). im really getting frustrated here, ive tried booting up with hundreds of altered bios setting to no avail. tried the windows recovery thing, nothing. any other ideas? or an idea on what the problem is definitley related to? my guess right now is that my win2k was set up exclusively for my aopen board, and now with the asus its just screwing it up. damn this just sucks.


thanks for the help once again.

pX1138

 

[pX1138]

little bit of an update, i found this regarding the Stop Error I was getting:

<< Failed boot device. During I/O system initialization, the boot device driver might have failed to initialize the boot device (typically a hard disk). File system initialization might have failed because it did not recognize the data on the boot device.
Also, repartitioning the system partition or installing a new SCSI adapter or disk controller might induce this error. If this happens, the Boot.ini file must be edited >>


which resembles my problem. how would i need to change my boot.ini in this case? heres what mine says now:

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=&quot;Microsoft Windows 2000 Professional&quot; /fastdetect
C:\=&quot;WIN98SE&quot;

Anything wrong?

thanks again...



pX

 

[pX1138]

anymore ideas?

 

[pX1138]

im dying here!

 

[medic]

px1138
Do you have everything backed up?
I remember a few on this board who started changing things in Boot.ini and hosed the whole system.

Check here:
http://forums1.anandtech.com/arcmessageview.cfm?catid=27&amp;threadid=77133

 

[pX1138]

don't have jack backed up, but i guess I can sort of because I can still access all the files on my win2000 drive. man, this really sucks.

if I choose the &quot;install win2000&quot; option from when you boot off the CD would I be able to keep my setting and such, like when upgrading from 98?

pX

 

[medic]

Before you go much further try to backup important files.

 

[Dennis Travis]

pX1138

I had the exact same message when upgrading to an ASUS CUBX last week. What is going on is 2k is not recognising the ATA66 controler. Since the CUBX has a separate controler for ATA66 I plugged the hard drives into the BX ATA33 controler and booted into 2k and then installed the CMD ATA66 driver for the CUBX but with your board you just have the main HDD controlers built into the VIA chipset so I don't know what to tell you. I am sure ASUS gave you a CDROM with the p3v4x correct? If so boot into 98 and put in the ASUS CD and see if there is a Win 2k driver for the ATA66 Via IDE controler. If so put in the win 2k cd and do a new install [not the upgrade as that would zap your 98 install] and when it reboots to install and asks for you to specify any aditional HDD controlers hit S I think and point it to the driver on the ASUS CDROM for the VIA IDE controler and then do a repair instead of a reinstall. I hope this makes sense and works for you and that there is a driver there for 2k as if not I can see no other way but to reinstall 2k. I see no other way as right now you can't boot into 2k to install the new Via drivers!

Good luck.

 

[medic]

From Microsoft:

INACCESSIBLE_BOOT_DEVICE (0x7B)

During the initialization of the I/O system, the driver for the boot device may have failed to initialize the device that the system is attempting to boot from, or the file system that is supposed to read that device may have either failed its initialization or simply not recognized the data on the boot device as a file system structure. In the former case, the first argument is the address of a Unicode string data structure that is the ARC name of the device from which the boot was being attempted. In the latter case, the first argument is the address of the device object that could not be mounted.

If this is the initial setup of the system, this error may have occurred because the system was installed on an unsupported disk or SCSI controller. Note that some controllers are supported only by drivers that are in the Windows Driver Library (WDL), which requires the user to do a custom installation.

This error can also be caused by the installation of a new SCSI adapter or disk controller or by repartitioning the disk with the system partition. If this is the case, on x86 systems, the BOOT.INI file must be edited; on ARC systems, Setup must be run. For information on changing BOOT.INI, see the Windows NT Advanced Server &quot;Administrator's Guide.&quot;

 

[AndyHui]

Hmm...exact same thing happened to me when I switched from a P2L97 to the P3V4X. What I did was boot up off the Win2K CDROM, and got it to re-install. I didn't lose very much, just one or 2 settings, and Diskeeper. No data was lost, and I only had to re-install Diskeeper. Other than that it was fine, and it changed my system HAL from Standard to ACPI.