Crash on Launch
- Login to post comments
Mon, 01/03/2011 - 18:15
As the subject suggests, my WOG crashes on launch. Specifically it launches to a black screen and then sits there. If you alt-tab you can see the error reporter, which has the following.
Exception: Access Violation (code 0xc0000005) at address 6986019C in thread 1180 Module: d3d9.dll Logical Address: 0001:0013F19C 0018F680 6986019C DebugSetLevel+97B63 Params: 0018F69C 0018F708 69844031 0000047C StackWalk failed (error 299) EAX:00000001 EBX:0018F68C ECX:0000047C EDX:00000000 ESI:000021EC EDI:00000000 EIP:6986019C ESP:0018F630 EBP:0018F680 CS:0023 SS:002B DS:002B ES:002B FS:0053 GS:002B Flags:00210246 Windows Ver: NT 6.1 Build 7600 DDraw Ver: 6.1.7600.16385 DSound Ver: 6.1.7600.16385 Product: Product Version: Time Loaded: 00:00:01 Fullscreen: No Primary ThreadId: 1180
Any help would be appreciated.
What happens when you try to run it again? Does it always crash? What kinda system/machine do you have?
And do you have dual monitor setup?
My Gooish profile | Videos on YouTube | My WOG Mods
Identical error reports on successive runs, (Thread ID naturally changes though).
Win 7 x64, Game is running through Steam. I do have dual monitors, however I have tested with disabling one of them to no success.
I'm not sure, but maybe you need the v1.30 patch for WoG to work on a 64-bit OS. In any case, you should download it here if you don't already have it: http://www.worldofgoo.com/dl2.php?lk=patch
New GooFans Rules | My Addins
Oh yeah, I think puggsoy is right. i just noticed you said you use Steam. Steams WoG isn't updated to 1.3 its still 1.0 so yeah, you probably need the patch.
My Gooish profile | Videos on YouTube | My WOG Mods
I find that running World of Goo with administrator privileges on Windows 7 helps me!
After a bit more testing (after patching), I managed to get the game to work, albeit in a way that isn't feasible for me to play it regularly.
The game seems to be incompatible with larger numbers of processor cores. By restricting my system to the minimum amount of CPU cores, and disabling HyperThreading, I managed to get the game to launch successfully. (Disabling the Second Monitor was also required.) Unfortunately I regularly use this machine and spending a couple minutes rebooting because I feel like playing a bit of WOG isn't an attractive thought, especially when as a casual game I suspect I'd be playing it randomly for short periods of time.
I much appreciate everyone's help however. Hopefully I can save anyone else reading these forums with an above average number of CPU cores the hassle, at least until a patch for this issue is released.
Thanks Chareon. This really useful stuff. Maybe you should report this problem directly to developers http://2dboy.com/contact.php They might be interested
My Gooish profile | Videos on YouTube | My WOG Mods