>I know Chuck had some problems getting it hooked up but, I>can assure you it fits. I didn't have the ability to get a>pic of it when he was working on his system and it's kind of>tough now the way my system sits in my desk but, at least you>can see it in place.>>Regards,>Jeff>I see it, but for the life of me I have no idea how you did it. I spent an entire evening trying to get that bloody thing in, but it just didn't sit high enough on the CPU to clear the fins. Jeff, I think you had that photo dusted by I.L.M. :-)

I have read this entire thread and can't for the life of me figure out how I could adapt these settings for my rig. I started to play around with OCing the memory and now I'm getting OOMs on short final every time. I just backed everything off to Auto and will be landing at EGLL in about 40 mins.These OOMs started right after I installed FSDream Teams KJFK, KORD and Zurich, too, so it may be them. (I hate auto installers on scenery.)

>>I know Chuck had some problems getting it hooked up but, I>>can assure you it fits. I didn't have the ability to get a>>pic of it when he was working on his system and it's kind of>>tough now the way my system sits in my desk but, at least>you>>can see it in place.>>>>Regards,>>Jeff>>>>I see it, but for the life of me I have no idea how you did>it. I spent an entire evening trying to get that bloody thing>in, but it just didn't sit high enough on the CPU to clear the>fins. Jeff, I think you had that photo dusted by I.L.M. :-)>>:-lol :-lol No, nobody at ILM would answer the phone yesterday. Just a low res cell phone cam pic. It took a bit of contortion to get that pic. There's just enough room for me to get my arm in next to the case, the way it is enclosed in my desk. "I have read this entire thread and can't for the life of me figure out how I could adapt these settings for my rig. I started to play around with OCing the memory and now I'm getting OOMs on short final every time. I just backed everything off to Auto and will be landing at EGLL in about 40 mins.These OOMs started right after I installed FSDream Teams KJFK, KORD and Zurich, too, so it may be them. (I hate auto installers >>on scenery.)"A couple of things Chuck. One is that you have 4gb of RAM. You won't be able to get quite the same results. Another is our system's are quite different except for the MB. I've read a number of threads about that particular scenery causing problems for some folks. You might try in a different area, areas that aren't too hard on the frames, to verify if it's memory or scenery related. If that is the payware Heathrow, you may have some problems there too as it is a pretty tough area for FS also. I'll try to help you out if I can.I'd bet it's the scenery. Most of the OOM errors I've experienced have had nothing to do with the actual available memory but, more to do with how FS is using it. You see OOM errors when FS tries to access more than 2GB of process space and it's not setup to use more than 2GB. That's why, as you noticed the other day, you can just move the error box aside and keep flying. It was a momentary thing where FS tried to use a memory address that wasn't available to it.Best Regards,Jeff

Thanks, Jeff. I had no problems until I installed those 3 airports which came as a "package" of buy 2, and get the 3rd free. I've been to their forums and there are several posts about OOMs there, and tech support is pretty unsympathetic. They say they test their sceneries on a fresh install of FS9 and never have any problems. Well, duh. :-) I'm playing around right now with some of the settings you posted above along with the /4(!) Gb switch, and I just got my first BSOD so I need to go. But I'll post again in a day or two because I'm not really sure where my H/W should be to maximize it's performance and I've already learned a lot here. (I've been reading all of Nick's posts too -- He's been a busy beaver lately here, hasn' he?)As in the past, thanks for your help, oh "Great Master of the mythical Zalman Fan."

Good evening Jeff. Thanks for your help late last night/early this morning. I can't believe we were posting back and fourth at such an early hour. I ended up actually falling asleep in my chair in front of the compter after I changed my BIOS settings again then tested FSX and started a Prime95 test. Of course my girl friend, who was already in bed thinks I am crazy for staying up so late tinkering with a computer, they just don't understand.Anyway, here is what I set and the results.FSB at 400FSB strap to NB 400DRAM at 1066CPU Voltage 1.25vNB Voltgage 1.45vDRAM at 2.1vI actually had the NB set all day at 1.49 while I ran a P95 test since this morning, but just before I typed this I went in and changed it to 1.45 and am running another P95 as we speak. The P95 that I ran all day seemed ok. Temps never got above 49 degrees and stayed around 45-46 all day under load. I didn't get any errors. Since I changed it back to 1.45 we shall see. I hate to have to run another P95 test since it consumes so much time.BTW, I tested FSX with the FSB Strap at 333 and 960 ram, and FSB Strap at 400 with 1066 RAM, and in FSX it seems to be smoother and faster with it set to FSB NB at 400 and 1066 ram. In fact, all day when it was on P95 it was set at 400/1066.So, I guess after a few days or weeks after the burn in period we shall see how it stands up. If no problems I would consider my self lucky that this was so easy and was able to get a good stable over clock with not much and no system crashes. Thanks for all the help. I will post again in the next week or two and let you know how its been.Regards,SeanPS - Shame our teams lost today. Broncos are my favs since the days of Elway, Sharpe, Terrel Davis, etc., but living in Dallas I am also a Cowboys fan and they stunk it up today :-(

