EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Pages: [1]   Go Down

Author Topic: Crashes in 4.04  (Read 10240 times)

ianf123

  • Karma: 0
  • Offline Offline
  • Posts: 2
  • Operating System:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Firefox 10.0.2 Firefox 10.0.2
    • View Profile
Crashes in 4.04
« on: 09 March 2012, 23:00 »

I'm hoping someone can give me some advice.

I have a MAME v0.144 collection which I was in the process of updating to v0.145.  Both source and add files are ZIPs.  I initially used the 64 bit version of 4.04, which was working beautifully.  Then the crashes started, and since then, any attempt to update a ROM crashes ClrMamePro.

I've tried the 32 bit version, recreating the profile, cleaning out the caches, reencoding the add files.  It scans just fine, but seems to crash during the ROM update process.

Any advice anyone can provide would be most appreciated.

Crash reporter data (sans crash dump) is below:

<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
   <OSVersionInformation>
      <WindowsNTVersion>6.1</WindowsNTVersion>
      <Build>7601 Service Pack 1</Build>
      <Product>(0x1): Windows 7 Ultimate</Product>
      <Edition>Ultimate</Edition>
      <BuildString>7601.17640.amd64fre.win7sp1_gdr.110622-1506</BuildString>
      <Revision>1130</Revision>
      <Flavor>Multiprocessor Free</Flavor>
      <Architecture>X64</Architecture>
      <LCID>1033</LCID>
   </OSVersionInformation>
   <ParentProcessInformation>
      <ParentProcessId>6012</ParentProcessId>
      <ParentProcessPath>C:\Windows\explorer.exe</ParentProcessPath>
      <ParentProcessCmdLine>C:\Windows\Explorer.EXE</ParentProcessCmdLine>
   </ParentProcessInformation>
   <ProblemSignatures>
      <EventType>APPCRASH</EventType>
      <Parameter0>cmpro64.exe</Parameter0>
      <Parameter1>4.0.4.0</Parameter1>
      <Parameter2>4f4ff56c</Parameter2>
      <Parameter3>cmpro64.exe</Parameter3>
      <Parameter4>4.0.4.0</Parameter4>
      <Parameter5>4f4ff56c</Parameter5>
      <Parameter6>40000015</Parameter6>
      <Parameter7>00000000002a01e2</Parameter7>
   </ProblemSignatures>
   <DynamicSignatures>
      <Parameter1>6.1.7601.2.1.0.256.1</Parameter1>
      <Parameter2>3081</Parameter2>
      <Parameter22>6ee0</Parameter22>
      <Parameter23>6ee090077202ce0bd92401269acde305</Parameter23>
      <Parameter24>fa98</Parameter24>
      <Parameter25>fa982b1ef7a1160a9eb1993d700f949a</Parameter25>
   </DynamicSignatures>
   <SystemInformation>
      <MID>3AD2AD16-F27F-4E5A-991F-8868126FB79F</MID>
      <SystemManufacturer>Gigabyte Technology Co., Ltd.</SystemManufacturer>
      <SystemProductName>GA-880GMA-UD2H</SystemProductName>
      <BIOSVersion>F5</BIOSVersion>
   </SystemInformation>
</WERReportMetadata>

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="cmpro64.exe" FILTER="CMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="cmpro64.exe" SIZE="6424064" CHECKSUM="0xC7BE2129" BIN_FILE_VERSION="4.0.4.0" BIN_PRODUCT_VERSION="4.0.4.0" PRODUCT_VERSION="4, 0, 4, 0" FILE_DESCRIPTION="clrmamepro" PRODUCT_NAME="clrmamepro" FILE_VERSION="4, 0, 4, 0" ORIGINAL_FILENAME="cmpro.exe" INTERNAL_NAME="clrmamepro" LEGAL_COPYRIGHT="Copyright (C) 1999 - 2012 by Roman Scherzer" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x6238D1" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.0.4.0" UPTO_BIN_PRODUCT_VERSION="4.0.4.0" LINK_DATE="03/01/2012 22:17:16" UPTO_LINK_DATE="03/01/2012 22:17:16" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="uninstall.exe" SIZE="35919" CHECKSUM="0xD0B0C21C" BIN_FILE_VERSION="4.0.4.0" BIN_PRODUCT_VERSION="4.0.4.0" PRODUCT_VERSION="4.00.04.0" FILE_DESCRIPTION="" COMPANY_NAME="Roman Scherzer" PRODUCT_NAME="clrmamepro" FILE_VERSION="" LEGAL_COPYRIGHT="" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="4.0.4.0" UPTO_BIN_PRODUCT_VERSION="4.0.4.0" LINK_DATE="12/05/2009 22:50:46" UPTO_LINK_DATE="12/05/2009 22:50:46" VER_LANGUAGE="Language Neutral [0x0]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="Unrar64.dll" SIZE="203264" CHECKSUM="0xE658A2E6" BIN_FILE_VERSION="4.0.4.3" BIN_PRODUCT_VERSION="4.0.4.3" FILE_DESCRIPTION="RAR decompression library" COMPANY_NAME="Alexander Roshal" PRODUCT_NAME="RAR decompression library" FILE_VERSION="4.0.4" ORIGINAL_FILENAME="Unrar.dll" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3CF2E" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.0.4.3" UPTO_BIN_PRODUCT_VERSION="4.0.4.3" LINK_DATE="01/04/2011 12:28:06" UPTO_LINK_DATE="01/04/2011 12:28:06" EXPORT_NAME="unrar64.dll" VER_LANGUAGE="Language Neutral [0x0]" EXE_WRAPPER="0x0" />
    <MATCHING_FILE NAME="update.dll" SIZE="221696" CHECKSUM="0xE68F49DB" BIN_FILE_VERSION="1.0.0.5" BIN_PRODUCT_VERSION="1.0.0.5" PRODUCT_VERSION="1, 0, 0, 5" FILE_DESCRIPTION="clrmamepro Updater" PRODUCT_NAME=" updatecm Application" FILE_VERSION="1, 0, 0, 5" ORIGINAL_FILENAME="updatecm.exe" INTERNAL_NAME="clrmamepro Updater" LEGAL_COPYRIGHT="Copyright (C) 2010 by Roman Scherzer" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.5" UPTO_BIN_PRODUCT_VERSION="1.0.0.5" LINK_DATE="12/06/2010 20:43:42" UPTO_LINK_DATE="12/06/2010 20:43:42" VER_LANGUAGE="German (Germany) [0x407]" EXE_WRAPPER="0x0" />
