Pls Help Me Find Right Dptf Driver

guys after a hard HDD crash I have fresh installed on a new SSD Windows 10 x64 home, toshiba laptop P55W-B5224 and cannot find the right driver for:
PCI\VEN_8086&DEV_0A03&SUBSYS_F96A1179

best I can tell by association this is the DPTF device. Windows catalog has nothing for it. Tried the usual googling and can't find. Toshiba has hidden it probably in a wad of stuff one would not want on your PC. Had MS chat on the line and they could not help. I'm hoping the resolution of this will solve several other troubles generating windows errors, and the throttling of the i7 this system has.

pls help if you can - i suspect I'm going to have to roll dice on a driver for some other vendor's system.

 

You could also download IOBit's Driver Booster from Major Geeks. It will scan for missing drivers and download and install them. I've used it for drivers I could not find on my own.

 

Hi my fellow , you can try one

http://www.station-drivers.com/down...dptf_82110002996(www.station-drivers.com).exe

 

I appreciate all these attempts. as you would expect I've combed toshiba's site for the specific model and other near kin in the type, under 8.0/8.1/10 . they do not list things plainly like other vendors so there is no 'motherboard' package per se.
Best I can guess, one of the packages I grabbed, or the original auto-installed drivers via Windows 10 clean install either partially installed DPTF [ie. it was not correct drivers] or installed a 'soft' device and not the others. Done correctly, DPTF will have at least three sub-component installed. In this case it has one, shown as DPTF, then the mystery PCI Data Acquisition device. I had a MS chat help guy on the unit with me and he [actually there were 3 different techs] tried gamely to find the right drivers in the Intel & MS catalogs, as I did, but failed. blowing up bubbles.
Toshiba has awful tech support. i see no way to chat them up or email them.

Do any of you know a way to scour the debris of the failed hard drive for the right install package? maybe a toshiba directory??

 

Try a reputable driver scanner. My preferred program is Driver Talent

 

That ID string looks like an Intel PCI standard host CPU bridge, download the main Intel chipset drivers for your make/model motherboard or PC from the maker's Support/Downloads site.

 

I'm done; at least it appears so. satrow it was/is not cpu bridge [did you mean south bridge?]; the haswell-ult chipset drivers were ok. at least that part win 10 catalog does not miss on. No the orphan was, as suspected, one of the DPTF devices, dubbed Intel DPTF "Processor Participant". the "participant" was left non-participating. The fail was/is Toshiba's fault: the installer package, which is for "Intel thermal" devices per their web pages [plural: I tried windows 8.0 theoriginal OS, 8.1, and windows 10 - ], in each case failing to pickup that device while installing others - populating the DPTF entry with one or two other devices. I tried a few other DPTF packages, sometimes resulting in Blue Screen but thankfully the windows 10 repair functions worked out though in some cases had to limp around in safe mode. I picked up a 2014 vintage Dell installer package and extracted to a folder. then disabled wifi and went through a couple of device uninstalls ticking the "Delete Driver" box to remove the errant DPTF entries [these prohibiting installing the device]. Then picked FIRST the one shown here in my OP, pointed to the folder, and Bingo! finally installed with no drama. Then picked up the other device [which I had just uninstalled] via same, and it installed right.

If you're running windows 10, and especially if you have some version of Haswell family check your Intel Dynamic Platform Thermal sub-entries. IIRC I've seen as many as 4 devices in the group [my own ASUS Zenbook shows 3].

I don't think I'll be buying any Satellites for my own purposes after this....

thanks to each of you for giving it a try.
Now I need to figure out why it goes to sleep and refuses to wakeup... I strongly suspect a USB wireless mouse but can't catch a hard error log