CheckEmoji Community · the emoji forum
🏠 Home 🆕 What's new ❓ Unanswered 🔥 Popular 📡 RSS Members 👥 0 online log in · register
Home › IT › IT Support › Blue screen - stop ERROR 0 x0000007b

Blue screen - stop ERROR 0 x0000007b

Started by Patrick Kern3 · · 👁 2 views · 11 replies

📡 Subscribe to replies

Participants Patrick Kern3Zachary Barrett4Noah Miller6Benjamin King2velvetbison58Larry Ortiz5
Patrick Kern3 Patrick Kern3 NewcomerOP
5 messages
joined Jul 2010
#1 ·
I need some help here. I'm working on a Dell Latitude running Windows XP Professional SP2, and every time I boot up, I get this message:

Check for viruses on your computer..... Run CHKDSK /F to check hard drive for corruption...
stop ERROR 0 x0000007b (0xF78AA528, 0xc0000034, 0x00000000, 0x00000000)

How am I supposed to run chkdsk? I can't get to the command prompt at all. Even when I pop in a Windows CD, it won't take me there. I've successfully used chkdsk to fix issues on this exact machine before, but now it’s just refusing to cooperate.

Thanks.
Zachary Barrett4 Zachary Barrett4 Member
22 messages
joined Jul 2010
#2 ·
You might want to try booting up from a Windows CD
and then, once you're in that repair console, you should find that chkdsk is available for you to run.
Patrick Kern3 Patrick Kern3 NewcomerOP
5 messages
joined Jul 2010
#3 ·
I booted up my Windows CD, and when it gave me the option to run a repair (R), I hit that key only to be slapped in the face with this message:

Setup did not find any hard disk drives installed in your computer. .....

?? Now what? How am I supposed to move forward with this??
Noah Miller6 Noah Miller6 Active Member
56 messages
joined Jul 2010
#4 ·
Are we talking about a SATA drive here?
If so, jump into the BIOS and look for the IDE Configuration setting.
Set that to Compatible.
If that isn't the case, you should see an option to disable SATA Native Control—go ahead and switch that off.
Patrick Kern3 Patrick Kern3 NewcomerOP
5 messages
joined Jul 2010
#5 ·
The drive is SATA, but I couldn't find an IDE configuration setting in the BIOS. I read somewhere yesterday that I should disable the AHCI Configuration—is that even the same thing?—so I went ahead and did that, and now I've managed to boot into Windows. Is this going to be okay?
Benjamin King2 Benjamin King2 Active Member
138 messages
joined Apr 2007
#6 ·
It might work... you could try running chkdsk in the console now, though honestly, I wouldn't hold my breath—it probably won't do much at this stage. Your other move is to attempt an XP repair—the steps for that are laid out right here -> http://pcsupport.about.com/od/operat...txprepair1.htm
Patrick Kern3 Patrick Kern3 NewcomerOP
5 messages
joined Jul 2010
#7 ·
Benjamin King2 said:It might work... you could try running chkdsk in the console now, though honestly, I wouldn't hold my breath—it probably won't do much at this stage. Your other move is to attempt an XP repair—the steps for that are laid out right here -> http://pcsupport.about.com/od/operat...txprepair1.htm

I ran the Repair. Everything seems to be working fine for now.

Thanks for the help!
Noah Miller6 Noah Miller6 Active Member
56 messages
joined Jul 2010
#8 ·
Well, have fun dealing with those windows now...
Patrick Kern3 Patrick Kern3 NewcomerOP
5 messages
joined Jul 2010
#9 ·
Noah Miller6 said:Well, have fun dealing with those windows now...

The kids are already playing games on it. Thanks again.
velvetbison58 velvetbison58 Newcomer
3 messages
joined Oct 2015
#10 ·
I'm running into the exact same headache with my PC
any other ideas?
Larry Ortiz5 Larry Ortiz5 Regular
710 messages
joined May 2020
#11 ·
velvetbison58 said:I'm running into the exact same headache with my PC
any other ideas?

So, I guess none of the suggestions the guys posted earlier actually worked?
velvetbison58 velvetbison58 Newcomer
3 messages
joined Oct 2015
#12 ·
Larry Ortiz5 said:So, I guess none of the suggestions the guys posted earlier actually worked?

I actually stumbled onto what was causing this mess last night—it turns out that article I was looking at was talking about "stop ERROR 0 x0000007b "
The thing is, the article claims my boot volume got corrupted, which isn't exactly what ended up being the case in the end
Anyway, here are the commands I used in cmd.
I just opened a cmd window from my USB Stich, and honestly, a little bonus for me was learning how to do this along the way 🙂
Command 1# – Diskpart

Command 2# – List volume

Command 3# – EXIT Command 4
Command 4# – D: (You’re Windows Drive Letter)

Command 5# – Bootrec /fixmbr

Command 6# – Bootrec /fixboot

Command 7# – Chkdsk /f (Try chkdsk /f /r If “Chkdsk /f” command Wont Works)

Command 8# – Y

Once the "chkdsk" command finished, I just rebooted my computer and—boom—problem solved. 🙂

Just one more thing... does anyone actually know why all those steps even work?

You must log in or register to reply here.

Log in Register

🔗 Similar threads