|Open up your case and examine the mboard to see if you have bad capacitors, and/or other findable signs of mboard damage .|
This was the original bad capacitor problem - has some example pictures.
History of why the exploding capacitors and which mboard makers were affected:
What to look for, mboard symptoms, example pictures:
Home page that site
- what the problem is caused by
- he says there are STILL bad capacitors on more recent mboards.
Pictures of blown capacitors, other components - power supplies, Athlon cpu's, etc.:
If you find nothing regarding that....
Your onboard sound has a vaccum tube for the sound, and your mboard was first released in about spring of 2006 and it may be 3 years old or older. The vaccum tube's filament MUST light up in order for the onboard sound to work (if you can't see it, if the filament is okay it should get quite warm, warmer than it's environment, possibly warm enough you can't keep a finger on it for long). If it doesn't light up or get warm you need to replace the vacuum tube, or use a sound card in a slot instead.
".....i even went so far as to buy another sound card...."
Onboard sound IS NOT A CARD!
"k8n diamond plus"
MSI k8n diamond plus
MSI k8n diamond plus support
The proper software for your onboard sound is here, including for Vista32 bit:
If your Windows 7 is 32 bit, the Vista drivers should work fine.
If it's 64 bit, you're going to have to find the proper 64 bit drivers.
NOTE that I know from previous experince there is more than one possible chip or chipset for many Creative or SoundBlaster sound devices (the same applies to many other sound chip or chipset makers), including for the Audigy series. Sometimes Windows has e.g. Audigy drivers built in, but it installs the drivers and often associated software for the wrong chip or chipset and the sound won't work or won't work properly.
In this case this mboard has the Creative CAO106 DSP chip.
If you randomly get drivers / associated software (sound "driver" downloads usually have both of those) for Audigy sound from the web, it may not be the software that actually works with your particular chip or chipset.
If you need 64 bit drivers you need to find the 64 bit drivers for the Creative CAO106 DSP chip in this case, probably found on the Creative or Soundblaster web sites, although sometimes they are not found on your own region and you have to find the software in another region.
Windows 95 and up supports you installing than one sound device, and the software for it, but only one sound device can be used by Windows at any one time. Whatever software for a sound device you installed last becomes the default sound device software Windows uses, but you can change that from the default in in Control Panel - some sound related icon . You DO NOT have to disable onboard sound in the bios Setup in order to be able to use a sound device installed in a slot.
It is usually a BAD idea to load drivers for a device Windows does not have the built in drivers for while booting the computer, before the software for the device has been installed, when Windows detects the device while booting, you have it search for drivers, it doesn't find any or finds only a generic device, and it asks you to point to where the drivers are. In many cases if you DO load the drivers that way, at the very least some features of the device are likely to NOT work properly, and associated programs for the device may not work properly or may not be installed at all.
Instead of doing that, CANCEL installing the drivers while booting, let the desktop load, then install the software for the device by using it's proper installation program, from the CD that came with it, or by using the proper download you get from the web.
If it's built into the mboard, the proper installation program is in the downloads for your model on the mboard manfacturer's or brand name builder's web site, and/or on the CD that came with the mboard if it's a generic desktop system.
If the CD doesn't have software for your operating system, or if downloads for your operating system are not listed (Vista drivers work for Windows 7; 2000 drivers usually work for XP; 98SE drivers often work for ME, or sometimes visa versa; 98 (original version) drivers won't work for 98SE or ME; 95 drivers usually work for 98, and maybe visa versa), you need to find downloads that will work for the device for the operating system you are using, often found on the maker of the chipset's web site.
Un-install all software for a device listed in Add/Remove Programs (or whatever is similar in Vista or Windows 7) if you DID install drivers while booting and the device is not working properly, or if you did install the software for the device properly but it might have been for the wrong chip or chipset because the device isn't working with that software, BEFORE you try installing software for the same device again, otherwise installing software for it may not install it correctly.
It is also a good idea to DISABLE loading of any resident module (one that runs all the time) of any anti-malware software you have installed, because sometimes that interferes with you installing software properly, and you may get no indication that it has not installed properly in that case.
If you don't know how to do that, tell us which anti-malware programs you have loaded.