MonsterWarp.lua crash on startup [SOLVED]

[terrorcell]

I'm afraid I am completely out of ideas then . I only suggested memory because I had a really weird issue once with HL2 once that turned out to be a RAM problem, but it doesn't sound like that's happening with you if other (more intensive) games run fine. You might want to send an email to he LOG support address if you haven't already.

Just to confirm, I've been running Grimrock 2 with all of the latest driver updates since release on my NVidia laptop and not had any problems. You've clearly found a weird fringe-case that has slipped through the net because it's likely that nobody else has ever seen this crash!

I emailed them way back when I first found the error.
It's just disappointing is all, I was so keen to play it.

I'm with John here but also kinda out of ideas. Maybe the RAM timing setting in your BIOS are extremely tight. Make sure you set the correct speed for your memory chips and at least have their timings set to "use SPD".

Beside a non-optimal RAM setting i can only think of one other cause of memory corruption being a virus infections.

I'll take a look but I'm pretty sure everything's as it should be.
If I have a virus, it's an extremely well hidden one

[terrorcell]

Ok so I've found the real solution (reproducible). I have two programs that interfere with the game somehow (have never had any problems with them and any other games the entire time I've had this computer):
RocketDock (an application that creates a floating dock on the desktop that you can add program icons to) stops the game from loading if the cursor is over the game's window. This is the original error I found in the first post.
Gigabyte OC GURU II (lets you monitor various aspects of your motherboard, and overclock things like the fans, etc.) produces the error caused by starting the game with the cursor off the game's window, and then moving the cursor onto the game's window.

I still have another error that won't let me enter the options screen in the game and I don't know what program is causing that to happen, but that's not too big a deal for me right now.

I'll edit the original post with this post for others to see if anyone else ever comes across this.