Results 1 to 10 of 21

Thread: ZCM 11.3.1 and BSOD (7B Inaccessible boot device)

Threaded View

  1. #1

    ZCM 11.3.1 and BSOD (7B Inaccessible boot device)

    Hi all,
    We have been struggling with seemingly random BSOD for many months across our laptop and desktop fleet. Different vendors, model, different model hard drives.
    Today we have finally been able to do something that has been reproducible, for probably the first time.
    (Thanks to Donald Jones, Great Basin College for the push in the right direction)

    Windows 7Pro SP1 (x86-64)
    Novell Client 2SP3IR8
    ZCM 11.3.1

    (Also, Mcafee Virusscan 8.8)

    On a clean HDD, we physically image (drive replicator) with our SOE (Sysprepped image, none of the above software pre-installed)
    At Windows "First Boot, OOBE", we install :
    -Machine specific drivers
    -Novell Client 2SP3IR8
    -iPrint 5.98
    -ZCM 11.3.1
    -Mcafee Virusscan 8.8
    as part of the OOBE.

    Machine completes build fine. We have had a few machines BSOD within hours. Others may take months of use.

    When a machine fails, it seems to be after a clean shutdown, at the next startup.
    At boot, the Windows Startup screen appears, but within a second or two we see a BSOD, with a 7B (Inaccessible boot device) error.

    BSOD Error details:
    (0xFFFFF880009A97E8, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

    If we load the SYSTEM registry hive of the device, and edit this key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4d36e967-e325-11ce-bfc1-08002be10318}
    Before: Lowerfilters: = zesdac
    After: Lowerfilters: =

    The machine will now boot OK.

    We then shutdown the device, and load the SYSTEM hive to check the key and it has been repopulated (self healed?) with:
    Lowerfilters: = zesdac

    However, we can now boot cycle the machine numerous times, and the machine boots fine, as normal.

    The c:\windows\system32\zesdac.sys file has these properties:

    File Description: Novell ZESM Device Access Control Driver
    Type: System File
    File Version:
    Product Name: Novell ZENWorks Endpoint Security
    Product Version:
    Copyright: Copyright (c) 2003-2013 Novell Inc
    Size: 31.2 KB
    Date Modified: 24/06/2014 12:58pm
    Language: English (United States)
    Original Filename: ZESDAC.SYS

    These TIDs don't relate to the 11.3.1 version we use, but started me looking..

    We have also checked things like 'force run bundles' that may push changes to the device, and have disabled the 'automatic install/launch' relationships.

    We will continue to investigate, but if anyone has any further ideas, I'd love to hear them.
    Last edited by mickers; 21-Aug-2014 at 11:52 PM.
    Michael Mollard
    Network Administrator, Moreton Bay College, Brisbane Australia

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts