Advertisements

Windows 2008 R2 BSOD error STOP: 0x0000006B

None of us like it when Windows servers fail and give you a nice BSOD, specially when the issue happens after they are patched.

I cannot state in strong enough terms to make sure YOU as an Admin of your environment controls/creates the process and procedures of patching.  Patching folks simply patch, their job is to pull the trigger.  Yes they do best effort to test, but it is never certain that production fully mimics the test environment.

Take a look at this article from an excellent engineer/blogger that I personally know who wrote some of his thoughts on patching.

Now lets fix this BSOD issue… 🙂

Environment:

  • Windows 2008 R2
  • XenApp 6.5
  • UPM 4.1
  • vSphere 4.0 <-  What the heck? I know, I know 😛

Issue:

You have a host that is running Windows Server 2008 R2.  You receive a Stop error message that resembles the following: STOP: 0x0000006B ( Parameter1, Parameter2, Parameter3, Parameter4)
PROCESS1_INITIALIZATION_FAILED Note The four parameters in the Stop error message may vary, depending on the configuration of the computer.

BSOD

Cause:

This issue occurs because the Bootcat.cache file located under %SystemRoot%\system32\codeintegrity is corrupted or because the size of the Bootcat.cache file is changed since the last successful start.

Solution:

  • Check out this MSFT support article, it is mentioned here to delete the Bootcat.cache file and reboot.  This did not work for me.
  • Copy the Bootcat.cache file from another system that is similar to yours (In my case a VM with the same level of virtual hardware), reboot, reinstall VMtools and you are in good shape.

Steps: If option 1 does not work

  • Copy Bootcat.cache file from your VM template
  • Create an ISO or put it in a USB stick.  You can create your ISO with a free tool like ImgBurn
  • Mount the ISO to your VM by clicking on the CD/DVD Drive (in this case VMware), and select “Connect to ISO image on local disk” then select the ISO containing the Bootcat.cache file

mount_iso

 

mount_boot_cache

  • Now reboot the VM and let the System Recovery Process start, select your desired language, then click on “Command Prompt”

system_recovery_reboot

recovery_options

  • Authenticate as one of your local Admin users

admin_log_in

  • Confirm you see the file on the ISO you mounted to your VM (In my case the E: drive)

bootcat_cache_on_iso

  • Now copy the bootcat.cache file form the mounted ISO to %SystemRoot%\system32\codeintegrity\ and verify the file is copied successfully

copy_bootcat_cache

  • Now reboot the VM… and welcome back Windows 🙂

welcome_back_windows

  • When you log back in, I notice some of my drivers were out of whack, make sure you take care of them, a VMTools reinstall did it for me.

post_fix_driver_issues

  • Once VMTools is reinstalled, reboot.
  • When the system is back up, verify your drivers are all fine, patch it, reboot and you are all set 🙂

device_manager_with_hidden

windows_update

 

  • Once the system is back up, just verify all your Citrix Services below.

Check the following services are set to auto and are started:
Citrix System Monitoring Agent Service
Citrix System Monitoring Agent Firebird service
Citrix CPU Rebalancing Service
Citrix CPU Rebalancing Service
XenApp Health Monitoring Service
XenApp XML Service
XenApp MFCOM Service
Citrix WMI Service
Citrix Independent Management Architecture and dependent services
Citrix Print Manager Service
Print Spooler Service
CitrixTools Cloning Service
Citrix Profile Management Service

Check your Citrix Profile Management Service Cache
C:\Program Files x86\Citrix\User Profile Manager\

Advertisements

About CyberRuiz
Highly motivated with over 12 years experience on Citrix/VMWare/Microsoft/technologies. Exceptional communication skills and team player. CCIA – Citrix Certified Integration Architect. CCEA – Citrix Certified Enterprise Administrator. VCP – VMWare Certified Professional in ESX 2.x, VI3, VI4 MCSE – Microsoft Certified Systems Engineer

4 Responses to Windows 2008 R2 BSOD error STOP: 0x0000006B

  1. Marco B. says:

    Hello Daniel,
    Thank you for sharing this information. It has also solved my problem.
    Regards,
    Marco B.

  2. John says:

    This worked beautifully!

  3. zain says:

    even after deleted the bootcache file the message still arrives what to do next i am stuck…

  4. Ally says:

    This saved my skin. Copied the bootcat.cache file from a second server (which was luckily another node in the same cluster).

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: