Looks to me like your trying to straighten out a plate of spaghetti. Good to see you got it under control!

 

Seems like to me that 99% of all CTD's are user error, poor computer config, and bad installs.

Ha, yes it does feel like that. Honestly, 6 weeks ago I was like a kid at Christmas, building a new FSX rig, splashing the cash, it was amazing. I've spent the last 2 weeks pulling my hair out with it.

 

BUT i think I'm getting somewhere...and without the need for tens of hours of uninstalling and reinstalling.

 

More positive news Jim - I've re-enabled my XMP and set the frequency of the RAM to 18.66, and I still can't make the thing crash no matter what I throw at it. So that leaves the CPU overclock as the culprit. So I guess it's back to square one with that. I guess the way to approach it is to do it very gradually, increasing the voltage as necessary and then lots of stress testing. And when I get to a point where FSX is crashing on me again, going back to the last point at which it was stable?

 

Thanks

Martin

Should I turn it ON and see if that works?

 

As I said before the XMP profile is the best for your installed memory as it provides the highest voltages and higher frequencies/timings. In other words, you're getting the most out of the product you bought. Just make sure the DRAM voltage is at 1.65v.

 

More positive news Jim - I've re-enabled my XMP and set the frequency of the RAM to 18.66, and I still can't make the thing crash no matter what I throw at it.

 

Great news for sure as it looks like postive progress is being made.

 

So that leaves the CPU overclock as the culprit.

 

I suspect you kept it at the default 3.4GHz and now you want to bump it up to the highest overclock possible and still maintain stability? Just put 100 in the BCLK frequency. Then in the By All Cores start out with 44 or, if you want go on up to 48. Enable your PLL overvoltage. Disable EUP Power Saving. Now I have an ASUS board and you have the Gigabyte board the the BIOS are basically the same. Under DIGI+VRM:

 

Load-line Calibration - Ultra High

VRM Freq - Manual

VRM Fixed Freq Mode - 350

Phase Control - Extreme

Duty Control - T.Probe

CPU Current Capability - 130%

CPU Voltage - Manual Mode

CPU Manual Voltage - 1.400

DRAM Voltage - 1.65000

VCCSA Voltage - Auto

VCCIO Voltage - Auto

CPU PLL Voltage - Auto

PCH Voltage - Auto

All the DRAM Voltage on CHA - Auto all the way down

CPU Spread Spectrum - Auto

 

CPU Power Management

CPU Ratio - Auto

Enhanced Intel SpeedStep Tech - Enabled

Turbo Mode - Enabled

 

Turbo Mode Parameters - All auto

 

CPU Configuration

CPU Ratio - Auto

Intel Adaptive Thermal Monitor - Enabled

Hyper-threading - Disabled

Active Processor Cores - All

Limit CPUID Max - Enabled

Execute Disable Bit - Enabled

 

