Fatal error: Verification of knownDll failed.

Hi all,

Have an Advent laptop here, BSODing when booting with the error message above.

Cannot run in safe mode and any start up repair attempts have failed.

I have run disk checks both in the Windows start up tool and in Linux and they both say no problems but when I try a system restore it says there is one. Here is the .dmp file and the laptops specs.

I also ran sfc /scannow but everytime I do I get a message saying there is a repari waiting for me to restart the laptop and that's all I ever get.

The start up repair gives the information below.0

Sorry I couldn't display the error logs better but I cannot figure out how to read them.

Thanks a lot,
StubbyHS

Specs:
Windows 7 HE
4GB RAM
Celeron T3500
320GB HDD

Startup Repair log:

Event name:StartupRepairOffline
PS1 - 6.1.7600.16385
PS2 - 6.1.7600.16385
PS3 - unknown
PS4 - 21200327
PS5 - AutoFailover
PS6 - 2
PS7 - BadPatch

Thanks, doing that now. Just a quick note to say that my D:\Windows\System32\config\regback\default folder is on 782kB's, and \Sam and \Security are only 24.5kBs big.

stubbyhs said:

Thanks, doing that now. Just a quick note to say that my D:\Windows\System32\config\regback\default folder is on 782kB's, and \Sam and \Security are only 24.5kBs big.

You should not proceed, then. We'll need to get SFC /SCANNOW working. There are two files you will need to delete to get it working. I need to determine what two files those are. Bear with me while I do some research.

writhziden said:

The information you provided was rather vague. Please follow the https://www.sevenforums.com/crashes-d...tructions.html to provide us with more information. Thank you. :)

Sorry I forgot to mention that I can't run these tools as I cannot boot up. Is there anything I can do to the .dmp file to make it readable?

writhziden said:

If you are unable to boot into Windows and startup repair keeps saying it needs to be run, see Startup Repair Infinite Loop Recovery for a good method to resolve the issue.

No dice. But like I said, the file sizes weren't as the guide said they should be. ANy ideas?

stubbyhs said:

Sorry I forgot to mention that I can't run these tools as I cannot boot up. Is there anything I can do to the .dmp file to make it readable?

Yeah, I was a little confused until I read the post a third time and realized you were having boot issues rather than just BSOD issues. There isn't anything to do to get the .dmp files until we can get your system running again. See my above post to provide us with more information and also for further reading to possibly get the system file check working.

writhziden said:

How many times have you run a startup repair?

Have you tried the boot using Last Known Good Configuration option?

Mike's Technology and Finance Blog: How to Perform an Offline System Integrity Verification is also good further reading.

Yes run that as well.

Ehh 5 or 6? SHould I keep going?

I managed to get the dmp file copied onto a mem stick and have run the tool so the report is below, hope it helps!

I will read that article while you rack your brains:)

Thanks,
StubbyHS

Nah, the Startup Repair should complete within three times. More further reading: Startup Repair - Run 3 Separate Times

Your blue screen crash was caused by AVAST. When you get your computer running, uninstall AVAST using the avast! Uninstall Utility and replace with Microsoft Security Essentials - Free Antivirus for Windows to run with Windows firewall.

Also, you may have hard disk errors. Use Advanced Boot Options to select Repair Your Computer and get to the System Recovery Options. Then select the command prompt. Do the following:

chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:

.etc until you get the message that the volume could not be found. For any drives that do not give the message:
"Windows has checked the file system and found no problems"
run chkdsk again as above.

I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your laptop that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery).

Aha it's my friends laptop and I have it to fix it and remove AVAST as she doesn't like it and put on MSE.

The chkdsk is still running through D:, but it looks like it is doing something this time.

What does the /r command do and why did none of this work when I ran chkdsk on D: earlier?

Thanks a lot!