0000599: Crash on startup with software render cheked.

[Solus]

https://mantis.zdoom.org/view.php?id=599

Code: Select all

Summary	0000599: Crash on startup with software render cheked.
Description	QZDoom q1.3.0.1-x64 (downloaded from the QZDoom page) crashes on startup if in video settings is selected to Software.
It works fine if selected to Hardware.
Steps To Reproduce	Just select Software and run QZDoom.
Additional Information	I'm not using any mods. Just vanilla Doom.

https://mantis.zdoom.org/file_download. ... 6&type=bug

[dpJudas]

Very odd crash. The call stack reports a crash deep inside Direct3D code:

Code: Select all

 	d3d9.dll!CSwapChain::Reset()	Unknown
     d3d9.dll!CSwapChain::Init(struct _D3DPRESENT_PARAMETERS_ *,struct D3DDISPLAYMODEEX const *,long 
*,int,int)	Unknown
     d3d9.dll!CBaseDevice::Init()	Unknown
     d3d9.dll!CEnum::CreateDeviceImpl()	Unknown
     d3d9.dll!CEnum::CreateDevice()	Unknown
>	qzdoom.exe!D3DFB::D3DFB(unsigned int adapter, int width, int height, bool bgra, bool fullscreen) 
Line 335	C++
     qzdoom.exe!Win32Video::CreateFrameBuffer(int width, int height, bool bgra, bool fullscreen, DFrameBuffer 
* old) Line 678	C++
     qzdoom.exe!I_SetMode(int & width, int & height, DFrameBuffer * old) Line 251	C++
     qzdoom.exe!V_DoModeSetup(int width, int height, int bits) Line 1312	C++
     qzdoom.exe!IVideo::SetResolution(int width, int height, int bits) Line 1477	C++
     qzdoom.exe!V_Init2() Line 1607	C++
     qzdoom.exe!D_DoomMain() Line 2624	C++

[Solus]

Sorry, I don't understand the code on your answer. I'm no coder. I just want to help you guys.
Anyway, I tested GZDoom (both 2.4.0 and most recent build) in software mode and crashes too. But ZDoom 2.8.1 doesn't.
I'm updated to 381.65 (04/06/2017). I checked if there were new updates and got that I'm updated.
It must be my computer then. Sorry to bother you.

[_mental_]

Could you please check with GZDoom 2.1.1, 2.2.0 and 2.3.2?
The results will probably help to narrow down set of changes in question.
Please also try 32-bit versions.

[dpJudas]

@Solus: Don't worry about not understanding the call stack - that was pasted here mostly as reference for myself and the other GZDoom/QZDoom developers.

Do you have a multi monitor setup? There is something about your system that differs from mine, the question is what. Based on the crash location, the main thing I could imagine going wrong is monitor selection. It could also be interesting to know if it can start up if you set it to windowed mode. Also, what resolution do you run at?

[Solus]

_mental_ I don't have them anymore and don't know where to get those versions. But, I tested the 32-bit versions and they run fine. Both GZDoom 2.4.0 and the most recent build and QZDoom 1.3.0 and most recent build.

dpjudas I have just one monitor. I run at 1920-1080, my native resolution. It still crashes in windowed mode.

EDIT: I've uninstalled and reinstalled my gpu drivers. The ports still crash. Don't know what to do more on my end. Hope it helps.

[_mental_]

Old builds are here. There is no need to check 32-bit builds, please try 64-bit only.

[Solus]

_mental_ They all crash.

[Solus]

Nvidia released a new driver today. I've updated from scratch but the ports still crash.

https://mantis.zdoom.org/file_download. ... 8&type=bug

[dpJudas]

This crash is exactly the same location of the other one. I examined the code at that location and I can't see anything obvious that could cause a crash here. My best guess is that there's something broken on your system unless we get a similar call stack from another computer.

You could try reinstall Direct3D 9 on your computer ( https://www.microsoft.com/en-us/downloa ... px?id=8109 ) - if that doesn't fix it I don't know what could be wrong.

[Solus]

Unfortunately it didn't fix the issue.
I guess I'll have to stick with ZDoom for software render.
Thanks for your help!

[_mental_]

There is some unknown issue with Direct3D for 64-bit processes on your system.
You can try to run just released 3.0.0 with +vid_used3d 0 command line.
This CVAR will enable OpenGL canvas instead of D3D.

[Solus]

Hi. For some reason I stopped being able to post on the bugs page. I don't know if its a issue of the site or if I've been blocked. Hoping it's not the last, I don't know what I did...
Anyway, MSI Afterbuner was crashing the ports. They run fine on software mode without the Afterburner.
I guess that's it.

[Rachael]

Yes - we are migrating away from the tracker. As you can see your issue was reposted here.