lensman

Hi all, I downloaded and installed the 747v3 last night. During installation, there was a box that popped up saying some Microsoft software had to be installed. After a few seconds the box message changed and said it could not reach Microsoft and try again later. I searched the PMDG forums but didn't find any clues. What software failed to install, and how do I get it from Microsoft? Thanks in advance, dan davison

Tom, We've never met but AVSIM has meant a great deal to me. To say I was stunned by your news is an understatement. I've been in tears for the last 30 minutes. The primary thing is to take whatever time you need to be with your family and friends. Everything else is a very distant second. I can state this because I was just diagnosed with cancer six days ago. Wow did my priorities change in a day. Thank you for AVSIM and everything you've done for our hobby. You are in my prayers, and Godspeed. dan davison

Just tried it again - yes, AT and AP are off, FDs off, flaps up, The plane will respond to F1/F2/F3/F4, but not the throttle on the joystick. Nose landing gear still doesn't turn, so I can't get off the main runway. Thanks for the hints, any other ideas? dan davison

Hi Peter and Pau, Yes, the autopilot is off -- that siren drives me crazy. I will double-check the auto-thrust: I'm 99.9% sure it's off. Thanks! dan davison

Hi All, I apologize for asking this, but what is the trick to getting a 777 steering after it lands? I remember this being asked after shortly after it was released, but a bunch of searches did not turn up the original thread. In brief, I land OK, slow to a high-speed turnoff, but the nose wheel doesn't turn. The throttles also don't work unless I use the F3 and F4 keys. The throttles will then move in the cockpit view and the plane will roll. The joystick will not turn the front wheels, though. The brakes are not on, taxi and landing lights are on, no smoke or overtemp from the tires, I know it's something simple, but I dunno what it is. Thanks for any help! dan davison There should be a signature here, but the way life is going, who knows.

This is great news. Plus, I haven't heard of "Circle Error Probable" since a couple decades ago at Los Alamos. I didn't know the term was still in use. I will not hit F5 every minute for the next 8440 (approximate) minutes. I will not hit F5 every minute for the next 8440 (approximate) minutes, I will not hit F5 every 8440 (approximate) minutes. I will not hit F5 .... dan "lensman" davison

We've not seen much of the interiors yet, but .... most importantly .... where is the PMDG cola? "Only 1,250 calories". :rolleyes: dan davison

Folks, in one of the screenshots, both VNAV and LNAV are on during the takeoff roll. I thought one did not use them on takeoff. I'm sure it's in one of the PMDG tutorials, and the real manuals. If I remember correctly, arming LNAV will make the plane rotate by itself. Also, the tutorials and manuals both say takeoff flaps should be 10 (regardless of derate). dan davison

While your post isn't exactly clear (see above reply), on the 747X when starting in the cold and dark panel state, the image on your monitor will be very dark until you click on the battery button to start powering up the aircraft. After you power it up a few times, you'll be able to start (i.e. to engines on) in the dark. If you're referring to your monitor, first put FS9 into windowed mode instead of full-screen mode. That will tell you whether it's FS9 or PMDG. Its's really unlikely that it's PMDG. Disclaimer: I've never even seen FS9, this is from FSX experience on multiple 747 models. HTH, dan davison

From the PMDG web site: PMDG 737NGX Video Training by AoA Price $2,000,000.00 It's been this way for almost 2 months. Is this the airline price? That's not how much it costs on the AOA web site - I subscribed as soon as AOA announced they'd be making the training videos. dan "lensman" davison p.s. I would post a direct link to the PMDG and AOA sites for comparison but IIRC we're not allowed to do that on AVSIM. I just cut-and-pasted the above from the PMDG site. I don't know how to get rid of the link, otherwise I would.

True enough. I take it you've never had a tonic-clonic seizure. Good, and I hope it stays that way. Aside from physical damage (from the seizure) you lose your driver's license for 6 months in most states. Mine are myoclonic, but I still get the aura. I really liked the effect, it was just the speed that could cause problems. An amazing number of people find out the hard way, especially at dances, concerts, and driving in poorly lit tunnels. dan "lensman" davison

