SurClaro Flight Simulator Resources

Posted: Sat Mar 15, 2008 8:51 am Post subject:

Ummm......

Posted: Sat Mar 15, 2008 1:05 pm Post subject:

I will say up front that I am not a fan of overclocking CPUs. I have spent many years working with mainframe computers and we never overclocked them. I have owned several cars and I have always read the owners manuals to determine "guidelines" for best performance. I may not change my filters and rotate my tires as often as recommended. However, I realize that by not following their guidelines, I will be limiting the life of my cars. When it is time to trade in the car, the mechanic who inspects it can usually tell how well I took care of it.

I wish you luck with your experiments. However, I can only conclude by repeating when Clint Eastwood said in his Dirty Harry movie,

DO YOU FEEL LUCKY SUCKER

Posted: Wed Apr 02, 2008 8:46 pm Post subject:

I've been playing FSX for a while no problems Q6600 @ 3.51GHz and 3.5GB DDR2-800 @ 936.. But it seems like I get BSoD after 1 - 2 hours of playing if I have music running in the background, when I'm flying up a massive aircraft (PMDG). Is it possible the cause of this the starving RAM? (I only increased DDR2 OverVoltage to +.20V over stock). I raised it to +.25V.

Not only do I get BSoD in FSX.. but I have had several BSoD's when I have music playing and executing a program (or driver). Is this a DDR2 starvation or CPU starvation? CPU clock is 2.4GHz @ 3510MHz at 1.52V and DDR2-800 at 936MHz with 2.06V. the 3.51GHz at 1.52 should be MORE than enough.. (Am I missing something?)

It's annoying though.. because even when I am not doing anything, merely executing a software installation (not nearly loading the CPU.. max 10%) and I get BSoD while listening to music. Does it sound like a CPU issue or a RAM issue or something else?

The BSoD reported error is something that looked like "0x0000000000.. bla bla numbers bla"

Captain El

Posted: Thu Apr 03, 2008 12:19 am Post subject:

What else does the BSOD say? There's usually a cause somewhere in the middle of the BSOD.

I assume you are using Vista. Once a BSOD strikes, Vista automatically restarts the computer after a small memory dump has been performed. If this happens, one probably doesn't have enough time to read what's on the screen. To disable the restart, perform the following steps.
1. Right-click on Computer (on the desktop or Start Menu)
2. In the "System" window, on the left, click on Advanced System settings
3. In the "System Properties" window, click on the Advanced tab.
4. Under "Startup and Recovery" sub-section, click on Settings
5. In "Startup and Recovery" window, under "System failure," un-check Automatically Restart.
6. Click OK in every previous window to save changes. You may have to restart your computer.

Good luck! At this point, I would think the cause is your overclocked RAM. A CPU issue usually would cause a total system lock-up, not a BSOD.

Posted: Thu Apr 03, 2008 3:07 pm Post subject:

I got another and it said as follows:

Posted: Thu Apr 03, 2008 10:29 pm Post subject:

A quick Google search of the STOP code yields something related to NVidia hardware. Have you updated BIOS and video card drivers yet?

Posted: Fri Apr 04, 2008 7:41 am Post subject:

Yesterday I just updated my NVidia 8800 Ultra driver to the newest version (169.25). My BIOS is updated to the latest F7 version on my Gigabyte GA-X38-DQ6.

I haven't gotten a BSoD yet since, because I avoided music while tasking, (but I know there are some due when I am listening to music while executing programs and tasks), but I was getting these BSoD's running normal tasks with music. ONLY with music; no music (iTunes), no BSoD. And I am getting these BSoD's when with music in the most random situations, like executing a download in firefox!

Captain El

Posted: Fri Apr 04, 2008 11:16 am Post subject: have you...

Have you contacted i-tunes with your problem to see if others are having hardware compatibility issues? i-tunes has been out for a while now, there may be some glitch-fixes or other things popping up as hardware technology advances. Then again you may also have version errors or possibly an erroneous handling issue that isnt so obvious. I wonder if "Hijack-This" can catch the problem before BSOD so you can analyze the cause?