February 2019
Check your event viewer for the error.
For windows 10 search for "event viewer desktop app"
Once Event Viewer is up Event Viewer (Local) > Windows Logs > Application
You will see 3 different kinds of notifications. Warning, error and information.
Under Error you can see the exact time the error occurred.
Copy and paste or screen shot "General" and "Detail" Tabs that occurred when the crash happened.
Do this again for "System" and "Hardware Events"
Being able to see the exact errors will make it much easier to diagnose and fix issues.
I can possibly help with that information.
February 2019
Just got this one:
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000001
Faulting process id: 0x1c88
Faulting application start time: 0x01d4ce5fda73a3ec
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: e9bf5646-5223-41d8-9658-6cbcb6471e5f
Faulting package full name:
Faulting package-relative application ID:
February 2019
February 2019 - last edited February 2019
@2Cavalier wrote:Just got this one:
Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000001
Faulting process id: 0x1c88
Faulting application start time: 0x01d4ce5fda73a3ec
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: e9bf5646-5223-41d8-9658-6cbcb6471e5f
Faulting package full name:
Faulting package-relative application ID:
Bad module info is an access violation because of a bad address. Could be the app or could be your memory not writing correctly.
To fix this issue head to the microsoft website and download RAMMAP
https://docs.microsoft.com/en-us/sysinternals/downloads/rammap
Select empty> empty working sets
This clears memory cache
then attempt to run the game again.
Second Solution:
Go to the game EXE file > rightclick > properties > compatibility > check "disable fullscreen optimizations"
attempt to run the game again
This error is from a windows update last year that did not get fixed.
February 2019
February 2019 - last edited February 2019
@2Cavalier wrote:
DllHost (12844,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.
Ive edited my previous post with a possible solution If it does not work it is the app
February 2019
Can you guys put all that in ENGRISH now?
February 2019
Ive posted 2 possible solutions.
February 2019
February 2019