TI 2014 :: Universal Restore :: Any idea what driver this relates to?
Hello,
I am using ATI 2014 with Universal Restore. Any idea what driver this code is referring to?
(See attached).
Thank you in advance!
supercell
Attachment | Size |
---|---|
img_8498.jpg | 3.01 MB |


- Log in to post comments

I have only SATA (included RAID), Chipset drivers. Didn't think I would need USB and LAN drivers. I will try this.
Thank you,
supercell
- Log in to post comments

My answer to your post in the older version forum applies here as well.
- Log in to post comments

Device driver 'PCI\VEN_1002&DEV_4396&SUBSYS_43961002&REV_00' for 'Windows 7' cannot be found.
Device driver 'PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00' for 'Windows 7' cannot be found.
Device driver 'PCI\VEN_1002&DEV_4399&SUBSYS_43991002&REV_00' for 'Windows 7' cannot be found.
I'm finding that this is related to the onboard Realtek Audio Driver. Why would not having an audio driver in the HAL not allow the OS to boot?
- Log in to post comments

Ah, now I see why:
PCI\VEN_1002&DEV_4396&SUBSYS_43961002&REV_00 Driver Download
Also Supports: Standard Enhanced PCI to USB Host Controller,
- Log in to post comments

Someone else said, when having issues with their ASUS Crosshair IV:
OpenHCD USB Host Controller
Driver version:
6.1.7601.17586
Inf name:
usbport.inf
Hardware Ids:
PCI\VEN_1002&DEV_4399&SUBSYS_43991002&REV_00 <#### That's definitely one of them!
- Log in to post comments

