erick

Iris F-15E Mudhen Driver around Alaska. (most of which is really orbx's awesome Stewart, b.c.) Thanks Eric

Just a follow up if anyone else was having the same problem. ie: BSOD with PMDG at high detail airports! I believe I have solved the problem. As mentioned earlier in this thread, I thought setting the memory to XMP had helped but turns out it didn't. Problem persisted. After running Blue Screen View and determining that the problem was related to "ntoskrnl.exe". I reset my bios and disabled the overclock. Problem stopped but obviously I wanted to bring my cpu speed back up. I changed the multiplier to 44 instead of the previous 45 and set the v core back to 1.385, which it had been previous set at. So basically I just ended up downgrading the cpu clock a little. I did not change the memory (just set it back) which is running at 1600 - 9 9 9 24 @ 1.5v. I do NOT have XMP enabled and multistep LLC is disabled. So far it seems to have done the trick. I am now getting 4.4 very stable at that voltage after running Prime 95, etc. After a few test flights with the NGX at Fly Tampa and FSDT KLAX all is pretty good. No BSOD's so far. Fingers crossed. Just a side note, I also looked into pagefiles being a possible cause but have since determined that my set up is good. 3072-3072 on the os drive (ssd) and NO pagefile on the fsx drive or my storage drive. **One last thing, a big thank you to Word Not Allowed and his fantastic settings guide. Up until now (within the last few hours!) I have only had the highmexfix in my cfg. I bounced back and forth between Nickn and Bojotes tweaks over the last few years and ended up finding only mixed success. I had removed everything except the highmexfix. However, now that I am using the more demanding aircraft and scenery, Word Not Allowed's suggestion about the FFTF=0.1 and the affinitymask=84 (I have HT enabled!) have made a GIGANTIC difference in framerates. These 3 mentioned tweaks are the only ones I am using. Results - Before - KSEA (with Orbx pnw) in the NGX with UT2 at 60% and REX clouds at 2048 I was only able to get 20-24 fps during the take off from the VC. After 32 - 39 (locked at 39 because lower is too jerky and higher makes the AI planes fly and look funny!!) Amazing! Hope something in my long message may help some other hardware rookie like me. Thanks again Eric

Oh yah it was used. I did not pay anyone to OC it. I was actually going to get my friend to build me a rig specifically for FSX and then I found out he was selling his own personal system. That is what I bought. I got a great deal and it was only about 7 months old. Bought it 6 months ago. (paid $1500 with both monitors, win7, etc. and all receipts, pretty good I think!?) It has actually been fantastic. Now if I can just catch up in the knowledge department to match the equipment!! haha

Amazing set up TechguyMaxC! Here are 2 quick pics of mine. I absolutely love my Case. Sorta reminds me of "Portal!" I do need to get some better control devices after seeing all of your guys pics. Unbelievable! My little "Av8r stick" just isn't going to cut it!! haha Thanks Eric

Hi TechguyMaxC. Thanks for the reply. I will download that Blue Screen Viewer and post the results. Also my next move would be to disable the Overclock. Since I do have "touchbios" and can do it in windows, it shouldn't be too hard. However, I think I may have found a SOLUTION! On another thread at this site, "firehawk44" posted some advise to someone else with a similar problem and it may have solved it. His advise - ""My memory has a max frequency of 1600 MHz and I was trying to run my system at that frequency. But 1600 MHz only works when the BIOS profile is set from Manual to X.M.P. Manual profiles can only handle the lower frequencies as noted in the SPD Tab of the CPU-Z program"" I did the above and haven't had a BSOD since, no matter what the load or situation. Could be just luck but I will continue to watch. If I get another Blue Screen, I will begin the steps that you have suggested and report back. Thanks again, its really appreciated. Eric

Hi there My system specs are in my sig. I am running my i7 2600k at [email protected] vcore and memory is 8gb running at 1600. Now I have to be honest up front. I am a extremely proficient with FSX but from a hardware perspective I am a rookie. I bought my system used from someone who actually knew what they were doing. It was already overclocked and I merely picked it up, installed FSX and an insane amount of high quality payware and off I went. Now don't get me wrong, tweaking, be it the cfg. or inside fsx or graphic card settings, etc, I have done it all and bought the t-shirt. My problem is hardware, OS, CPU, motherboard, etc. I only know just enough to be dangerous. My system has been running perfect for the last while. REX with ORBX PNW at Orcas Island with settings cranked in any Carenado at any time of day, in any weather. Eats it alive, smooth as butter, and no crashes whatsoever. Lately though I have been using more commercial jets, specifically the PMDG ngx. I have been flying into places like FSDT LAX and Fly Tampa airports and as the title of my thread states, I have been getting the odd BSOD lately. I have been unable to recreate it though. It is strange because (while trying to figure this out) I can fire up the NGX, fly out of a Fly Tampa airport buzz around in Rex clouds above chicago, then land 20 minutes later and no problems. According to "realtemp" my CPU never goes over 50 degrees and my GPU never really breaks a sweat!? However, the BSOD's seem to have occurred when I stop using one aircraft and start a flight with another at another location. Ex. exiting the sim then switching from NGX to airbus X then loading another airport flying for 2 minutes, changing the view a view times and BOOM!!!! Blue Screen and complete crash. I have googled the "error report" and searched the forums and most seem to indicate a memory problem of some kind relating to voltage and possibly my overclock or ram, etc. This is where I get scared and start to feel out of my depth. Just say BIOS and I will run!! haha Since I did not do my overclock, would you guys maybe suggest that it may be a place to start looking or do you think I am on the wrong track? My motherboard does have "touchbios" which is not as scary to me and I was thinking that maybe I should reset everything to default then use the included Turbo Boost preset to bring my clock back up a little? I do know that my GPU came overclocked as well and was causing some instability at first. I used MSI afterburner and reset it to default. That solved those problems at that time and I was thinking that doing something similar this time but with the CPU might help get rid of those blood Blue Screens!? Any advice is very much appreciated. I am learning as I go but I have a long way to go in this area! Thanks Eric

Count me in as well. As I have just started up again with FSX after a long hiatus and I have just recently purchased some new add-ons. (UT2 and some others). However, as I am fully in support of this outlook, movement, statement, whatever you want to call it..... I am in!!Here is my little recipe for that day - Mix up some PMDG, add some FSDT, mix in some Orbx, a dash of Iris, a sprinkle of Fly Tampa and I'll top it off with a little Carenado! OK maybe I'll have to leave out some ingredients as funds may not permit, but it will be a good cake.

Hi DanielThat is funny! Many years ago, I was using the original Ultimate Traffic and I was standing outside on a carrier deck (original moving carriers program of some sort) As I stood there admiring one of Dino's F14s or something, a British Airways 747 slowly passed by me about 200 feet away on the surface of the ocean at exactly the right height of a boat (even creating a wake!!) It was the strangest thing and had me thinking I had just been doing a little too much flight simming! lolEric

Hi guysThanks for the replies. It appears Frank ruffled a few with the .cfg comment! haha! I have always tweeked my .cfg in the past with FS2004 and FS9 even with FSX on my last system a few years ago. The thing is, I tend to lean towards the sentiment that you can "buy smoothness but not tweek smoothness". That is why I got this machine and for the most part, I have been right, in my "much less than expert" technical opinion. Out of the box, it performs like nothing I have every seen. In my 15 years or so of doing this, I have never experienced performance like I have now. It's just the small things that are tricky and I think that maybe some (key word - some!) tweeking can help. The problem is my addictive personality and my desire for perfection (which I am certain many in our hobby possess!) I don't just stop at one tweek, I do everything, test, do more, test, and finally I realize I may have done too much!!!!! haha Long story short, after posting last night, I continued playing around and was able to fix my problem about 95%. I lowered my in-game AA to 50. It has maintained my terrain smoothness and overall fluidity and it has made the AI planes fly smoothly. (There was a lot of testing involved!!) As for FS Recorder, I changed the "recording interval" which I had set to the max of "1 frame" down to "1/8" and it made a complete difference. Smooth recorded "traffic". I also think the lower setting of 50fps in game helped that as well. Anyway, I think I am pretty satisfied at this point. Smooth AI and killer fps. For the record, the only tweek in my .cfg is the "AI sound improvement" by Bojote. Sound lod=1. Also the texture max load= 2048. That's it. I am throwing away the key and never opening that .cfg door again. Well....... that is until I install UT2!! hahaEric

Ya they are strange. Its just that I know the power is there, something is just not working right. For example if I am in slew mode the AI are perfect and smooth or is I lower my FPS limit to 59 instead of 60 they are much smoother. Not at 58 though then they jerk again!!? 56 is good but, 54 is better!! I mean it is just crazy, I can't understand how they work. I am about to purchase UT2 but I am holding off until I get this sorted. Also, I just love FS recorder and I can't seem to get the AI versions of my plane to not stutter. It doesn't seem like a lack of frame rates either. If anything, its the opposite. TOO MUCH POWER. Like fps spikes rather than delays. They want to surge forward. Now I understand that the more consistent the fps, the better, but it doesn't seem to follow what I am seeing on the screen as far as my fps counter. It is pegged solid at 60fps (maybe 60.2 here and there!) but the AI are doing there seizure thing anyway!?.....so weird. I guess I am just hoping that someone has an idea. Something simple....like "oh, just enable LOD clamp" and presto, its fixed. I guess I can dream, right!

Haha Thanks FrankI have already reverted back to stock .cfg and gone back to in-game 60fps limit, aa, ansitropic. It''s all good again, except for those pesky epileptic AI. There has to be a simple fix, I just know it!?!!....... Ideas anyone?

Hi thereI have been a longtime lurker around here. I have recently gotten back into Flight Sim after a long hiatus. I have been doing this a long time but I am just now getting back into it with a new system and a steep learning curve. Could really use some help right about now. I have exhausted all search functions on all forums that I can find and it is becoming a bit of a merry-go-round!! Too many contradictions and now I just feel like I am "going fishing with dynamite" as my original issue was not that big.My system - i7 [email protected], Z68x-UD3H-B3, MSI GTX560Ti Hawk OC@950mhz 1gb, G.Skill Sniper 2x4gb DDR3-1600, OCZ Vertex 2 60gb SSD, 2x1TB wdc Black, Antec Kuhler H20 920 Cooling, OCZ Memory Cooling, Cougar 700CMX 700w PS, Corsair 600T White CaseMy basics - FSX Gold sp2/accel (FSX on 1tb dedicated drive, win7 on ssd, 2nd drive storage) - REX, Orbx, Aerosoft, Iris, DBS w/f, etc,etc. - Setting mostly high to max - Resolution - 1920x1080 on a 24" Asus monitor - Tweeks - Well, there in lies the problems!!My problem - At first, none really, then I started to fiddle!! haha (basically Jerky AI planes in game and using fs recorder)My initial setting where pretty basic. A stock .cfg (with 2048 max texture for REX, etc. and thats about it) and using some of Nickn's advise but found my system worked best with unlimited frames (no nhancer/inspector) AA set in-game, ansitropic in-game and mostly "application controlled" settings in the nvidia control panel (NO v-sync). These setting provide 100+ frames and amazing smoothness. That is until I encountered some heavy REX clouds, then BOOM, it all went sideways. My gpu overheated and shut down with a black screen! After some research, I discovered that limiting the frame rates in-game to 60 solved this problem. It did create another problem though. Screen tearing. To solve this, I enabled (v-sync force on) in my nvidia control panel. Problem solved. Everthing was great for a bit. Smooth, no problems, etc.Then I encountered traffic. The "AI" did nothing to my framerates as my machine is a beast. The problem was that the "AI" looked like they where having an epileptic seizure. Forward and backward lunging and stuttering like crazy. I also installed FS recorder at about the same time I noticed this. Using that program and "record as traffic", the problem was even more pronounced. This made me crazy and I looked for a fix. The fix I found was that if my limited the FPS (in-game) to 30, problem solved. No more "seizure AI". New problem though!!! Now my terrain was stuttering!!! This is where I began to research BOJOTE and all of his fixes and tweaks. I decided that maybe I should use an external FPS limiter and run my .cfg through his nifty little website device. I proceeded to install Nvidia inspector and send my .cfg through the Bojote tune up shop. I also limited my FPS to 30 using the new nvidia inspector.Well that brings me to the present. After doing these last few tweeks, I fired up FSX and discovered that it was running like absolute CRAP!!! Barely able to make 25fps stable and jerking like 1920's black and white movie!!!!!!!!!All of this, just so I could make a little AI airplane stop jerking a little bit. I literally took a machine running FSX at over 100+ fps steady with sliders maxed and reduced it to a crying sad shell of it's former self.I believe there is a lot of value in the tweeks from people like Bojote and Nickn. The problem for me has been the contradictory info and opposing views but mostly my impatience for a fix for the AI problem. I am lost in the middle somewhere and only because I want to fix a VERY SMALL problem. Like I said at the beginning "Fishing with dynamite!".Sorry for the long read. If anyone has been patient enough to read all of this and could point me in the right direction, I would be eternally grateful. I am honestly lost. All I want to do is smooth out the "AI" visuals and maintain my 60fps limit with AA and v-sync enabled. Also be able to record some video with FS recorder and have smooth AI. I know my machine has the horsepower but I just think that there has to be a simpler way to get the AI to fly smooth without limiting the frames so much, or do all this tweaking OVERKILL!!Thank you so much for reading and any input is greatly appreciated.Eric