Good to hear from you Sean. I started checking CNN to see if any houses exploded in Dallas in the middle of the night. :-lol Your numbers look pretty good. If 400/1066 is what you like then, go with it. I'm actually doing some more testing as well. I seem to have found a sweet spot with my mem at 4-4-3-10. Fast and smooth is good, assuming your textures are crisp and clear. Tighter timings will clear up the blurries and the snapping into focus that you may see. We'll save that for down the road though. I've never been a big Cowboys fan but, I am even less a Redskins fan! Tough loss. KC just put an ol' fashion whoopin' on us in the second half. My boys are the Patriots though. I grew up back there. My season ended in week 1 when Brady went down.:-bang Anyhow, let me know how it goes. See Ya!:-wave Best Regards,Jeff

>Thanks, Jeff. I had no problems until I installed those 3>airports which came as a "package" of buy 2, and get the 3rd>free. I've been to their forums and there are several posts>about OOMs there, and tech support is pretty unsympathetic. >They say they test their sceneries on a fresh install of FS9>and never have any problems. Well, duh. :-) >>I'm playing around right now with some of the settings you>posted above along with the /4(!) Gb switch, and I just got my>first BSOD so I need to go. But I'll post again in a day or>two because I'm not really sure where my H/W should be to>maximize it's performance and I've already learned a lot here.> (I've been reading all of Nick's posts too -- He's been a>busy beaver lately here, hasn' he?)>>As in the past, thanks for your help, oh "Great Master of the>mythical Zalman Fan." Glad to help Chuck. Give me a shout anytime.Best Regards,Jeff

>>My boys are the Patriots though. I grew up back there. My season >>ended in week 1 when Brady went down. Jeff:You're obviously a man of fine taste and good breeding! Where'd you grow up? I went to High School and College near Hartford, but spent 10 years shuttling back and forth between a 9-5 in the little town of Greenfield, MA and my weekends in Boston from the time I was 21. I have been thrown out of (the old) Foxboro Stadium, AND Fenway, many times. ;-)I watched the play on Brady in week 1 like it was in in slow motion (I have the NFL package on sattelite). That play was like the nightmare you knew had to come sometime, just not today.

>>>My boys are the Patriots though. I grew up back there. My>season >>ended in week 1 when Brady went down. > >Jeff:>>You're obviously a man of fine taste and good breeding! >Where'd you grow up? I went to High School and College near>Hartford, but spent 10 years shuttling back and forth between>a 9-5 in the little town of Greenfield, MA and my weekends in>Boston from the time I was 21. I have been thrown out of (the>old) Foxboro Stadium, AND Fenway, many times. ;-)>>I watched the play on Brady in week 1 like it was in in slow>motion (I have the NFL package on sattelite). That play was>like the nightmare you knew had to come sometime, just not>today.>Well, I was born in Fall River and grew up a little south of Boston. I actually worked for the Pats for a year around '86 or '87, in security. My job was to stand behind the bench during the game and then, at the end, escort players from interviews to the locker room. Tough job I know but, somebody's got to do it, right? The toughest part was hitting the buffet in the press box at halftime! :-hah I saw some great stuff at that old jewel of a stadium that year. The Pats, BC, Aerosmith, and a few others. Steve Tyler was a real party animal back then!Fenway is still my favorite though. Coors Field has alot of that ambiance but, nowhere near the history. I grew up with Rice, Lynn, Yastrzemski, Dewey, The Spaceman, and all those heartbreaks.The playoffs just don't feel the same without the Red Sox going up against the Yanks. Maybe next year. I get out to the "Island" every so often on business. I'll let you know next time I head that way. I'll buy the pizza, you get the beer! :-lol All the Best,Jeff

Hey Jeff. I thought of something when I was in bed last night. When you were talking about the FSB Strap at 333 and how you got better performance with your ram timimgs at 4-4-3-10, it made me realize that when I tried my Strap set at 333 I didn't change the timimgs of the ram, just left them at 5-5-5-15. Perhaps thats why the 333 FSB Strap at 960mhz RAM didn't work as good as the 400 Strap/1066mhz combo. DO you think I should go ahead and try the 333/960mhz RAM 4-4-3-10 combo. I have absolutely no ideas of what those numbers correspond to in RAM timings, except that I guess the lower the number the faster it is? If the 4-4-3-10 combo is within limits of the sticks I will give it a try, or 4-4-4-10.Let me know your thoughts, if your not busy watching the Monday night game.BTW, my girlfriend is a huge Pats fan, although I think its just because she likes looking at Tom Brady, lol. She was so upset when he got hurt. I actually like them also. I went to school with Teddy Bruschi at the U of Arizona and know his sister. He and his sister are really nice. In fact, when I was in college, I worked part time at Circuit City and installed car stereos in both his and his sisters car.TTYL,Sean

