Jump to content

Found Another Bug/memory Leak Solution !


12 replies to this topic

#1 smokefield

    Member

  • PipPipPipPipPipPipPip
  • 994 posts
  • Locationalways on

Posted 05 January 2013 - 12:32 AM

Maybe some of you already know that i was pretty ****** up by the last patch, unable to play AT ALL, game crashing every time. After a lot of tests, both hardware and software, all drivers and SO updated..i turned over to dev's. They had a hard time identifying the problem, actually telling me to do what I already did it before mailing them.

Well..it seems i manage to identify the problem..so it may be helpfull for others.

my hardware specs are :

i5 3570k
2x4gb kingston 2400mxz


here was the problem. before the patch i was able to play the game like everyone else...crashin gnow and then or having the fps bug.
after all went to hell :)

well..i was running the cpu and ram at their default specs. I remembered that in the past i encountered the same issue with some games - when you run the CPU and ram asynchronous. (i am IT engineer :( ).

So i got it tested - I set the ram to be synchronous with cpu clock..so actually underclocked my ram...and all crashes dissapeard. I got until now around 3h play without ANY crash ! So I could say I have found my issue.

Those who expperiment a lot of crashes should check the hardware settings.


have fun ;)

#2 ElmoWithAGun

    Member

  • PipPipPipPipPip
  • 164 posts
  • Location123 Sesame Street

Posted 05 January 2013 - 05:51 AM

We shouldn't have to change our hardware in order to have the game run the way it should.

#3 Kylere

    Member

  • PipPipPipPipPipPipPip
  • Bad Company
  • 690 posts
  • LocationCincinnati

Posted 05 January 2013 - 06:00 AM

Have you done a long term memtest?

You mean the RAM and the FSB btw

#4 Oderint dum Metuant

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 4,758 posts
  • LocationUnited Kingdom

Posted 05 January 2013 - 06:24 AM

Interesting, but even more so if more than one persons issue are resolved by this

#5 Suicidal Idiot

    Member

  • PipPipPipPipPipPip
  • 404 posts

Posted 05 January 2013 - 06:27 AM

Way to go! It's always good to find a problem's solution.

View PostElmoWithAGun, on 05 January 2013 - 05:51 AM, said:

We shouldn't have to change our hardware in order to have the game run the way it should.


You are completely correct. I very much doubt that PGI is going to recommend motherboard BIOS changes to customers. Rather PGI is going to try to replicate the problem, then fix it in software.

However, until you figure out what the problem is, it's darn near impossible to fix it. Now that a band-aid has been found, the nuts and bolts programming guys can try to replicate the bug, then squash it.

This thread isn't about modifying your hardware to get the game running. It's about a hack fixing a symptom, which will tip off the programmers about where to start looking for this new bug.

Meanwhile, "Liking" the post might help bring it to the dev's attention. Heck, it should be liked on it's own merits, as he can't be the only person with this problem.

#6 Oderint dum Metuant

    Member

  • PipPipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 4,758 posts
  • LocationUnited Kingdom

Posted 05 January 2013 - 06:29 AM

I would not get that excited quickly, it requires significant play testing to be confirmed a fix, and then return the settings to normal values, to see if the issues come back.

He'd also be better off posting this in the patch forums above, rather than general discussion.

#7 Dirkdaring

    Member

  • PipPipPipPipPipPipPip
  • Survivor
  • 685 posts
  • LocationTwycross

Posted 05 January 2013 - 06:50 AM

Sounds more like just an error with your hardware.

#8 Xeven

    Member

  • PipPipPipPipPipPipPip
  • 977 posts
  • LocationFlorida

Posted 05 January 2013 - 06:55 AM

Sounds like your system is running hot when put under heavy loads (MWO). underclocking of course makes your system run cooler. It could also be voltage issue when your system is under heavy loads. Again underclocking would reduce your voltage requirment to remain stable under load. Lastly your RAM may not be up to specs (defective) and replacing it might let you run normal speeds.

Edited by Xeven, 05 January 2013 - 06:57 AM.


#9 DogmeatX

    Member

  • PipPipPipPipPipPip
  • 295 posts

Posted 05 January 2013 - 06:57 AM

Not sure if this likely an issue. If it was why is it only MWO is affected but not other games? I think most systems by default are async anyway i.e. not 1:1

As mentioned elsewhere the problem (one anyway) appears to be related to mechs themselves, texture/video ram or something..

In any case asking users to mess about in CMOS settings is no real "solution"

Edited by DogmeatX, 05 January 2013 - 06:59 AM.


#10 Carnivoris

    Member

  • PipPipPipPipPipPip
  • 463 posts

Posted 05 January 2013 - 07:03 AM

WOOOOOOOOOOO! UPS FOR OP! Finally! Someone who knows what he's supposed to do in a beta test! Indeed, good on you, sir. This should go a long way towards resolving stability issues.

#11 MrPils

    Member

  • PipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 142 posts
  • LocationLiverpool, UK

Posted 05 January 2013 - 07:40 AM

So you found your memory or CPU IMC wasnt stable @ 2400mhz? Nothing to do with the game Im afraid.

Id suggest you do some stability testing. Linx and Prime95 are both good, make sure you set them both to use at least 80% system ram when you test. Youll need to do some bios tweaking (voltage, speed or timings) to get it stable. Some cpu's just cant run 2400mhz, others take a lot of work. Its very much down to each individual system whether itll just work or take some tweaking.

As an example my 3770k isnt stable at 2400mhz even with a good dose of extra voltage. It will get to windows and last for about an hour in game before a lockup/ctd/bsod/restart. Im actually using it at 2000mhz with tight timings as that was the combination that gave me best performance and low voltage. My 3570k on the other hand will run 2600mhz stable all day and night in the same system with minimal voltage increases.

MWO is very hard on your cpu and memory (and graphics memory actually), its quite possible that you will see stability or heat related crashes playing MWO that you wouldnt see playing other games. I can cause the game to generate all sorts of bugs by running slightly low cpu volts or 95% stable ram. FPS drops, yellow screen, CTD, no hud, excessive lag. Basically all sorts of weirdness can go on if your PC isnt 100% rock solid stable when playing MWO.

Sorry for the wall of text :)

#12 smokefield

    Member

  • PipPipPipPipPipPipPip
  • 994 posts
  • Locationalways on

Posted 05 January 2013 - 07:56 AM

Ok...maybe some of you didn't read very carefully what i wrote in my post, there is no problem..happens all the time on the internet. I will make it shorter so it wil be much easier to understand :)


1. before the patch i was able to play the game like everyone else...crashing now and then or having the fps bug.
after all went to hell.

2. After a lot of tests, both hardware and software, all drivers and SO updated..i turned over to dev's.

I didn't go into detail about the tests here but I can if anyone is interested.

3. I am IT engineer...I know there is always something to learn in this field but I think i know the basics and what i am doing, I am not talking just to talk.

4. So I could say I have found my issue.

underline MY issue...it is a hint for others who may encounter a lot of crashes.

only MWO was crashing, and trust me mwo is not stressing my specs at all...but it is buggy and from there comes the problem.


System is perfectly stable in any test. cpu temp is not going over 40 when playing mwo.

#13 AlexEss

    Member

  • PipPipPipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 2,491 posts
  • Locationthe ol north

Posted 05 January 2013 - 07:56 AM

Best solution i found..

A little program called memory cleaner..





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users