dovebar13

Every Captain Sim product: 727 especially. No cockpit sounds after applying every fix (many posted on their own website 3 years ago). How can a such a fundamental aspect of a simulation remain broken for so long, with dismissive responses to customer inquiries? I've spent hours trying to fix this and other faults with their products. With December here, I bet the Captain Sim fire sale will begin. Take the +\- $70 you would spend collecting several incomplete simulations and buy something that works or that someone is willing to fix.

I've tried the method above and had no luck can you share how you got it to work? Thanks.

Possibly Resolved:I brought the hardware back to optimized defaults but still had the problem. At that point I was about to pull my hair out, until I went back to my event log and noticed the Cyberlink PowerDVD warning. I read some posts on forums that the PMDG crashed on people if a program tried to access the internet for updates but couldn't.Removed the Creative X-Fi card and all of its drivers and autoupdate functions (read that there was a conflict between these cards and Nvidia chipsets)Then I painstakingly removed all record of PowerDVD and Creative from the registries, program files, etc. and I made it through my cold start checklist!!!!!!!!!!! Which I couldn't come close to doing before.I'm saved at Runway 34L Paine Field ready to takeoff tomorrow I hope this gets it solved.I think something fouled up those programs when i uninstalled FSX and cleaned the registry and they choked on autoupdate and blew up the FSX. I hope so. Maybe even the overclock wasn't the issue but we'll find out.Apologies for the length of these posts but the forums have been so helpful to me maybe this detail can help others in the future.... check what programs are doing what behind the scenes!

Here are the event viewer error logs: (I get about 8 of #2). Having trouble attaching the screenshot but will keep trying.1) Source: WMIEvent filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.2) Source: SearchThe entry <C:\USERS\COLIN DOVE\APPDATA\ROAMING\MICROSOFT\WINDOWS\START MENU\PROGRAMS\CYBERLINK POWERDVD\UNINSTALL POWERDVD.LNK> in the hash map cannot be updated.Context: Application, SystemIndex CatalogDetails:A device attached to the system is not functioning. (0x8007001f)

Hi Everyone,I recently upgraded several computer components and did a reinstall, and have an FSX freeze issue that locks the computer up and requires a press of the reset button. It's happened since I've owned the machine, every several months, but now it is every flight. The problem always begins with the gauges going blurry in VC mode, Baron G1000 and PMDG 747X especially, then the mouse cursor gets ugly, then the whole system freezes. And I can't find error messages in history. I got into windowed mode once and the desktop looked awful, wild colors and waves: will post a picture next time I can manage a screen capture before I lose control.I have tried many fixes from this and other boards, and will try to give you the sequence of component additions, specs below (this is my first time posting to a tech board I apologize for newbie mistakes and length but I hope this thread will help others someday)Beginning Specs (ran FSX for 1 year with moderate tweaks, FPS limiter, nHancer 2.5.7):Vista 64Q9300 @2.54 GB DDR2-800200 GB HD2 NVidia 9800 GTX, 196.21 driversMSI P7N Mainboard600W PSUA+ Case (not sure of model with 2 huge fans and lots of space, ambient temperature 68F)REX2, GEX US, UT US & Europe, PMDG 7471/1/10: Installed Thermaltake 120 SpinQ HeatsinkOverclock Q9300 to 2.9, test in prime 95 three seperate overnights, temperatures never above 64, and only then once. Usually around 54-54-45-45 range. CPU voltage 1.24, Mem Volt 1.95, NB 1.28Played FSX for three weeks no hiccups at all.1/20/10: Installed New 1 TB Caviar Black HD to give FSX its own home, as well as a Creative Blaster X-Fi Titaniam SoundcardInstalled sound card, did not move FSX to new HD yet. Disabled onboard audio in BIOS (but did not uninstall default RealTek drivers.... doing that now after my thorough virus Scan completes but wanted to post here first)Played for 2 weeks no issues, opened PMDG 747 and BAM, graphics corrupted and fsx freeze. Updated video drivers to newest versions.Decided: well I won't fly for a while and will install FSX on new HD. Uninstall/reinstall went very badly: I did not unpeel the the onion (didn't realize that you have to uninstall Acceleration and then FSX). As a result, on reinstall, was getting all sorts of errors with Acceleration, then didn't have to register the game, very bad sign of an unclean reinstall, then got tons of fatal errors in flight for missing .dlls. That was frustrating itself... it was the typical Microsoft "encountered a fatal error and needs to close and FSX will restart." It did just that, system did not freeze. It is very important to delete FSX from every location, including all the C:/Users/Appdata/Roaming etc.1.22.10 Finally got the thing installed correctly (had to enter keys) and to fly without "fatal error." And all addons installed... defragged after each, ran the game after each, etc. 737-800 worked ok! lots of touch and goes in VC at big airports.Opened the Baron 58 G1000 and now we have the blurry gauges and complete system lockup problem and its killing me because the uninstall reinstall process is very tedious and I love this game. There is one other symptom. I hear a small "bu dum" sound before the freeze from the speakers like an MS error behind the game, but when I get to desktop I can't see any error messages. that's what got me to thinking it could be the default Realtek drivers still on the machine.Here are the fixes I've tried:Ownership taken of new hard drive, run FSX as admin just in case (even though I have admin rights)Installed newest NVidia driversUpdated/reinstalled vcredist_x86 and dxwebsetupSlowed overclockRun Prime 95 again no errors in 8+ hoursRan flight1 dll repair/restoreregistry defrag and cc cleaner after uninstallI know the gut is to suspect the overclock but this happened 1.5 years ago before I even touched bios, just very (every 100 flights) infrequently. Its the same exact problem. Any help or ideas would be greatly appreciated.