ALF1

Thanks Dan

Not overly impressed based on the youtube video. I did not hear any sound when they turned the Fuel Pump on. We can't hear anything on the hydraulic systems. And nothing is heard on equipment cooling and high N1 cruise engine sounds. Basically it is just the same switches sounds a bit accentuated.

Ahhhh!!, Thanks so much Paul. And or else it is the master or engaged command system A or B which becomes automatically the master that provides the clues correct ? One last question: Back from old school the flight Director the brains and the autopilot the muscle, but in small piston we never did dual channel autolands. What happens exactly when dual channel autoland engages at 1500 RA I believe and both masters, which FCC flies the airplane ?

You guys are not answering my question. Please see my not being clear on the FCC providing clues for the FD when both nav radios are tuned in to ILS. I THINK that the master provides clues unless both masters are active with both A and B systems engaged but I am not sure.

SPOT ON!!! GREAT THREAD!! I want to thank both the OP and Rostyslav for enriching my knowledge today. I had never flown an ILS from the F/O side. With only the NAV1 frequency tuned into the ILS, VORLOC and GS arm in the FMA's, because the airplane is still flying other roll and pitch modes. Notice however that during this time the VORLOC and GS triangles in the PFD are not shown in the F/O side PFD. As soon as CMD A goes into approach mode however, the FD and FMA's in the F/O side disappear. Now tune the ILS frequency in NAV2 radio, everything back to normal. Except that now channel B is providing FD clues for the F/O side. Learn something every day. EDIT: I want to ADD to this post instead of correcting what might be a wrong last sentence. This for knowledge base reasons. It appears I am still a bit confused and would like further enrichment. So now that we have the ILS freq. tuned in NAV2 radio, is the FD on the F/O side now receiving clues from channel B ? or from the MASTER channel ? Then, what happens during DUAL CHANNEL AUTOLAND with both CMD A and CMD B engaged ? is each one independent and the aircraft flying from which FCC ?

I see what you are saying. My wideaspectview was false. Set it to true in the fsx.config and the result at .76 zoom is very nice, better than .32 and false. Here is a view. Capture

This does not cut it and I am using Ezdok. Correct me if I am wrong but any zoom setting has to go with a seat depth position. The virtual cockpit does not work, I cannot operate anything as the little hand is not available.

Kyle, what are your recommended settings ? Maybe .40 ? although when I pan around the cockpit I stumble on a few things because I am actually leaning behind the seat rest.

Go for zoom 0.31.

Check my thread "Blue Screen after 15 minutes." These guys especially Jim helped me get to the root of the problem. I updated all my drivers, least of which and hardest to do is the BIOS--you can probably fix your problem without updating the BIOS. I purchased DriverAgentPlus, and it does a scan of your system and you can download and update the outdated drivers very easily. Then, you can monitor your core temperatures. I am now almost 100% sure that my unstable overclock was the cause of the problem. According to tech inferno real temp, some core temperatures shot suddenly from 49 celcius to over 70 celcius. I lowered the overclock in the BIOS as per Jim´s guidance and videos, and lowered the voltage too. Since then, temperatures at the most demanding moments during FSX seldom go above 65 celcius and if they do they read much smoother with no spikes. I think, but I am not sure, that those spikes in temperatures are signaling an unstable system. I now run 4.6GHz on 1.25 Volts with absolutely no problems. P.S., As Kyle says, there is no such thing as too much airplane. The NG consumes about 700,000K of your available 4 Giga for FSX, or about 17.5% of total available memory, and would result in an OOM instead of a BSOD. Further, the airplane would not be to blame as it is the SUM of all your goodies running that causes the overflow. You can download Process explorer for free and see how much virtual memory you are running for FSX. The more scenery, airports, traffic etc etc. you have active, and an OOM is coming. It will not be a BSOD. The NG is software, and BSOD is a hardware issue as Jim and others have stated.

Hey guys, I really appreciate the input from all of you gurus. Paul, it is nice to see those settings as they are my next step if my 4.6 with 1.20V yields more BSOD's....so far so good though. Jim, I have downloaded and installed ALL driver updates available subscribing to Driver Agent. The only thing pending is the dreaded BIOS upgrade. I finished the NVIdia upgrade to the 368 drivers, and wanted to share my settings since they yield a SWEET!!!! graphic presentation and very smooth. This with the GTX 780Ti. You have to enable anisotropic and antialiasing in the FSX graphics section. [url=https://flic.kr/p/KDuoWd]

And you have verified that the speed brake is not armed in the cockpit ? Sorry dumb question but just make sure. Then we'd have to see what is arming it.

Did you arm APP in the MCP ? if so, what were our white indications for roll and pitch mode in the FMA´s ? Sometimes when you arm APP, FAC and or G/P show up instead of VORLOC and G/S, then your aircraft while still in LNAV turns the wrong way while you think it is going to intercept your localizer.

I have a Corsair AX 850I. I have lowered the Core voltage down to 1.20V and the system runs even cooler in FSX--no problems so far. temperatures don't go over 60 celcius. I have 4.6 GHz. I must have a good overclocker in this particular unit. As I lowered the voltage FSX seems to be running smoother at the same frequency but lower voltage. I plan to fly with this setting for a very long time--a full month many flights in all kinds of weather. If it holds well, I might try bumping up a bit but I will never ever go over 1.30 volts again. I don't know what the heck they were thinking when they did that.

Dan, why don't you get the Paro Buthan airport scenery ? you would enjoy it. You go to a fix TAKTI FL160, come on down towards Paro VOR, go over the airport at 11,500. If you see the airport, you go for the approach, if you don't you bingo. The whole procedure from then on is visual, you use the mountain ridges, the river, the temple, the roads--all ground reference maneuvers. Getting out is the inverse--same way you got in. Lots of fun.

More news, I fired up FSX and made what had thus far been an unforgiving flight to KSEA loaded with ORBX scenery and T2Gate KSEA. Sunshine and clear skies in Seatle this morning , but even as I approached the airport the highest temperature recorded with the new settings at 4.6 GHZ was only 69 Celcius, and no air conditioner in the room--about 26 Celcius ambient. The performance hit is a bit noticeable but with that scenery nothing is enough. If this runs stable for a good while I might try pumping up to 4.7 GHz and 1.35V, though I have seen from ASUS that there is almost no way to cool over 1.30V adequately. Thank you Jim for pushing me to do this. I am gaining confidence. Capture

Jim, I got another BSOD so I took the courage up to access the BIOS and found the modification on "last modified" in July 2014, where I found this BIOS MOD So I went ahead and only messed with two things: Instead of the 48 went down to 46, and in the manual core voltage brought it down from 1.40 to 1.30, and saved the changes so I now show this in Realtemp: Capture Obviously I have the computer up and running with browser writing this but before I load it with FSX wanted to ask you if this wont break anything. If I get more BSOD's naturally my next step is to lower some more. I watched the video you suggested and others, and learned that for each 100 MHz you bring down you can bring voltage down 0.05 so that is what I did.

Many thanks Jim !!

:bad:Yes Jim (SIGH!!) , I had it done from Cyberpower PC where I bought the computer. It came that way and has worked flawlessly for over 2 years now. I have been doing more reading and see that this is an abnormal overclock and this processor runs very hot. I also read that in all likelihood they used 22 celcius as ambient temperature for the OC, and I have been flying here at 26 celcius. So I turned up my air conditioner to get 22C ambient, separated my Tower from the wall some more, and surprisingly the same flight same weather and airplane with this ambient temp now yielded the following temperatures: Capture Luckily no issues, but it is too early to tell for sure. I am sorry Jim if I made you waste your time, hopefully this thread will be a reference to other folks. If I have any more BSOD's I will report back after I change the overclock. But just wanted to show what a difference in core temperatures I obtained with the difference in ambient temperature and better breathing by the case. P.S. I mentioned in post #9 the 4.8 GHZ overclock.

Before I update the drivers, I want to show this. The second core always runs hotter than any. I was able to complete this flight however note that at 18:28 first three cores spiked at the same time, with the second at 79 celcius. I am nonw almost certain that it is one of these spikes above 80 that causes the BSOD. I want to mention also that the second core jumps from 49 to above 70 in the readings--there is no 50's or 60's in between while the others might be there. Why is this core running hotter ? I also want to mention that I have absolutely no experience tinkering with overclock or the BIOS, and feel very uncomfortable doing it. Any help would be appreciated. Capture

I checked my temperatures using tech inferno on a flight that I was able to complete. The first two cores always ran hotter, with the second one the hottest peaking out at 75 celcius. I am sure that on other flights the scenery has been more demanding with more weather. My Haswell I4790K is OC'd to 4.8 GHZ with a core voltage of 1.40V using CPU-Z I am going to work on updating my drivers like Jim suggested. I ran the system checker for corrupted or missing files and everything is up to date.

I have all my sceneries and airports checked in the scenery library. Do these all load no matter where I am flying ? I am going to try unchecking and leaving only what I will use. EDIT: that did not work, unchecked everything and still the exact same issue. Thanks for the memory and overclock tip. I wanted to see if something could be done before I mess around with the overclock.

Jim, I have not done anything of what you suggested because the system ran fine for a good while. And before I have the overclock loaded, I wanted to see if with these bugcheck codes maybe you can pinpoint to the problem easier. I suspect of a USB. Sorry to come back to this but maybe you know exactly what is going on with this ? As you can see, it involves all 0124 and the same driver .exe [url=https://flic.kr/p/LhCUFH][/url

Turning green Vernon !!!!

I have had it from day 1 with FSX. WONDERFUL!!! This is really a piece of software that you need to toy with and learn well, it will make all the difference in your sim experience. Enjoy yourself through this process. Basically what I did, is get a front view from the Captain's seat (which I have to tweak from time to time depending on where in the globe you are flying), and other realistic views from the captains seat towards the CDU, Radio panel, overhead panel, mcp etc. Do the same for the First officer if you want to fly from the right sometimes, I also have a view from the jump seat. Enable the zoom with mouse wheel for these views. Setting up your outside views and world views is another story.