Capture One 6 evaluation has stopped working

NN160157UL2

• 30 de diciembre de 2010 11:41

I'm currently running (or was) the 30 day trial copy (12 days left) of CO 6.0.1 it was working fine until a few days ago when it stopped working and I get the following error

Description:
Stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: CaptureOne.exe
Application Version: 6.0.44545.135
Application Timestamp: 4cf677c1
Fault Module Name: mscorwks.dll
Fault Module Version: 2.0.50727.4952
Fault Module Timestamp: 4bebe78c
Exception Code: c0000005
Exception Offset: 00000000001a598c
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 2057

My licensed version of CO 5.2.1 works perfectly

I did install 2 new games; after which CO 6 stopped working, so I'm willing to accept that they are the culprit. However I have uninstalled the games and CO 6, and reinstalled CO 6 it still gives the same error.

Any ideas how I can get CO6 working again?

Chris

0

• 

  Jim MSP

  • 30 de diciembre de 2010 16:44

  The next step I would take is to clean the registries after you uninstalled the games.
  A simple uninstall using the basic Windows capabilities does not always clean things up.
  I generally use a couple of different programs, depending on whether its my XP or Win 7 system; they tend to find different things. On Win 7, I am using the free versions of CCleaner and COMODO, as well as Norton Utilities.
  
  Good luck,
  
  Jim

  0
• 

  Paul Steunebrink

  • 30 de diciembre de 2010 21:11

  Your report points the finger towards the mscorwks.dll. This is a .NET Framework 2.0 component, which is part of Win7. Maybe it was overridden or altered by the game installer. If that is the case, reinstallation of CO6 won't help you.
  
  You can do a search for mscorwks.dll on the Windows folder. On a Win7 x64 system, I found many entries with it in the name, but only two count (at least, I think):
  

  C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
  (time stamp (DD-MM-YYYY) and size: 21-5 2010 0:49 5,54MB)

  
  

  C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
  (time stamp (DD-MM-YYYY) and size: 21-5 2010 0:38 9,59MB)

  
  
  Note that some malware seems to camouflage itself as mscorwks.dll. Check with your anti-virus/malware software.

  0
• 

  NN160157UL2

  • 6 de enero de 2011 15:23

  Well, I still haven't got this working.
  
  Everything seems to be OK from the Windows side as far as I can tell...
  
  I ran sfc /scannow and that didn't report any issues
  
  Interestingly I installed the 32bit version of 6.0.1 alongside the 64bit and that works just fine .......as 5.x is 32bit I guess I could stick with the 32bit, but I would like to get this resolved.
  
  
  Chris

  0
• 

  Paul Steunebrink

  • 6 de enero de 2011 17:17

  [quote="NN160157UL" wrote:
  I ran sfc /scannow and that didn't report any issues

  
  Are you aware that SFC does not report to your screen but to a log? Have you reviewed the log? In this Microsoft article you can find information how to extract the SFC entries from the log: http://support.microsoft.com/kb/929833
  

  [quote="NN160157UL" wrote:
  Interestingly I installed the 32bit version of 6.0.1 alongside the 64bit and that works just fine .......as 5.x is 32bit I guess I could stick with the 32bit, but I would like to get this resolved.

  
  This again feeds my assumption that one .NET file (the 64-bit version) was corrupted, the other (32-bit version) not. Have you been able to do the search as I suggested earlier for size and time stamp comparison?

  0

La publicación no admite más comentarios.