david1986
asked on
Windows 7 BSOD "Verification of a KnownDLL Failed." Hangs at ClassPNP.SYS in Safe Mode.
I'm receiving the following BSOD error:
STOP: C000021a {Fatal System Error}
The verification of a KnownDLL Failed. System process terminated unexpected with a status of 0xc000012f(0x0068b4e0 0x00000000)
The system has been shut down.
If I restart and try to boot into safe mode, the last file that loads prior to the blue screen of death is: "ClassPNP.SYS"
I have:
1) Unplugged ALL USB devices less the keyboard
2) Ran chkdsk
3) Tried Windows 7 built in start-up repair.
4) "Last Known Good Configuration"
5) "Disable driver signature enforcement"
6) sfc /scannow -- Unfortunately this will not run off the Windows 7 recovery environement. You must be booted into Windows to run this utillity from what I understand.
I'm not sure what happend prior to this error ocurring. (I.e. Windows Updates?)
No other new software has been installed. No other new hardware has been installed.
Obviously I can pull the drive and recover files and do a fresh install, but this is NOT a route I wish to proceed with unless absolutely critical!
No system restore -- It's an SSD hard drive and not enough space for it.
I do have an image that's about a month old that I could restore from if required. Again, I'd rather solve the issue than resort to this, if possible!
Any advice is much appreciated.
STOP: C000021a {Fatal System Error}
The verification of a KnownDLL Failed. System process terminated unexpected with a status of 0xc000012f(0x0068b4e0 0x00000000)
The system has been shut down.
If I restart and try to boot into safe mode, the last file that loads prior to the blue screen of death is: "ClassPNP.SYS"
I have:
1) Unplugged ALL USB devices less the keyboard
2) Ran chkdsk
3) Tried Windows 7 built in start-up repair.
4) "Last Known Good Configuration"
5) "Disable driver signature enforcement"
6) sfc /scannow -- Unfortunately this will not run off the Windows 7 recovery environement. You must be booted into Windows to run this utillity from what I understand.
I'm not sure what happend prior to this error ocurring. (I.e. Windows Updates?)
No other new software has been installed. No other new hardware has been installed.
Obviously I can pull the drive and recover files and do a fresh install, but this is NOT a route I wish to proceed with unless absolutely critical!
No system restore -- It's an SSD hard drive and not enough space for it.
I do have an image that's about a month old that I could restore from if required. Again, I'd rather solve the issue than resort to this, if possible!
Any advice is much appreciated.
It seems like the most likely problems are:
1) faulty or inoperable RAM
2) winlogon error
In the first case, you should try testing your RAM to see if there are any problems with it. Do this with MemTest (http://www.memtest86.com/ free for Windows machines; http://www.memtestosx.org/download/ under $2 for Mac machines). If you don't want to try that, you should switch out RAM sticks until you find the one that is causing the error.
In the second case, it could be a problem reading the memory at a certain location because of a corrupt operating system installation (including update installation). If this is the case, your best bet is to reinstall the operating system. Of course you'll want to back up all your files beforehand.
Please let me know if you require any clarification.
1) faulty or inoperable RAM
2) winlogon error
In the first case, you should try testing your RAM to see if there are any problems with it. Do this with MemTest (http://www.memtest86.com/ free for Windows machines; http://www.memtestosx.org/download/ under $2 for Mac machines). If you don't want to try that, you should switch out RAM sticks until you find the one that is causing the error.
In the second case, it could be a problem reading the memory at a certain location because of a corrupt operating system installation (including update installation). If this is the case, your best bet is to reinstall the operating system. Of course you'll want to back up all your files beforehand.
Please let me know if you require any clarification.
ASKER
Although BSOD is commonly caused by faulty RAM, this BSOD usually isn't. Just to be safe -- I'll check!
As stated in the original post, I prefer not to do a fresh install.
Any way to repair Windows 7, besides what I've already tried?
As stated in the original post, I prefer not to do a fresh install.
Any way to repair Windows 7, besides what I've already tried?
If this Blue Screen was caused by a Microsoft Update you have the right to a free support call from microsoft.
You may try repairing MBR(master boot record) which seems to have helped other people experiencing this similar issue.
In recorvery console write: bootsect /nt60 ALL
Insert the installation disc.
Restart your computer.
Click the Start button , click the arrow next to the Lock button , and then click Restart.
If prompted, press any key to start Windows from the installation disc. Note
If your computer is not configured to start from a CD or DVD, check the information that came with your computer. You may need to change your computer's BIOS settings. For more information, see BIOS: frequently asked questions.
Choose your language settings, and then click Next.
Click Repair your computer.
Select the operating system you want to repair, and then click Next.
On the System Recovery Options menu, click a tool to open it.
If your computer has preinstalled recovery options:
Remove all floppy disks, CDs, and DVDs from your computer, and then restart your computer.
Click the Start button , click the arrow next to the Lock button , and then click Restart.
Do one of the following:
If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer.
If your computer has more than one operating system, use the arrow keys to highlight the operating system you want to repair, and then press and hold F8.
On the Advanced Boot Options screen, use the arrow keys to highlight Repair your computer, and then press ENTER. (If Repair your computer is not listed as an option, then your computer does not include the System Recovery Options menu as a preinstalled recovery option.)
Select a keyboard layout, and then click Next.
Select a user name and enter the password, and then click OK.
On the System Recovery Options menu, click a tool to open it.
he Recovery Console in earlier versions of Windows was a limited console that only allowed you to use certain commands. It has been replaced by an actual command prompt. Advanced users can use the command prompt to perform recovery-related operations and also run other command line tools for diagnosing and troubleshooting problems. For more information about command line tools and commands, see Command-line reference for IT Pros ( "http://windows.microsoft.com/en-US/windows-vista/Command-line-reference-for-IT-Pros" )
You may try repairing MBR(master boot record) which seems to have helped other people experiencing this similar issue.
In recorvery console write: bootsect /nt60 ALL
Insert the installation disc.
Restart your computer.
Click the Start button , click the arrow next to the Lock button , and then click Restart.
If prompted, press any key to start Windows from the installation disc. Note
If your computer is not configured to start from a CD or DVD, check the information that came with your computer. You may need to change your computer's BIOS settings. For more information, see BIOS: frequently asked questions.
Choose your language settings, and then click Next.
Click Repair your computer.
Select the operating system you want to repair, and then click Next.
On the System Recovery Options menu, click a tool to open it.
If your computer has preinstalled recovery options:
Remove all floppy disks, CDs, and DVDs from your computer, and then restart your computer.
Click the Start button , click the arrow next to the Lock button , and then click Restart.
Do one of the following:
If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again by waiting until the Windows logon prompt appears, and then shutting down and restarting your computer.
If your computer has more than one operating system, use the arrow keys to highlight the operating system you want to repair, and then press and hold F8.
On the Advanced Boot Options screen, use the arrow keys to highlight Repair your computer, and then press ENTER. (If Repair your computer is not listed as an option, then your computer does not include the System Recovery Options menu as a preinstalled recovery option.)
Select a keyboard layout, and then click Next.
Select a user name and enter the password, and then click OK.
On the System Recovery Options menu, click a tool to open it.
he Recovery Console in earlier versions of Windows was a limited console that only allowed you to use certain commands. It has been replaced by an actual command prompt. Advanced users can use the command prompt to perform recovery-related operations and also run other command line tools for diagnosing and troubleshooting problems. For more information about command line tools and commands, see Command-line reference for IT Pros ( "http://windows.microsoft.com/en-US/windows-vista/Command-line-reference-for-IT-Pros" )
ASKER
As requested -- I tested the memory.
All is well!
What's next?
All is well!
What's next?
ASKER
Thanks Rosly777.
We'll try repairing the MBR. I thought of that but didn't think it was applicable since the MBR loads initially BEFORE Windows starts loading. (Right?)
If Windows failed to even start loading, I'd suspect the MBR, but since it starts, gets ALMOST finished, and fails, I don't suspect the MBR.
Is this thought process right?
Thanks for the help. Will report back in 5 minutes.
We'll try repairing the MBR. I thought of that but didn't think it was applicable since the MBR loads initially BEFORE Windows starts loading. (Right?)
If Windows failed to even start loading, I'd suspect the MBR, but since it starts, gets ALMOST finished, and fails, I don't suspect the MBR.
Is this thought process right?
Thanks for the help. Will report back in 5 minutes.
ASKER
I have tried the repairing the MBR and still same codes. I have found that in the Startup Repair/ Diagnostic and repair Detailes, it says in there that a root problems has been found "A patch is preventing the system from starting."
Hopefully this will help everyone out.
Hopefully this will help everyone out.
David if this is the case I would suggest contacting Microsoft as windows updates and patches receive a free support call
Here is a link to Microsoft's website discussing a similar issue and steps to remove the pending patch: http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/f0f4a1f6-31d1-4c80-a324-4c7fea6c0d05
ASKER
This is great advice! Will try this step:
"Step 2: Try to remove the pending update via Windows Recovery Environment (WIN RE) command prompt
a) Access advanced boot options menu by pressing F8 key when computer restarts>On the Advanced Boot Options screen >Select repair your computer option (As mentioned in the previous step)
b) Now select command prompt recovery tool
c) At the command prompt type Dism /online /get-packages and then press enter.
This will produce a list of installed updates and packages. They will look like this:
Package Identity: WUClient-SelfUpdate-Core-T
State: Installed
Release Type: Feature Pack
Install Time: 9/25/2009 12:02 AM
Find the most recent one and then make a note of the package name.
d) Then run the command: dism /online /remove-package /PackageName:WUClient-Self
Restart the computer and test to see if the issue persists"
Thanks for the helpful comment.
"Step 2: Try to remove the pending update via Windows Recovery Environment (WIN RE) command prompt
a) Access advanced boot options menu by pressing F8 key when computer restarts>On the Advanced Boot Options screen >Select repair your computer option (As mentioned in the previous step)
b) Now select command prompt recovery tool
c) At the command prompt type Dism /online /get-packages and then press enter.
This will produce a list of installed updates and packages. They will look like this:
Package Identity: WUClient-SelfUpdate-Core-T
State: Installed
Release Type: Feature Pack
Install Time: 9/25/2009 12:02 AM
Find the most recent one and then make a note of the package name.
d) Then run the command: dism /online /remove-package /PackageName:WUClient-Self
Restart the computer and test to see if the issue persists"
Thanks for the helpful comment.
ASKER
We have tried to uninstall the last windows update via the method above but we keep getting an errors on the commands that we use. We have typed in "dism /?" to see the list of commands that is able to be used and now it is prompting us for the file. We have not been able to figure out what the file name is due to the fact of not being able to bring up any kind of list as to what is installed.
If anyone has any ideas on what we are doing wrong, the help would be great. I think as soon as we can figure out how to get the list up, We will be able to get this thing up and running again.
Thanks ahead of time for your help.
If anyone has any ideas on what we are doing wrong, the help would be great. I think as soon as we can figure out how to get the list up, We will be able to get this thing up and running again.
Thanks ahead of time for your help.
ASKER
Also, I have called Microsoft and they were not able to figure it out.
ASKER
I think I've figured out the syntax for doing it offline.
Something like this:
dism /Images:C:/???? /get-packages
I'm just not sure where the WIM images are located. Any ideas guys?
Something like this:
dism /Images:C:/???? /get-packages
I'm just not sure where the WIM images are located. Any ideas guys?
ASKER
Using Microsoft's DART I was able to remove the bad hotfixes.
After doing so, windows boots fine. - However nothing else will load. I.e. Programs immediately crash upon opening. The system itself continues to run. (No BSOD's!)
I suspect that it's because prior to doing this, we contacted Microsoft support and they had us restore our registry hives to default.
I tried restoring these registry hives back to the originals, since they had us make a backup. After doing this, we now get a Windows Logon Initially has failed error upon boot. (Standard context window, not BSOD)
Pushing OKAY yields the same screen over and over...
The other tech that spoke with Microsoft said they had him do a few other things...but he can't remember what they were exactly. I'm thinking that if we reversed those too, it would solve the issue.
What do you think??
After doing so, windows boots fine. - However nothing else will load. I.e. Programs immediately crash upon opening. The system itself continues to run. (No BSOD's!)
I suspect that it's because prior to doing this, we contacted Microsoft support and they had us restore our registry hives to default.
I tried restoring these registry hives back to the originals, since they had us make a backup. After doing this, we now get a Windows Logon Initially has failed error upon boot. (Standard context window, not BSOD)
Pushing OKAY yields the same screen over and over...
The other tech that spoke with Microsoft said they had him do a few other things...but he can't remember what they were exactly. I'm thinking that if we reversed those too, it would solve the issue.
What do you think??
It is definitely worth trying. worst case scenario in the end is you recover what files you need and rebuild the machine.....
@david1986
The WIM files you asked about are Windows Image files. Microsoft uses them as a container for their setup installation in Windows 7 and 2008.
The WIM files you asked about are Windows Image files. Microsoft uses them as a container for their setup installation in Windows 7 and 2008.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sorry to hear that. Hope everything works all the better for you.
David, Bummer about the re-install but great finding on the DaRT 6.0 which is apparently part of the Microsoft Desktop Optomization Pack and appears not to be a free product, you can read more about it below
http://www.microsoft.com/windows/enterprise/products/mdop/dart.aspx
http://www.microsoft.com/windows/enterprise/products/mdop/default.aspx
http://www.microsoft.com/windows/enterprise/products/mdop/dart.aspx
http://www.microsoft.com/windows/enterprise/products/mdop/default.aspx
I don't know what day this started for you but I had two users with Windows 7 x86 come in and have the exact same error on their systems on 11/2. We didn't deploy any patches to those machine the day before so I'm not sure what triggered it. Same OS, different model computers, different department images. I had to re-image their systems as well, they had to get them back ASAP. I loaded an new hard drive and recovered their data. I tried to use the DSIM tools also but hard drive encryption prevented it from detecting the OS.
This was posted on 11/01 but sounds like there may have been a qwirk in MS Updates, but very coincidental since you did not deploy any patches I have not seen any reference info on this from Microsoft yet. It appears this was directly related to the patch
ASKER
Thanks again for everyones help.
After the fresh install of Windows 7, I reinstalled the same updates that had previously caused the issue -- this time all went well!
I'm still absolutely LIVID with Microsoft for wasting a good 10+ hrs after they suggested restoring the registry to defaults.
Had I gone with my original instinct (instead of trusting their judgement) we could have completely reversed the issue WITHOUT having to reinstall or re-image.
That original path being: Remove the updates using the command line OR (what I did) Microsoft DaRT recovery disc.
After the fresh install of Windows 7, I reinstalled the same updates that had previously caused the issue -- this time all went well!
I'm still absolutely LIVID with Microsoft for wasting a good 10+ hrs after they suggested restoring the registry to defaults.
Had I gone with my original instinct (instead of trusting their judgement) we could have completely reversed the issue WITHOUT having to reinstall or re-image.
That original path being: Remove the updates using the command line OR (what I did) Microsoft DaRT recovery disc.
A Dell Technician had me perform the following on an E6410 Latitude after booting the Win7 installation DVD and selecting repair with command prompt:
bootrec.exe /fixboot
Fixed the problem.
bootrec.exe /fixboot
Fixed the problem.
ASKER
http://www.google.com/#hl=en&expIds=17259,18168,24548,25638,26637,27059,27196,27284,27357&sugexp=ldymls&xhr=t&q=the+verification+of++a+known+DLL+failed+Windows+7+classpnp.sys&cp=62&pf=p&sclient=psy&aq=f&aqi=&aql=&oq=the+verification+of++a+known+DLL+failed+Windows+7+classpnp.sys&gs_rfai=&pbx=1&fp=8e8f35a77978fbf6