BSOD after running Sysprep

Hello eightforums!

I am having an issue with a Dell Venu 11 Pro tablet and I have battled with this for a few days now. I am trying to get sysprep to work, and I finally got it to successfully run yesterday after much battling with it. Many Appex application uninstalls and registry edits later, I got it to successfully run.

Though, after it runs, next restart the tablet will BSOD with a DRIVER_POWER_STATE_FAILURE error. After installing the Windows Debugger, I got far enough to figure out that it is telling me that it is some driver issue with usbccgp.sys, but after reading some other threads here, I understand that this is not the true driver that is the issue, but what driver is reporting to the OS. However, I lack the knowledge of how to actually figure out what actual underlining driver is throwing the issue.

Any help you could provide me would be greatly appreciated, TYIA!

I have attached the dmp file below.

View attachment 65120

EDIT: I went and pulled 4 more dump files off the tablet, they are older tho View attachment 65135

EDIT 2: dmp file with the power cord disconnected (still same bug code DRIVER_POWER_STATE_FAILURE) View attachment 65136

Hi addyftw,

Welcome to the 8forums.

The usbccgp.sys driver is a driver from windows, this driver is for the connections (usb ports), this could mean 1 of the ports is giving problems.
This could also mean that there is another 3rd party driver causing the issue, usually when a windows driver is blamed a 3rd party driver is actually causing the problem.

From how I understand the Dell Venu 11 Pro, everything other than the: Video Card, Memory, CPU and Motherboard, are considered a USB device.

The touch screen, WiFi card, and the mobile wireless card, are all considered USB devices.

(I am not sure about the SSD, if it is considered a USB device or not)

Additionally, when these BSOD occur, there is nothing plugged into the 1 x USB 3.0 port and there is the power cord plugged into the 1 x USB OTG port.

Do you have a bluescreen when connected to power?

It is always connected to the power supply, which is connected to the USB OTG port.

EDIT: I will go ahead and try to rerun sysprep without the power cord plugged in and respond back.

EDIT 2: Still got BSOD, will add new dmp file to OP

What registry edits did you make exactly?
Did you follow any kind of a tutorial for these edits?

I think that some of those registry edits are causing the problem, the dump file are blaming the following drivers:
Driver Reference Table - usbccgp.sys
Driver Reference Table - USBHUB3.sys

The registry edits I made are the standard sysprep work around registry edits:

HKEY_LOCAL_MACHINE\SYSTEM\Setup\SysprepStatus "GenerationState" set to 7 (7 means the system can be syspreped) as this key sets itself to 3 after a sysprep attempt.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform "SkipRearm" set to 1, sysprep will not run at all if it is not set to 1 (meaning for Windows to not rearm aka burn a volume license key, as that key is to be used up when you deploy the image to another device, which is why after you run Sysprep this is automatically reset to 0)

I already have talked to Dell's licensing department and they have OKed me doing this, since we have 1000 of these tablets are are acting as a 3ed party OEM, besides the fact when looking at the total ream count left on the current tablet [I cant remember the command offhand], we have over 2000 rearms left.

Neither of these two registry edits should affect any drivers.

Have you tried disabling power management on the USB chips/hubs/devices via Device Manager? It almost seems to me like something is being disabled for power savings during the generalization stage and not re-enabled after reboot.

How are you deploying the images to the machines? I wonder if you’re using MDT if you might have better results exporting the driver files from a working OEM system into the Deployment Share and having MDT explicitly inject those drivers during deployment.

Lastly, I’d wonder about compatibility of the touchscreen driver. If you uninstall the touchscreen driver prior to Sysprep and run through OOBE with a keyboard and mouse, do you get the BSOD?

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet

WinOutreach2 said:

Have you tried disabling power management on the USB chips/hubs/devices via Device Manager? It almost seems to me like something is being disabled for power savings during the generalization stage and not re-enabled after reboot.

Click to expand...

Will try this now and edit this reply with result.

WinOutreach2 said:

How are you deploying the images to the machines? I wonder if you’re using MDT if you might have better results exporting the driver files from a working OEM system into the Deployment Share and having MDT explicitly inject those drivers during deployment.

Click to expand...

I am using WDK, at this point I am just trying to get the device to successfully sysprep so that I can create an image (already have the capture image and I have gotten everything to work thus far, up until the step of actually capturing the image of the OS due to the requirement of the device being syspreped)

WinOutreach2 said:

Lastly, I’d wonder about compatibility of the touchscreen driver. If you uninstall the touchscreen driver prior to Sysprep and run through OOBE with a keyboard and mouse, do you get the BSOD?

Click to expand...

I got a fresh device from my warehouse manager, that was manually set-up out of the box without any driver updates. It is just showing as a generic PnP Monitor and generic HID Keyboard with separate generic HID Mouse, no specific touchscreen driver.

Something else to consider might be specifying PersistAllDeviceInstalls in your answer file to avoid drivers being reset by generalization. Of course this makes the image hardware specific, but from the sound of your description, it is intended to be hardware specific (if you’re even creating an image vs. Syspreping each machine individually).

Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet