Page 1 of 1

Very Fatal Error

Posted: Tue Jul 08, 2014 20:42
by NilkadNaquada
GZDoom keeps giving me a "Very Fatal Error" report each time I try to load it. I downloaded it on this laptop while it had Windows 7 as the operating system, it stopped working after I installed Windows 8. I tried redownloading the latest release and it still didn't work. I've tried loading multiple different iwads and it encounters the same error every time. I am currently running Windows 8.1 for my operating system, which doesn't seem to have changed anything.

Re: Very Fatal Error

Posted: Wed Jul 09, 2014 0:04
by Blue Shadow
When getting the crash, you'll be allowed to save a crash report to disk, could you upload that crash report?

By the way, GZDoom should run fine on Windows 8 or 8.1, so it must be something else. In most cases, it's graphics card-related, like outdated drivers or not having the needed OpenGL support to run GZDoom.

Re: Very Fatal Error

Posted: Wed Jul 09, 2014 0:30
by NilkadNaquada
Here it is:
CrashReport.zip
(20.41 KiB) Downloaded 110 times

Re: Very Fatal Error

Posted: Wed Jul 09, 2014 13:20
by Graf Zahl
What is this:
OS: Windows 95 4.0.950
There seems to be something seriously wrong with your system. BTW, it crashes while trying to initialize OpenGL so I suspect a broken Windows installation.

Re: Very Fatal Error

Posted: Wed Jul 09, 2014 18:39
by NilkadNaquada
There is something seriously wrong with it, I'm using my brother's laptop and he is really really stupid about what he downloads.

Any clue what I can do to fix it?

Re: Very Fatal Error

Posted: Fri Jul 11, 2014 17:53
by NilkadNaquada
Nevermind, I tried reinstalling Windows 8.1 and trying opening GZDoom again, which didn't work, but just now I was browsing around seeing if I could find a fix anywhere else, and found a thread which seemed to have the same problem as me. It included a screenshot of the error message the person got, and i wanted to make sure it was the same error, so I tried loading up GZDoom expecting the message as usual so I could check that the error code was the same, and for whatever reason it's working now.