Posted September 15, 2016

EDIT but the 3D message went away.
Looking at your second suggestion, what module is that that's being modified?
EDIT: tail end of debug
err:ole:CoGetClassObject class {b9f3eb85-b781-4ac1-8d90-93a05ee37d7d} not registered
err:ole:CoGetClassObject no class object {b9f3eb85-b781-4ac1-8d90-93a05ee37d7d} could be created for context 0x1
fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled
fixme:wbemprox:enum_class_object_Next timeout not supported
err:wbemprox:wql_error syntax error, unexpected TK_ID, expecting $end
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:dbghelp:elf_search_auxv can't find symbol in module
fixme:dbghelp:MiniDumpWriteDump NIY MiniDumpWithDataSegs
wine: Unhandled page fault on read access to 0x00000000 at address 0x44124d (thread 0022), starting debugger...
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x0044124d).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
<snip>