Ditto, and also for FSX. I was using a Kingston SSD but it didn't set me on fire tbh.Arjen, I get the FR's you speak of (except in very heavy payware airports) I have everything in FSX maxed out all the time bar water which i have set at 2x high. I use ASE, ORBX and GEX.I notice you have a slightly lower CPU speed. I'm afraid that with FSX, for the most part, and when all is maxed, it is a bigger CPU that will give you consistently higher frame rates. I have mine at 4.9 and stable now and it's good. It still has issues though, and tbh, I'm not that into frame rates any more; it's a losing battle lol. it's smoothness I'm after now. If I can have a really smooth flight, relatively low down (I get >60FPS in crz but that's not a good reference point imo) with Ryan's Nvidia Inspector settings at around 30-40FPS I'm happy.Don't get hung up on frame rates; you'll die trying lol

Yeah you're right. It's a loosing battle. I would be happy if my FPS wouldn't get under around 30-35. But mostly I get around 30 fps on add-on airports, and round 45 on default scenery. 25 in the worst cases. But one big problem though, when my mouse cursor is displayed I get around 25% less FPS, never had this with my previous GPU. Any one else noticing this?ALso, I'm trying to get my CPU to 4.7 GHz, but it just doesn't want to run stable at 1.35V. Have had 2 BSOD's so far with that. In the past it's been running at 1.35V and 4.5 GHz perfectly stable for 3 months. 1.35V is already a little high for 4.5 GHz. And now I need 1.37V for 4.7 GHz. Seems a little high to me, or is this normal?

Seems a little high to me, or is this normal?

Hmm, well I have an i7 2600K using the X.M.P profile in my mobo BIOS and pretty much standard OC settings (raised multiplier to 49 and using offset Vcore) my Vcore regularly jumps above 1.55 (!) when I'm running FSX but my CPU never goes hotter than 60deg (Water cooled). I have a channel into Intel as we are resellers of their servers and I've spoken to the nerds there who say if it works, and it isn't running consistantly above 75deg then it works! No warranty implied, however lol!A very good resource for ASUS boards is http://rog.asus.com/forum/showthread.php?2161-ASUS-P8P67-Series-Overclocking-Guide-and-InformationRead the bit about the percentage of CPU's that can reach the higher speeds; seems it varies even in the same CPU type. Very useful read if you have aan ASUS mobo.Keeping this NGX related, though; I find NGX to not be as bad a hog as I was fearing. Not having used any previous PMDG planes I have nothing to compare, but it loses me c. 5fps in heavy payware airports, I reckon..

Hmm, well I have an i7 2600K using the X.M.P profile in my mobo BIOS and pretty much standard OC settings (raised multiplier to 49 and using offset Vcore) my Vcore regularly jumps above 1.55 (!) when I'm running FSX but my CPU never goes hotter than 60deg (Water cooled). I have a channel into Intel as we are resellers of their servers and I've spoken to the nerds there who say if it works, and it isn't running consistantly above 75deg then it works! No warranty implied, however lol!A very good resource for ASUS boards is http://rog.asus.com/...and-InformationRead the bit about the percentage of CPU's that can reach the higher speeds; seems it varies even in the same CPU type. Very useful read if you have aan ASUS mobo.Keeping this NGX related, though; I find NGX to not be as bad a hog as I was fearing. Not having used any previous PMDG planes I have nothing to compare, but it loses me c. 5fps in heavy payware airports, I reckon..

Ok then. I just read that it can be normal that some CPU's might require more power than others. As they are not all the same. Some might need 1.33, mine needs 1.37V. But about your CPU, 1.55V??? OMG! You must be really unlucky with your CPU that it can run stable at 1.55V only? I shoud run stable at around 1.4-1.42V. I would never go above 1.45V! Don't you have BSOD's?And yes, I think this is NGX related. Because the "goodness" of my PC affects the way that I can enjoy the NGX. It's not my fault that the NGX is such a masterpiece!

I shoud run stable at around 1.4-1.42V. I would never go above 1.45V! Don't you have BSOD's?

Nope. I do at >5 though. I haven't set my Vcore to that; the mobo does it when it needs the juice. I think it's set at around 1.4; I'll reboot and have a look. Shame I can't screenie my BIOS :)I tried limiting the offset to .05 but I got BSODS! Go figure..I have turned off HT as well (but only yesterday; still seeing what happens - apparently this is good for FSX; anyone?)I'm sure my CPU will explode at some point, and I wouldn't recommend this kind of abuse; I have a ready supply of CPU's though :Nerd:so, with offset and turbo mode enabled, it "ramps" up the power when asked by an app like FSX (bit like 27k bump TO LOL)

