Just got some new Lenovos and at least one is having random BSODs. Minidump suggests the culprit is the Intel SATA driver... I will be testing if the updated driver fixes it later today.

Which raises a question: Is there a DriverPack containing this newer driver?

2

(5 replies, posted in DriverPack Sound)

Version of the sound pack was 8.05 (I integrated both packs, if that's relevant).
We have SP3 slipstreamed also, so the KB888111 is already included.

Vendor driver is here:
http://www-307.ibm.com/pc/support/site. … MIGR-65315

Edit: I'm not at work at the moment, so I can't be sure that download is the same version I have used previously on these boxes... I have previously used a version of the drivers from that site though, and judging from the release date, I'd say it was those.

The current Sound packs cause really bad audio on our Lenovo "MT-M 8813-AQ5" boxes. It's sort of stuttering and echoing parts of any audio that comes out.

The PCI ids I've scabbed off them are:
MS UAA bus driver for High Definition Audio: PCI\VEN_8086&DEV_284B&SUBSYS_100D17AA&REV_02\3&61AAA01&0&D8

SoundMAX Integrated Digital HD Audio: HDAUDIO\FUNC_01&VEN_11D4&DEV_1983&SUBSYS_17AA100D&REV_1004\4&18E065F3&0&0201


I don't know if these worked in previous driver packs. I have a vague memory of them not having any support (so the crackly audio is sort of better than none  ;-)

Would this be due to a wrong generic driver being chosen?


Edit: Fixed model name... Previously incorrectly said "MT-T". Correct name is "MT-M".

Well, I tried what Rockbow suggested just then. Didn't work.
I mean it stopped it asking for the disk, but it also stopped the HD Audio driver installing, so kind of pointless still.

Edit: That's using the same old driverpacks from last time I posted. I haven't upgraded because it's too much hassle... Have to find a Windows box to do it on, etc.

Ven: 11D4
Dev: 1981
Subsys: 101402F9

Is the driver for this device missing? It did not install on the 15 IBM desktops I reinstalled earlier in the week.
I had to manually install it, which for 15 computers is not fun.

Edit: I have both Sound A and Sound B installed, and the HDAudio update is installed.

Can someone explain why this happens? What causes this hdaudio driver to be the only one that gets this "wrong dir" problem? And why does it only happen with certain methods of installing?

It's not a case sensitivity thing (and thus hitting people who store their files on *nix boxes) is it?

I'm getting this too... I'm using Unattended (unattended.sf.net) to do the install, which might be stuffing things.

Any ideas on a solution? I wish MS would give us easy ways to integrate things instead of these hacks... Do they not install new hardware in their offices?