2009Scape Official Forums

Works great now! Thanks

I'm having this same issue, game crashes a few seconds after trying to chop down trees, same error in the console log (also in singleplayer using the latest version from a few days ago via GIT). Has a fix been found for this or is it something on my end too? Definitely using java 11 that auto-downlo...

Yeah, that didn't work. I suspected it was Nvidia but figured I'd double check the java thing anyways. I'll try to get support to look into it. Thanks!

Hey everyone, me again. Decided to take another stab at this. I know one thing we haven't discussed here is trying Java 8 instead of 11. I tried installing that version and made sure the command line was seeing that version, however it looks like 2009scape is auto-downloading JDK11, which I understa...

Thanks again everyone for all the help. At this point I can't seem to figure out what keeps crashing it, I get the feeling it is still related to my GPU. It works fine on my 10 year old laptop that still runs, but it's a shitty resolution even with HD, so I don't really want to play on that. I just ...

I don't play Minecraft, no Overwolf installed. What specifically would you like to see in the Java Control Panel?

Okay, after that, it's still crashing, but this is all that showing up now in the command line. Seems Java.exe keeps crashing.

Okay so I downloaded version 425.31 from 4/11/2019, and it seems a different issue is happening now, this is what shows up at the end of the terminal when it crashes. It doesn't generate an error log though like it was before. This is good! This is a cache read error. Maybe you corrupted your cache...

Well, I tried version 528, 3 versions back from the current one (which I assume is what you meant, rather than a few back from the old one I was using earlier), and I get the nvoglv64.dll errors again. At this point I think I might just give up. I don't want to take up even more of your time, you ha...

Okay so I downloaded version 425.31 from 4/11/2019, and it seems a different issue is happening now, this is what shows up at the end of the terminal when it crashes. It doesn't generate an error log though like it was before.