Jump to content

Help. Getting Irritated


32 replies to this topic

#21 Terona

    Member

  • PipPipPipPipPip
  • Bad Company
  • 143 posts

Posted 19 July 2016 - 07:29 PM

i got a ticket in with tech support (mwo) ill keep the thread updated on their findings.


what setup you got smoke?

amd phenom x4 955BE
asrock socket 3mb (a cheap one)
gigabyte ram 8gb (4sticks of 2) 1333
GeForce GTX 660TI
win 10 64bit

#22 Terona

    Member

  • PipPipPipPipPip
  • Bad Company
  • 143 posts

Posted 19 July 2016 - 07:52 PM

ran the mem diag tool

says I have a memory problem. no details on what the problem is... Posted Image

event viewer has a metric asstonn of errors and warnings. Posted Image

mostly services ive disabled.. going to pull my ram and reseat.

works 99% of the time. be back in an hour :P

Edited by Darth Terona, 19 July 2016 - 07:59 PM.


#23 Revis Volek

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 7,247 posts
  • Google+: Link
  • Facebook: Link
  • LocationBack in the Pilots chair

Posted 19 July 2016 - 07:58 PM

View PostDarth Terona, on 19 July 2016 - 07:52 PM, said:

ran the mem diag tool

says I have a memory problem. no details on what the problem is... Posted Image



MWO i think killed or finished off some old RAM i had in my rig as well. Just get two new sticks matching the ones you got now and then try them in pairs to see which stick is actually bad.


If its bad its bad, not much you can do yourself to service a pc of RAM.

#24 Terona

    Member

  • PipPipPipPipPip
  • Bad Company
  • 143 posts

Posted 19 July 2016 - 08:06 PM

the speedfan download is a virus/net tracker. recommend no one clicks on that.

well. yea.. but I recently broke the whole pc down to install new coolermaster cpu cooler. so it could be some dust got into a ram slot, or some of it wasn't seated properly. (although windows does detect all 8gigs of ram).. so its a long shot, but worth it.

#25 Smokewolf

    Member

  • PipPip
  • Philanthropist
  • Philanthropist
  • 39 posts

Posted 19 July 2016 - 08:59 PM

Uninstalling and reinstalling seemed to work. Just played about 8 matches with no problems. Saved my profiles so I did not have to redo all my settings. Good luck Darth.

oh..my rig is
core i7 4770k
gigabyte z97x mobo
24 GB of RAM
GeForce GTX 760
win 64bit.

#26 Terona

    Member

  • PipPipPipPipPip
  • Bad Company
  • 143 posts

Posted 19 July 2016 - 09:15 PM

yea, my issue is a bad stick of ram.

#27 AnTi90d

    Member

  • PipPipPipPipPipPipPipPip
  • Ace Of Spades
  • Ace Of Spades
  • 1,229 posts
  • Google+: Link
  • Facebook: Link
  • Twitter: Link
  • Twitch: Link
  • Locationhttps://voat.co/

Posted 19 July 2016 - 10:57 PM

View PostDarth Terona, on 19 July 2016 - 08:06 PM, said:

the speedfan download is a virus/net tracker. recommend no one clicks on that.


No, that's a false positive. The program gives false positives on a lot of lower end antivirus software.

http://www.tomsguide...ilities-viruses

It hooks in to get fan speeds and all the temperature sensor readings and can manually control the fan speed settings. (The hooking is where the false positives come from.) It just also happens to have a really good SMART diagnostic utility that spits out the results in a web page.

The program is 100% safe to download and install. It's a legitimate diagnostic utility and that is the official link.

#28 Terona

    Member

  • PipPipPipPipPip
  • Bad Company
  • 143 posts

Posted 20 July 2016 - 12:42 AM

mkay :P

#29 Rakshasa

    Member

  • PipPipPipPipPipPipPip
  • Urban Commando
  • Urban Commando
  • 560 posts
  • LocationThe Underhive, Pomme De Terre

Posted 20 July 2016 - 02:16 AM

I get this error sometimes too, running the Repair Tool through the launcher fixes it though. Good luck with issue :D

#30 Terona

    Member

  • PipPipPipPipPip
  • Bad Company
  • 143 posts

Posted 20 July 2016 - 06:13 AM

I think its fixed.

pulled bad ram and am now enjoying even more fps :P

#31 Mudhutwarrior

    Member

  • PipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 4,183 posts
  • LocationThe perimieter, out here there are no stars.

Posted 20 July 2016 - 07:11 AM

View PostDarth Terona, on 19 July 2016 - 06:54 PM, said:

overall, thank you Naduk for a very helpful post.. even if it don't fix the problem (may be ram or hdd) I can see the work you put into posting that.

appreciate it.

(needs to be mc/mech swapping cause id totally compensate you for your contribution)



It would have been nice if PGI didn't direct you to a private conversation with tech support and instead they came here and walked you through it. Then anyone could easily come back for future reference. Everything is closed doors with them. Everything.

Naduk has got it going on.

View PostAnTi90d, on 19 July 2016 - 10:57 PM, said:


No, that's a false positive. The program gives false positives on a lot of lower end antivirus software.

http://www.tomsguide...ilities-viruses

It hooks in to get fan speeds and all the temperature sensor readings and can manually control the fan speed settings. (The hooking is where the false positives come from.) It just also happens to have a really good SMART diagnostic utility that spits out the results in a web page.

The program is 100% safe to download and install. It's a legitimate diagnostic utility and that is the official link.



Run it myself. Great piece of kit in the toolbox

#32 MadDach5und

    Member

  • PipPip
  • Ace Of Spades
  • 46 posts
  • LocationMinnesota

Posted 23 December 2016 - 11:08 AM

I'm pretty sure this is happening from a memory shortage of some sort, using virtual memory has its glitches -- what bugs me is the timing is always the same.

Any patch, any hot fix that gets downloaded and installed - once completed, I start up the game, and it works pretty much flawlessly. Can play matches for hours. No errors.

After I shut down the app - the NEXT time I start it up again, it ALWAYS fails. It starts up, lets me log in, I can do whatever I want in Mech Lab - even enter a match and have it loading -- it always, ALWAYS crashes at the point where you are supposed to see the team preview window before being deployed into the actual match. I cannot re-start the app and re-join the match - it will still crash at that same exact window, again and again.

Running the RepairTool will fix the problem. It purges the cache and re-sets the game clean so it will work. The scan takes a good ten minutes sometimes, and therefore that match is forfeit and I get penalized for a disconnect that wasn't my fault. I generally won't get the error again until another upgrade or patch needs to be installed.

What I can't understand is why the cache is always an issue upon re-starting a fresh game, but NOT after a patch install. Seems to me, it should be the other way around. And why can't the cache dump be a quick fix setting without having to scan the ENTIRE file structure within the Repair Tool? Am I missing something?

My Rig: (Yeah, I know it's old)
Toshiba Satellite A505 Laptop
i3 CPU 330 @ 2.13 ghz 64-bit
4 GB RAM (2x2GB)
500 GB HD (only 1/2 full)

#33 Revis Volek

    Member

  • PipPipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 7,247 posts
  • Google+: Link
  • Facebook: Link
  • LocationBack in the Pilots chair

Posted 23 December 2016 - 12:06 PM

Im gonna wager 100 Cbills you have a stick of RAM going bad or not properly seated.


But thats just my guess...

View PostMadDach5und, on 23 December 2016 - 11:08 AM, said:

I'm pretty sure this is happening from a memory shortage of some sort, using virtual memory has its glitches -- what bugs me is the timing is always the same.

Any patch, any hot fix that gets downloaded and installed - once completed, I start up the game, and it works pretty much flawlessly. Can play matches for hours. No errors.

After I shut down the app - the NEXT time I start it up again, it ALWAYS fails. It starts up, lets me log in, I can do whatever I want in Mech Lab - even enter a match and have it loading -- it always, ALWAYS crashes at the point where you are supposed to see the team preview window before being deployed into the actual match. I cannot re-start the app and re-join the match - it will still crash at that same exact window, again and again.

Running the RepairTool will fix the problem. It purges the cache and re-sets the game clean so it will work. The scan takes a good ten minutes sometimes, and therefore that match is forfeit and I get penalized for a disconnect that wasn't my fault. I generally won't get the error again until another upgrade or patch needs to be installed.

What I can't understand is why the cache is always an issue upon re-starting a fresh game, but NOT after a patch install. Seems to me, it should be the other way around. And why can't the cache dump be a quick fix setting without having to scan the ENTIRE file structure within the Repair Tool? Am I missing something?

My Rig: (Yeah, I know it's old)
Toshiba Satellite A505 Laptop
i3 CPU 330 @ 2.13 ghz 64-bit
4 GB RAM (2x2GB)
500 GB HD (only 1/2 full)



IT is from memory issues, i got this all the time before i replaced my RAM, it was just ONE stick that was wonky.

I also suggest upgrading your amount, 4GB is very little. Hardly can even surf the internet with 4gb these days. GO 8GB if you must replace it.

Edited by Revis Volek, 23 December 2016 - 12:07 PM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users