17 replies to this topic

[Kyle Polulak]

Game crashes with an R6025 Run-time Error

Steps to Reproduce
0. Boot the game.
1. Login to the game.
2. Launch a match.
3. ????
4. Observe crash with C++ Runtime error dialogue.

Notes
Problem occurs more frequently when a visual bug has occured, and notes include the following details:

Spoiler

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

Workarounds
None Known (Niko says: Walk-time can lead to less accidents)

Questions
How often does this issue occur?
Does this occur on a specific map or any map?
Does this occur with a specific mech or any mech?
What are your basic system specs? (CPU, GPU, RAM)

[Rashhaverak]

Happened only once about a week ago. Thought it was a windows problem vice a MWO problem so I didn't report it. Should have known better, I guess.

I had just finished in mechlab and exitted out of game after saving.

CPU: i7-3820
GPU: GeForce GTX 570
RAM:8 GB

[Willie Sauerland]

I see it if I play a long time (say, two hours). During that time, it will be fine then I will notice textures missing or not completed. The next game will be a 4FPS game and I will receive this error when trying to exit out of the game to restart my client. I usually have to kill the client via Task Manager.

Unfortunately, the only map I have seen this on is Ice City (day time) playing any mech. Usually, the tunnel exit at E4 will not render correctly and some buildings will also be missing textures. The next 4FPS game doesn't seem to matter....

My specs:

AMD FX-8150 8 Core Processor
32 GB DDR3 RAM
Nvidia GeForce GTX-550 Ti

Edited by Willie Sauerland, 03 January 2013 - 01:02 PM.

[TML Winston]

This only happens to me when I EXIT the game.

[Sir Stomps A Lot]

Happens for me frequently after getting the 4 FPS bug. Basic system specs:
Core i5 2500K
8GB RAM
Geforce GTX 650
Windows 7 x64

My brother had the same problem when we played last weekend. His system is nearly the same as mine, except he has a Geforce GTX 470 and runs Windows 8 x64.

[Mudhawk]

Happens to me all the time when I get the FPS bug or the yellow screen bug. Happens every dozend or so games, though FPS issues are more frequent.
Also if FPS bug happes I experience difficultys only when looking towards players. Not when looking towards empty parts of the map. So I guess some Mech Models are not loading correctly.

My system :
Intel Core i5
8 GB DDR3 Ram
Geforce GTX 60 TI (Driver 310.70)
Windows 7 64 bit

[Mass Fogger]

After playing 5 rounds loaded in to river city night map. FPS drops when ever more then 1 mech is in my field of view. after the match was over quit and got error.

intel I5
16GB RAM
GTX 550TI
Windows 7 64Bit

[The Wolfe]

I have received this error about 4 time now. Always after a longer session. In the game the fps goes way down, so I restart and get the error.

Intel i5
8 Gb RAM
GTX 570
Win 7

[Gryphdog]

After checking the logs, I found these errors which stack up the longer the client is running. The following errors occured when loading the frozencity map:

Spoiler

[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/forestcolony_clouddome_a.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/forestcolony_clouddome_a.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'objects/environments/skyboxes/rivercity_cloud_fulldome.dds' compressed texture is dangerous (only single mip) [File=objects/environments/skyboxes/rivercity_cloud_fulldome.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop0.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop0.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/ppc_beam_b.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/ppc_beam_b.dds]
[Error] Error: CTexMan::ImagePreprocessing: Scaling of 'textures/particles/weapons/laser_beam_1x4_lop1.dds' compressed texture is dangerous (only single mip) [File=textures/particles/weapons/laser_beam_1x4_lop1.dds]

[Shaio]

Questions
error happens at exit of game client.

Computer:
5i CPU
16GB RAM
Nvidia GTX470

[Mad Porthos]

This has happened to me three times recently, right after I experienced the "4fps" bug. I'm not trying to conflate the two different things, but the cause that makes me wish to quit game is the 4 fps bug for a "restart" and I get this...

Runtime Error!
Program C:...
R6025
_pure virtual function call

At that same time, when I bring up Mechwarrior in the task manager it will still be running until I actually end task it.
If I am trying to exit mechwarrior but have not had the 4fps bug, I do NOT get this Runtime Error so far, but it may simply be chance as I am much more likely to be exiting game several times in a session from desire to restart from the 4fps bug, rather than anything else. Also, typically this is exit game from a currently connected (albeit bugged) game, as opposed to say, from Mechlab or such when I'd normally be quitting when I was simply done playing.

CPU: Qx-9650 quad core, running at 3.6ghz
Graphics: 2 zotac geforce 660ti 2gb cards running in SLI.
Memory: 4gb ddr2-pc8500 (running at 1066.6mhz)
FSB: Running at 400mhz
Motherboard: An ancient EVGA 780i SLI
Cooling, Antec Kuhler h20 920 water cooling, close loop.

Edited by Mad Porthos, 06 January 2013 - 01:57 PM.

[StraferX]

I get this every time I exit the game if I use the quit function.

I7 9770k
asus p8z77-v propatrion intel extreme master ddr3 1600 x 16g
evag 9600 ti 2 gb
2 x OCZ ssd Vector 4 256g + 1 500g Velociraptor
30 up/12 down cable connection

[HoppinRaven]

Happens when I exit the game and mech is still in battle or stuck loading from battle.

[Popolou]

I fairly regularly have this error. However what i have noticed is that it has always occured when playing River City. Massive game lag and background error dialog box.

I7 860
8GB Ram
Ati 5800 1GB Ram

Edited by Popolou, 12 January 2013 - 09:29 AM.

[MGoo]

I have this Every time i have to exit due to the 4 fps bug (which happens if i play for too long and dont restart the game), I have noticed that if i quit a match and get back to mechlab, that my gpu is still under load (i have a temp,gpu load,fan speed etc etc widget + everest widget) and it will continue to be under load until i actually exit the MWO program, then the error comes up and windows just forces it to exit.

This Issue Occurs Everytime I play for an extended period but the time interval from starting to buggin out is not consistent, some time its in the 4th match, sometimes the 20th, so i try to restart every so often.
Happens on any map
Happens with any mech
i7 2600k
16 GB RAM
Asus Gtx 570 Direc CUII (1280mb ddr5 iirc and driver are latest version tho it occured alot before too)

Oh and WIN 7 x64 premium

[Popolou]

Popolou, on 12 January 2013 - 09:29 AM, said:

I fairly regularly have this error. However what i have noticed is that it has always occured when playing River City. Massive game lag and background error dialog box.

I7 860
8GB Ram
Ati 5800 1GB Ram

Had it again.

Was on Frozen City and serious amounts of lag. Seemed to me that there was a memory leak somewhere cos i started seeing the hard disk going wild. Virtual mem swapping perhaps?

Exited to desktop with R6025 - pure virtual function call.

[The Bleyz]

I get an error when I try to open the game up when I have mumble running.

[memorandum]

i only get this error after getting the fps bug, but i only get the fps bug after 3-4 hours gameplay.

i've started having the fps counter(F9) always on, since i usually have 60+ fps steady, but when it starts to drop and it will after a bunch of games, when it starts jumping between 35-60 i can expect the next game to be fps bugged.

i find the fps bug weird cause it sometimes seems to be moving, like it's attached to a mech.

my specs:

cpu: I7 920 D0 2,67Ghz @ 4,2Ghz
ram: corsair 3x2gb tripple channel
mobo: evga x58 sli
gfx: 2x asus gtx580 sli