MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN.
×
goodidea
-
Content Count
9 -
Joined
-
Last visited
-
Donations
$0.00
About goodidea
-
Tripredicus, Thank you for all your help. I chanced it and just removed all the Intel/USB drivers you listed. I was able to get the image to work on the hardware. I still need to test the image on my older hardware - but at least I am rolling with my current systems ( specifically Dell Optiplex 7010). I am still interested in learning more about troubleshooting .wim issues. If you know any good links - I'd appreciate them greatly. Again. Thank you.
-
Thanks again for all your help!
-
I was able to remove the following drivers: oem141.inf oem148.inf oem149.inf I searched the mounted directory and could no longer find the REV_05 entry for the HW IDs you specified. Unfortunately, there has been no change and the system still boots with a BSOD ( which appears to be the same ). I have updated the new BSOD screen to the shared location. Please let me know if you need further information. I was hoping you were right, the systems I am having problems with appear to have USB 3.0 ports exclusively. I appreciate all your help.
-
Just to be clear, I should do the following: Mount the image and search for the HW IDs in the Windows folder: VEN_8086&DEV_8C31 VEN_8086&DEV_9C31 I should find the oem*.inf which has the REV_05 entry. In this case, the .inf files are: oem138.inf (Published name oem148.inf) oem136.inf (Published name oem141.inf) Remove the entry from the inf? Or, remove the driver using DISM? I wasn't sure about the final step. How do you determine which of the drivers is in conflict with each other? Is that information derived from the setupact.log alone? Thanks!
-
Got it! I will check it out and see what can be done. Thanks!
-
Correct. How embarrassing! Wrong index number. I was able to get the proper version of the files uploaded to the same location along with some of the log files from the panther folder. Thanks again!
-
Ok. I have added the results without the /all switch. It has two printer drivers. Most of the drivers, were from working systems. I would use Driver Magician Portable to grab the drivers from a fresh install. Apparently, most were approved by Microsoft - possibly not considered 3rd party. Any idea on how to pull the USB drivers off the wim? I'm not sure how to locate the drivers that need to be removed. I am interested how to go about finding the proper method to troubleshoot issues like these. Thank you in advance.
-
I've uploaded the files to this location: https://docs.google.com/a/carlsbadusd.net/folderview?id=0B8-aI2sI6_K9Wm1qcFNGZzR5UnM&usp=docslist_api# There should be a DISM output and a picture of the BSOD. Thanks!
-
Greetings! I have a problem I am unsure how to resolve. I have created an unattended Windows 7 installation. I install Windows 7 it over the network by running the unattended setup with various batch files. I've had to update the .wim files in the source directory by adding various drivers using DISM. I have run into a problem with the 64-bit Windows 7 Professional wim. Once it starts the initial start up, after expanding and installing the Windows source files - it crashes with a BSOD. This makes the OS unusable because you are unable to access a desktop or command line before it cras