Systems Deployment Question

Driver causes BSOD on system install - K2000 scripted install

01/25/2016 1201 views

I am deploying default Windows 7 x64 enterprise to new hardware we recently bought.
It is an HP EliteDesk 705 G2 Mini and I am able to deploy drivers to the system when Windows is being installed.

Now the problem we have is that the system crashed with BSOD on a particular driver that is necessary.
If I install Windows i have 4 unknown devices that need a driver, I am able to deploy this trough Kace in the K2000 share but than I get a BSOD.

So installed Windows without the driver that is causing the BSOD, this works but still there is 1 unknown device. If i manually search in the folder that i also added in the K2000 share before the unknown device is recognized but it needs a reboot. After I reboot there is no BSOD but it is the same folder with the same content I added in the K2000 share before.

I don't know how I can solve this issue because it causes problems BSOD but is still needed for the system and doesn't make errors with manual install.
0 Comments   [ + ] Show comments


All Answers


troubleshooting drivers conflict can be really tedious. What is happening most probably is that your device matches more than one driver the same hardware device and one of them is not good for some reason (wrong platform, wrong architecture...etc etc)

In this case your deployed OS works even without that particular drivers so, to ease the resolution of the issue and give you a quick fix, I'd recommend to deploy the missing driver with a post installation action.

Post installation actions are able to handle reboots as well.
 Kind regards,
Marco - StockTrader 

Answered 01/25/2016 by: StockTrader
Red Belt

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