10 replies to this topic

[Eraos]

This has been reported before, but I don't see a report under patch 1.2.168, so I am reporting it here to be clear that the issue still exists.

I can fairly reliably recreate this by playing some matches (grouped with a friend) and then exiting the client. I get an R6025 runtime error, and when I close that out I get the standard Windows 7 "MechWarrior Online has stopped working" dialog (both are shown below).






The full problem details given in the "MechWarrior Online has stopped working" dialog are as follows (I am assuming that the hashes given in the "Additional Information" parameters are not privileged information in disguise):


Problem signature:
Problem Event Name: APPCRASH
Application Name: MWOClient.exe
Application Version: 3.4.1.4418
Application Timestamp: 50cfac5e
Fault Module Name: MSVCR100.dll
Fault Module Version: 10.0.40219.325
Fault Module Timestamp: 4df2be1e
Exception Code: 40000015
Exception Offset: 0008d6fd
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 3252
Additional Information 2: 32528dd6159ece4b0813cd35b5d99269
Additional Information 3: 26c4
Additional Information 4: 26c46992914718aa4e84ae3552ec22b9

Read our privacy statement online:
http://go.microsoft....88&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[RudeDogX]

I have been getting the exact same thing. Thought it was just my computer.

[Acid Phreak]

no that is a error in the programming!

[Mass Fogger]

I dont know was side its on , but i have been getting alot of them.Im running a i5 processsoer and a 550 ti Gcard. im thinking it a driver support issue, but i could be wrong

[Terse]

I always get this when I get the fps bug. I sometimes get it without having got the fps bug -- having quit before the time I predict the bug to occur. I never get this if I only play a game or two and quit. I don't know if it is related to the fps bug but from my observations I am suspicious.

[Willie Sauerland]

Terse, on 31 December 2012 - 09:16 AM, said:

I always get this when I get the fps bug. I sometimes get it without having got the fps bug -- having quit before the time I predict the bug to occur. I never get this if I only play a game or two and quit. I don't know if it is related to the fps bug but from my observations I am suspicious.

I get this bug when I get the FPS bug as well. Seems to me to be related to the memory leak issue which has been reported many times before. Last night, my video driver (it is the newest stable driver from NVIDIA for my card, released in December) crashed twice and then I got the FPS bug and this error immediately after.

[krolmir]

Yeah i see this one after the game bugs or crashes at least once a day

[3ffigy]

I experienced this bug for the first time just yesterday.

[Gallowglas]

Terse, on 31 December 2012 - 09:16 AM, said:

I always get this when I get the fps bug. I sometimes get it without having got the fps bug -- having quit before the time I predict the bug to occur. I never get this if I only play a game or two and quit. I don't know if it is related to the fps bug but from my observations I am suspicious.

Same.

[Henry Morgan]

Getting the same error myself. Some of the in-game symptoms that occur when I get this error on exit are:
- Yellow screen of doom at the start of a match.
- FPS bug
- Will find myself unable to use any of the Chat functions
- Building textures suddenly blank, just flat polygons

OS: Windows 8 Professional (64 bit)
CPU: Intel Core i7-3930K (3.2 GHz)
Memory: 16 Gig RAM (DDR3-2133)
GPU: nvidia GeForce 670 GTX

[Allekai]

something to do with a memory leak or something.. I get that all the time but only after i've played 5-6 games in a row.. the last game I can tell it's going to happen becuase my game freeze up when in the middle of combat and becomes so unresposive I can bearly see whent i'm shooting at.. like 2-3 FPS.. then i restart the game and all is fine again.