Hi all,I really like the "spinning" avatar and banners effect today (April 1, 2012). However, a gentle reminder is in order. Those of us with epilepsy or movement disorders can have seizures/tremors triggered by that kind of effect. I think they are rotating fast enough that it won't be a problem for most people, but I sure felt the beginnings of tremors (the "aura") start up the first time one started spinning. I figured out what was making the banners spin, so I can just look away, and there's no problem for me.I really like the effect, but you may want to warn people or really slow it down (yes, it loses the propeller feeling).Best wishes,dan "lensman" davison

I would have fallen for this if I hadn't watched the PMDG videos on YouTube yesterday. RR said the MD-11 was their most disappointing-selling project. Which makes no sense to me, because it is an awesome a/c and an awesome sim. Drive by KEWR before midnight and it's practically the only a/c visible (FedEx and UPS liveries).Anyone know why all the avatars and sig banners are rotating?Dan "lensman" Davison

Well, there are other reasons for needing 2D panels - readability for those of us with low vision. Vic & artists did a **superb** job on the NGX - in the 3D view all labels are readable, as are the popups. But, some're not visible from an angle. I'm not sure what EZCO is, but it sounds like it could solve the "I can't locate that switch from this angle, or this angle, or this angle" (if/when I can afford it).The main challenge is the center consoles. When I'm trying to change HUD settings, or NAV radio settings, I switch views and wind up looking at the door, floor, or ceiling for some reason. Then I have to pause, roll the mouse around to try to find the right view, switch back, and unpause. So much for immersion.There are still parts of the upper panel I haven't seen clearly (far upper left and far upper right) in 3D view, because of the angle. There must be some trick I haven't found yet, but I don't know what it is. (I use the posters in the Captain's kit instead).PMDG did a superb job on making everything readable in the NGX (except for the soda cans and the pogo stick!) so I don't have to use the 2D panels as much. In a competitor's 767 I can't make out switch and button labels in any view, with W7's built-in magnifier or third-party magnifiers).So I'm in the minority, and I'd have to give a -1 on the loss of 2D panels, although I understand why.

Awesome advice. I think I'll go with either the H60 or the Antec 620 for cooling and rearrange fans as superglide17 suggests. Reviews of the H60 and 620 both say they are easy to install, and YouTube videos and the installation manuals both seem relatively straightforward.The stock cooler is indeed firmly mounted, so the high temps aren't due to one of the clips working loose.@superglide17: do you know where I'd find instructions on replacing the Big Boy fan? I have a replacement already, but cannot figure out how to get the current one out (has 2 broken blades). I found 2 screws and 2 clips by comparing to the replacement fan. I can get the left side up (as seen from the front), and sort of get the right side clip loose, but can't figure out where to go from there. It looks like the metal top has to come off, but if there's a way, I don't have the visual acuity to see it. I asked Antec tech support and didn't get an answer I could understand (although the reply came after the microstroke which affected mostly language processing).Again, thank you both *very* much for the advice. I really want to get this fixed, because Tuesday is chemo day. I need something relatively mindless to do late that day and the next. FSX missions, with a few changes, are perfect.dan

Thanks for the quick reply. I do intend to overclock the processor when I get the machine stable. You're right-that's why I went for the "K". I've not reseated the fan but that's worth a try. Those Intel/AMD connectors come loose but usually it happens when the machine is moved or bumped.I'll check out the coolers you mention although I dread having to take everything apart again.Oddly enough, I've never had a noise problem with the case. I've had a hissing sound in my ears since a stroke and infection about a year ago, and the machines that keep me breathing make enough background noise that I've never heard the fans in the case.Thanks again,dan

Hi,My recently built gaming machine has strangely started overheating. Specs are in the signature. It had been running FSX in the 50C range, but after a complete reinstall of W7x64, FSX, and all my files, it runs FSX in the 70-85C range. Processor is i7-2600K, not overclocked. The case (Antec 900) has six fans, two 140 mm over the drive bays blowing in, one 140 mm on the side panel blowing in, one 200 mm on top blowing in, and two 140 mm (one on the PSU, one on the case) blowing out. There's also two fans on the Radeon 6950, blowing into the case, but the side fan blows cool air onto it. All are running as fast as they can. The stock Intel CPU cooler fan runs proportionally to the temp of the CPU. There were no hardware changes, no position-of-hardware changes, and no changes to the cabling. I'm not sure reversing the fans (to make a negative-pressure setup) would make any difference.The case does not have a cutout in the motherboard tray to install an aftermarket cooler. My vision is not that good, so I'd prefer to get a cooler that "plugs" into the board (ASUS P8X68-V-Pro) the way the stock cooler does. In looking at reviews, I've not seen a cooler that does that. I don't care whether it's air or liquid-cooled (although liquid sounds better at this point), I just need the part that contacts the CPU be of the "push-pin" Intel type.Any recommendations would be very welcome.Thanks in advance,dan "lensman19067" davison

What a disaster. The BIOS flashing went OK ... but completely destroyed the boot sector(s) of the W7 HDD. I tried half a dozen "repair" utilities (EasyBCD, testdisk, Paragon something-or-other, EBCD, various live CDs, and W7 "recovery". It would not even boot off the W7x64 DVD. I wound up having to reinstall everything. I had backups of my files, of course, but finding all the programs, blech. When HDD prices come down I'll get an extra HDD and make an image clone. I ran Microsoft Update four times before it was satisfied that I was updated on everything (OS, Office, whatever Silverlight is, but I did not let it update drivers: some were from 2006 (!)). I got those from the mfr's web site.Back to the original issues. The first was pausing, the second "fogging".Pausing: The fresh install of FSX+Acceleration still does the pausing. I set up Task manager, Process Explorer, and Process Monitor (separately) and was stunned by what happens. When FSX pauses, nothing else is increasing its I/O or CPU. FSX is literally being removed from memory. The working set goes from about 1.2GB to 24MB (that's not a typo). After it all "drains" out, it then reloads and after it gets ~75% of the way, the program resumes. virus scanning and Carbonite are turned off, Google Desktop and Windows Search are configured not to touch the SSD (which only has FSX). "Game Booster"-type programs are not in use, and FSUIPC is not loaded. It is as if the program is checkpointing itself, which would be a very nice feature, but I haven't seen that since CRAY OS days.Fogging: Remember, this is a fresh install of W7. When FSX pauses, if I click the mouse a couple times, it still fogs, but eventually (< 5 minutes) comes back. In these cases, FSX does *not* "drain" out of memory. Task Manager lists it as running, Process Explorer does not show any I/O (of any kind) and the working set size does not change. All FSX threads are in either Wait:I/O or Wait:Executive Something state. Now for the real special change: the "fogging" happens in any program, including the windows 7x64 desktop. Happens in Firefox, Opera, Google Chrome, Safari for Windows, Word 2010, Excel 2010, and while running installers. Unlike before re-installing everythingA new behavior: Now the machine runs hot (no I don't overclock). Previously, when running FSX, the temp might spike to the upper 60s, but run in the upper 50'sC. Now, all four cores happily run themselves into the lower 'sC. All temps monitored by RealTemp 3.0 and ASUS's monitoring utilities (AI Suite). No voltage/current changes, just the temp. (I am running the stock cooler: that will be the subject of another post). Leaving services alone, but killing all possible user processes (e.g. Dropbox, Carbonite, Google Desktop, search indexing, yada yada) does not alter the behavior. It happens with the PMDG 737NGX, the PMDG 747X/XF/LCF/8i/8F and the LDS 767.The case has six fans, two 140 mm over the drive bays blowing in, one 140 mm on the side panel blowing in, one 200 mm on top blowing in, and two 140 mm (one on the PSU, one on the case) blowing out. There's also two fans on the Radeon 6950, blowing into the case, but the side fan blows cool air onto it. All are running as fast as they can. The stock Intel CPU cooler fan runs proportionally to the temp of the CPU. I don't know what has changed that the temps are running so high.If you've read this far, thanks, and any advice/comments are welcome.dan "lensman19067" davison

That did it! What I didn't notice the first few times I tried it was that it opens a new *tab*. I can log in on that tab but then lose my place in the original tab I was working in. I'm still expecting the autologin to work, and not having it after 3 or 4 years is disconcerting.Thanks for the help!dan "lensman19067" davison

Same here, with Firefox 9.0.1, scripts blocked but avsim.com, avsim.net both allowed. I hope there's a fix!dadan davison

Ooh, good point. Windows search indexer is running, as is google desktop, and I've never watched their I/O. I'veonly watched FSX's I/O. It's also a good point because the timing is right, in the sense that how long the "whiteout/pause" takes and the interval in between them. Even though the Kingston SNV425S2 is 3 GB/sec SATA II, I originally had it plugged into a 6GB/sec SATA III port. I'll make sure it's still plugged into the 6GB/sec port.That won't make the SSD faster, but it should prevent saturation of the port. Yes, Windows Update enabled, but it never hurts to check by hand. Gulp. My BIOS 0801, 08/15/2011, isn't even on the Asus' list of downloadable BIOS for this board. There have been five releases since that date, the most recent 12/02/2011. Guess I'll be flashing a BIOS later today. I *hate* doing that.@torkermax: memory is indeed at 1333 MHz. I won't mess with it!thanks again,dan

Hi Jahman,I applied the atc fix, the uicoreautomation fix, the PMDG fix, and the latest FSUIPC update, rebooted, and got mixed success. No CTDs in three tests, but the long pauses still happen. There's no I/O activity on the CPU graph from SysInternals' Process Explorer, but during the long pause there *is* activity on the CPU's GPU. There's usually no activity on the embedded GPU. This was with two-hour flights, one with 4X speedup for about 30 minutes.The new appearance is that when the spinning circle appears, if I click again, the screen gets "fogged", as if a white veil has been drawn over the entire FSX display. It does not matter if the screen in windowed or in full-screen mode, nor does switching between one or the other affect it.Other symptoms are CPU usage drops to 0.25%; only the system idle process uses any notable CPU (90%), there's no significant network activity, and all threads are in "Wait" states of various kinds. I've seen this kind of problem 25-ish years ago when I was writing a VMEbus driver on VMS - I used the queued-IO-wait instruction instead of the queued-IO instruction. The former waited for the I/O operation to finish, the latter just proceeded on its merry way and the device driver writer (i.e. me) had to periodically check that the I/O had completed. In a brief look around with Google and Yahoo I didn't see anything similar.@torkermax - I had not even considered memory timings. The memory is rated at 1600, but CPUZ reports XMP-1600 and JEDEC #4 at 667, voltage 1.5V (I don't overclock memory, and I haven't even started trying to OC this machine). CAS is 9. I will have to find out what "JEDEC 667" means...There must be a multiplier, because SIW reports memory is running at 1333 MHz.@DescendDescend: This board (P8X58-V-Pro Asus) has that BIOS replacement whose letters I haven't learned yet :( , something like EFCI (?). When a calculation finishes I'll check the hot-swappable status of the SSD. It never occurred to me that the power settings in W7 might try to turn off the SSD. I've set the "sleep" time to the same as yours.I very much appreciate the help! dan "lensman" davison

I hope you mean the data that appears in the Event Viewer. I can't cut-and-paste for some reason, so the most recent in XML format (highly edited). If there's a way to get a full dump of the process, I can use WinDbg to get more information.Note that in every case, it's a different module that faults. I always thought that this exception was a Data Execution Protection error, i.e. trying to access memory outside a process' memory space.Log Name: ApplicationSource: Application ErrorDate: 12/30/2011 8:14:12 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: striderDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: atc.dll, version: 10.0.61637.0, time stamp: 0x46fadb59Exception code: 0xc0000005Fault offset: 0x00043cb9Faulting process id: 0x1f9cFaulting application start time: 0x01ccc74796f60805Faulting application path: E:\FSX\fsx.exeFaulting module path: E:\FSX\atc.dllReport Id: bf42ae44-334c-11e1-8d55-14dae9d820beEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-12-31T01:14:12.000000000Z" /> <EventRecordID>11484</EventRecordID> <Channel>Application</Channel> <Computer>strider</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>atc.dll</Data> <Data>10.0.61637.0</Data> <Data>46fadb59</Data> <Data>c0000005</Data> <Data>00043cb9</Data> <Data>1f9c</Data> <Data>01ccc74796f60805</Data> <Data>E:\FSX\fsx.exe</Data> <Data>E:\FSX\atc.dll</Data> <Data>bf42ae44-334c-11e1-8d55-14dae9d820be</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 12/30/2011 5:13:16 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: striderDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: uiautomationcore.dll, version: 7.0.0.0, time stamp: 0x4a5bdb1dException code: 0xc0000005Fault offset: 0x0000e52aFaulting process id: 0x230cFaulting application start time: 0x01ccc71c99bcd53cFaulting application path: E:\FSX\fsx.exeFaulting module path: C:\Windows\system32\uiautomationcore.dllReport Id: 7828aa53-3333-11e1-8d55-14dae9d820beEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-12-30T22:13:16.000000000Z" /> <EventRecordID>10860</EventRecordID> <Channel>Application</Channel> <Computer>strider</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>uiautomationcore.dll</Data> <Data>7.0.0.0</Data> <Data>4a5bdb1d</Data> <Data>c0000005</Data> <Data>0000e52a</Data> <Data>230c</Data> <Data>01ccc71c99bcd53c</Data> <Data>E:\FSX\fsx.exe</Data> <Data>C:\Windows\system32\uiautomationcore.dll</Data> <Data>7828aa53-3333-11e1-8d55-14dae9d820be</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 12/30/2011 11:41:37 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: striderDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0x00ffffffFaulting process id: 0x1c88Faulting application start time: 0x01ccc6f452898e65Faulting application path: E:\FSX\fsx.exeFaulting module path: unknownReport Id: 2375d5e7-3305-11e1-8d55-14dae9d820beEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-12-30T16:41:37.000000000Z" /> <EventRecordID>10377</EventRecordID> <Channel>Application</Channel> <Computer>strider</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>00ffffff</Data> <Data>1c88</Data> <Data>01ccc6f452898e65</Data> <Data>E:\FSX\fsx.exe</Data> <Data>unknown</Data> <Data>2375d5e7-3305-11e1-8d55-14dae9d820be</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 12/29/2011 7:45:03 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: striderDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0xff0f0f0fFaulting process id: 0x1ffcFaulting application start time: 0x01ccc67f3a3bf61eFaulting application path: E:\FSX\fsx.exeFaulting module path: unknownReport Id: 823d488a-327f-11e1-ac9b-14dae9d820beEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-12-30T00:45:03.000000000Z" /> <EventRecordID>10154</EventRecordID> <Channel>Application</Channel> <Computer>strider</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>ff0f0f0f</Data> <Data>1ffc</Data> <Data>01ccc67f3a3bf61e</Data> <Data>E:\FSX\fsx.exe</Data> <Data>unknown</Data> <Data>823d488a-327f-11e1-ac9b-14dae9d820be</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 12/23/2011 11:03:48 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: striderDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: PMDG_MD11.DLL, version: 10.0.61355.62, time stamp: 0x49b7c81dException code: 0xc0000005Fault offset: 0x00154bc5Faulting process id: 0x504Faulting application start time: 0x01ccc1e71aed67a2Faulting application path: E:\FSX\fsx.exeFaulting module path: E:\FSX\GAUGES\PMDG_MD11.DLLReport Id: 47a3781a-2de4-11e1-822f-14dae9d820beEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-12-24T04:03:48.000000000Z" /> <EventRecordID>9180</EventRecordID> <Channel>Application</Channel> <Computer>strider</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>PMDG_MD11.DLL</Data> <Data>10.0.61355.62</Data> <Data>49b7c81d</Data> <Data>c0000005</Data> <Data>00154bc5</Data> <Data>504</Data> <Data>01ccc1e71aed67a2</Data> <Data>E:\FSX\fsx.exe</Data> <Data>E:\FSX\GAUGES\PMDG_MD11.DLL</Data> <Data>47a3781a-2de4-11e1-822f-14dae9d820be</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 12/23/2011 9:20:22 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: striderDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0xc183948aFaulting process id: 0x23c4Faulting application start time: 0x01ccc17ae4237072Faulting application path: E:\FSX\fsx.exeFaulting module path: unknownReport Id: 3f574c98-2d71-11e1-822f-14dae9d820beEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-12-23T14:20:22.000000000Z" /> <EventRecordID>9124</EventRecordID> <Channel>Application</Channel> <Computer>strider</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>c183948a</Data> <Data>23c4</Data> <Data>01ccc17ae4237072</Data> <Data>E:\FSX\fsx.exe</Data> <Data>unknown</Data> <Data>3f574c98-2d71-11e1-822f-14dae9d820be</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 12/23/2011 8:57:40 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: striderDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0x51084d8dFaulting process id: 0x1c40Faulting application start time: 0x01ccc0fc35a8faf6Faulting application path: E:\FSX\fsx.exeFaulting module path: unknownReport Id: 13adabff-2d6e-11e1-822f-14dae9d820beEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-12-23T13:57:40.000000000Z" /> <EventRecordID>9115</EventRecordID> <Channel>Application</Channel> <Computer>strider</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>51084d8d</Data> <Data>1c40</Data> <Data>01ccc0fc35a8faf6</Data> <Data>E:\FSX\fsx.exe</Data> <Data>unknown</Data> <Data>13adabff-2d6e-11e1-822f-14dae9d820be</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 12/22/2011 5:47:15 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: striderDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0xf845c7d0Faulting process id: 0x16acFaulting application start time: 0x01ccc0caa882b721Faulting application path: E:\FSX\fsx.exeFaulting module path: unknownReport Id: e48e6bcd-2cee-11e1-822f-14dae9d820beEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-12-22T22:47:15.000000000Z" /> <EventRecordID>9017</EventRecordID> <Channel>Application</Channel> <Computer>strider</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>unknown</Data> <Data>0.0.0.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>f845c7d0</Data> <Data>16ac</Data> <Data>01ccc0caa882b721</Data> <Data>E:\FSX\fsx.exe</Data> <Data>unknown</Data> <Data>e48e6bcd-2cee-11e1-822f-14dae9d820be</Data> </EventData></Event>Thanks for any help!!!!dan davison

I'm having an unexpected problem with FSX on an SSD. The full machine specs are below, but the problem is that FSX will pause for several minutes (up to 8 min so far) and then resume. After 2 or 3 pauses at the next pause it CTDs. Using Process Explorer, there is no I/O at all from FSX, and there are 68-73 threads running or waiting to run. Active threads are all in a Wait stateThis happens with default aircraft and scenery, with REX, all PMDG a/c, and FSUIPC running. Only FSX-related software is on the SSD. It's an older 64 GB Kingston SNV425-S2 "desktop bundle" (circa 2009) but not used until Oct. 2011. I'm running W7 64 bit Home Premium on a WD Caviar 1TB 7200 RPM, as system drive and data drive. I've confirmed that TRIM support is turned on.I should add that I ran the OS off the SSD, with FSX on the hard disk, for about 2 weeks, with TRIM turned on. There was no noticeable problem.I don't know what the controller is on the Kingston SSD, but I suspect what's happening is garbage collection. What triggers it is clicking on a menu or a DU; or pressing any keyboard key.I have deleted the FSX.CFG file and allowed FSX to re-create it (several times). The only edits I add are HIGHMEMFIX=1 and those required by REX.So, I'm at a loss. There is no firmware update for this model of SSD on the Kingston web site. Should I replace the SSD? Is there a way to suppress/delay garbage collection? In the Elder Days on LISP machines there was a way to control when GC occurred.Thanks in advance,dan "lensman" davisonSystem: Antec 900 case, 850W XFX PSU, Radeon 6950 2GB GDDR5, Asus P8X58-V-Pro mobo, 8GB Crucial dual-channel memory, CPU i7-2600K@3.4 GHz,

You are right. Norton Internet Security caught it. I'm confused because (1) I turned the AV off when I did the installs and re-installs as administrator, (2) I turn AV off when using FSX, (3) the date/time of quarantine doesn't correspond to when the installs and re-installs were done. (4) it didn't touch the performance manager, (5) E:FSX was on the "exclude" list as suggested in the NGX introduction. Oh well.Thanks very much!dan davison