More...
(From: http://theoven.org/index.php?topic=119.5;wap2)
PCI\VEN_1002&DEV_4396&SUBSYS_75991462&REV_00\3&267A616A&0&92: Universal Serial Bus (USB) Controller
PCI\VEN_1002&DEV_4396&SUBSYS_75991462&REV_00\3&267A616A&0&9A: Universal Serial Bus (USB) Controller
PCI\VEN_1002&DEV_4396&SUBSYS_75991462&REV_00\3&267A616A&0&B2: Universal Serial Bus (USB) Controller
PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00\3&267A616A&0&90: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00\3&267A616A&0&98: Universal Serial Bus (USB) Controller
PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00\3&267A616A&0&B0: Universal Serial Bus (USB) Controller
PCI\VEN_1002&DEV_4399&SUBSYS_75991462&REV_00\3&267A616A&0&A5: Universal Serial Bus (USB) Controller
Ok. Got it now.
I will test this out when I get home in a few. I swear that I added all the USB drivers that I downloaded from ASUS for this specific motherboard.
I'll let you know.
supercell
- Log in to post comments

So I downloaded the latest USB, Chipset and Sata drivers for win7 x64 from ASUSs' site, pointed Universal Restore to these USB, Chipset and Sata drivers (in root dir on my flash drive), included only the .sys, .inf files and I STILL get the same errors on both TI 2014 and 2015:
Device driver 'PCI\VEN_1002&DEV_4396&SUBSYS_43961002&REV_00' for 'Windows 7' cannot be found.
Device driver 'PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00' for 'Windows 7' cannot be found.
Device driver 'PCI\VEN_1002&DEV_4399&SUBSYS_43991002&REV_00' for 'Windows 7' cannot be found.
Any suggestions would be very much appreciated.
supercell
- Log in to post comments

My suggestion would be to run the restore process after having wiped the target disk if you have not done that already.
- Log in to post comments

That's part of the TI 2014 UR process. It will wipe the target disk prior to installing the new image.
- Log in to post comments

supercell29,
Is the USB removable media you are using formatted FAT32? If not, please try that. Does UR appear to be reading the drive when you point Acronis to it, or does the error occur immediately once you click "ok"?
All of MVP Enchantech's support has been spot on.
- Log in to post comments

Is the USB removable media you are using formatted FAT32? -- Pretty sure it's NTFS. If not, I will format it and create a FAT32 partition.
Does UR appear to be reading the drive when you point Acronis to it, or does the error occur immediately once you click "ok"? -- Yes it is reading the drive (flash drives' LED blinks during the process for quite a while) and it shows the path where it failed. However, I'm not sure (and there's no way to tell as far as I know) if Acronis UR is going down the list of all the paths I've created.
Thank you so far,
supercell
- Log in to post comments

The UR feature in 2014 is pretty robust compared to earlier versions. So you've tried the latest driver versions from the Asus website. I'm surprised windows 7 is being this picky. You should only need chipset and storage controller drivers for the restore. What kind of system was the image you are using to restore with? You aren't going from Intel to AMD are you? It seems like it would have to be dramatically different from the CrossHair to fail? And you're sure you have unpacked the .exe's or .zip files completely? You're installing to the SSD, yes?
- Log in to post comments

The UR feature in 2014 is pretty robust compared to earlier versions. -- I agree entirely! I used it to move a Windows 7 Pro OS from a Dell laptop to a new Lenovo T430 without an issue (well, actually this isn't entirely true. It was also a driver nightmare! It took me several days to find the right ones.)
So you've tried the latest driver versions from the Asus website. I'm surprised windows 7 is being this picky. -- So am I.
You should only need chipset and storage controller drivers for the restore. -- Yes. So why is it asking for USB controller drivers? I recall this happening with the Dell/Lenovo transfer as well.
What kind of system was the image you are using to restore with? -- It was a ASUS Crosshair IV (AM3 socket - AMD). The mobo I'm trying to migrate it to is a ASUS Crosshair V Formula - Z (AM3 socket - AMD). The processor hasn't changed. Neither has the RAM, or HDD's. The only changes are the mobo and the Crucial 200MX 1TB SSD which I am trying to migrate the Acronis image/drivers to.
You aren't going from Intel to AMD are you? -- No (see just above)
It seems like it would have to be dramatically different from the CrossHair to fail? -- Agreed
And you're sure you have unpacked the .exe's or .zip files completely? -- I looked, via 7zip, into several .exe's (not all of them) and found no .inf's, or .sys files. Acronis documentation states that only .inf, .sys and .oem files are necessary, so I'm ignoring the .cat files.
You're installing to the SSD, yes? -- Yes. Interestingly enough, the whole reason I am migrating to a more recent version of ASUSs' Crosshair mobo series is because I was getting BSOD's after copying an Acronis image to them (verified it prior and Acronis TI said that the image was good [used it finally to migrate to an older sata spindle and it worked just fine]). These were 3 different, brand new SSD's. (Crucial recommended for the Crosshair IV. I also tried a Samsung EVO 850 and received the same results). I was told by ASUS that the mobo drivers were too old (they haven't updated the Crosshair IV drivers since 2012) and that they aren't supporting the newer SSD drives. I'm wondering if the same issue exists in conjunction to Acronis not finding the correct drivers for the HAL, but ASUS shows all of the Crosshair V Formula - Z drivers to be 2013 up to 5/2014 and also on the mobo box it says "Windows 8.1 ready". Too hard to determine. The sata drives (spindle) worked just fine on the older Crosshair IV with the same TI image. And, yes, I just thought that perhaps I should try to migrate A) a TI image and B) using UR to a spindle sata drive on the Crosshair V to see what happens. I will, but will not be able to test this until the 31st as I'm going away for a while. I'd like to keep this going, so please try to come back to help out come 5/31.
Please feel free to respond anytime as I certainly will be checking my emails.
Thank you for all the well thought out advice! Much appreciated! :~)
supercell
- Log in to post comments

Drivers confirmed again from this URL:
https://support.rockstargames.com/hc/communities/public/questions/20370…
###### SYSTEM DEVICES #####
Name: Standard Enhanced PCI to USB Host Controller
Device ID: PCI\VEN1002&DEV4396&SUBSYS43961002&REV00\3&267A616A&0&B2
Driver: n/a
#####
Name: Standard OpenHCD USB Host Controller
Device ID: PCI\VEN1002&DEV4397&SUBSYS43971002&REV00\3&267A616A&0&B0
Driver: n/a
#####
Name: Standard OpenHCD USB Host Controller
Device ID: PCI\VEN1002&DEV4399&SUBSYS43991002&REV00\3&267A616A&0&A5
Driver: n/a
- Log in to post comments

I'm now down to two (see below. Universal Restore [TI 2015] also gives me the same issue). The Windows drivers seen below are NOT one's I am using. I'm not sure that using the Windows drivers will even work, but I have, (or at least I think I don't) no other option as the most recent ASMedia USB/Chipset drivers that ASUS provides for this motherboard do not work via TI 2014/2015 UR. I am just showing these (below) for reference. The .sys files I grabbed for TI Universal Restore will be from my Crosshair IV TI 2015 image (again, not seen below):
Device driver 'PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00' for 'Windows 7' cannot be found.
Name: Standard OpenHCD USB Host Controller
Device ID: PCI\VEN_1002&DEV_4397&SUBSYS_43971002&REV_00\3&267A616A&0&90
Driver: C:\Windows\system32\drivers\usbohci.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:30, 25600 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:31, 324608 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7600.16385 (English), 7/13/2009 20:07:09, 343040 bytes
Device driver 'PCI\VEN_1002&DEV_4399&SUBSYS_43991002&REV_00' for 'Windows 7' cannot be found.
Name: Standard OpenHCD USB Host Controller
Device ID: PCI\VEN_1002&DEV_4399&SUBSYS_43991002&REV_00\3&267A616A&0&A5
Driver: C:\Windows\system32\drivers\usbohci.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:30, 25600 bytes
Driver: C:\Windows\system32\drivers\usbport.sys, 6.01.7600.16385 (English), 7/13/2009 20:06:31, 324608 bytes
Driver: C:\Windows\system32\drivers\usbhub.sys, 6.01.7600.16385 (English), 7/13/2009 20:07:09, 343040 bytes
- Log in to post comments

Earlier in this post I suggested that you should wipe the target drive prior to a subsequent attempt at Universal Recovery. Your response was that UR does that. My suspicion is that what UR does is not a wipe of the drive but rather it marks sectors of the disk as available for write. This means that previous data is still present on the disk but can be overwritten. It is possible that UR when performing the restore sees these offending files on disk and therefore does not overwrite them.
There are a good number of free tools available to wipe a disk, my personal favorites are Windows Diskpart and Gparted. If I were you I would use one of these tools to wipe the disk thus insuring that no data is present on the drive then, run UR with your updated drivers again and see if that will solve your issue as quite frankly this should not be as difficult as this has been for you. In cases such as yours it has been my experience that residual data is the cause of such issues.
- Log in to post comments