You may be onto something with the hardware stuff. Good luck.

I think my memory needs to run at 1.6V. I'll open my case up and check the exact model of them in a couple hours and try to find the exact spec. They have always been at 1.5 and I have never had any issues before.

 

You can only set your memory voltage to 1.6V if you have your Ai Overclock Tuner set to X.M.P. on the Ai Tweaker page of your BIOS. Look on the ASUS Tool tab in your BIOS and look under ASUS SPD Information. It tells everything about your BIOS and what it is rated. Only at XMP can you have your frequency turned up to 1600MHz. The other settings are to 1333MHz and lower voltages. The CPU-Z SPD tab provides much of the same info and provides the max voltages for each memory timing/frequency.

 

Best regards,

Jim

Hey Jim, I have set my memory to XMP.

 

 

I think what's happening was that I was running the tighter CAS 7 timings at 1.5 volts. The memory needs the .1 voltage bump to achieve those advertised timings.

I now understand Intel only supports 1333 at 1.5 volts unless the memory is made for Sandy Bridge like mine is and it has the XMP profile. Only then will Intel support 1.6 under XMP. I will keep these for a couple flights and see how it goes.

Thank you for your help.

Hmm, a few days ago, I had a G3D.dll crash. I have latest version of FSUPIC installed.

 

Really a mystery, I am pretty sure it was caused by REX weather engine, because that was the first time I have ever used the REX weather engine before, and have never had a g3d.dll crash.

I got my G3D.dll crashes on AS2012 weather and REX E+ supplying the textures. The obvious thing to do now would be to restore your textures to default and give it a couple flights. :Phbbbt:

 

I completed KLAS to KLAX last night with XMP settings. It was the same conditions (without the XMP obviously) I got my first G3D.dll crash. I made it there and shut down. Only after that I minimized VAT-Spy on my second monitor and it caused a nvlddmkm.sys driver CTD.

My memory.dmp log pointed to VATSpy. I guess I can't win.

Oh well I'm willing to accept VAT-Spy crashing only because I now it's underdeveloped and I have not seen any updates since 2010.

Chuck, in your opening post, you've said that you ran Win8 before. With the only trouble being that joystick disconnect (is that solved by the way?). Is that correct?

 

Asking because it's the same hardware, only the OS and drivers changed, right?

I reinstalled Win7 because of the joystick disconects. I did not have any CTDs with Win8. I monitor http://forum.avsim.n...-win8-os-forum/ to stay updated with any tweaks or fixes from Microsoft. It is the same hardware and I have not had any disconnects since going back.

I know some people are saying it could be tied to a windows update in Win7 and Win8. I had no issues in the first week or 2 of using Win8 then it started happening like clockwork on every flight.

I am fairly sure I have Win7 fully updated to today. I make it check for updates daily even when it says its current. If I do get a disconnect with WIn7, updates will the first thing that gets checked.

 

I like Win8 and metro (sound strange to hear, uh). I picked it up fairly quickly and I can do things in Win8 more efficiently with shortcuts,hotkeys and the charms bar. I hope a fix is found so I can go back.

I also lost 3 weeks worth of minesweeper daily challenges swithing back to 7.

 

My theory for my G3D.dll CTDs are that when I was on Win7 and Win8 it was very stable. In this installation I was very meticoulous with the installation process. I followed this http://www.simforums....=198187#198187. It's Nick's FSX install guide. I am now gettiing 70-90 FPS (when I take the frame limiter off) in spot view where before I was struggling to hit the limiter. This has got to stress the memory and exposes any vulnerabilities that were slipping by before. Maybe I'm thinking too hard about it. :blink:

No problem with liking Win8. I was just wondering about possible hardware issues but then realized that the same hardware ran fine win Win8. Unfortunately, that g3d.dll error offers a huge set of possible sources.

 

I also lost 3 weeks worth of minesweeper daily challenges swithing back to 7.

I feel your pain. ^_^

 

Only after that I minimized VAT-Spy on my second monitor and it caused a nvlddmkm.sys driver CTD.

Can you try flying with a single monitor setup for one or two flights? I don't recall VATspy crashing, but I'm on a single monitor setup. Still only guessing, sorry.