No sound in windows 7 after BSOD, tested with 3 different soundcards

[peterenton]

i think i posted thisd in the wrong place (under drivers)
After an update last night (but not SP1 - this is now installing) there was a BSOD on bootup and then no sound at all. I have an external card (Fast Track) for recording, an internal card for watching movies (x-Fi titanium) and the onboard which i have disabled. None of these are picked up by Windows 7 - the audio in the taskbar says "No Audio Output Device Available." They appear in Device Manager, but with a little yellow ! sign by them, and it says driver installed but "Code 39." This is definately a Windows error - I plugged the fasttrack into a mac and it worked fine, so the soundcard is not burnt out.
I tried rolling back the drivers - this did nothing, and it only gave me one choice to roll back with. I have a deadline to export music by and its giving me a major headache.
Anyone have any idea why Windows would suddenly decide not to see sound cards?
i have tried reinstalling drivers, unplugging the internal and external soundcards, scanning for new hardware and nothing works.
Any help would be appreciated, Pete

 

[Crispy]

Please use this thread so we can help you with the blue screen problem you are having atm: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[fireberd]

There are two separate issues here. First the Fast Track (I have an MAudio Fastrack Ultra 8R that I use with Sonar) should be disconnected until you get your PC audio fixed. Second, since you are using a separate sound card, the Integrated audio needs to be disabled in the BIOS as conflicts between devices can also cause a Code 39 error (along with a driver problem).

After disabling the Integrated audio, boot up and check the Device Manager. If you still have the Code 39 for the SoundBlaster, uninstall the SoundBlaster (DO NOT check the box to uninstall the drivers) in the Device Manager and then restart and when Windows starts it should detect and reinstall it. If there was a corruption between the SoundBlaster and Windows this will usually fix it. If it's still bad after this, reinstall the SoundBlaster drivers. If you are still having problems, reinstall the motherboard chipset drivers, restart the PC and check the status.

 

[peterenton]

Yes, the fast track is removed at present. Onboard has been disabled - this set up has been working fine until the last update, in which the above happened. I have done all you have recommended except reinstalling the motherboard chipset drivers. I still think its related to the last windows update - though have no idea how. Its just very weird how Windows doesnt recognise anything at all sound related. a quick google revealed that I am not alone, but couldnt not find any threads on this forum so thought i would start my own. Thanks for the help, will reinstall the motherboard chipset drivers.

Just one thing - I did check the box to uninstall the drivers at one point in one of my many attempts, then reinstalled them. Is there a reason that should not be checked (i tried with and without, thought a fresh look might help.)

Im fairly sure this is a windows update issue, on google people were reverting back using system restore and not installing the updates, and this solved the issue. however, due to ( i think lack of space) there not being that option im kinda stuck. would prefer not to have to reinstall windows. However, I habe got my music program to work so have managed to export my work, so at least Its not so much of a hurry.
Thanks again, pete

 

[peterenton]

Sorry - didnt see the BSOD post. Here is the info you asked for:

Thanks again, Pete

 

[peterenton]

Another odd thing - devices showing up now include a whole host of bizarre things ive never seen before:

 

[fireberd]

The Microsoft stuff appears, from google searches, to be related to possibly a web cam. I've never seen those entries before.

You should have a list of updates that were installed. You could try uninstalling them, one at a time, if one of those did cause the problems - if you can't do a System Restore.

When I "uninstall" a device in the Device Manager I don't normally uninstall the drivers too. The uninstall/reinstall by Windows is a "catchall" that fixes a lot of flakey problems. If that doesn't do it then an uninstall along with drivers is a next step then reinstall - but do not let Windows install drivers - install the manufacturers drivers.