Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
When this version will be launched?
This new version don't worked either.
The same message appears: "Adobe Projector stopped working"
I tried again and the same message appears: "Adobe Projector stopped working"
I see the file details for the main EXE Show:
File Description: Adobe Projector
Type: Application
File Version: 12.0.1.122
Product Name: Director 12.0
Original File Name: Projector.exe
Which I think is why the "Stopped Working" message states "Adobe Projector" rather than
"DungeonsOfCastleMadness229.exe"
For grins I attached a copy of VS 2015 and took a quick look.
Exception states:
Unhandled exception at 0x5C499C81 (iml32.dll) in DungeonsOfCastleMadness229.exe: 0xC0000005: Access violation reading location 0x00640071.
Same type of message logged in event viewer:
Faulting application name: DungeonsOfCastleMadness229.exe, version: 12.0.1.122, time stamp: 0x519a586f
Faulting module name: IML32.dll, version: 12.0.0.111, time stamp: 0x510127ab
Exception code: 0xc0000005
Fault offset: 0x00009c81
Faulting process id: 0x4704
Faulting application start time: 0x01d28987f977493d
Faulting application path: M:\SteamLibrary\SteamApps\common\The Dungeons of Castle Madness\DungeonsOfCastleMadness229.exe
Faulting module path: C:/Users/Tim/AppData/Local/Temp/TempFolder.aag/IML32.dll
Report Id: e6dfc02b-d926-4188-b28a-482331fa3305
Faulting package full name:
Faulting package-relative application ID:
===
So, something is causing an invalid memory access. No source code here obviously, so no idea what the issue is.
===
FWIW, saw the exact same behavior as Original Poster with the various compatibility options.
===
For some reason was unable to actually run some of the Win 10 tests. My anti-virus went nuts trying to deal with them, and complained about possible 'damage' to the system. I got results with 1 & 15, but none of the others actually produced any visible output.
As another suggestion there is a registry fix mentioned in this thread for Windows 10 users with Flash that might help: http://www.tomsguide.com/answers/id-2750596/unfixable-flash-player-problem.html
If any of these do resolve the issue then please post here to help others too.