I've never used Sysprep myself only read a little when I created a Unattended setup so I've had a little play and a bit more of a read.
About the drivers
and the info I gave previously.
I came to the conclusion that using Sysprep with Generalize will uninstall the driver
but not remove the driver files. The next time that image is booted you will see a mini setup and part of that will display "Configuring Device Drivers" or something like that and during this stage (specialize pass) any previously installed 3rd-Party drivers will be installed. Now if that doesn't make much sense I found another thread that seems to confirm this but explains it differently (maybe better) - Deployment: sysprep and answer files
Using PersistAllDeviceInstalls I think keeps the driver installed so during the mini setup it probably skips the "Configuring Device Drivers" stage but would cause errors if installed to a system with different hardware. I have not tried this yet so this is only a guess. Your video driver
Now with your video driver and considering the above I would try installing Windows then your video driver. Next open Device Manager select your Display Adaptor and search automatically for a updated driver.
If Windows chooses a different driver then I would think this is your problem. During the "Configuring Device Drivers" stage it would be choosing the driver it thinks is best. Let us know what happens and maybe we can find a way around this.
If this image will only be installed to systems with identical hardware then you could also try the PersistAllDeviceInstalls. Sysprep GUI will need to be closed and run from the command line and include the /unattend switch. eg. sysprep.exe /oobe /generalize /shutdown /quiet /unattend:answerfile Product Key.
I have read conflicting threads about Sysprep removing this so I can not say if it can be removed by Sysprep but I guessing your key remains after using Sysprep with Generalize which also happened with me, although my test may not be correct.
I can confirm that if you do not enter a Product Key during setup then you will be prompted for one when booting OOBE, so I would suggest if you can customise everything for your image without it and in less than 30 days then don't enter it. When you Sysprep with Generalize the Activation clock will rearm but if you plan on generalizing the image more than once then beware
If you do not use KMS, you can generalize the image to rearm the activation clock. However, you can rearm the clock only a limited number of times, determined by the Windows edition. After you reach this limit, you can still generalize the image, but the activation clock is not rearmed.