• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

help me troubleshoot a STOP message

QueBert

QueBert

Lifer
trying to do a repair install of XP Pro, having problems, it would sit @ 33 minutes remaining durring the hardware installing portion. Tried everything, so I went out and bought a new MB + CPU. Got them home, put them in. Booted, and after the XP install starts, when it gets to the "setup is staring" after the first set of drivers install. It sits there, then I get a BSOD with 0x0000007b (0xf7cae524

googled, said it was a HD problem. So I ran spinrite, the drive didn't have any issues. For good measure I ran memtest and the memory is fine. the bios is detecting both HD's fine. But unless I unplug the master (XP is on the slave) the system won't even try to boot. I managed to get it back to where it was yesterday, where the setup is installing, but it will still stop @ 34 minutes. there are no USB devices, and the only card in the system is the video (Radeon 9800) I've tried 3 MB's, and 2 CPU's. This is really confusing the hell out of me. I hope somebody has some idea for me? ugh this sucks 🙂

thanks in advance
 
Are you hitting F6 during the very start of text mode setup then providing mass storage drivers via diskette when prompted to 'S'pecify?

Stop 7b during setup = wrong mass storage driver or hardware error. No other options.

Stop 7b during a repair = one of the above or possibly a filter driver trying to load that is either missing or no longer applies. There are several other things as well but this is the most likely. The troubleshooting tree for this forks pretty wide pretty fast. One way to tell for absolutely sure is do a new parallel install. If it works then your driver and hardware are fine and you need to get that filter driver uninstalled.
 
some advanced goo for ya. stuff the MS setup team might be able to walk you through but you'll have to pay for the call...

If you are getting stuck in gui mode setup and need to get a filter driver removed (if you have to ask what a filter driver is this won't do you much good) do a shift-f10 to pop a command prompt and run regedit.

uber advanced kung fu, only seen it work about 50/50 in specific circumstances:
Do a new install to same folder (not a repair). Let setup finish text mode then finish hardware detection in gui mode. When it comes to the first input prompt past hardware detection, shift-f10 out, bring up regedit and manually knock yourself out of gui mode setup (there is a kb out there somewhere for reg hacking a machine out of mini setup after running sysprep...use that). After the registry change, close regedit and wait a few seconds then cold boot. You will have replaced the hardware portions of your registry and left everything else intact.

edit http://support.microsoft.com/kb/287506/en-us


getting out of a stop 7b reboot loop during a failed inplace upgrade is a bitch and if this stuff sounds way out there you might need to call support or settle on a new (non formatting!) install to retrieve your old data.

I'm really hoping my first post about using F6 is all you need 😛 good luck.
 
just put a 40 gig drive in, unplugged both others. got the same BSOD. this is before the setup reboots, it's the first DOS looking portion. I am very confused now. just popped in a different video card because I am out of ideas. I can't imagine 3 bad MB's and 2 bad CPU's. it has to be something.
 
Originally posted by: Smilin
some advanced goo for ya. stuff the MS setup team might be able to walk you through but you'll have to pay for the call...

If you are getting stuck in gui mode setup and need to get a filter driver removed (if you have to ask what a filter driver is this won't do you much good) do a shift-f10 to pop a command prompt and run regedit.

uber advanced kung fu, only seen it work about 50/50 in specific circumstances:
Do a new install to same folder (not a repair). Let setup finish text mode then finish hardware detection in gui mode. When it comes to the first input prompt past hardware detection, shift-f10 out, bring up regedit and manually knock yourself out of gui mode setup (there is a kb out there somewhere for reg hacking a machine out of mini setup after running sysprep...use that). After the registry change, close regedit and wait a few seconds then cold boot. You will have replaced the hardware portions of your registry and left everything else intact.

getting out of a stop 7b reboot loop during a failed inplace upgrade is a bitch and if this stuff sounds way out there you might need to call support or settle on a new (non formatting!) install to retrieve your old data.

I'm really hoping my first post about using F6 is all you need 😛 good luck.
Click to expand...

about to try the f6 thing, after trying a new HD that never had XP on it, i figured it can't be a HD issue, and hardware I went threw a box full, 2 video cards, a 2 k7 MB's, 1 a64 MB and 4 different sticks of memory. Thanks for the advice I hope it works. if it does you will hear from me 😀
 
you might be on to something with that f6 thing, not sure why but always when I tried to do upgrade installs it would tell me XP detected a mass storage device that might need drivers. and there is nothing on the PC besides 2 HD's and a burner. I think I got that message the other day before I tried the repair install 🙁
any ideas there??
 
What type of hard drives are they sata? ide?

Where did you get your windows cd? Is it legit? a copy?

How old is your cd drive?



@Smilin
Now that's some advanced sh!t!!!!
 
IDE, DVD drive is umm less then a year old. yes on the legit windows, not that there couldn't be something messed up with the CD, I've never used it.
 
condensed version of what I've tried in the past 2 days *still no luck*

a 2500+ XP cpu on 2 different MB's
a Sempron 3300+ on 1 mb
4 sticks of memory, 2 pc3200 and 2 2600
2 different sets of ide cables (4 cables)
3 HD's
2 optical drives
2 video cards
2 copies of xp.

I put the XP cd in, it starts to boot, I get the first text portion of the install, when it gets to setup is starting, it sits there for a minute or 2 and I get the BSOD I mentioned eairler. which google says points to a bad HD or hardware. Now, I've tested everything I could imagine, with the exception of a different PSU *any chance there??* 2 of the HD's never had windows on them. I am beyond confused. I appericate the few people who helped me already, but I'm still in need of some serious ideas!
 
Your power supply would have to be defective or really weak to not be able to power that system. What are all the components you are running in it? Does your motherboard have an additional power connector on it?
 
Originally posted by: ivwshane
Your power supply would have to be defective or really weak to not be able to power that system. What are all the components you are running in it? Does your motherboard have an additional power connector on it?
Click to expand...

right now it's barebones. I have a GF4 MX, which I know works because I pulled it out of another box. Aside from that, no pci cards, no usb devices. I just called the store I bought it at (PC Club) and their tech told me as long as the MB is posting it's good, and the CPU is good. His logic is if it's bad, you won't get a VGA signal hahah. At this point I know it has to be the MB or the CPU, there's no other explination. He wanted me to try more ide cables and more optical drives before I bring it in. So to humor myself I'm trying a few more. it's hopeless, getting this current setup to work right now.

about the additional connector, you mean that 4 pin ATX one? yes, and I have it hooked up. It's an Nforce3 250 MB, nothing that new or that fancy
 
Did you do a reset defaults in your BIOS, to make sure you weren't overclocking or anything? I know on my Abit-AV8, it had a factory default of 204mHz on the memory which would blue screen on my W2K installations. So when I ever do a default or fail-safe on my board I have to take down the memory speed.

What was the purpose behind doing a repair install of XP?
 
Originally posted by: TGS
Did you do a reset defaults in your BIOS, to make sure you weren't overclocking or anything? I know on my Abit-AV8, it had a factory default of 204mHz on the memory which would blue screen on my W2K installations. So when I ever do a default or fail-safe on my board I have to take down the memory speed.

What was the purpose behind doing a repair install of XP?
Click to expand...


it's not my box, it's my GF's, she has issues playing on pogo on her system, she is like a pogo addict. I've had success with repair installs in the past fixing little issues, so I tried it. Now, I'm at the point of trying to do a clean install on a unused HD with zero luck. Hopefully I can get the PC store to exchange my stuff, apparently they think it's either something I did, or a peice of hardware. idiots 🙂
 
Originally posted by: TGS
Did you do a reset defaults in your BIOS, to make sure you weren't overclocking or anything? I know on my Abit-AV8, it had a factory default of 204mHz on the memory which would blue screen on my W2K installations. So when I ever do a default or fail-safe on my board I have to take down the memory speed.

What was the purpose behind doing a repair install of XP?
Click to expand...

changed the memory speed in the bios from 200 to 166, it got past the BSOD point, I dunno if it's going to actually install or not, but it's doing something new now. hummm the memory I tested is pc3200 so it should run at 200mhz with no issues. Well, this is better then nothing. Thanks for the idea!
 
The problem was caused by swapping your motherboard out from under the OS.

NTLDR loads boot-start drivers, such as the IDE driver, before the OS starts. The OS then starts and uses that driver to get access to the disk.

Your original mobo had a chipset that used driver A. Your new mobo has a chipset that doesn't use that driver. So the OS starts and can't get access to the disk drive.

Either put your old mobo back in, or move your drive temporarily to a mobo that uses the chipset from the old mobo and install the drivers for the new mobo's chipset then move the drive to the new mobo.

If you're doing an install, you'll need to use the F6 trick that has been mentioned.
 
Originally posted by: NogginBoink
The problem was caused by swapping your motherboard out from under the OS.

NTLDR loads boot-start drivers, such as the IDE driver, before the OS starts. The OS then starts and uses that driver to get access to the disk.

Your original mobo had a chipset that used driver A. Your new mobo has a chipset that doesn't use that driver. So the OS starts and can't get access to the disk drive.

Either put your old mobo back in, or move your drive temporarily to a mobo that uses the chipset from the old mobo and install the drivers for the new mobo's chipset then move the drive to the new mobo.

If you're doing an install, you'll need to use the F6 trick that has been mentioned.
Click to expand...

I'm not sure if that's exactly what it is, lowering the memory speed got it to get past the first BDOS, I still get one though just after the 1st reboot where the xp screen comes up. I'm trying a clean install on another HD to see if your idea is right.
 
Your new board may have more aggresive timings on the memory, hence the need to drop the speed. Double check those settings in the BIOS before setting it back to 200. You should be able to try another repair install, which prior to that point should let you do the F6 process to load the drivers.
 
Originally posted by: TGS
Your new board may have more aggresive timings on the memory, hence the need to drop the speed. Double check those settings in the BIOS before setting it back to 200. You should be able to try another repair install, which prior to that point should let you do the F6 process to load the drivers.
Click to expand...

it's a very entry level board, I don't think I saw any memory settings besides a slight voltage tweak and the speed. the f6 thing, that will work for sata drives and such, but can I do anything about the ide? I'm sure the BSOD stop is due to a driver, not anything with the HD itself.
 
You should still need a chipset driver, or try to rollback to the CD supplied generic drivers through a repair. You still shouldn't have to do a complete reinstall unless there was some logical corruption on your OS files.

As for the memory, I would double check the voltage settings if there are no other options present.
 
TGS, Smilin & ivwshane thanks for the ideas. I finally got it to work by using some of y'alls tips and deleting and copying a file in system recovery console. system just booted up with the memory set @ 200mhz, all is well. thanks again
 
sweet!

do the following now that you are running:
1. install recovery console from you xp cd.. <cdromletter>:\i386\winnt32 /cmdcons
2. Run a system state backup to a file anywhere.
3. Turn system restore on if it is not already.


 
I wanted to add this for anyone getting 7Bs from a new drive. I recently purchased a newer 3Gb SATA drive. When I plugged it in, after the windows bootscreen it would bluescreen with a 7B error. I had to put a jumper in it to knock it down to 150MB/s operation. My Abit AV8 is an older board and does not support the faster speeds. So if anyone is moving to or adding a new SATA drive, keep in mind the fastest supported SATA speed for your board.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top