Nope. I do at >5 though. I haven't set my Vcore to that; the mobo does it when it needs the juice. I think it's set at around 1.4; I'll reboot and have a look. Shame I can't screenie my BIOS :)I tried limiting the offset to .05 but I got BSODS! Go figure..I have turned off HT as well (but only yesterday; still seeing what happens - apparently this is good for FSX; anyone?)I'm sure my CPU will explode at some point, and I wouldn't recommend this kind of abuse; I have a ready supply of CPU's though :Nerd:so, with offset and turbo mode enabled, it "ramps" up the power when asked by an app like FSX (bit like 27k bump TO LOL)

Alright, this is really worrying me now. I have ran Prime95 for 2 hours and got a BSOD. 4.7 GHz and 1.37V. At least it runs longer than with 1.35. I think I'm also a little unlucky with my chip. I'm getting the "uncorrectable hardware error" BSOD.Can't these BSOD's damage my hardware? I think I should just roll back to 4.5 GHz and 1.35V. Has always ran stable.

I think there is your problem though..if you read that doc, they say (or I read) that the higher the clock, the higher your Vcore needs to go. Not all the time, but when it needs the speed.I only have an i7 so I can only comment on that, but as I said before; limiting my Vcore range through the offset value, rather than leaving it at the default, caused BSODs. It didn't have enough power for the chosen setttings/clock when stressed.Read through that post from the ASUS jedi (all of it) and then googlise the same thing but with your board and CPU and just experiment. Heat will kill your CPU quicker than anything, and the board I have has lots of very spoddy but good heat reduction settings like Digi+VRM, Phase cycle; Duty cycle and all sorts, all of which can be tweaked to allow those kinds of Vcore without extreme heat and instability. Having a water cooler helps too..ALC one; best £50 I ever spent!

Hi,Finally have rig that is on top of the notch for FSX. Really quite happy with the performance. But I'm just wondering if I can still get more out of it. You can see my hardware specs below.In heavy circumstances (Aerosoft Airports like EHAM, LFPG...), with bad weather, maxed out scenery with UTX, GEX, REX, in the NGX, I'm getting around 27-30 fps on the ground. And around 30-35 fps in the air, around 40-50 fps in cruise. A few bad things I"m noticing though, is that I'm still seeing stutters, but I think that's because of my HDD. What's the recommend HDD for FSX (a one that is not too expensive?). Or is there another way to reduce stutters (without an FPS limiter, because 30 fps is just not it yet. Above 35 fps I'm really happy.)I've got a tweaked FSX.cfg, with UsePools=0 ( I always use this as I'm seeing much better performacne than with UsePools=1, never understood the point of Bufferpools, so what does it actually do?) Also have HIGHMEMFIX=1, TEXTURE_MAX_LOAD=4096, AffinityMask=14 etc.Just wondering if I can even get more out of it.Thanks!

If you can, go for a much faster HDD. That 5400rpm is a bit on the slow side.7200rpm is is min. Rest of the specs are upto the benchmark.

I think there is your problem though..if you read that doc, they say (or I read) that the higher the clock, the higher your Vcore needs to go. Not all the time, but when it needs the speed.I only have an i7 so I can only comment on that, but as I said before; limiting my Vcore range through the offset value, rather than leaving it at the default, caused BSODs. It didn't have enough power for the chosen setttings/clock when stressed.Read through that post from the ASUS jedi (all of it) and then googlise the same thing but with your board and CPU and just experiment. Heat will kill your CPU quicker than anything, and the board I have has lots of very spoddy but good heat reduction settings like Digi+VRM, Phase cycle; Duty cycle and all sorts, all of which can be tweaked to allow those kinds of Vcore without extreme heat and instability. Having a water cooler helps too..ALC one; best £50 I ever spent!

Yeah I know what I"m doing when overclocking. I'm using manual mode at 1.37V. I now try 4.6 GHz and 1.37V. But I'm just afraid that those BSOD are causing damage to my hardware. Or is it no problem is this happens?Also, temps are not a problem, my max core temp is around 65C.

If you can, go for a much faster HDD. That 5400rpm is a bit on the slow side.7200rpm is is min

