0

I recently got a 0xc000007b error whenever I tried to run some application software. I found that CHKDSK for C drive might be a solution. When I tried to do it from C drive properties, it said the drive was in use and asked to schedule CHKDSK at the next reboot. I clicked OK.

When I restart, I experience a BSOD. I waited for 10 minutes but still nothing happens. So I forced a shutdown (laptop) and again booted up the computer and got a BSOD for just 5 or 10 seconds and system boots and works with no problem.

I repeated all these steps four or five times and yet with the same results.

  1. Is there any other way other than CHKDSK to solve the 0xc000007b error?
  2. If not, why is CHKDSK not working at boot up? Can I force CHKDSK on drive C: to perform while the system is on?

Platform: Windows 7 64-bit.

Improve this question
9
  • Do you have a second computer? If you have remove the drive from the first computer and checkdisk it in an other computer. (Make sure that that other computer is up to date with all updates. - Just in case there is a virus somewhere. )
    – Hennes
    Commented Jun 16, 2012 at 12:48
  • hold up... "then BSOD for just 5 or 10 seconds and system boots" do you mean that a BSOD comes up, and stays on the screen for 5 to 10 seconds, and then the computer continues to boot normally? Or that you get a BSOD that stays on the screen for a few seconds and then the computer RESTARTS and functions normally? Because if it doesn't restart after the BSOD... if the BSOD just appears for a few seconds and then goes away, that's more than likely an infection... not an error.
    – Bon Gart
    Commented Jun 16, 2012 at 13:02
  • @Bon-Gart how do you find whether 'the computer Restarts after 5 or 10 seconds of BSOD' or not? because BSOD appears as soon as the dos screen-from where you get into safe mode. If you mean whether the dos screen appears again after BSOD, its not.
    – pras92
    Commented Jun 16, 2012 at 13:06
  • @BonGart Yeah weird, could be a threatening splash screen
    – WikiWitz
    Commented Jun 16, 2012 at 13:09
  • because a BSOD is a show stopper. It's not a passing notification. When your system gets to the point where Windows is killing everything that is going on and replacing it with a Blue Screen notification of what error has occurred and a message that it is dumping the contents of your memory to a file for analysis... it is not going to THEN continue to function normally. Not without restarting
    – Bon Gart
    Commented Jun 16, 2012 at 13:09

4 Answers 4

Reset to default
1

For the header question, simply issue chkdsk and checking will be scheduled to run on reboot.

In this paricular scenario, the reason chkdsk can't do its job is during the bootstrap process, before Windows is fully operational, it has to load drivers first. A bad driver can cause BSOD, so Windows loading will halt and chkdsk will not run.

You should boot into safe mode and open Device Manager, disable each suspect device one at a time and then follow that with a reboot until the BSOD is gone. But this is a pedestrian solution. The problem is printed at the BSOD output. Gather the information printed on the screen and search the Internet for the solution to your BSOD.

Try this solution for the 0xc000007b error: 0xc000007B Error - The Application Failed To Initialize Properly

See if that stops the BSOD. But as per the Wikipedia article Blue Screen of Death and personal experience, BSOD is hardware or driver related.

Improve this answer
7
  • But, on scheduling on reboot, BSOD happens. since BSOD happens only while chkdsk is scheduled on re-boot, i have to come to conclusion that chkdsk itself causes BSOD, in which case i cannot succesfully carry out chkdsk by scheduling it on reboot. Oh yeah i forgot safe mode. i'll try that and reply
    – pras92
    Commented Jun 16, 2012 at 12:56
  • @BonGart sorry i was wrong, after BSOD system restarts and functions normally
    – pras92
    Commented Jun 16, 2012 at 13:27
  • Not going to schedule a chkdsk anymore. not even once. even for testing. its really a pain in the a**. chkdsk is the sole reason for BSOD. So now, BSOD is not my problem. Only 0xc000007b error. I have to figure out a way other than chkdsk to eliminate this error. I hope there is an alternative. BTW, the link you provided for this purpose is not a solution to me.
    – pras92
    Commented Jun 16, 2012 at 16:47
  • Ah i forgot to add this, even safe mode not works (due to BSOD) when chkdsk is scheduled. I also tried windows diagnostic repair tool during boot up. that too didn't help.
    – pras92
    Commented Jun 16, 2012 at 17:01
  • I don't know how but the 0xc000007B Error doesn't happen anymore. I didn't do anything specifically to eliminate this. Just did reboot a few times because of BSOD. i think my problem is solved, at least temporarily.
    – pras92
    Commented Jun 17, 2012 at 13:12
0

If for whatever reason you cannot schedule CHKDSK just insert a windows install disk, and run it from there. (repair -> command prompt)

Improve this answer
0

Reboot PC and use key F8, It'll give you a advanced boot options, selelect there Repair your computer, after it boots it'll show a menu, there select command prompt. As command appears you can run chkdsk from there on disk c:

Improve this answer
1
  • I just tried this and chkdsk still aborts with an error message saying the drive is write protected.
    – jadkins4
    Commented Jan 2, 2015 at 19:00
-1

At this point, you will have to boot into a Windows DVD, and you can run CHKDSK from there, but then you also need to remove the CHKDSK entry in your registry so it doesn't attempt to run again after you reboot... HKLM/Software/Microsoft/Windows/CurrentControlSet/RunOnce...

Improve this answer
1
  • This doesn't solve the author's question. The author didn't want to run CHKDSK so why exactly are you telling him to run CHKDSK besides he already FIXED the problem.
    – Ramhound
    Commented Oct 12, 2012 at 19:13

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .