Results 1 to 8 of 8

Thread: GTA 4 fatal error dd3d30

  1. #1
    Join Date
    Oct 2008
    Posts
    42

    GTA 4 fatal error dd3d30

    Hi,

    So I've been having this problem ever since I installed GTA IV yesterday. Every time I try to launch the game, I get the DD3D30 error. Reading the Rockstar support site, their recommendation is to restart the system. This of course, doesn't work. Neither does uninstalling or reinstalling drivers, updating to the latest beta drivers, or uninstalling and reinstalling the game itself. Anyone else having this problem?

  2. #2
    Join Date
    Oct 2008
    Posts
    128

    Re: GTA 4 fatal error dd3d30

    Hi, I bought the game today and hat the same problem (Fatal Error: DD3D30 )

    I changed the resolution from 1920x1200 to 1440x900, and it works now !

    I hope i helped you !

  3. #3
    Join Date
    Dec 2008
    Posts
    128

    Re: GTA 4 fatal error dd3d30

    This is caused by a refresh rate, if your monitor is not able to handle it, it will result in dd3d80. You can use parameter -windowed in your command line to get rid of it and then in game set up the supported refresh rate + resolution.

  4. #4
    Join Date
    Jan 2009
    Posts
    1

    Re: GTA 4 fatal error dd3d30

    i have the same problem...but how can i change the resolution?

  5. #5
    Join Date
    Apr 2008
    Posts
    2,465

    Re: GTA 4 fatal error dd3d30

    Hey! Start the game go to options then go to video. there change the resolution! If you want to change the screen resolution of the operating system itself, right-click anywhere on desktop go to settings tab and change the resolution by sliding the screen resolution slider on the bottom left. have fun!

  6. #6
    Join Date
    Dec 2008
    Posts
    102

    Solution for GTA 4 fatal error dd3d30

    its the fault of the new engine of GTA4 that is the cause of all that laggy problem. it always "resizes" to give the same quality even in different resolution ...there is a simple solution for it actually...

    change your GTA 4 resolution to your "native resolution" or change your "native resolution" to desired GTA 4 resolution in other words.. make your resolution same with the game... thats it!

    your "native resolution" is not your monitor resolution but rather your current desktop resolution...(windows resolution...monitor resolution...ect...)

    this is to make sure that gta 4 does not resize..upscale or downscale in anyway. leaving the scale to 1:1 , up scaling or down scaling uses the cpu and video card power . i run game at 1280 x 720 ( w00t.gif minimum specs)
    • texture: medium
    • render: high


    it runs much faster (looks better too) compared before when my native resolution was 1440 x 900 . gta 4 was running at 1024 x 640

    Tip : also press "p" when playing to enable motion blur--- looks cool and hides the lags

  7. #7
    Join Date
    Jan 2007
    Posts
    200

    Re: GTA 4 fatal error dd3d30

    Hi,

    Try to change your desktop resolution to 800 x 600 and start the game to avoid GTA 4 fatal error dd3d30 that what i do to play GTA IV all the time.

  8. #8
    Join Date
    Mar 2011
    Posts
    1

    Re: GTA 4 fatal error dd3d30

    One thing I did and worked was, I have Windows xp, (Right click desktop, go to properties, settings tab, click advanced button, and click monitor tab, properties button) I did not have the correct monitor for my system. I updated my monitor drivers to the correct ones. Works perfect now!!! It's basically the same procedure for Windows 7. Let me know if this works for ya.

Similar Threads

  1. Replies: 5
    Last Post: 19-03-2012, 09:48 AM
  2. Replies: 5
    Last Post: 08-03-2012, 09:44 AM
  3. Replies: 4
    Last Post: 02-06-2011, 10:32 AM
  4. Replies: 4
    Last Post: 25-05-2009, 11:35 PM
  5. Replies: 2
    Last Post: 14-05-2007, 11:06 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,455,635.05598 seconds with 17 queries