</EXE>
<EXE NAME="cmpro64.exe" FILTER="CMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="cmpro64.exe" SIZE="6424064" CHECKSUM="0xC7BE2129" BIN_FILE_VERSION="4.0.4.0" BIN_PRODUCT_VERSION="4.0.4.0" PRODUCT_VERSION="4, 0, 4, 0" FILE_DESCRIPTION="clrmamepro" PRODUCT_NAME="clrmamepro" FILE_VERSION="4, 0, 4, 0" ORIGINAL_FILENAME="cmpro.exe" INTERNAL_NAME="clrmamepro" LEGAL_COPYRIGHT="Copyright (C) 1999 - 2012 by Roman Scherzer" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x6238D1" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.0.4.0" UPTO_BIN_PRODUCT_VERSION="4.0.4.0" LINK_DATE="03/01/2012 22:17:16" UPTO_LINK_DATE="03/01/2012 22:17:16" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="CMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="1162752" CHECKSUM="0x38678646" BIN_FILE_VERSION="6.1.7601.17651" BIN_PRODUCT_VERSION="6.1.7601.17651" PRODUCT_VERSION="6.1.7600.16385" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.1.7600.16385 (win7_rtm.090713-1255)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x12386D" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7601.17651" UPTO_BIN_PRODUCT_VERSION="6.1.7601.17651" LINK_DATE="07/16/2011 05:27:23" UPTO_LINK_DATE="07/16/2011 05:27:23" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" FILE_ID="0000ade184001d3b1d5cb68c5922428c6148303b63cd" PROGRAM_ID="0000f519feec486de87ed73cb92d3cac802400000000" />
</EXE>
</DATABASE>
« Last Edit: 09 March 2012, 23:00 by ianf123 »
Logged


Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 115
  • Offline Offline
  • Posts: 3295
  • Operating System:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Chrome 17.0.963.78 Chrome 17.0.963.78
    • View Profile
Re: Crashes in 4.04
« Reply #1 on: 10 March 2012, 12:56 »

sounds weird...please send me:

cmpro.ini file from the cmpro main folder
the to your profiler belonging .cmp file from cmpro's settings folder

If it crashes for you when it tries to fix a file, then maybe the file is somehow corrupt. Please try to find out which file is causing the issue and send it as well.
Try to minimize your environment, e.g. by scanning an empty rompath and then add some files only...
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 115
  • Offline Offline
  • Posts: 3295
  • Operating System:
  • Windows XP Windows XP
  • Browser:
  • Chrome 17.0.963.79 Chrome 17.0.963.79
    • View Profile
Re: Crashes in 4.04
« Reply #2 on: 14 March 2012, 07:37 »

any update on that? or anyone else who got that?
Logged

ianf123

  • Karma: 0
  • Offline Offline
  • Posts: 2
  • Operating System:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Firefox 10.0.2 Firefox 10.0.2
    • View Profile
Re: Crashes in 4.04
« Reply #3 on: 14 March 2012, 08:19 »

Hi Roman,

Thanks for your help.  As suggested, I am trying to narrow it down to a small config I can share with you to demonstrate the issue.

Right now, I'm finding the crash easy to duplicate with the full config, but working fine if I narrow it down to a small set of files.

Ian.
Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 115
  • Offline Offline
  • Posts: 3295
  • Operating System:
  • Windows XP Windows XP
  • Browser:
  • Chrome 17.0.963.79 Chrome 17.0.963.79
    • View Profile
Re: Crashes in 4.04
« Reply #4 on: 14 March 2012, 09:16 »

Well...yes...not an easy task I know.......since not only the files in the rompath might be affected but also files in the backup folder.

Usually you should be able to see the setname in the progress window when the crash happens (I hope the progress window is still visible when the system error prompt appears)...that could be a start....you can then e.g. limit the files to that set (and its parents) by entering the name in scanner->setinformation->select sets and hitting apply...the next scan will then only work on that file...

You said it happens during fixing....maybe you can try to disable all fix options...then you can scan and see which files have issue listed....and try to recreate that (limited to the sets in question) in a clean new scenario...
This would also help to check which fix operation might be the reason (name, case, unneeded, etc..)..

as mentioned, a start would be to send me your cmpro.ini file and the .cmp file from your cmpro settings folder...

Logged

Roman

  • Global Moderator
  • Member
  • ***
  • Karma: 115
  • Offline Offline
  • Posts: 3295
  • Operating System:
  • Windows 7/Server 2008 R2 Windows 7/Server 2008 R2
  • Browser:
  • Chrome 17.0.963.79 Chrome 17.0.963.79
    • View Profile
Re: Crashes in 4.04
« Reply #5 on: 14 March 2012, 19:41 »

you might want to give this:

http://mamedev.emulab.it/clrmamepro/binaries/cmp20120314.rar

a try...please let me know if it still crashes for you....
Logged
Pages: [1]   Go Up
 

Page created in 0.135 seconds with 19 queries.