12-01-2015, 09:42 AM
The first one shows that it crashed inside libgui, but that's just where the crash finished at. This: Exception Code: c0000005 shows that the memory stack was blown, so the actual crash was between clicking the mouse and after all the events are finished for clicking the mouse. When you change "rooms" the click happens, it loads the rooms, renders once, and then the click is "finished"
In the logfile, the "Made It" happens when you get to the first rendering inside the office. So the crash isn't in the GUI, but rather rendering something blew the memory stack causing the rest of the program to forget where variables are stored, thus crashed with c0000005 inside quickgui when it tried to use a variable.
So in short, still probably driver issues.
If QuickGUI was the issue, it would throw an exception in the logfiles or have the same issue all the time.
In the logfile, the "Made It" happens when you get to the first rendering inside the office. So the crash isn't in the GUI, but rather rendering something blew the memory stack causing the rest of the program to forget where variables are stored, thus crashed with c0000005 inside quickgui when it tried to use a variable.
So in short, still probably driver issues.
If QuickGUI was the issue, it would throw an exception in the logfiles or have the same issue all the time.
"great writers are indecent people, they live unfairly, saving the best part for paper.
good human beings save the world, so that bastards like me can keep creating art, become immortal.
if you read this after I am dead it means I made it." ― Charles Bukowski
good human beings save the world, so that bastards like me can keep creating art, become immortal.
if you read this after I am dead it means I made it." ― Charles Bukowski