Location: COMFORTABLY NUMB, in U.S.A. *** KOFF ***
Age: 51
Gender: Male
Well, Richy was very helpful with getting my two new sticks to work on my system.
However, I now have a problem with a crash with a message. While flying for anywhere from 1 min to 3 min max, FS9 crashes. I get an error report of *g2d.dll*. I got this several times. When flying my F-16, it CTD. Don't know what happened there, but was real fast in the CTD.
I took out the 2 sticks, and replaced it with the original, and guess what?? I flew for 20 min, with no problems.
I noticed a huge improvement ( however short it was ) in the scenery and what not.
But what the heck is *g2d.dll*. I have googled it, and found alot of FS2000 info for updates, but nothing for FS2004/FS9 as to what could be causing this.
LOL...go into your bios, disable video caching and shadowing. Disable fast writes on your vid card found under settings. Also make sure your BIOS is updated (find latest update on mobo manufacturer's page and get your Bro to flash the BIOS). Double check mem settings for compliance in the BIOS and try that. Shout back if no go...
You wouldn't by any chance have an ATI video card? If so the following I found in a user forum may be of interest to you "I was able to solve my crash to desktop with g2d.dll error -- had to turn ATI Overdrive OFF and stability returned."
In my last post in the thread in question, My comment was made with a copy of your post in an effort to give credit where due. I just tried to verify that the setup was the same for rd's board. You had it pegged!
Richy.......
Now for the bios settings.....I think Exx has that covered.
RD:
I am referring to your reply in the posting labeled DUAL CHANNEL where I explained how I had configured my three memory boards.
Richy:
I saw your response to RD and appreciate the credit.
I am from the old school where "HUH" is what I used to say when the teacher would ask me a question about the homework assignment that I did not do. I guess that "HUH" must be some kind of Internet Shorthand.
I'm glad that the misunderstanding has been cleared up.
My system only runs at 333MH which only requires PC2700 (333MH) but my motherboard is rated at 400MH. I am successfully using PC3200 (400MH). I figured that I could always use the faster memory in the future if I ever upgrade or purchase a new system.
Yes, if your system can handle the faster memory, you will get better results by using the faster memory boards in all three slots. However, I doubt if after spending another $65 you will notice a big difference.
The higher the number, the faster the memory; for example, PC133 is faster than PC100, and DDR is faster than SDR.
Remember, it's best to match the memory that is currently in your system.
It might seem confusing, but faster memory will NOT necessarily make your system faster. Your computer will run only as fast as the "slowest link" in your system, so you can't speed up your computer by adding faster memory. The way to make your system faster is to add more megabytes (MB) of memory.
Do I need error checking?
Most desktop computers take what's called "non-parity" memory and do not need error correction code (ECC), or "parity" modules. (However, in most cases ECC modules will work in desktops.) ECC modules look for errors in data and are most often found in servers and other mission-critical applications used by large networks and businesses. There are, however, a few desktop systems that do use ECC modules. In any case, you should buy the type of memory that's already installed in your system. You can tell which kind you have by looking at one of the modules currently installed. Count the RAM chips on one module. If the number of chips can be evenly divided by three or five, you should buy ECC or parity (whichever is offered for your system). If not, you should buy non-parity. For example, if one of your modules has nine RAM chips, you should buy ECC or parity. If one of your modules has eight RAM chips, you should buy non-parity. Or, you can look up your system in the Memory Advisor tool.
If you're building your own system, we recommend using non-parity parts unless you will be using your system as a server or have a need for error checking. ECC and parity parts are slower than non-parity parts.
What does "CL" stand for?
CL stands for CAS (column address strobe) latency, which is the number of clock cycles it takes before data starts to flow after a command is received. Low CAS latency at a given frequency is faster than high CAS latency at that same frequency. (For example, CAS2 is faster than CAS3.) However, lower CAS latency will NOT necessarily make your system faster. Your computer will only run as fast as the "slowest link" in your system, so you can't speed up your computer by adding memory that is faster than your current memory. The way to make your system faster is to add more megabytes (MB) of memory.
In general, we recommend using parts with the fastest speeds. This will give you the highest level of compatibility and future upgrade path.
If you don't know the CAS latency of the memory you currently have installed, don't worry; any of the modules listed in the Memory Advisor tool are guaranteed to work in your system.
Here is a paragraph from the Crucial website that may help you.
Common types of memory technology today include DDR2 (double data rate, second generation) SDRAM and DDR (double data rate, first generation) SDRAM. Many older systems use SDR (single data rate) SDRAM, fast page mode (FPM), or extended data out (EDO). Each of these memory types comes in a variety of speeds. And while most systems will accept only one type of memory technology (the very few motherboards that can accept more than one type of memory will only allow you to use one type at a time), it's okay to mix the speed of the memory in a system. Just keep in mind that your computer is made to handle a specific memory speed, so even if you add a faster speed memory, your computer will only allow it to run at the speed your computer was made to handle.
Location: COMFORTABLY NUMB, in U.S.A. *** KOFF ***
Age: 51
Gender: Male
Happy New Year all,
OK, I have 3 compatible sticks, 512 mb, PC3200. Over 1.5 gb of memory.
After junking my FS9.CFG, and getting a new one, and modifying the terrain details, I finally can run 35 fps, with very heavy scenery and heavy a/c.
However, I am still getting the *g2d.dll* error. I can fly for different time amounts, on the same scenery. Some times 2 minutes, sometimes 10 minutes. But I still keep crashing with this error.
Quote:
Exxman Posted: Fri Dec 30, 2005 12:14 pm Post subject:
LOL...go into your bios, disable video caching and shadowing. Disable fast writes on your vid card found under settings. Also make sure your BIOS is updated (find latest update on mobo manufacturer's page and get your Bro to flash the BIOS). Double check mem settings for compliance in the BIOS and try that. Shout back if no go...
Exx
On the Fast write, I cannot disable it, or change it to *NO*. Everything is current/new for my mobo and BIOS, including drivers.
Any other idea's guys. I would very much appreciate it.
Check out the following statements from the Instructions for the 9.1 Upgrade. I hope that you can find a solution soon.
To install the default .dll file:
1. Insert the “Flight Simulator 2004: A Century of Flight” CD-ROM number 2 in your CD-ROM drive.
2. Click the Windows Start button and choose “My Computer.”
3. Highlight and right-click the icon for the CD-ROM drive containing the number 2 CD-ROM. From the right-click menu, choose Open.
4. Select MSGAME3.CAB and open it using Windows Explorer.
5. Copy the affected .dll (for example gps_export.dll to the Modules subdirectory of your Flight Simulator installation directory. (For example, C:\Program Files\Microsoft Games\Flight Simulator 9\Modules.)
6. Remove the CD-ROM from the drive and restart the Update setup.
NOTE: Previously installed the 3rd party add-on software for Flight Simulator may not work. If any action (such as re-installing the 3rd party add-on software) causes an overwrite of the updated module .dll file, you will lose significant fixes included in the Flight Simulator 2004: A Century of Flight (update).
Location: COMFORTABLY NUMB, in U.S.A. *** KOFF ***
Age: 51
Gender: Male
Skipper, not to you directly, but I did exactly what you said.
Now, what the hell. I start my flight, fly, and in 30 seconds, crash to REBOOT !!! I try to fly again, and it locked up / froze. RESET was the only option.
Location: COMFORTABLY NUMB, in U.S.A. *** KOFF ***
Age: 51
Gender: Male
Great,
I just uninstalled FS9, reinstalled it. Basically, another virgin install. Everything, and I do mean everything was deleted. Ran disc clean up, then defrag. Reinstalled FS9, flew for 30+ seconds, and WHAM.
Friggin *g2d.dll* error.
I am done with FS9. I will still be here since I just paid for renewing my membership here.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