Ooh..didn't see that. That will bottleneck your system. I know it's a texture thing but it all goes up the system bus in the end and if FSX is on a slow (and 5400 is way too slow) then it will slow the whole machine generally.But Arjen, remember: the ASUS ninja also says that only 10% of retail CPU's will go above 4.7Ghz and only 2% above 4.9 (mine is actually a grey OEM import from Thailand I bought on the bay of E, so that shoots that one out of the water) so your CPU may just be at its limits..try raising your Vcore above 1.4As for O/C BSODS, again, it's rare for them to cause real damage if your temps are low, as in the most part, they are caused by the software reacting to "faulty" or in your case overclocked hardware. It's too much to deal with it all without having a hissy fit as it can't get the power it needs and shuts down. Note: this does not apply to most BSODS as they can often indicate faulty hardware. GPF's and CTD's are usually software related, although when I was running at 5Ghz I got lots of ntdll.dll errors in FSX which is the system corrupting data on the HDD' s as it is just too freaked out. Again, this will mess up your HDD and windows/FSX install if you keep it up.I guess If you ran it too high for too long with BSODS all the time you'd eventually burn something out, but these boards are so much more robust than they have ever been. Heat is your enemy. All you're doing when raising Vcore is passing more power through the CPU with the direct result of it getting hotter. It needs this extra power to raise the clock when asked to by the system load (if you use turbo mode) The theoretical limit of your CPU's ability to overclock is limited by the amount of heat it can deal with when the Vcore speeds are very high, and still boot into Windows..I like tweaking, and going from 4.4 to 4.9 gave me c. an extra 10-20fps overall I reckon (your results may vary, I have an i7 remember)But even I get very faint stutters sometimes so there we go...and slight pauses every three seconds or so..for about a third of a second..so it's endless lolAlso, do you use the BIOS or the Windows util to O/C?

Edited January 22, 201214 yr by quadraspleen

And use Vcore automatic + offset mode (leave value at default)That's Offset+ rather than offset- + raises it and - lowers it (both on the fly)

Ooh..didn't see that. That will bottleneck your system. I know it's a texture thing but it all goes up the system bus in the end and if FSX is on a slow (and 5400 is way too slow) then it will slow the whole machine generally.But Arjen, remember: the ASUS ninja also says that only 10% of retail CPU's will go above 4.7Ghz and only 2% above 4.9 (mine is actually a grey OEM import from Thailand I bought on the bay of E, so that shoots that one out of the water) so your CPU may just be at its limits..try raising your Vcore above 1.4As for O/C BSODS, again, it's rare for them to cause real damage if your temps are low, as in the most part, they are caused by the software reacting to "faulty" or in your case overclocked hardware. It's too much to deal with it all without having a hissy fit as it can't get the power it needs and shuts down. Note: this does not apply to most BSODS as they can often indicate faulty hardware. GPF's and CTD's are usually software related, although when I was running at 5Ghz I got lots of ntdll.dll errors in FSX which is the system corrupting data on the HDD' s as it is just too freaked out. Again, this will mess up your HDD and windows/FSX install if you keep it up.I guess If you ran it too high for too long with BSODS all the time you'd eventually burn something out, but these boards are so much more robust than they have ever been. Heat is your enemy. All you're doing when raising Vcore is passing more power through the CPU with the direct result of it getting hotter. It needs this extra power to raise the clock when asked to by the system load (if you use turbo mode) The theoretical limit of your CPU's ability to overclock is limited by the amount of heat it can deal with when the Vcore speeds are very high, and still boot into Windows..I like tweaking, and going from 4.4 to 4.9 gave me c. an extra 10-20fps overall I reckon (your results may vary, I have an i7 remember)But even I get very faint stutters sometimes so there we go...and slight pauses every three seconds or so..for about a third of a second..so it's endless lolAlso, do you use the BIOS or the Windows util to O/C?

Hey thanks for that reply. That made me a little less worried. I think I'm running a stress test for 4.6 GHz tomorrow at 1.37V. I hope that works. Before, when running at 4.5GHz, I never had problems for three months. Until 2 BSOD's recently with a "CRITICAL_OBJECT_TERMINATION" error. I scanned my HDD for virusses and found 4 virusses. All four called "Exploit:Java/Blacole.XX" (XX indicating letters that varied in the 4 virusses.). After this it worked fine. I ran a test in Prime95 last week for me 4.5 ~ 1.35V overclock, after 12 hours I stopped it and there were no errors* that means it's good. Right now, I'm just trying to take it up a little higher. I don't think it's making much difference though, because I only got around 2 fps more, lol. But all bits help.

Edited January 22, 201214 yr by arjenfsx

And one last thing before I crash (not literally obv.) At rest (like now; typing on a BBS and not running lots of stuff), CPUID reports me as having a 1600Ghz CPU! When running FSX and ASE and REX and etc etc it's 4801 all the time. I only get a >1.5 Vcore warning every five mins or so (highest being c. 1.579)