Grim Dawn PC Crash

[Mint Berry Crunch]

Decided to start up Grim Dawn again. A couple of seconds after I hit level 2 near the starting quest zone my PC decides to crash. Won't minimize, won't respond to any keyboard or mouse commands, only fix was to restart my PC. This only happens when I'm on Grim Dawn, it's a brand new PC built a couple of weeks ago and definitely isn't a performance issue.

Has anyone been experiencing this or has a fix for this?

Thanks.

[mikeydsc]

Crashes are usually hardware or driver related. What OS are you on? Look in the logs and alerts APPs section for a clue.

[Mint Berry Crunch]

OS is Windows 7. And as for the logs:
<Release priority="warning">0: UPnP services unavailable or disabled in game options. RouterServices initialization cancelled.</Release>

Not sure what it means though.

[mikeydsc]

Have you verified local files or used the repair;exe utility found in the GD folder?

[Mint Berry Crunch]

Originally posted by Insertprofilenamehere:

Originally posted by Shockinc:

Decided to start up Grim Dawn again. A couple of seconds after I hit level 2 near the starting quest zone my PC decides to crash. Won't minimize, won't respond to any keyboard or mouse commands, only fix was to restart my PC. This only happens when I'm on Grim Dawn, it's a brand new PC built a couple of weeks ago and definitely isn't a performance issue.

Has anyone been experiencing this or has a fix for this?

Thanks.

WHat does this have to do with Grim Dawn? Pro -tip: nothing at all. Games dont make your PC crash. You're simply seeing a symptom of a issue you need to resolve and this isn't related to Grim Dawn. Like...at all.

You're right. I just thought this was the best place to post it because because the crash only occurs when I play Grim Dawn. So I ended up here. Mikeydsc is trying to help out though, and I appreciate that very much!

Mikeydsc: There is no repair;exe utility located in the GD folder. I uninstalled and reinstalled the game but to no avail. I validated the game and will try it out. I will let you know what happens.

[Mint Berry Crunch]

It crashed.
<?xml version="1.0" encoding="ISO-8859-1"?>

-<log version="v0.3.5.7 (b27)" time="02:21:17" date="09/27/15">

<Release priority="warning">0: UPnP services unavailable or disabled in game options. RouterServices initialization cancelled.</Release>

</log>

Same as usual.

[mikeydsc]

...:\steam\steamapps\common\Grim Dawn is the folder that the repair utility is in.

You arent in the right log. That is the system log.

Right click Computer or My Computer and select manage. Next open up the event viewer. Windows log > Application. Look for the error meesage with a red exclamation mark. One should have a faulted module for GD listed. That should help narow it down to whether its a hardware, or driver issue.

[Mint Berry Crunch]

It worked! No more crashes. I repaired GD and disabled Microsoft software that was apparently causing the crashes. I turned off the software and no more crashes! Thanks Mikey, you've helped out a bunch!

[mikeydsc]

Hey good for you. Enjoy the game.

[atrasan]

Grim Dawn crashes here too. My OS is Win 7 64-bit. Here's the crash dumb analysis:

On Wed 21.10.2015 14:17:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102115-10327-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)
Bugcheck code: 0x100000EA (0xFFFFFA8007C6A4C0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

So how can I fix this problem? Is it an AMD Catalyst drivers issue?

[Vasilisa]

Originally posted by Cow:

It worked! No more crashes. I repaired GD and disabled Microsoft software that was apparently causing the crashes. I turned off the software and no more crashes! Thanks Mikey, you've helped out a bunch!

Have the same problem! Could you please write what exact Microsoft software was causing crashes? (there are no any error meesages with a red mark in my windows event viewer).

[Alphametric]

I got this, what does it mean?

Activation context generation failed for "C:\Program Files (x86)\Steam\steamapps\common\Grim Dawn\CrashReporter.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_d3c2e4e965da4528.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_8c15ae12515e1c22.manifest.

Also this, will look for more...

Faulting application name: crashreporter.exe, version: 0.0.0.0, time stamp: 0x56604c8b
Faulting module name: EasyHook32.dll, version: 2.7.5159.0, time stamp: 0x53327257
Exception code: 0xc0000005

[Alphametric]

Is there anyone who know about this stuff?

[Seroczynski]

Using Windows 10 x64 and the latest NVIDIA drivers.

Grim Dawn is the only game which causes my computer to be non-responsive. The first time I had to completely shutdown my computer, but the second and third time I just had to wait a little and Windows would respond again so I could ALT+F4 Grim Dawn.

I have no red exclamation marks in my error log that seem to be linked with Grim Dawn.

[mikeydsc]

Originally posted by Alphametric:

I got this, what does it mean?

Activation context generation failed for "C:\Program Files (x86)\Steam\steamapps\common\Grim Dawn\CrashReporter.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_d3c2e4e965da4528.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_8c15ae12515e1c22.manifest.

Also this, will look for more...

Faulting application name: crashreporter.exe, version: 0.0.0.0, time stamp: 0x56604c8b
Faulting module name: EasyHook32.dll, version: 2.7.5159.0, time stamp: 0x53327257
Exception code: 0xc0000005

What OS are you using? Usually manifest files work with older OS systems. (XP & Vista) or now since Win 10 is released 7 and 8. Manifests direst the OS to interpret older codes so the new OS can work with the old code.

Try to run the repair.exe as listed above. Update your OS.

[mikeydsc]

Originally posted by Seroczynski:

Using Windows 10 x64 and the latest NVIDIA drivers.

Grim Dawn is the only game which causes my computer to be non-responsive. The first time I had to completely shutdown my computer, but the second and third time I just had to wait a little and Windows would respond again so I could ALT+F4 Grim Dawn.

I have no red exclamation marks in my error log that seem to be linked with Grim Dawn.

A comnplete lockup is driver related usually.
Roll back your vid drivers a version or 2. Also check that your audio drivers are up to date. Verify local files and make sure the game has proper privleges to run.