Sound Devices Have Disappeared

Here's what i see going on...

As mentioned earlier, a device name can change when the driver is installed.

I inspected the chipset driver file from Gateway. When the chipset driver is installed the "PCI bus" gets renamed to the ATI PCI Express (3GIO)! Since we see that name appearing in your DevMgr snapshot, the chipset driver is already installed! To verify and see if its the same version i see in the Gateway download, right click the ATI PCI (3GIO) device->Properties->Driver tab. If it's the same driver, i believe the Driver tab will display provider= AMD (or ATI), and driver version= 11/02/2006, v1.00.0000.1

Next, you do have TWO HD audio controllers. After some thinking, it makes sense (even for a laptop!). Here's why:

• You have one HD Audio Controller that connects to the downstream ATI HD device. The ATI/AMD HD audio device we se in DevMgr supports sound for the computer's HDMI port! (It also seems this controller may be related to your BSODs)
• The other HD Audio Controller connects to the HD Audio device on the motherboard that supports HD sound for the speakers and mic.

Download DevManView (32-bit)32 bit version of DevManView. (fyi to anyone reading in the future, there's a 64bit version as well).

• Run the DevManView.exe
• Click Ctl-A to select all, Ctl-S to save
• Before you save! be sure you change the SAVE AS type to Tab Delimited text.
• attach the text file to next post

p.s. DevManView will give me a look at your Device Manager data. Let's also check for any Problem Devices while we're at it

> Hit the Start Orb. Enter msinfo32 in the search box. Hit Enter
> When the report appears, click to expand Components. Then select Problem Devices
> Anything appear? Ctl-A to select all the paste into next post
> If no problem devices listed tell us that too

Slartybart said:

Not much in the readme.....

AFTER the system file checker has done it's job, you could try to manually install the inf file and then scan for updates in DevMgr.

I stress after because SFC might correct the PCI bus issue and then you can follow the readme instructions. I could be wrong on SFC, but it won't hurt and it has great potential in resolving file system FUBARs.

Bill
.

When I right-click on the .inf file, then left-click on install, this is what I get.

ComputerGeek said:

Here's what i see going on...

As mentioned earlier, a device name can change when the driver is installed.

I inspected the chipset driver file from Gateway. When the chipset driver is installed the "PCI bus" gets renamed to the ATI PCI Express (3GIO)! Since we see that name appearing in your DevMgr snapshot, the chipset driver is already installed! To verify and see if its the same version i see in the Gateway download, right click the ATI PCI (3GIO) device->Properties->Driver tab. If it's the same driver, i believe the Driver tab will display provider= AMD (or ATI), and driver version= 11/02/2006, v1.00.0000.1

You are correct, sir! I am impressed.

ComputerGeek said:

Next, you do have TWO HD audio controllers. After some thinking, it makes sense (even for a laptop!). Here's why:

• You have one HD Audio Controller that connects to the downstream ATI HD device. The ATI/AMD HD audio device we se in DevMgr supports sound for the computer's HDMI port! (It also seems this controller may be related to your BSODs)
• The other HD Audio Controller connects to the HD Audio device on the motherboard that supports HD sound for the speakers and mic.

Wow! You ARE good! Yes this laptop has an HDMI port

ComputerGeek said:

Download DevManView (32-bit)32 bit version of DevManView. (fyi to anyone reading in the future, there's a 64bit version as well).

• Run the DevManView.exe
• Click Ctl-A to select all, Ctl-S to save
• Before you save! be sure you change the SAVE AS type to Tab Delimited text.
• attach the text file to next post

I'm actually becoming hopeful....

ComputerGeek said:

p.s. DevManView will give me a look at your Device Manager data. Let's also check for any Problem Devices while we're at it

> Hit the Start Orb. Enter msinfo32 in the search box. Hit Enter
> When the report appears, click to expand Components. Then select Problem Devices
> Anything appear? Ctl-A to select all the paste into next post
> If no problem devices listed tell us that too

No Problem Devices listed. Of course, I have no audio output devices at this juncture, so how could there be a problem with a non-existent device?

Slartybart said:

Thanks for the CBS log. There are a few INFO entries that might be resolved by running this MS Automated Trouble Shooter (MATS)

Temporary connection-related errors may occur when you use Windows Update or Microsoft Update

Other than that it looks good. Are you getting any errors when you run Windows Update(WU)?

Haven't really had any problems with WU, but I ran the MATS utility anyway - there were no important updates and the optional ones were totally bogus - a Bing Bar and a Bing Bar Desktop (what a load of BS - promoting your own crappy products under the umbrella of Windows Updates).