kdcom.dll is corrupt after 2/14 update

[AWS]

I'm running Windows 7 professional. After the automatic update that was installed on 2/14, I started to bluescreen, particularly when waking up from hibernation. The crash report indicates that kdcom.dll is corrupt.I tried some system-restores which failed, so I formatted my C: drive and did a fresh install of Windows 7. Everything was fine until 133 updates were installed, then the same crashes started again. I plan and re-reinstalling windows 7 and turning off automatic

updates as there seems to be an issue with the latest one. My computer is home-built, I7 990extreme chip, Asus MB, and a Nvidia GTX560 GPU.The crash/recovery report contained this:Problem signature:

  Problem Event Name:                        BlueScreen

  OS Version:                                          6.1.7600.2.0.0.256.48

  Locale ID:                                             1033

 

Additional information about the problem:

  BCCode:                                               a

  BCP1:                                                    00000001000000DC

  BCP2:                                                    0000000000000002

  BCP3:                                                    0000000000000001

  BCP4:                                                    FFFFF80002EA2265

  OS Version:                                          6_1_7600

  Service Pack:                                       0_0

  Product:                                               256_1

Startup Repair diagnosis and repair log---------------------------Last successful boot time: ?2/?21/?2013 11:52:50 AM (GMT)Number of repair attempts: 1Session details---------------------------System Disk = DeviceHarddisk0Windows directory = C:WindowsAutoChk Run = 0Number of root causes = 1Test Performed: ---------------------------Name: Check for updatesResult: Completed successfully. Error code =  0x0Time taken = 0 msTest Performed: ---------------------------Name: System disk testResult: Completed successfully. Error code =  0x0Time taken = 15 msTest Performed: ---------------------------Name: Disk failure diagnosisResult: Completed successfully. Error code =  0x0Time taken = 110 msTest Performed: ---------------------------Name: Disk metadata testResult: Completed successfully. Error code =  0x0Time taken = 15 msTest Performed: ---------------------------Name: Target OS testResult: Completed successfully. Error code =  0x0Time taken = 141 msTest Performed: ---------------------------Name: Volume content checkResult: Completed successfully. Error code =  0x0Time taken = 140 msTest Performed: ---------------------------Name: Boot manager diagnosisResult: Completed successfully. Error code =  0x0Time taken = 0 msTest Performed: ---------------------------Name: System boot log diagnosisResult: Completed successfully. Error code =  0x0Time taken = 0 msTest Performed: ---------------------------Name: Event log diagnosisResult: Completed successfully. Error code =  0x0Time taken = 499 msTest Performed: ---------------------------Name: Internal state checkResult: Completed successfully. Error code =  0x0Time taken = 16 msTest Performed: ---------------------------Name: Boot status testResult: Completed successfully. Error code =  0x0Time taken = 15 msTest Performed: ---------------------------Name: Setup state checkResult: Completed successfully. Error code =  0x0Time taken = 344 msTest Performed: ---------------------------Name: Registry hives testResult: Completed successfully. Error code =  0x0Time taken = 2028 msTest Performed: ---------------------------Name: Windows boot log diagnosisResult: Completed successfully. Error code =  0x0Time taken = 15 msRoot cause found: ---------------------------Boot critical file c:windowssystem32kdcom.dll is corrupt.Repair action: File repairResult: Failed. Error code =  0x490Time taken = 3651 msRepair action: System RestoreResult: Failed. Error code =  0x1fTime taken = 270272 msRepair action: System files integrity check and repairResult: Failed. Error code =  0x3Time taken = 0 ms------------------------------------------------------

 

View this thread