Had this problem some time ago- tore my system apart - wound up doing a lot of cleaning and reapplying thermal paste. Problem disappeared. Now it's back.

Anyone?

See and hear it at YouTube (this is NOT my system, but it sounds pretty much like this)

 

To HEAR this sound, click the "YouTube" icon in the lower-right of the player window.  For some reason, I can't get the audio to play here on Avsim in the media viewer window.

 

Thanks for any help.  From what I know, this is a COMMON problem with newer PCs, not just those playing FSX.  Note:  nVidia GTX690 card w/onboard audio (HDMI) disabled.  Onboard ASUS motherboard audio DISABLED in BIOS.  Soundblaster X-Fi HiFi PCI audio w/ latest drivers.

 

**The 'possible' fix was suggested by clicking on the SPEAKER icon in the Win7 taskbar, the the SPEAKER icon in the Win 7 MIXER,  and then clicking on the ADVANCED tab in the Speakers Properties dialog box.  Untick the Allow Applications to take Exclusive Control of this device and also untick Give Exclusive Mode Applications Priority.  Then click APPLY and then OK.

 

What my working hypothesis is (subject to testing) is that some applications "fight" with FSX for the sound card's time, and when these applications are switching back and forth, if they are given "exclusive" control of the speakers (and/or soundcard), then a lockup 'could' occur!  This fits with what I remember in some past incidents, where all I did was swap EZ dok camera views from inside the plane to outside the plane.  What happens when you do that?  The sounds switch- because the EXTERIOR views involve supplemental ENGINE sounds that are not operating when inside the plane.  So we will see.  Testing on a 2+ hour flight that crashed earlier tonight.

Update:  Flew 2+ hours flight with no crash, using the fix described in the original post.  More testing underway.

It seems to have been a problem with your Soundblaster X-Fi soundcard. If you disabled the X-Fi and used your motherboards audio does it cause the same lockup?

 

If it is exclusive to the X-Fi, I would be bugging Creative to work on their drivers. Probably a fruitless exercise, as it took them forever to even release a decent 64-bit driver for W7 back in the day, but it never hurts to try! Their lack of good driver support is what has kept me away from their products since the 64-bit debacle to this day.

It seems to have been a problem with your Soundblaster X-Fi soundcard. If you disabled the X-Fi and used your motherboards audio does it cause the same lockup?

 

If it is exclusive to the X-Fi, I would be bugging Creative to work on their drivers. Probably a fruitless exercise, as it took them forever to even release a decent 64-bit driver for W7 back in the day, but it never hurts to try! Their lack of good driver support is what has kept me away from their products since the 64-bit debacle to this day.

 

 

It's hard to know.  I don't think it's the Creative card, I think more likely some kind of conflict with multiple programs all trying to send sound data to the PC simultaneously.  Since adopting the 'fix' that I listed in my original post - I'm cautiously optimistic that I may have resolved the problem.  I also rolled the nVidia drivers back to the latest WHQL-certified (Windows Hardware Quality Labs) driver.   I will consider the case resolved unless the buzz re-occurs.  Thank you for your idea, though.