test content
What is the Arc Client?
Install Arc

Can we please get some help with the CTD decompressing data issues??

SystemSystem Member, NoReporting Posts: 178,019 Arc User
I've had this problem since launch. I see other threads on it too. PLEASE stop telling us to delete the file and patch the (usually 1.5 GIG) file, it doesn't work. It just crashes again on a different file. Enough people are getting this that it can't be system issues. I run software and games from other sources all day without this.

This REALLY needs to get fixed. Why does the game work sometimes for hours and others crash everytime
I try to transition to a ground map?

The one clue I have is it only happens, but OFTEN happens, when I try to transition from space to ground. Space seems to be fine, it's almost always when I try to transition to ground.

Am I being punished for running a 64x OS (Windows 7) or 2 ATI cards in crossfire? Does this game only run stable on Intel / Nvidia platforms?

It's also not my memory. Yes I bought new ram (2-2gig to 4-2gig DDR3 sticks for 8gigs total) but it's passed Windows, Linux, and memtest each twice and as I stated above all other software runs fine for hours+.

I'm not close-minded, I'm willing to continue exploring this but it seems increasingly unlikely. Is anyone else running:

GSKILL MEM 2Gx2|GSK F3-10666CL9D-4GBNQ R - Retail

If so, what timings are you using? I'm set to auto right now. I read in another thread lowering graphics may help but I'm not willing to do that below 1 setting down, plus sometimes in Exploration nebula missions it will run for hours fine at max resolution (1920x1200).
Post edited by Unknown User on

Comments

  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    I have never had the decompressed file problem from closed beta to now.
    From using XP with 2 gig memory with 8800 GTXoc with a Pentium D CPU
    to my current system with Win7 9 gig memory GTX260 and I7 950 CPU.

    Now on both systems I have never installed the game in the default directory or in the programs file directory.
    My old system it was installed in d:\games directory and on my new system itis in C:\games directory.

    I wonder if that is why I don't have the problem.

    What directory is the game installed on (and the OS) people having the problem are using?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Thanks for the reply but I don't think the directory matters or even more people would be having this problem. The two things I know for sure is I can fly in warp space and sector space all day and in nebula explore missions I can transition to ground the majority of the time without incident. It's in the public areas, Sol, etc. that it really seems to crash with this error. I think maybe it has something to do with the number of players near me or on the map.

    Whatever causes it, it seems to corrupt the file for *that* character or that specific map at least. I can login with a different character without rebooting and beam down to other maps (again usually nebulas) for hours. If I reboot, I can sometimes login and I will already be on the station when I get in game. Other times I have to delete the file and re-download it when a reboot doesn't resolve it.
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Anyone else getting this? If you're getting the decompressed fatal error crash to desktop issue on any of the .hogg files, do you notice it in the same instances? I mean transitioning from space to ground or a station, especially Earth? Does it work better for you in nebulas?

    Anyone running 2 ATI 48xx series cards in crossfire with crossfire enabled without this issue?
  • Archived PostArchived Post Member Posts: 2,264,498 Arc User
    edited April 2010
    Did you just add your new memory to your system or did you remove your old memory and replace it with the new sticks.

    What make of motherboard do you have I've seen voltage problems on the 2nd pair of memory sticks on Gigabyte and Asus motherboards

    Try setting the timings and voltages manually in the bios rather than trusting them to an Auto setting
    Run a program called CPU-Z to determine what the spd on your memory states it should be run at timing wise and at what voltage

    Try running Prime 95 (64 bit) torture test for a good 12 hours minimum seen it run many times for less time than this before kicking up any error

    If you get any errors with prime95 with manual timings/voltages your memory is faulty

    Running windows or Lynux for any number of hours does not test your memory thoroughly
Sign In or Register to comment.