Jump to content
Welcome to the virtual battlefield, Guest!

World War II Online is a Massively Multiplayer Online First Person Shooter based in Western Europe between 1939 and 1943. Through land, sea, and air combat using a ultra-realistic game engine, combined with a strategic layer, in the largest game world ever created - We offer the best WWII simulation experience around.

hmm, new application error


ratatosk
 Share

Recommended Posts

ok, this has happened twice in the past few days and is a new one for me. Playing for some time, then get system message that runtime error has occured, then wwiionline has quit working, etc. Nothing of interest in WW2_Log.txt, but when I look at application log using event viewer, I see this:

Faulting application name: ww2.exe, version: 1.33.4.255, time stamp: 0x4da86f0a

Faulting module name: ww2.exe, version: 1.33.4.255, time stamp: 0x4da86f0a

Exception code: 0x40000015

Fault offset: 0x005cb637

Faulting process id: 0xcdc

Faulting application start time: 0x01cc1d841fc0e8bd

Faulting application path: C:\PROGRA~2\CRS\BATTLE~1\ww2.exe

Faulting module path: C:\PROGRA~2\CRS\BATTLE~1\ww2.exe

Report Id: bb5250ab-8992-11e0-89bc-0025648c1293

so what mischief is this? Thanks.

Link to comment
Share on other sites

  • Registered Users
ok, this has happened twice in the past few days and is a new one for me. Playing for some time, then get system message that runtime error has occured, then wwiionline has quit working, etc. Nothing of interest in WW2_Log.txt, but when I look at application log using event viewer, I see this:

Faulting application name: ww2.exe, version: 1.33.4.255, time stamp: 0x4da86f0a

Faulting module name: ww2.exe, version: 1.33.4.255, time stamp: 0x4da86f0a

Exception code: 0x40000015

Fault offset: 0x005cb637

Faulting process id: 0xcdc

Faulting application start time: 0x01cc1d841fc0e8bd

Faulting application path: C:\PROGRA~2\CRS\BATTLE~1\ww2.exe

Faulting module path: C:\PROGRA~2\CRS\BATTLE~1\ww2.exe

Report Id: bb5250ab-8992-11e0-89bc-0025648c1293

so what mischief is this? Thanks.

32 bit windows?

I'm just guessing but if you are running 32 bit OS do you have a ton of stuff running in the background?

I'm thinking that's a out of memory error.

Link to comment
Share on other sites

More like a virtual memory error, probably from an errant video driver. This is one of those #$@$@ crashes that don't get reported to the exception handler. Likely Windows said "O crap" and punted the app. I hate these, we get no report. I noticed from an earlier CTD you have a 260 - the NVidia drivers for the 240/250/260 are total crappola.

Link to comment
Share on other sites

One thing I could recommend , and its helped me heaps as I run a 32 system , is to download a tool called 'Gamebooster' from IOBit software.

The full package costs 10USD and its well worth it , there is a 'free' version also.

It basically closes down all those services that are not required , the free version does this but the paid version closes down a hell of a lot more...and then some.

Plus it has some other tools in there above the free version.

http://www.iobit.com/gamebooster.html

Link to comment
Share on other sites

win7/64 bit, 9GB memory. I think ahwulf is right, it is prolly some more of nvidia's incompetence. But it seems like last time I had an ati card, it was also cursed with driver weirdness- how are they now?

Link to comment
Share on other sites

I know with the latest Nividia drivers it also installs a handy 'update' now feature so that might cure your issue, no more hunting around and guessing when the new ones are out.

Might pay you to wipe the old ones out and go on Nividia and do a scan from there (they now do a hardware detect update)

Link to comment
Share on other sites

I know with the latest Nividia drivers it also installs a handy 'update' now feature so that might cure your issue, no more hunting around and guessing when the new ones are out.

Might pay you to wipe the old ones out and go on Nividia and do a scan from there (they now do a hardware detect update)

Thanks, I will give that a try altho the problem hasn't recurred since I posted about it.

Link to comment
Share on other sites

More like a virtual memory error' date=' probably from an errant video driver. This is one of those #$@$@ crashes that don't get reported to the exception handler. Likely Windows said "O crap" and punted the app. I hate these, we get no report. I noticed from an earlier CTD you have a 260 - the NVidia drivers for the 240/250/260 are total crappola.[/quote']

My 260 never crashes. Mac guys... what would they no from video cards anyway!!! =]

It's the 460 drivers that are poo poo.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...