Solved Non BSOD, APPCRASH:DKII.exe, Exception Code:c0000005

[DirtAlliance]

Problem signature:
Problem Event Name: APPCRASH
Application Name: DKII.exe
Application Version: 0.0.0.0
Application Timestamp: 37643c7b
Fault Module Name: DKII.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 37643c7b
Exception Code: c0000005
Exception Offset: 00220e22
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: efc1
Additional Information 2: efc18393bcad5376d541fd6d19e6268e
Additional Information 3: 1753
Additional Information 4: 1753ad9a83c01c811ef7520d890fc3e6

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt



I keep seeing this crash to desktop c0000005 code after the logo credits. After a clean install of WIN7 to resolve another problem i'm getting this error now. Lol I know for a fact it has nothing to do with my video card or drivers.

Games installed since Win7-reload that work:
METAL GEAR SOLID 2 SUBSTANCE
Minecraft
EDuke32/mapster32
Counterstrike:Source
Deadisland:Riptide

 

[x BlueRobot]

Does DKII.exe belong to Dungeon Keeper II? There's quite a few threads on other forums, suggesting the game isn't compatible with Windows 7.

 

[DirtAlliance]

Yes it is. But also I have had this run before on windows 7 with editing the registry to turn off hardware acceleration. Which is the problem with the main menu being all black. But changing the settings makes it work. But this new code has happened for another game as well. I actually posted a post relating to the game crash and it has the same code but everyone tried to blame the video drivers. And from looking at other people chime in on a microsoft forum and they went out and got the latest video card and still didn't solve that code.

Here's the other games crash with that same c0000005 error:
Problem signature:
Problem Event Name: APPCRASH
Application Name: ROTT.exe
Application Version: 1.0.10508.0
Application Timestamp: 51efd1cc
Fault Module Name: d3d9.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7b7b3
Exception Code: c0000005
Exception Offset: 00061345
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: cf98
Additional Information 2: cf98f581689a300a7343d58e30dc6cbb
Additional Information 3: c61b
Additional Information 4: c61b6d45e83a105811fad9f8697c11a1

DirectX is all up to date** Just to add so that question is not asked.

 

[DirtAlliance]

Solved.

- you need to download this https://app.box.com/shared/ff6phvi1p1 and use the new exe and replace the WEANETR.dll.

- then you need to start the game. Go into graphics options and uncheck hardware acceleration.

- then blindly start the first mission. Save and keep playing. Or you can quit to main menu and you will have gotten rid of the black screen problem.

- if you want to play the game in a higher screen resolution you can open regedit by pressing the windows key+r then typing in regedit. Navigate through HKEY_CURRENT_USER/Software/Bullfrog Productions Ltd/Dungeon Keeper II/Configuration/Video
Now you can click on one of the three 'res' keys and change value from 0 to 1. Screen Hardware3D should be set to 0.

- if you launch the game and your hit with the stupid black screen again. Go into the graphics options again and uncheck the hardware acceleration again. Then load your saved game, quit to menu to see it's not black anymore. Quit program. Then right click on your 1.73 shortcut and add " -32bitdisplay" without the quotes and you will no longer have to mess with any settings now. This was done last. So maybe instead of having to do the blindly start the game and save thing. Maybe this makes it work right away with the 1.73 exe.


Game at least is playable now with a minor setback on how to get it up and running. But the game is worth it. Sucks it's not running like it used to run on win7 for me. Don't know whats different. Maybe the latest version of directx messed any compatibility there was up completely.

 

[x BlueRobot]

I'm glad you were able to solve your issue