Jump to content

Frequent Ctd's


2 replies to this topic

#1 Mr Fistr Kerensky

    Member

  • Pip
  • 10 posts

Posted 22 December 2014 - 05:52 AM

Having an issue on a system with an i5 2500k, 8GB ram, 660Ti video card on Windows 7 64-bit off an SSD.

Frequent crashes to desktop from in game, it can be at the start of the match or well into a match. In one instance I was not able to rejoin the game due to a connection error although I could launch into another match from a different mech.

I was using the Windows task manager to monitor the CPU and Ram activity and MSI Afterburner to monitor GPU temp and activity. Other than the CPU and GPU being pegged once in game I did not notice anything out of the ordinary. No crashes while monitoring of course nothing was captured in the Windows event logging service.

This occurred while running the 64-bit client but thinking that was the cause I switched back to 32-bit and it still occurred.

Any ideas, suggestions, thoughts?

I keep Windows current on updates and drivers for software as well so we can take that out of the equation.

#2 Mr Fistr Kerensky

    Member

  • Pip
  • 10 posts

Posted 06 January 2015 - 03:57 AM

So what's it take for support to reply to a ticket? I am still getting client crashes, I have reinstalled the game twice now and have the same recurring issues.

View PostMr Fistr Kerensky, on 22 December 2014 - 05:52 AM, said:

Having an issue on a system with an i5 2500k, 8GB ram, 660Ti video card on Windows 7 64-bit off an SSD.

Frequent crashes to desktop from in game, it can be at the start of the match or well into a match. In one instance I was not able to rejoin the game due to a connection error although I could launch into another match from a different mech.

I was using the Windows task manager to monitor the CPU and Ram activity and MSI Afterburner to monitor GPU temp and activity. Other than the CPU and GPU being pegged once in game I did not notice anything out of the ordinary. No crashes while monitoring of course nothing was captured in the Windows event logging service.

This occurred while running the 64-bit client but thinking that was the cause I switched back to 32-bit and it still occurred.

Any ideas, suggestions, thoughts?

I keep Windows current on updates and drivers for software as well so we can take that out of the equation.


#3 Tarl Cabot

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • Tai-sho
  • Tai-sho
  • 7,831 posts
  • LocationImperial City, Luthien - Draconis Combine

Posted 06 January 2015 - 07:12 AM

They just got back from the holiday break and their top priority is the financial side/tickets dealing with purchases and such.

Is the system OC?
On ram, are you able to drop it to 4gigs?
Have you run any programs to stress test the system?





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users