Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Win2k8 RTM (Non SP1)/Win2k8 R2 RTM/Win2k8 R2 SP1 server gets BSOD with 0x6b cod


  • Please log in to reply
1 reply to this topic

#1 laxmi261

laxmi261

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:11:04 PM

Posted 27 November 2013 - 06:01 AM

Hi All,

 

Here is a best solution for following very common problem in Win2k8 servers;

 

(RESOLVED)Win2k8 RTM (Non SP1)//Win2k8 R2 RTM / Win2k8 R2 SP1  server gets BSOD with 0x6b code.

 

Solution:

 

  1. Copy "Bootcat.cache" file from "C:\Windows\system32\CodeIntegrity" and "NTDLL.DLL" file from "System32" folder from a SIMILAR ( Win2k8 RTM (Non SP1) / Win2k8 R2 RTM / Win2k8 R2 SP1) working server and make a ISO or FLP image using any ISO / flp image creator software (like Magic ISO WWW.magiciso.com ).
  2. Mount the ISO/FLP image to the BSOD server.
  3. Reboot the server with Startup repair boot menu by pressing F8 at the startup.
  4. Go to CMD and restore the Bootcat.cache file from the CD/Floppy mounted to "%systemroot%\system32\CodeIntegrity" folder and NTDLL.DLL to "%systemroot%\system32\" folder. (Also, do not forget to keep a copy of the file some ware on the server, so that, it can be used next time the BSOD occurs if the server rebooted by any means).
  5. Reboot the server, press F8, and then select "Disable Driver Signature Enforcement" menu.
  6. Server will be up now.
  7. Upgrade the server to SP1 (if applicable). (After upgrading, once you reboot the server, you may get the BSOD again. Follow the same steps to bring back to normal. Once the SP1 upgrade process is over, issue will fix!.)
  8. Verify by rebooting the server.

 

Reason for this issue:

 

 

 

Ntdll.dll file under System32 folder is corrupt.

This file is used to create bootcat.cache file.

Bootcat.cache file creation mechanism failed. Once you delete the file and reboot, it should create it again automatically. But, in this case, it never creates the file. So, this concludes, some kernal files related to bootcat.cache file creation is damaged.


Edited by hamluis, 27 November 2013 - 08:17 AM.
Moved from Introductions to Win NT - Hamluis.


BC AdBot (Login to Remove)

 


#2 Sneakycyber

Sneakycyber

    Network Engineer


  • BC Advisor
  • 6,133 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Ohio
  • Local time:12:34 PM

Posted 04 January 2014 - 11:51 PM

Thanks for the tip! :thumbup2:


Chad Mockensturm 
Network Engineer
Certified CompTia Network +, A +




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users