Sean,I wouldn't recommend that, no. Running at 4-4-3-10 isn't always peaches and cream. I keep trying to stay stable at those timings in FS and it just isn't working out. One minute it's great and another, FS gets really cranky. These sticks will run at that timing but, it just seems hard on them. If you go anywhere with the timings, I think the best setting is 5-5-3-13. A 333 strap will require you to use a 1:1 ratio at 4-4-3-10. You won't be able to boot with 5:6 at those timings unless you pull the FSB back to about 370MHz. Remember, earlier I said that the tighter timings helped "to a point". You're looking for the balance between speed and performance. I think, with 4-4-3-10, we're sacrificing too much of both. I'm back to 5-5-3-13 again. That just seems to be the best setting. Also, as I metioned before, the closer to a 450MHz FSB you can get, the better my settings will perform. I do want to mention again that you should do some research on how timings work because your sub-timings will come into play as well, to make the most of 5-5-3-13. Getting into these areas, I wouldn't be comfortable advising you because I'm still learning myself. Maybe Nick will see this and jump in if he has a bit of time to go into more detail. One motto I try to live by, though not always successfully, is "if it ain't broke, don't fix it". That's why I'm back to 5-5-3-13.Sorry, I know that doesn't help you alot. Of course, I'll try to help in any other way that I can.I've heard that Teddy is one of the true nice guys off the field. He's an animal during a game though. I love watching him play.As for your girlfriend, I'll echo Chuck's words. She's obviously a woman of fine taste and good breeding! Maybe you should think more about her when you're in bed, and less about me.:-lol :-lol All the best my friend,Jeff

I don

Thanks for jumping in Nick. I appreciate it!Sean,I can also say now that you shouldn't even bother trying the 4-4-3-10 timings for one good reason. You will compromise the performance of the memory. Every time I've tried it, I've done a little damage to the RAM. I know this because each time I have gone back to the 5-5-3-13 timings after using 4-4-3-10, I've found that I have to pull the speed back a bit more to maintain stability. 4-4-3-10 will shorten the lifespan, and reduce the top end speed of your sticks. I'm done trying to get better than 5-5-3-13. That's about as tight as it's going without burning it up. Just thought I'd share that with you. I hope things are working out for you.Regards,Jeff

hold hold hold hold hold!!!Timing does not shorten the lifespan of a product any more than FSB increases on a motherboard doesWhat shortens the useful life of a product is voltage and heat, nothing else.If you are running those sticks, in example, at Corsair spec of 2.1-2.2v they are not going to burn out like a light-bulb! They are also not going to die sooner if you try to run them at CAS 4.. unless you start pushing the voltage past what the manufacture warranties the product for trying to stabilize a CAS 4 timing.. then you start killing the product, not before.We all have to get past that around here. I know its tough because all the time that was spent in shooting myths into this forum but forget faster timing, FSB. GHz, = shorter life thats just plain hogwashMore than likely the reason for a lower CAS perf difference was instability. Just because a system does not crash does not mean its stable. There can be all sorts of errata flying around creating the perf issues because the sticks are on the complete edge of being unstable but not enough to force a lockup or crash.Another reason would be from heat if you had to jack up the voltage to over the spec even slightly to maintain the clock.. heat at that point can play into the physics of the electronics and force a perf loss even with lower timing/higher speed in use.Lower timing and higher speed is always better assuming all factors are in place. One must find the series of values that play together ie; FSB, STRAP, MEMSPEED, Timing, CPU speed, that places the system in the zone for its highest perf ability.

>>>>hold hold hold hold hold!!!>>>>Timing does not shorten the lifespan of a product any more>than FSB increases on a motherboard does>>What shortens the useful life of a product is voltage and>heat, nothing else.>>If you are running those sticks, in example, at Corsair spec>of 2.1-2.2v they are not going to burn out like a light-bulb!>They are also not going to die sooner if you try to run them>at CAS 4.. unless you start pushing the voltage past what the>manufacture warranties the product for trying to stabilize a>CAS 4 timing.. then you start killing the product, not>before.>>>We all have to get past that around here. I know its tough>because all the time that was spent in shooting myths into>this forum but forget faster timing, FSB. GHz, = shorter life>thats just plain hogwash>>>More than likely the reason for a lower CAS perf difference>was instability. Just because a system does not crash does not>mean its stable. There can be all sorts of errata flying>around creating the perf issues because the sticks are on the>complete edge of being unstable but not enough to force a>lockup or crash.>>Another reason would be from heat if you had to jack up the>voltage to over the spec even slightly to maintain the clock..>heat at that point can play into the physics of the>electronics and force a perf loss even with lower>timing/higher speed in use.>>>Lower timing and higher speed is always better assuming all>factors are in place. One must find the series of values that>play together ie; FSB, STRAP, MEMSPEED, Timing, CPU speed,>that places the system in the zone for its highest perf>ability.>Thank you for clearing that up Nick. I just noticed a pattern where I could run at 5-5-3-13 at a certain speed and then, after trying the tighter timings for a day or two, going back to the 5-5-3-13, I could not get stable at the speed they were at previously. When I went back this time, running FS resulted in a BSOD every time. I had to pull the speed back about 20MHz. At least I know that I can keep working at it without causing damage. Back to the books for me I guess. Thanks again,Jeff