CPU C1E (all auto - C1, C3, C6

Intel Virtualization Tech - Enabled

 

And that should be it! You may or may not have the same parameters in your bios but don't be concerned if you don't. I see your BIOS can be overclocked automatically by the Gigabyte program. ASUS had that too. When I set mine automatically, my system crashed. My system became stable with my own overclock settings. Don't think you can use the automatically overclock program anyway with the XMP profile.

 

Take things slow. If you get a crash at 4.8 or higher, your system is unstable and you'll need to lower the clock to 4.6 or 4.4. (But then you knew that! LOL!).

 

Good luck!

 

Best regards,

Jim

 

As I said before the XMP profile is the best for your installed memory as it provides the highest voltages and higher frequencies/timings. In other words, you're getting the most out of the product you bought. Just make sure the DRAM voltage is at 1.65v.

 

 

 

Great news for sure as it looks like postive progress is being made.

 

 

 

I suspect you kept it at the default 3.4GHz and now you want to bump it up to the highest overclock possible and still maintain stability? Just put 100 in the BCLK frequency. Then in the By All Cores start out with 44 or, if you want go on up to 48. Enable your PLL overvoltage. Disable EUP Power Saving. Now I have an ASUS board and you have the Gigabyte board the the BIOS are basically the same. Under DIGI+VRM:

 

Load-line Calibration - Ultra High

VRM Freq - Manual

VRM Fixed Freq Mode - 350

Phase Control - Extreme

Duty Control - T.Probe

CPU Current Capability - 130%

CPU Voltage - Manual Mode

CPU Manual Voltage - 1.400

DRAM Voltage - 1.65000

VCCSA Voltage - Auto

VCCIO Voltage - Auto

CPU PLL Voltage - Auto

PCH Voltage - Auto

All the DRAM Voltage on CHA - Auto all the way down

CPU Spread Spectrum - Auto

 

CPU Power Management

CPU Ratio - Auto

Enhanced Intel SpeedStep Tech - Enabled

Turbo Mode - Enabled

 

Turbo Mode Parameters - All auto

 

CPU Configuration

CPU Ratio - Auto

Intel Adaptive Thermal Monitor - Enabled

Hyper-threading - Disabled

Active Processor Cores - All

Limit CPUID Max - Enabled

Execute Disable Bit - Enabled

 

CPU C1E (all auto - C1, C3, C6

Intel Virtualization Tech - Enabled

 

And that should be it! You may or may not have the same parameters in your bios but don't be concerned if you don't. I see your BIOS can be overclocked automatically by the Gigabyte program. ASUS had that too. When I set mine automatically, my system crashed. My system became stable with my own overclock settings. Don't think you can use the automatically overclock program anyway with the XMP profile.

 

Take things slow. If you get a crash at 4.8 or higher, your system is unstable and you'll need to lower the clock to 4.6 or 4.4. (But then you knew that! LOL!).

 

Good luck!

 

Best regards,

Jim

 

Thanks for all you help Jim. Now that I know the problem was an incorrectly configured overclock I'm a LOT happier knowing I'm not going to have to go through hell removing and reinstalling everything!

 

I will be spending some time over the weekend trying to get my overclock done properly and get it stable and crash free!

 

Will let you know how I get on!

 

Cheers

Martin

Hi Martin,

 

You're welcome! If you need info on overclocking, there's a lot of friendly people down in the Hardware Forum here. Pinned at the top are several examples of successful configurations.

 

Best regards,

Jim

Jim

 

OK so today I tried upping my frequency to 44 and upping the vcore to 1.35

 

Fire up fsx, load my "stress test" flight and BAM

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: g2d.dll, version: 10.0.61472.0, time stamp: 0x475e180c

Exception code: 0xc0000005

Fault offset: 0x0004374b

Faulting process id: 0xfb4

Faulting application start time: 0x01cdc97812316176

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\g2d.dll

Report Id: 3abcc8e3-356c-11e2-8b62-902b345949d4

 

So, does this mean I need to aim for a lower overclock than 4.4Ghz?

 

Thanks

Martin

Jim

 

UPDATE - I've (somehow - fingers crossed!!) managed to get it back up to 4.4Ghz, stable during FSX. Hooray. I'm stopping here lol.

 

Question, during some intense FSX testing I registered a max temp on the 4 cores of 62, 72, 76 and 71. Are these safe temps?

 

Thanks

Martin

during some intense FSX testing I registered a max temp on the 4 cores of 62, 72, 76 and 71. Are these safe temps?

 

Centigrade or faurenheit? Even in Centigrade they look okay. I did some searching and I could find nothing definitive even from Intel. Most of the topics I read said 100 degrees C is the max. That's hot! I believe there are things built into the CPU to shut it down if cooling fails. You have the same Noctua cooler I have so you should have no problems.

 

I have my system oc at 4.4GHz and it runs fsx very well. I hope yours continues to run stable too.

 

Best regards,

Jim

Thanks Jim, that's centigrade. So far so good on stability, hopefully this weekend I'll actually be able to do some actual flying and not just sat at my desk pulling my hair out So i'll let you know!

 

Thanks

Martin

not just sat at my desk pulling my hair out

 

LOL! Been there, did that....

 

Best regards,

Jim