Sysprep BSOD before Capture

I have been working on this issue for a few days and would welcome any advice!!!

I am sysprepping a custom image to capture to WDS. I have set this image up several times even on different machines but 2 issues are occurring: 1. It blue screens every time when shutting down after running sysprep (with generalize, and oobe set). 

2. Sometimes if I force it off and run capture image it will detect the hard drive, but will not go past 1 percent progress.

I ran bluescreen viewer and I see ntoskrnl.exe as the cause but am not sure what this refers to.


June 18th, 2015 10:39am

Are any dump files created?
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2015 10:44am

Are any dump files created?
Yes I have it. I don't see a way to attach it to a post, but I will try to get it shared via a link.
June 18th, 2015 10:55am

MiniDump
Free Windows Admin Tool Kit Click here and download it now
June 18th, 2015 11:00am

Added the link above thank you
June 18th, 2015 11:02am

Hi PaulRJUSD,

The issue is caused by the Usbhub3, it is a new hub driver, in the USB driver stack for 3.0 devices. Please unplug all the USB devices when you try to sysprep and reinstall the USB driver from the device manager to have a check.

Here is the analysis result for reference:

 *******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe00096989800, fffff80032320930, ffffe0009c49a3e0}

Probably caused by : UsbHub3.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe00096989800, Physical Device Object of the stack
Arg3: fffff80032320930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe0009c49a3e0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: ffffe00095bb0b20

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53897630

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80158c5e000 UsbHub3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

DPC_STACK_BASE:  FFFFF80032327FB0

STACK_TEXT: 
fffff800`323208f8 fffff800`30879c1e : 00000000`0000009f 00000000`00000003 ffffe000`96989800 fffff800`32320930 : nt!KeBugCheckEx
fffff800`32320900 fffff800`30879b3e : ffffe000`9b8642d0 00000000`ffffffff ffffe000`9b864310 fffff800`306da240 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`32320960 fffff800`306d6810 : 00000000`00000000 fffff800`32320ab0 ffffe000`9b864308 fffff800`00000002 : nt!PopIrpWatchdog+0x32
fffff800`323209b0 fffff800`307d4aea : fffff800`30963180 fffff800`30963180 fffff800`309caa00 ffffe000`9cda87c0 : nt!KiRetireDpcList+0x4f0
fffff800`32320c60 00000000`00000000 : fffff800`32321000 fffff800`3231b000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.3.9600.17195

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_UsbHub3.sys

BUCKET_ID:  0x9F_3_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_image_usbhub3.sys

FAILURE_ID_HASH:  {58bbe6fe-0b43-accc-1beb-340d4227ae9c}

Followup: MachineOwner
---------

0: kd> lmvm UsbHub3
start             end                 module name
fffff801`58c5e000 fffff801`58cd6000   UsbHub3    (pdb symbols)          c:\symbols\usbhub3.pdb\02ED5A8F3C1D43DAA08EE4177AD660242\usbhub3.pdb
    Loaded symbol image file: UsbHub3.sys
    Mapped memory image file: c:\symbols\UsbHub3.sys\5389763078000\UsbHub3.sys
    Image path: \SystemRoot\System32\drivers\UsbHub3.sys
    Image name: UsbHub3.sys
    Timestamp:        Sat May 31 14:26:56 2014 (53897630)
    CheckSum:         0007B1F0
    ImageSize:        00078000
    File version:     6.3.9600.17195
    Product version:  6.3.9600.17195
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft Windows Operating System
    InternalName:     usbhub3.sys
    OriginalFilename: usbhub3.sys
    ProductVersion:   6.3.9600.17195
    FileVersion:      6.3.9600.17195 (winblue_gdr.140530-1506)
    FileDescription:  USB3 HUB Driver
    LegalCopyright:   Microsoft Corporation. All rights reserved.

Best regards

Free Windows Admin Tool Kit Click here and download it now
June 19th, 2015 2:26am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics