LoG2 Crashes immediately upon execution

[sephirothizsin]

Normally I'm one to scour the deepest darkest reaches of the web in order to mend a problem I've come across however, this time is no different in that regard. What is different though, is... I couldn't fix my problem . Something worth noting, the games used to work without any problems, no crashing no nada. I'm very pleased I purchased these games, they've brought me much joy, which is why I want to play them again .

To be a little more clear... I get a black screen, windows error pops up, then tells me windows will notify me a fix is found (yeah right) haha. (there is no error code Just "grimrock2.exe has stopped working")
Now, if i DELETE the config file... I get nothing, steam tells me I'm playing LoG2 for 4 seconds, synchs, then right back to nothing. Also, By deleting my config file I get no black screen, just a whole lot of nothing.

Side note: These are fresh installs of the game, game cache verified and the whole 9 yards.

Originally I had this problem with the first LoG as well but, re-installing dx9 and vcredist seems to have fixed the startup problem without a hitch. I retract my previous statement, it seems uninstalling my video driver and reinstalling a new one has renewed this problem with the original LoG...

LoG2 however is a stubborn beast. Quite perplexing. I've read through about 4 hours worth of fixes for LoG2 here and on steam forums and nothing's worked for me, I used DDU to uninstall my video driver, and I re-installed the current up to date driver for my PC.

I have tried all different resolutions all different compatibility modes etc.
Any help would be greatly appreciated.
thank you for taking the time to read and go over everything I posted ahead of time. <3

||||||||||||| This is my Error log file for LoG2

SpoilerShow

=== System Info ===

Game Version: 2.2.4
Computer name: NOPE-PC
CPU Vendor: AuthenticAMD
CPU Brand: AMD FX(tm)-8320 Eight-Core Processor
OS Version: 6.1
OEM ID: 0
Physical CPUs: 8
Logical CPUs: 0
Page Size: 4096
Total Mem: 16365 MB
Free Mem: 13333 MB

=== GPUs ===

Device name: \\.\DISPLAY1
Device string: AMD Radeon (TM) R9 390 Series
State flags: 08080005

Device name: \\.\DISPLAY2
Device string: AMD Radeon (TM) R9 390 Series
State flags: 00080000

Device name: \\.\DISPLAY3
Device string: AMD Radeon (TM) R9 390 Series
State flags: 00080000

Device name: \\.\DISPLAY4
Device string: AMD Radeon (TM) R9 390 Series
State flags: 00080000

Device name: \\.\DISPLAY5
Device string: AMD Radeon (TM) R9 390 Series
State flags: 00080000

Device name: \\.\DISPLAY6
Device string: AMD Radeon (TM) R9 390 Series
State flags: 00080000

|||||||||||| This is my config file. There are no extra "characters" or any out of place.

SpoilerShow

-- options
resolution = "1920 x 1080"
displayMode = 1
verticalSync = 2
renderingQuality = 2
textureResolution = 3
textureFilter = 3
shadowQuality = 3
ssaoQuality = 3
fogParticles = true
muteMusic = false
muteSounds = false
musicVolume = 0.8
soundVolume = 0.8
arrowIcons = false
oneClickCasting = false
disableDamageTexts = false
hideItemProperties = false
mouseLook = true
invertX = false
invertY = false
autoSave = true
tabletMode = false
cameraBobbing = true
tooltipDelay = 0
maxFrameRate = 120
debugInfo = false
console = true
consoleKey = 192
windowPosX = nil
windowPosY = nil
editorWindowPosX = nil
editorWindowPosY = nil
editorWindowWidth = nil
editorWindowHeight = nil

-- key bindings
move_forward = 87
move_backward = 83
strafe_left = 65
strafe_right = 68
turn_left = 81
turn_right = 69
rest = 82
map = 9
swap_weapons = 88
character_sheet_1 = 49
character_sheet_2 = 50
character_sheet_3 = 51
character_sheet_4 = 52
quick_save = 116
quick_load = 120

-- editor key bindings
select_tool = 49
add_object_tool = 50
draw_walls_tool = 51
draw_heightmap_tool = 52
nudge_up = 87
nudge_down = 83
nudge_left = 65
nudge_right = 68
nudge_elevation_up = 4322
nudge_elevation_down = 226
rotate_left = 81
rotate_right = 69
delete = 46
set_starting_location = 89
teleport_party = 84
swap_tiles = 88
pick_tile_left = 188
pick_tile_right = 190
increase_height = 106
decrease_height = 111
increase_ceiling_height = 8298
decrease_ceiling_height = 8303
level_up = 33
level_down = 34
level_north = 8230
level_east = 8231
level_south = 8232
level_west = 8229
zoom_in = 107
zoom_out = 109
locate_object = 8262
selection_mask = 8264
start_preview = 116
stop_preview = 4212
toggle_fullscreen = 70
toggle_collisions = 112
open_door = 90
kill_monster = 75
heal_party = 72

||||||||||||
My system:

SpoilerShow

