PDA

View Full Version : Random Crash


Anach
11th Jan 2010, 9:58 AM
Win7 x64.

Experiencing a seemingly random crash with the latest version of s3pe (s3pe_1001-10-1727). Couldnt find an error log, so this is the event log.

Crashed a few times, each time I doing something different, though also whilst sitting there doing naught. No such issues with version s3pe_1001-03-1524



Faulting application name: s3pe.exe, version: 1001.10.17.31405, time stamp: 0x4b4a0dda
Faulting module name: mscorwks.dll, version: 2.0.50727.4927, time stamp: 0x4a27466f
Exception code: 0xc0000005
Fault offset: 0x00000000002ca360
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

.NET Runtime version 2.0.50727.4927 - Fatal Execution Engine Error (000007FEF915FA42) (80131506)

pljones
11th Jan 2010, 2:07 PM
Sorry, but there's nothing I can do with that report: mscorwks.dll is a Microsoft component, you're not able to say how to reproduce the error and it's on an OS I'm not able to do development work on.

No stack trace at all?

Is your OS installation up to date? It almost looks like .Net has got some kind of corruption from all the %nn in the message.

Can you try running on WinXP 32 bit and see if the problem remains?

Inge Jones
11th Jan 2010, 2:29 PM
See Peter I told you that you should install Win7

Anach
11th Jan 2010, 2:53 PM
XP. Isnt that the OS people were using back in 2001? :P

Ill try it in an XP VM later. Not really wanting to do much in this heat. I asked Lisa (The Mrs) to keep an eye out for error messages, as her's is doing it also (Win 7 x64) as all I remember getting is a very handy "s3pe has stopped working".

Inge Jones
11th Jan 2010, 3:10 PM
hehe it's not like you can *guess* at the error, in order to report it...

You say "this heat". Can you be sure the update wasn't just a coincidence and the crashes are your computer being a bit hot? Specially if they are happening when the app isn't even actively processing.

Anach
11th Jan 2010, 3:18 PM
XP. Isnt that the OS people were using back in 2001? :P

Ill try it in an XP VM later. Not really wanting to do much in this heat. I asked Lisa (The Mrs) to keep an eye out for error messages, as her's is doing it also (Win 7 x64) as all I remember getting is a very handy "s3pe has stopped working".

Pretty sure, as last time I was using s3pe with those errors, it was yesterday and cooler, besides i've just reverted back to the last known working version and no longer having the crash (even though its hotter today) :)

pljones
11th Jan 2010, 4:02 PM
See Peter I told you that you should install Win7Not on this laptop... Poor thing. When I showed it to the Win7-RC1 installer, it got laughed at... :rofl:

I'll have to set up a development environment on a Win7 partition on my big box (when the new disk comes). Hmm... when does the RC expire..? Must try to check that...

The RC will expire June 1, 2010, and the bi-hourly shutdowns will begin on March 1, 2010

Inge Jones
11th Jan 2010, 4:37 PM
Ok, because of the difficulty tracking this bug, it would be more efficient to wait until we can be sure it's something not just affecting you.

If anyone else experiences this problem, please post here! :D

Anach
11th Jan 2010, 4:57 PM
Not on this laptop... Poor thing. When I showed it to the Win7-RC1 installer, it got laughed at... :rofl:

I'll have to set up a development environment on a Win7 partition on my big box (when the new disk comes). Hmm... when does the RC expire..? Must try to check that...

Around July this year if I recall.

Ok, because of the difficulty tracking this bug, it would be more efficient to wait until we can be sure it's something not just affecting you.

If anyone else experiences this problem, please post here! :D

Well at least two people are, and we both use Win7 x64. Otherwise our hardware and software configs are entirely different. Yes it would be nice to know if anyone else is also having the issue.

pljones
11th Jan 2010, 5:01 PM
http://www.modthesims.info/showthread.php?t=379904
Unrelated bug but another Windows 7 user.