Partilhar via

KB981833 - STOP: 0x0000006B on Dell systems

  • Artigo

A very interesting case I worked on this week brought us on a new possible cause for blue-screens with STOP 0x6B, and I am now sharing this valuable information now :)

Symptom:

Your Windows 7 Dell Latitude E6510 systems are running in STOP 0x6B, although KB981833 is already installed.

Even if you delete the C:\Windows\system32\CodeIntegrity\bootcat.cache fie, the crashes persist.

 

Cause:

We found out that this is the result of some specific installation routines of an audio driver update with other system update components (not yet identified which exactly).

If a pack of several patches is installed, including Device IDT_92HDXXX-HD-AUDIO_A17_R278544.exe driver, the bootcat.cache might get corrupted (~11KB is size) and the systems run in STOP 0x6B.

If the pack is installed without the above mentioned driver, and the driver is installed only in the end, the system can be restarted successfully and the bootcat.cache file is updated accordingly.

 

Hint:

Should the system not boot after deleting the bootcat.cache file, try to copy the bootcat.cache file from an older backup image of the system. This might bring the system up.

 

If this article has helped, please add a comment.

 

Oni Sandru
Platforms Core Team

Comments

  • Anonymous
    December 04, 2010
    Dear Oni Sandru, I deleted the bootcat.cache file, and my Compaq CQ71 still refuses to boot. I tried using the bootcat.cache from a back-up, unsuccessfully. Can you explain how to install the KB981833 hotfix using only the commandprompt? Thank you in advance!

  • Anonymous
    March 17, 2012
    I have windows 7 home prem, sp1, the problem stated when i change my virtual memory from system managed to custom and change the cache from 6 gig(physical memore) to 12 gig and it all started with the virtual mem change. I have removed bootcat.cache with no success. i have restore the file from anothe machine and it works temporarily.  Virt/mem/cache is now back to system managed and still have problems rebooting

  • Anonymous
    July 16, 2012
    The comment has been removed