Sep 22, 2009. When installing Windows XP, on a Lenovo (IBM) M58p, type 7635-AE4, I get STOP error 0x0000007B. This is not related to a boot sector virus. I've tried it on a number of brand new PCs. I also tried. If you're getting a STOP error 0x7B during text-mode setup of XP, try replacing the ntdetect.com file with this one. If that doesn't fix it you can try changing the hard drive setting in BIOS or try integrating SATA drivers. Any feedback is more than welcome. You do not have the required permissions to view the. Possible solution for STOP: 0x0000007B (0xba4cb524, 0xc0000034, 0x00000000, 0x00000000) in WIn XP SP3. Windows XP IT Pro Windows XP Service Pack 3 (SP3). This is very helpful when you want to install an older operating system from a time period when SATA did not exist, and no one writes SATA drivers for that OS.
Hi, I received this same stop error recently because of CD driver issues. Nothing worked (normal, safe mode, LKGF). I finally resorted to running Windows repair, essentially reinstalling the OS. This is the second repair option, proceeding as if you're going to do a zero-based (reformat) installation, but at the selection screen for the partition where to install Windows, hit 'R.' This will reinstall Windows but won't delete any data or previously-installed programs. They'll be myriad patches and possibly a service pack to reinstall when you're done, but this worked for me.Good luck!
Kenny, here are my comments:You ask:?Is there anyway to determine (even approximately) the loading order of drivers??There are drivers and services. Up to a certain point, they might be the same for all installations, but after that it is different, depending on your configuration.?It seems that if I could determine the next driver that is going to be loaded after the last one is displayed in Safe mode, I would know where the problem is stemming from. Is that a reasonable assumption??The last driver on that list is not the last driver which was installed, but the driver which is going to be installed. This is to help you figure out what driver has a problem. The list stops at the faulty driver (service).To sort out the MBR problem, try to boot from other disk (other OS) and see if you can access this disk from there.
If you cannot, then MBR is affected. Maa tv serial pellante noorella panta. A good solution to fix it is not using fixmbr, or fixboot from RC, but trying to use the disk manufacture utilities (MaxBlast, SeaTools?).As you said, the second last solution (before reformatting) would be to repair XP and then update it. I think this is going to work, I used it many times.Good luck! HI,First of all, thanks to everyone who responded with your helpful suggestions. Having been working away at this problem for quite some time, I had already tried those approaches:- Chkdsk found 0 problems- Thorough inspection of the BIOS didn't show any problems- Hardware was fine, including testing with 100% new memory chips- Tried the hard disk in a similar PC (Dimension 8400) and it produced the same error-Thoroughly investigated the MS support sites, including TechNET.
What am I missing/doing wrong?XP dosn't support your approach by default.USB drivers are not loaded, hence the BSOD 0x7b. Change the drive load order.Dietmar described the behaviour and solution:There are two projectsTried 4 different versions of XP with the ngine guide, and re-did the files a couple times each, and I still got the 0x7B bsod after the first reboot. Also tried copying the 'XP embedded drivers' as per their forum post, and I still get the BSOD.Did a fresh install of XP and used USBoot on it, copied it to the drive, and it would give me a black screen after the boot select screen.Eff.EDIT Wierd! Tried adding different disks to the boot.ini file, incase it wasnt rdisk(0), which didnt work, but when I tried the original line again, it didnt BSOD. Updates to come! Edited June 14, 2009 by SpikedCola.
Try substituting the normal ntdetect.com by Dietmar's patched version. You can find it or.And just for you to be sure everything is OK, Dietmar's ntdetect.com MD5 is 42e5d3d11ef0d8ce52175727d581bc14I tried the ntdetect.com file, saved it with Tiny Hexer as the author said, checked the file size, and when I try to boot, I get 'NTDETECT failed'EDIT Renamed it from NTDETECT.COM to ntdetect.com and now it doesnt give the error, but still gives me the 0x7B bsod. Im trying to read through the 911cd.net thread but a lot of them speak in really broken English and it makes it really hard to understand. Edited June 14, 2009 by SpikedCola. I tried the ntdetect.com file, saved it with Tiny Hexer as the author said, checked the file size, and when I try to boot, I get 'NTDETECT failed'You may have better luck with the patcher:jaclazP.S.: Forget the above.This is the first report I ever saw about a Windows filesystem/app being CaSe SensItIvE.Are you sure of your last edited post?Have you tried the files I gave you a link previously?As far as I was aware, it didnt matter how it was named, thats why I named it NTDETECT.COM. In the first link you gave, the poster had a problem with the boot sector - I see the Windows XP loading screen & bar, so Im pretty sure the bootsector isnt my problem.In the second link you gave, the first link in your post (excluding the modified ntdetect one) links to the ngine.de forums - I have been doing lots of reading there but Ive decided to post here instead as there seems to be very little activity over there. The second link in your post is to the guide Ive been following this whole time.
The last link, ' Im reading through now. Im also going to give the patcher a shot. If you have any other ideas, Id love to hear 'em.
0x7b Xp Setup
Thanks!Well, NO.AFTER having solved the bootsector problem, he couldn't get it working by copying and pasting the engine.de settings, while the attached files made it working.In the same thread, OP had problems with SP3:It is very probable that you are using a somehow modified SOURCE.Use a 'pure' XP SP2 one.About FiLeNaMe BeInG CaSe SeNsItive, of course it is important on CD-ROM, but on it it should be UPPER CASE., on FAT16/FAT32/NTFS I can assure you that it is normally as well UPPER CASE.What are you using to create the.iso? With WHICH options? Well, NO.AFTER having solved the bootsector problem, he couldn't get it working by copying and pasting the engine.de settings, while the attached files made it working.In the same thread, OP had problems with SP3:It is very probable that you are using a somehow modified SOURCE.Use a 'pure' XP SP2 one.About FiLeNaMe BeInG CaSe SeNsItive, of course it is important on CD-ROM, but on it it should be UPPER CASE., on FAT16/FAT32/NTFS I can assure you that it is normally as well UPPER CASE.What are you using to create the.iso? With WHICH options? The SSD has been physically disconnected.
There isnt any actual problem with it, just a design flaw, so I decided not to use it. And I am installing off a USB CD-ROM (well, a SATA DVD-Rom with a SATA - USB adapter).Insert the SSD again.Install XP to the SSD card.Install UsbBootWatcherClone the XP SSD card to USB drive.Disconnect the SSD card.Boot from USB. Report the boot behaviour.You may require the edited ntdetect.com or XP Embedded usbhubb.sys.I don't trust ISO editing tools at Windows installation CD.Extract files, build a new CD, read the files: cdimage, mkisofs, ImgBurnUse a decent writer, good quality media and burn at appropiate speed.This is not always the lowest speed.Edited. The SSD has been physically disconnected.
Stop 0x7b Installing Xp
There isnt any actual problem with it, just a design flaw, so I decided not to use it. And I am installing off a USB CD-ROM (well, a SATA DVD-Rom with a SATA - USB adapter).Insert the SSD again.Install XP to the SSD card.Install UsbBootWatcherClone the XP SSD card to USB drive.Disconnect the SSD card.Boot from USB. Report the boot behaviour.You may require the edited ntdetect.com or XP Embedded usbhubb.sys.I don't trust ISO editing tools at Windows installation CD.Extract files, build a new CD, read the files: cdimage, mkisofs, ImgBurnUse a decent writer, good quality media and burn at appropiate speed.This is not always the lowest speed.Edited.
C:UsersJ SkobaDesktopusbxpinit.cmd D:windowssystem32prepare XP files after first installation rebootThe system cannot find the path specified.0 file(s) copied.The operation completed successfully.sp driver cab: D:windowsDriver CacheI386sp3.cabexpand usbohci.sysMicrosoft (R) File Expansion Utility Version 6.1.7100.0Copyright (c) Microsoft Corporation. All rights reserved.d:windowssystem32.driver cachei386driver.cab: No files matching 'usbohci.sys'.Microsoft (R) File Expansion Utility Version 6.1.7100.0Copyright (c) Microsoft Corporation. All rights reserved.Adding D:windowssystem32driversusbohci.sys to Extraction QueueExpanding Files.Expanding Files Complete.expand intelide.sysMicrosoft (R) File Expansion Utility Version 6.1.7100.0Copyright (c) Microsoft Corporation. All rights reserved.d:windowssystem32.driver cachei386driver.cab: No files matching 'intelide.sys'.Microsoft (R) File Expansion Utility Version 6.1.7100.0Copyright (c) Microsoft Corporation.
0x7b Installing Windows Xp
All rights reserved.Adding D:windowssystem32driversintelide.sys to Extraction QueueExpanding Files.Expanding Files Complete.The system cannot find the path specified.D:Windowssystem32 is the path to the usb drive that I am trying to install onto (I connected the drive to my computer after the first restart and ran your script).EDIT I tried doing an install with a nonpatched SP2 build and it bsod's on the laptop w/ usb drive, and installs fine in VMWare. Did the usb patch to it and I get the same thing.
However the SP3 builds dont give me the bsod on the laptop (but then files are different). Edited June 16, 2009 by SpikedCola.