mscorwks.dll causes application crash...

A

always

New Member
Hi.
Not sure if this goes here, but I was looking for some help.

I am running Windows Vista Ultimate x64.

When I start up an application, Saitek Profile Editor (Which for a joystick/throttle I purchased), seemingly at random times I get a ProfileEditor has stopped working error. I have updated my motherboard and graphic card drivers, and I have microsoft .Net Framework 3.5 installed...I haven't been able to find any useful info online about this problem.

The problem details are as fallows:

Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: Pr0fileEditor.exe
Application Version: 6.6.1.15
Application Timestamp: 4948e597
Fault Module Name: mscorwks.dll
Fault Module Version: 2.0.50727.3053
Fault Module Timestamp: 4889e870
Exception Code: c0000005
Exception Offset: 0000000000173be7
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
 

My Computer

System One

have you updated your saitkec???

this kind of error is access violation error in which the said program (saitkec) tries to access parts of the memory not allowed to it....

x64 is very picky about program memory access

try to look for the lasest drivers here...

Drivers & Software
 
Last edited:

My Computer

System One

always said:
Hi.
Not sure if this goes here, but I was looking for some help.

I am running Windows Vista Ultimate x64.

When I start up an application, Saitek Profile Editor (Which for a joystick/throttle I purchased), seemingly at random times I get a ProfileEditor has stopped working error. I have updated my motherboard and graphic card drivers, and I have microsoft .Net Framework 3.5 installed...I haven't been able to find any useful info online about this problem.

The problem details are as fallows:

Description:
Stopped working
Problem signature:
Problem Event Name: APPCRASH
Application Name: Pr0fileEditor.exe
Application Version: 6.6.1.15
Application Timestamp: 4948e597
Fault Module Name: mscorwks.dll
Fault Module Version: 2.0.50727.3053
Fault Module Timestamp: 4889e870
Exception Code: c0000005
Exception Offset: 0000000000173be7
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Click to expand...

Hi Always,

You have this backwards ;) Its actually Saitek Profile Editor crashing mscorwks, you need to contact them for an updated version or report the bug to Saitek as they are the only ones who are able to stop their application from crashing ;)

Steven
 

My Computer

System One

I have sadly come to that realization. That was supposedly the latest update to the program...Unfortunantly Saitek seems very unfriendly with their customer service. I'll just have to stick to an older version of the software.

Thanks for your replies.
 

My Computer

System One

always said:
I have sadly come to that realization. That was supposedly the latest update to the program...Unfortunantly Saitek seems very unfriendly with their customer service. I'll just have to stick to an older version of the software.

Thanks for your replies.
Click to expand...

I looked at my .net framework dev docs about that exception (Saitek obviously doesn't read the .net documentation...) and it says the following...

Code: 
Exception Code: c0000005 is due to buffer overruns - if an app uses pointers
 in .NET code then you have to be very careful not to overwrite your memory 
buffers because otherwise you will destroy data used by .NET itself and this can 
result in rather weird failures that are not obviously due to your code: if you use 
unsafe code you need to assume the worst and be on guard at all times meaning 
you must verify all [in] and [out] parameters being used and vet anything thats
 not expected during the Return [in] call.
Pointers in .NET allow an application to bypass internal checks that prevent reading or writing of data from/to memory that is not actually the memory that was allocated for the application. This means that if the application doesn't properly pass required values or contains a mistake while using unsafe code outside the framework you will write over some .NET data structures in memory that will crash the framework, or it will attempt to read from memory that you are not allowed to read from or was freed memory or was being used by another application - all this will lead to a crash of application.

Saitek needs to include some (Try <code here> Catch ex As Exception <handle crash here> End Try) around their code to find the cause, If they bothered to send you the debug file or include a try statement to identify the exact block of code causing the crash it could be fixed within 5 minutes :sarc:
 

My Computer

System One

You must log in or register to reply here.
Back
Top