fghdgdfdfgfgf

Glad I could help, sir. Lets get it on! :-)

I bet my grin is bigger than yours.

Well with my CPU/MOBO combo it takes me 1.45'ish to get 5.2 (that's no bs 100% stable). Also, I DO use C1E and Speedstep, so the only time my CPU would use that kind of voltage is under max load (brief periods of time) while running FSX.I have no idea what's safe, but I'm betting that under FSX situations (using Speedstep) that 1.55 (5.4GHz) is probably safe (based on my CPU experience). For 27/7 voltages, I'd probably run something closer to 1.35 ....anyway, if you find a definitive answer let me know. For the record: my default -everyday setup, uses 5.0 for turbo (max load is about 1.411). For what it's worth, I think the target voltage @ turbo is 1.392.

Well get it tuned Ryan! Don't sell your hardware short, man!

With much effort, and for your viewing pleasure, the community within this forum gives you this ---->FSX BenchmarksHigher FPS is better.FPS in the benchmark can be used as an indicator for the capacity of options that FSX can deliver with the given hardware.

Yeah, sorry 'bout the 2nd part of my post ...had some issues this mornin.

dbl post

Put your seatbelt on -absolutly.

Hi kleineMax,My 3.3 bench is valid -as per the benchmark specs. However, it's not a default I5 2500 configuration as I did disable the the cpu's turbo function. I posted the 3.3GHz score for reference purposes only.

Hmm ...maybe the posted Win7 64 averages are invalid? Maybe the 1st run scores better reflect actual FSX performance?Man, don't we love FSX!

Doods! I just ran the FSXMark11 on an XP Home (32 bit) OS. I must tell ya's the results are NOT in line with the Win7 64 bench results. Seems like the 32 bit system is not able to cache the bench mark like a 64 bit system with 8 gigs of ram can. For example, my 1st runs (of a 4 run series) with XP and Win 7 have very similar scores, however, where as the Win7 scores rise (as much as 30% over the 1st run) on runs 2 thru 4 the XP scores remain the same throughout the test.Is my XP setup wrong? <------ on same hardware as my previously submitted results.

Well, I'm just saying that based on the below FSX bench marks that the 580GTX is both underrated and overrated.The overrated:580GTX I7 860 at 4.2GHz link Vs560Ti Sandy Bridge at 3.3GHzlinkThe underrated:580GTX on a Sandy @ 5.2GHz linkVS560Ti on a Sandy @ 5.2GHz linkKen

I think the 580 shows it's muscle with FSX when you couple it with a Sandy Bridge at or near 5GHz.I also think the 560 is a better choice than the 460 for FSX.And .....you can't make up a video card's limitations with FSX by overclocking it.Ken C

I sealed the cover to my case 10 days ago with my cpu running 1.41 -turbo'd. Hell, if I had the need, and the cooler, I'd feel confident that my system would give me trouble free service @ 5.4GHz 1.54v.

All of my posted results were with the default MSI 560ti clock speeds:GPU 880MHzMemory 2100MhzShader 1760MHzNote: I've had this card bumped up to 1000/2450/2000 during FSXMark11 benchmark testing with no appreciable increase in FPS.

I'm certainly hitting a wall at 5.2 with FSX, but not with other benchmarks. Could it be that I'm reaching 'max headroom' with the 560? Maybe it's my memory settings, but a 10% hit? re: settingsI ran a series of tests for about an hour looking for anything that might limit the 5.2 bench and found nothing -I checked and double checked the FSX cfg., driver settings, disabled C states and Speed Stepping and even overclocked my video card. @DazzYeah, I too have wondered 'bout the clouds. FSX does not behave the same from run to run let alone session to session.

I figured I'd post this to compare and contrast the 5.2GHz that James posted.

Actually, it's a bios thing starting with 1305 on either the B2 or B3. Meaning, if you're still using the B2, like me, and update to 1305 you will not be able to flash back ...without major surgery.

It's a long shot but, I've had a similar experience. Try using the 4pin ATX12v cpu connector from the power supply, or the 8 pin if already using the 4pin.I dunno if it's my power supply or the motherboard, but when I experimented with the 8pin connector I got unexpected cpu voltages and the cpu would not turbo.

Just one other thing:I've been flying FSX (SFO is my home airport) since it was released and have gone through occcasional bouts over the years with this texture crash issue (mostly SFO at 19L and both 28's) and have often suspected the causes to be related to FSX Acelleration, EZdoc Camera (beta) and/or Rex runway and taxi textures.

I've experienced this very problem with the default SFO, Flightbeam and KBOS with my most recent OS and FSX install -since my Sandy Bridge upgrade. Although, I have not had any issues since I re-installed the FSGenesis West and East coast meshes and fine tuned FSX. One of the symptoms I was having during these rnwy threshold issues that I no longer see is a bouncy md11 and other sim objects at all of the airports I visited (FSDREAM Vegas and JFK; Fly Tampa-Tampa and KBOS, and of course the default SFO and once with the Flightbeam SFO. Again, I'm not sure what caused all of that, and I'm even less clear on why it all went away, but I'm all good now.Ken C.

Mr. Green,My guess is that you are running into a terrain texture. Why? Who knows? But, until you get it worked out you can try pausing the sim for a about minute while on final -at around 3 to 5 miles out- or until you're certain that all of the textures for the airport have loaded and are in place.Have you tried playing with the mesh setting?Is FSX dialed in ....Bjote dialed?If you use a mesh app, try reinstalling it, or put it atop the scenery library list.Finally, just out of curiosity, do you use a camera program like EZdoc?

Does FSX have an internal clock, if so what is it?Oh, could someone please point me to the FSX RedBull Reno Air race benchmarks?

Yeah. I'll get mine replaced as soon as the dust settles -probably go through Asus.