Did anyone ever solve the "verification of a known dll failed" BSOD?
Hi experts!
For the third time this year we had windows update ruin a windows vista installation (3 different computers, Vista Business 32/64). The users chose "install updates and shutdown" and the next morning, the computer would run into a bluescreen telling "the verification of a known dll failed".
Safe mode, last known good, checkdisk - all in vain, we had to re-image these machines. After re-imaging, installing the same updates again always worked.
Has anyone here ever overcome this problem?
All I can google is http://blogs.technet.com/b/ben_parker/archive/2009/06/05/debugging-a-fatal-system-error-0xc000021a-status-system-process-terminated-with-verification-of-a-known-dll-failed-x64-0xc000021a-c000012f.aspx which does not offer a solution.
For the third time this year we had windows update ruin a windows vista installation (3 different computers, Vista Business 32/64). The users chose "install updates and shutdown" and the next morning, the computer would run into a bluescreen telling "the verification of a known dll failed".
Safe mode, last known good, checkdisk - all in vain, we had to re-image these machines. After re-imaging, installing the same updates again always worked.
Has anyone here ever overcome this problem?
All I can google is http://blogs.technet.com/b/ben_parker/archive/2009/06/05/debugging-a-fatal-system-error-0xc000021a-status-system-process-terminated-with-verification-of-a-known-dll-failed-x64-0xc000021a-c000012f.aspx which does not offer a solution.
ASKER
-There are no code numbers
-Event viewer is of no help, the system cannot boot, the bluescreen comes on each boot. Also, there will be no entries (to extract from offline access) because the bluescreen happens before the services start (including the event log service).
Your links only add one new option: the "rename pending.xml thing". I will try it next time, the system is already re-imaged. However I am quite sure this will not work because pending.xml is used during the windows update process - in our case, the windows update process ("configuring updates, stage 1 of 3...") is not reached. The BSOD happens very early after POST.
-Event viewer is of no help, the system cannot boot, the bluescreen comes on each boot. Also, there will be no entries (to extract from offline access) because the bluescreen happens before the services start (including the event log service).
Your links only add one new option: the "rename pending.xml thing". I will try it next time, the system is already re-imaged. However I am quite sure this will not work because pending.xml is used during the windows update process - in our case, the windows update process ("configuring updates, stage 1 of 3...") is not reached. The BSOD happens very early after POST.
McKnife--When you install a Windows Update, Windows should create a System Restore point. If this problem occurs again, try to run it from Safe Mode.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am closing this question as no progress was made. I will ask a related question today, if anyone is interested.
Perhaps of help
http://social.answers.microsoft.com/Forums/en/w7repair/thread/ef957d71-0e42-4bcf-9313-31c9509c8ae7
http://social.answers.microsoft.com/Forums/en-US/vistarepair/thread/08bc9992-05a5-45ab-9633-424e82967ca1