Windows 7 No Boot - STOP: 0x0000007B and CLASSPNP.SYS problem?
Hello helpers, I have a W7 Pro 64 machine (Dell). Two days ago, all programs became very sluggish/hung up, so I restarted in an attempt to set things right. Ever since then, Windows has not booted. It goes to the Windows Recovery, but it cannot locate the Windows OS to repair/recover. Viewing the Boot Log, it hangs on CLASSPNP.SYS. The BSOD it throws has the error message: STOP: 0x0000007B (0xFFFFF880009A9928, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000) These threads outline my exact problem (http://www.overclockingwiki.org/forums/showthread.php/6052-O-K-I-m-Stuck!! and http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/b950c21f-46f4-4011-99f6-00e9c2780170). This is apparently a semi-well known issue. I found one fix that seems to work for most, which entails copying the CLASSPNP.SYS file from another system and copying it to the crippled machine (while renaming the original CLASSPNP.SYS.OLD or something along those lines). I have done this, but to no avail. I have run all diagnostics on the drive, no errors. I've also tried changing from AHCI mode to ATA in CMOS, but again no results. Please help if you can, I have no idea what to try next besides a clean install and I really would rather avoid that.
July 9th, 2010 10:57pm

If you would have searched either the Microsoft website or the internet you would have discovered that the 0x0000007B is a very well know error for the system not being able to find the boot device. You are either missing a driver for your hard drive controller or it is corrupt. See info @ http://pcsupport.about.com/od/findbyerrormessage/a/stop0x0000007b.htm
Free Windows Admin Tool Kit Click here and download it now
July 9th, 2010 11:29pm

I did search, hence my linking of the MS forums lol... I've looked over that link you posted as well, and I have ruled out or tried each option (besides replacing the hd). I know the problem. I don't know the solution. I have also updated the BIOS, tried recovery with the W7 disc (failed), checked all physical connections, used an alternate CLASSPNP.SYS. I am in the process now of trying to update my HD firmware if it exists. If that doesn't work, I'm stumped. Rick do you know of any way to update the drive controller in the DOS environment?
July 10th, 2010 12:48am

I don't know of a way to update the driver in the DOS environment. If you look at the links for STOP: 0x0000007B @ http://search.microsoft.com/results.aspx?form=MSHOME&mkt=en-US&setlang=en-US&q=STOP%3a+0x0000007B you will see that it is almost exclusively a driver problem. I did note at one of your links you posted that one person found they had a virus that had corrupted some files causing the 0x0000007b error. There are offline scanners you can get. One is Vipre Rescue @ http://live.sunbeltsoftware.com/ I think the CLASSPNP.SYS is a Red Herring and should be ignored with the exception that it may have caught a virus.
Free Windows Admin Tool Kit Click here and download it now
July 10th, 2010 1:07am

Hello Oversight: This “STOP: 0x0000007B” message shows when there are Boot-Sector Viruses, Device Driver Issues, Hardware Issues and other issues. The situation you mentioned that in the Boot Log, it hangs on CLASSPNP.SYS. This Classpnp.sys is the driver for SCSI devices, due to the Windows cannot be booted, this problem may occur in scenarios as following: · The registry is corrupted. · A System file is missing or damaged. · A device driver file is missing or damaged. In this case, you need to do a Startup Repair and System Restore from DVD to fix this issue. Find how to run the startup repair tool by using Windows 7 installation disc: http://support.microsoft.com/kb/925810 You can also learn more details here: Error message when you start a Windows 7 or Windows Vista-based computer after you change the SATA mode of the boot drive: "STOP 0x0000007B INACCESSABLE_BOOT_DEVICE" Hope it can help you! Best regards, Miya Yao
July 13th, 2010 10:57am

Miya, I did a test restore from a known good backup to a different machine. This is a legitimate scenario, and fortunately, I tested before a failure occurred. It should absolutely be conceivable that customers might restore from a non-SATA machine to a SATA containing machine. This should not be a customer issue. Instead, it should be dealt with by the O/S (at an engineering level).
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2011 12:53pm

Miya, I did a test restore from a known good backup to a different machine. This is a legitimate scenario, and fortunately, I tested before a failure occurred. It should absolutely be conceivable that customers might restore from a non-SATA machine to a SATA containing machine. This should not be a customer issue. Instead, it should be dealt with by the O/S (at an engineering level). So, what did you discover. Your post is about as clear as mud. Restoring a back-up from a non-SATA machine to a SATA machine is not a common scenario because there is a high probability that the overall hardware would have changed significantly so that a clean re-install would be necessary. And where does the OP ever mention he is going from a non-SATA machine to a SATA machine?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 18th, 2011 1:42pm

You put this up twice but since it doesn't always work what else is there to do? especially for a laptop?
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2011 4:45pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics