Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
Windows 7 No Boot - STOP: 0x0000007B and CLASSPNP.SYS problem?

Answered Windows 7 No Boot - STOP: 0x0000007B and CLASSPNP.SYS problem?

  • Friday, July 09, 2010 7:57 PM
     
     
    Sign In to Vote
    0

    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.

    • Edited by Oversight Friday, July 09, 2010 8:00 PM TItle too long
    •  
     

All Replies

  • Friday, July 09, 2010 8:29 PM
     
     
    Sign In to Vote
    0

    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

     
  • Friday, July 09, 2010 9:48 PM
     
     
    Sign In to Vote
    0

    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?

     

     
  • Friday, July 09, 2010 10:07 PM
     
     
    Sign In to Vote
    0

    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.

     
  • Tuesday, July 13, 2010 7:57 AM
    Moderator
     
     Answered
    Sign In to Vote
    1

    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

     
  • Friday, March 18, 2011 1:17 PM
     
     
    Sign In to Vote
    0

    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).

     
  • Friday, March 18, 2011 2:07 PM
     
     
    Sign In to Vote
    0

    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. ”
     
  • Wednesday, June 29, 2011 8:32 PM
     
     
    Sign In to Vote
    0
    You put this up twice but since it doesn't always work what else is there to do? especially for a laptop?
    • Proposed As Answer by HugoCore Monday, December 26, 2011 6:57 PM
    • Unproposed As Answer by HugoCore Monday, December 26, 2011 6:57 PM
    •  
     
  • Monday, December 26, 2011 7:11 PM
     
     Proposed
    Sign In to Vote
    4

    I had also Windows 7 with 0x0000007B blue screen while loading Windows 7.

    It's turn out that the BIOS had been change to another disk mode, IDE, ex-raid. For now I wanted IDE, to be simple.

    Here's what works with me:

    In the BIOS, i went change the SATA to IDE mode (NOT RAID, NOT AHCI)

    1.Boot Win7 DVD

    2.Choose the Language Selection.

    3.Choose Repair.

    4.On the recovery tools choose the Command Line Console

    5.Type:regedit <ENTER>

    7.Highlight HKEY_LOCAL_MACHINE

    8.File > Load Hive

    9.Select < windows partition with problem > \Windows\System32\config\system (Backup this first, it's advised)

    10.Regedit will ask for a Key name: Name it something like "temp"

    11.Located HKEY_LOCAL_MACHINE/temp/Select/Current

    12.Searched for every key containing the value “SCSI Miniport” where the "Start" value was a "3" and changed the "Start" value to a "0". (F3 to search next result).

    13.Highlight "temp"

    14.File > Unload Hive

    15.Restart

    16.Enter in Win7 :)


    Based on: http://www.askvg.com/how-to-change-sata-hard-disk-mode-from-ide-to-ahci-raid-in-bios-after-installing-windows/

     

    Core
    • Edited by HugoCore Thursday, December 29, 2011 7:54 PM Missing introduction.
    • Proposed As Answer by mback2k Sunday, October 28, 2012 11:17 AM
    •  
     
  • Monday, December 26, 2011 8:02 PM
     
     Proposed
    Sign In to Vote
    0

    Here's what works with me:

    In the BIOS, i have SATA with IDE mode (NOT RAID, NOT AHCI)

     

    1.Boot Win7 DVD

    2.Choose the Language Selection.

    3.Choose Repair.

    4.On the recovery tools choose the Command Line Console

    5.Type:regedit <ENTER>

    7.Highlight HKEY_LOCAL_MACHINE

    8.File > Load Hive

    9.Select < windows partition with problem > \Windows\System32\config\system (Backup this first, it's advised)

    10.Regedit will ask for a Key name: Name it something like "temp"

    11.Located HKEY_LOCAL_MACHINE/temp/Select/Current

    12.Searched for every key containing the value “SCSI Miniport” where the "Start" value was a "3" and changed the "Start" value to a "0". (F3 to search next result).

    13.Highlight "temp"

    14.File > Unload Hive

    15.Restart

    16.Enter in Win7 :)


    Based on: http://www.askvg.com/how-to-change-sata-hard-disk-mode-from-ide-to-ahci-raid-in-bios-after-installing-windows/

     

    Core


    HugoCore,

    What does your post have to do with the original post?  The original post is asking about the 0c7B error.  Your information has no relationship to a 0x7B error.

    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. ”
     
  • Thursday, December 29, 2011 7:58 PM
     
     Proposed
    Sign In to Vote
    0

    Rick Dee,

    I have changed the post. I was also having 0x7B problem. It's turns out that the reason was, changing the disk mode in BIOS create this error.

    Hope this help's some one.

    Ps. Once again, 7B error Based on: http://www.askvg.com/how-to-change-sata-hard-disk-mode-from-ide-to-ahci-raid-in-bios-after-installing-windows/

    Best Regards

    Core
    • Proposed As Answer by RTKIII Thursday, April 25, 2013 5:16 PM
    •  
     
  • Monday, July 16, 2012 9:36 AM
     
     
    Sign In to Vote
    0

    well ive been seareching and searching for answers. HugoCore your fix was the one i needed. I tried registry tricks. but to no avail. This one worked perfect! thx

     
  • Wednesday, February 20, 2013 12:19 AM
     
     
    Sign In to Vote
    0

    Hi

    I just had this problem on my dell and reading the posts decided to try something different. I disabled all my drives bar my original boot drive- I had 2 windows 7 partitions and both showing this issue and 3 drives. 

    I disabled my RAID array tried a boot -failed and then re-enabled my RAID array and the system managed to boot fine.


    • Edited by spud Wednesday, February 20, 2013 12:20 AM
    •  
     
  • Friday, March 01, 2013 6:49 PM
     
     
    Sign In to Vote
    0

    Hi Hugo!

    Thank you, you saved my day! This absolutly works. And sorry RickDee, but this has to do with the problem.

    I had a mainboard crash and bought a new mainboard. I just changed the mainboard and kept all the rest (CPU, RAM, HDD etc.). My WinXP in my first partition booted fine, but needed some time to reinstall all the drivers. But my Win7 on the second partition always crashed with this BSOD. But thanks to the help of Hugo, my Win7 started fine and now everything is perfect again!

    Regards,
    red


    • Edited by der_red Friday, March 01, 2013 6:49 PM
    •  
     
  • Wednesday, March 06, 2013 8:57 PM
     
     
    Sign In to Vote
    0

    I have put this reply here because it is the most recent thread discussing this problem I can find, I have posted this reponse elsewhere.

    I have been reading other threads to try and fix this and was not looking foward to rebuilding PC but I got lucky. Suggest you try this for yourselves as it worked for me.

    • Reboot in Safe Mode with Command Prompt
    • When the boot script freezes at "CLASSPNP.SYS" line hit <ctrl><break>
    • When I tried this it killed the frozen command line session and then Windows went on to reboot in safe mode
    • I then restarted in normal mode and hey presto no more problems
    • Not yet anyway

    What a surprise that an old MSDOS keyboard command seems to be able, at last in my case, to fix what appears to be a significant Windows problem for so many...

    Makes you think

    Hope this saves a few people from having to do major reinstall work or hardware fixes

     
  • Thursday, April 25, 2013 5:15 PM
     
     
    Sign In to Vote
    0

    Hugo's suggestion worked for me as well.  I did not mess with the BIOS but booted to WIN7CD and then ran through his instructions.  Win7 booted and re installed all the devices upon login..THANK YOU!!!!!

    I had exhausted all other normal options and I was like 'Might as well try this."  WORKED!!!!

    thank you!

     
  • Friday, April 26, 2013 7:22 PM
     
     
    Sign In to Vote
    0

    Hugo's method worked!

    thanks