Xp bsod 7b install

Meanwhile, the engineering side was creating a Dell Resource CD that included the SATA drivers plus a way to use the Resource CD to build a drivers diskette for loading them if the operating system was reinstalled. Unfortunately, the diskette builder and also the SATA drivers file on the support page required a diskette drive to be used.

That probably was reasonable since Windows XP requires the diskette drive to load drivers at the F6 prompt during installation. Unfortunately no one seems to have told that to the marketing folks who were making the configuration choices. With regard to the stop codes there are plenty of references on the net, especially on the Microsoft support page to investigate these codes.

I'm sure it is viewed as a duplication of effort. I'm sure that your guess about the being too old to worry about is close to the truth. Once Dell stops production on a given model there is little concern about providing support to keep it up to date. They're just too busy making the new machines which is where the money is.

The problem with this is it would require WAY too much effort to fulfill your order - look up your Service Tag, determine the drivers needed, slipstream the drivers, then ship the custom CD. The issue is not because your system is so old - this issue can still be seen with Windows 7 on new machines if the controller is not recognized.

I do, however, completely agree with finding stuff on Dell's website Browse Community. Windows General. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Last reply by psyop87 Solved. I reset the BIOS to factory default settings. Windows XP setup begins copying files, then starts it's process of installing Windows. Thank you for any help you can give me.

All forum topics Previous Topic Next Topic. XP will not open in any safe mode. It just restarts over and over until I stop it. I conclude this tells a knowledgeable person what is wrong but I don't know what it is or how to fix it. I consider myself an intermediate level person; I am comfortable with some things and others I am not. I am reluctant to make settings that I don't know what the results will be. I don't experiment. Until this, my Toshiba L laptop about a year old worked okay; I think it has a virus as a "news 11 window" kept popping up in IE.

I ran the Windows scan and it didn't find anything. I was trying to run a Norton software check which is supposed to run in the safe mode and that is when this happened. I may have inadvertantly done something incorrect; I don't know what.

Is this enough information for someone to help me fix this problem or do I need to take it to someone smarter than I am? Once the menu appears select "Last Known Good Configuration". For a little while, I have been using wimb's latest tools to create universal XP image, and then boot them from a USB flash disk.

As explained here , this has been working very well for me, till I tried to boot on a fussy Dell laptop which gave me the usual BSOD 7B. This is where I decided tro try the USBoot package for the first time And it worked flawlessly on the same Dell laptop. For some time I've been trying to understand what USBoot does so well, but it turns out to be way beyond my limited understanding.

Out of curiousity it would be nice to know if the above procedure also fixes the problem for some of you if not for all hardware, at least on some So I started investigating a bit more But I couldn't see the laptop's internal HDD. And for a good reason: USBoot doesn't even try to install iastor. But the high success rate that everyone is having with this package seems to be convicing evidence that iastor. Nevertheless, upon closer inspection, the driver was showing as not properly working exclamation mark in device manager But if I manually updated the driver and pointed to iastor.

That was really strange, given that everything related to iastor. So I dug a bit deeper. Same for a few other devices. I am pretty convinced there is a good reason, but then can someone try to explain why?

It is pure speculation, but is it possible that DriveGuard is just a bit more clever, and prevents any BSOD when non-critical drivers are missing? This would seem like a very future proof solution, as the whole thing is garanteed to work, even on very new hardware, for which XP drivers may not even exist This also seem like a very desirable feature, as the IMG can be copied from device to device without worrying at all. I don't quite understand why, but it is explained in this tutorial that installing dummydisk.

How does it play a role in pre-recognising or not the devices? Unfortunately I have tried installing dummydisk. I've been a bit long but hopefully this long tale will help a few people who have problems, and give great ideas to other people who know how to implement stuff.

Posted 21 March - PM Three things: good news! Posted 21 March - PM dummydisk. Some SATA controllers only. All hardware use cases may get different results. And BIOS may be importand too. Which hardware do you use? Yes, some Dell are famous for strange USB behaviour.

That's a special case. Another thing to keep in mind is that iaStor seems to be a very common driver for Dell and HP computers. Posted 22 March - AM 1. Hell yeah, I couldn't agree more. I've spent so much time on it, I would have commited suicide if I hadn't cracked it.

Usbootwatcher is already installed and configured by Wimb's tools, what more do you have in mind? As far as USB services are concerned, Wimb's tools used to configure a few registry keys differently compared to USBoot see here , but now Wimb has changed it and it's all configured in the same way.

But there may be something that you simply missed or overwrite or whatever given the great number of tests you made You make a good point here. Given the huge number of trials and combinations I have tried, it was likely I got something wrong. But I've just tried again, the procedure I'm following is well known and relatively idiot-proof I believe. One thing I should mention is that I haven't tried in a "regular" XP, I mean, properly installed on a physical drive.

Almost certainly that would work. But when I install dummy. Anyone can confirm? Posted 22 March - AM This may be the main reason: one fixed disk is required at system.

Help, a Dell and USB booting. A 0x7B is not thrown for a reason like "iaStor is referenced in the Registry, but not loaded Not loaded, do you mean, e. I haven't tried it yet, but I would expect only 2 copies. This is exactly what UsbBootWatcher does, doesn't it?

Posted 22 March - AM Just for the record, there is alredy one report that installing DriveGuard increases significantly the chances of booting: strange, but you are correct After installing the ubdrvgd. For that reason, DriveGuard isn't entirely working: at each and every boot it complains about an "invalid license", and removable storage still appears as removable not as fixed, which is supposed to be DriveGuard's effect, presumably when properly activated.

Nevertheless, it must be doing a little something, which improves the bootability. Posted 22 March - PM That is also my understanding. If you are not booting from the internal HDD, you do not need the driver for the storage adapter for the internal HDD, as the following tried to explain: If you are booting from a file-backed disk whose backing disk is USB storage, then iaStor. I disagree. What was on the black screen, anything? Did you notice if the video mode switched?

It doesn't reduce any chances of anything. Not loaded, do you mean, e. It can be missing from that directory or from your entire image and it still won't have anything to do with your ability to successfully boot from USB.

That certainly seems intuitive. I think you're mixing things up a bit. I don't think the two should be mushed together, as they can be discussed independently of one another. Read again cdob's message Assumption: Windows dosn't detect a single fixed hard disk at boot. Posted 22 March - PM You're preaching to the converted This has also been my understanding from day one. Nevertheless, if you r ead wim'b tutorial in details, here is what you can find: I don't know Windows 7's requirements.

They're wrong or I'm wrong. Because that mixes up disks and volumes. You could potentially have a volume without any fixed disks. There aren't any disks, fixed, removable, none! BartPE from a CD can be the same! The volume on the CD is found. Read again cdob's message See the explanation above. STOP 0x7B cares about the boot volume , not fixed disks.

It doesn't. Well maybe we can figure out what's going on, there. As you may have guessed, all this matter is bordering or a touch beyond my understanding.

Pardon me if I'm a bit thick sometimes, but I like to think naive questions are sometimes very useful to make some progress.