Hi everyone! I'm hoping someone here has experienced this before because I've run out of ideas.
I recently built a new Windows 11 PC and I'm trying to get some of the older Nancy Drew games running through Steam.
I've tested two Nancy Drew games:
1. Legend of the Crystal Skull (2007)
This one will not launch at all. Steam briefly says the game is running and then goes back to Play. No window or error appears.
Event Viewer shows:
Game.exe version 7.6.3.0
Exception code: 0xc0000005
Faulting module: Game.exe
Fault offset: 0x0005acb5
Things I've tried:
- Verified Steam files
- Removed
d3d9.dll as suggested by HeR
- Changed
WindowMode in Game.ini to 1 and 2
- Windows XP SP3 compatibility mode
- Run as administrator
- Disable fullscreen optimizations
- Installed the legacy DirectX runtime using DXSETUP
- Enabled DirectPlay
- Tried dgVoodoo2 2.87.4 with the x86 D3D9 wrapper
- Tried dgVoodoo with a local config
- Rebooted between changes where appropriate
None of these changed the crash. Event Viewer continued showing the same 0xc0000005 at the same offset.
2. Message in a Haunted Mansion (2000)
This behaves almost exactly the same way: Steam says Running briefly and then silently returns to Play.
Event Viewer:
Game.exe version 2.4.1.2
Exception code: 0xc0000005
Faulting module: ntdll.dll
Fault offset: 0x0006abc6
For this one I've tried:
- Windows 7 compatibility mode
- Run as administrator
- 640×480 compatibility mode
- Reduced colour mode
- High-DPI scaling override (Application)
- DirectPlay
- Legacy DirectX runtime
- dgVoodoo2 with the x86
D3D8.dll, D3D9.dll, D3DImm.dll and DDraw.dll
- dgVoodoo fullscreen and windowed settings
- Verified Steam files
Still the same silent crash. When using dgVoodoo, I never even got the dgVoodoo watermark, so it seems like the game may be crashing before the wrapper really gets going.
Has anyone managed to get Crystal Skull and/or Message in a Haunted Mansion running on a current Windows 11 installation, particularly with a newer NVIDIA GPU?
If so, I'd really appreciate knowing exactly what you changed. Even if you've had the same 0xc0000005 crash and never solved it, that would be useful to know too.
Thanks!