Time of this report: 3/13/2017, 02:47:27
Machine name: NOPE-PC
Machine Id: {A8A12FA7-C6FD-4944-A142-633434F6BF6B}
Operating System: Windows 10 Home 64-bit (10.0, Build 14393) (14393.rs1_release.161220-1747)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: GA-990FXA-UD3
BIOS: Award Modular BIOS v6.00PG
Processor: AMD FX(tm)-8320 Eight-Core Processor (8 CPUs), ~3.5GHz
Memory: 16384MB RAM
Available OS Memory: 16366MB RAM
Page File: 3988MB used, 28760MB available
Windows Dir: F:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 144 DPI (150 percent)
DWM DPI Scaling: UnKnown
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.14393.0000 64bit Unicode

------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Sound Tab 3: No problems found.
Sound Tab 4: No problems found.
Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)

---------------
Display Devices
---------------
Card name: AMD Radeon (TM) R9 390 Series
Manufacturer: Advanced Micro Devices, Inc.
Chip type: AMD Radeon Graphics Processor (0x67B1)
DAC type: Internal DAC(400MHz)
Device Type: Full Device
Device Key: Enum\PCI\VEN_1002&DEV_67B1&SUBSYS_E324174B&REV_80
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 16352 MB
Dedicated Memory: 8169 MB
Shared Memory: 8182 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: Generic PnP Monitor
Monitor Model: LG TV
Monitor Id: GSM0001
Native Mode: 3840 x 2160(p) (60.000Hz)
Output Type: HDMI

[sephirothizsin]

I just remembered you can take a look at the crashes through the event viewer. Posting them below

LoG2 crash report via windows:

SpoilerShow

Faulting application name: grimrock2.exe, version: 0.0.0.0, time stamp: 0x54ede8b1
Faulting module name: KERNELBASE.dll, version: 10.0.14393.479, time stamp: 0x58256d37
Exception code: 0xc00000fd
Fault offset: 0x000c92a4
Faulting process id: 0x530
Faulting application start time: 0x01d29bd0657f5d4c
Faulting application path: F:\Program Files (x86)\SteamLibrary\steamapps\common\Legend of Grimrock 2\grimrock2.exe
Faulting module path: F:\WINDOWS\System32\KERNELBASE.dll
Report Id: 810cd5fd-517e-4bd5-a505-db150a3973f0
Faulting package full name:
Faulting package-relative application ID:

Original LoG report:

SpoilerShow

Faulting application name: grimrock.exe, version: 0.0.0.0, time stamp: 0x5115140b
Faulting module name: KERNELBASE.dll, version: 10.0.14393.479, time stamp: 0x58256d37
Exception code: 0xc00000fd
Fault offset: 0x000c92b0
Faulting process id: 0x1ffc
Faulting application start time: 0x01d29bd061302336
Faulting application path: F:\Program Files (x86)\SteamLibrary\steamapps\common\Legend of Grimrock\grimrock.exe
Faulting module path: F:\WINDOWS\System32\KERNELBASE.dll
Report Id: 3c3d7075-13ed-493b-bba2-a3c576bfd070
Faulting package full name:
Faulting package-relative application ID:

I sorta know what it means, but fixing it I have no idea lol.

[sephirothizsin]

Okay so I figured it out, that Kernalbase.dll garbage is window's 10 user specific. Essentially what that means is, something is corrupted some how with the user on that specific login.

I fixed the problem with log and log2 by creating a new local user. It's tricky with window's 10 but pretty easy regardless.

SO FOR EVERYONE and anyone else to have this problem in the future
step 1: search for event viewer
step 2: once found right click run as admin
step 3: click dropdown of custom views
step 4: click on administrative events
step 5: check and see if you have a kernelbase.dll Faulting module name
Step 6: if yes create new local user with administrative rights
step 7: play them finally.

[Dr.Disaster]

Seems you figured it out before i could finish an answer

Aye given all the problems i've seen from players with Win10 that user account corruption seems to happen rather often. It kinda makes creating a new user account a measure of last resort thing; fixes most of the problems unless the DX system got corrupted. Praise yourself lucky that wasn't your problem because fixing that is a serious pain in the @§§ on Win10!

[sephirothizsin]

Seems you figured it out before i could finish an answer

Aye given all the problems i've seen from players with Win10 that user account corruption seems to happen rather often. It kinda makes creating a new user account a measure of last resort thing; fixes most of the problems unless the DX system got corrupted. Praise yourself lucky that wasn't your problem because fixing that is a serious pain in the @§§ on Win10!

Oh god, I can't even imagine having the patience to tackle that.

Idk if you got my message or not but, on behalf of everyone in this community you've helped (myself included, albeit indirectly) I thank you for the work you've done and the help you've provided to everyone here, and on steam.

You're the real MVP

[Dr.Disaster]

Well thx! Just trying to help other players out.
Aye, got your PM right when i responded regarding the new user account solution.

Just in case you'll ever encounter the DX corruption issue i mentioned. I ran into it once, prolly by trying a non-Win10 certified driver. If this DX corruption happens you'll see all kinds of weird D3D_Error messages but reinstalling the video drivers, DX drivers and even a new user account won't change anything. The reason why this does not fix stuff are corrupted DX reference files located in the Win10 component storage area that Win10 uses to repair(!) damaged system files. The only way to repair this kind of damage is to replace those corrupted reference files with working copies from a non-corrupted Win10 system and then let Win10 repair itself OR a classic reinstall. It's definately nothing a regular player would bother to fix unless it'll take him days to rebuild his system.