A driver again. If you're inclined to do some digging, you should search for the last occurrence of that code in both setuperr and setupact log files. A couple of lines above this last occurrence should be a line that says 'will return 0' (errors always begin with 0x...) and will contain the exact driver. This line will also contain another code which says why the driver returned 0. This is what I have gathered (and filtered) based on Microsoft recommendations for debugging setup errors (the links I already posted here).