View Issue Details

IDProjectCategoryView StatusLast Update
0000599Software Renderer(No Category)public2017-04-30 13:42
ReporterSolus 
Assigned ToRachael 
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionopen 
Platformi7 4790, 16GB, GTX980OSWindows 10 ProOS Version1703
Summary0000599: Crash on startup with software render cheked.
DescriptionQZDoom 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 ReproduceJust select Software and run QZDoom.
Additional InformationI'm not using any mods. Just vanilla Doom.
TagsNo tags attached.

Relationships

Activities

Solus

Solus

2017-04-18 17:22

reporter  

CrashReport.zip (23,994 bytes)
dpJudas

dpJudas

2017-04-18 19:35

developer   ~0001453

Very odd crash. The call stack reports a crash deep inside Direct3D code:
 	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++

You hardware is almost identical to mine, i7 and same GPU. I would attempt a driver update just to check if it isn't something weird that has gone wrong.
Solus

Solus

2017-04-19 13:40

reporter   ~0001463

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_

_mental_

2017-04-19 14:04

developer   ~0001464

Last edited: 2017-04-19 14:06

View 2 revisions

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

dpJudas

2017-04-19 18:38

developer   ~0001466

@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

Solus

2017-04-21 13:19

reporter   ~0001505

Last edited: 2017-04-21 13:43

View 2 revisions

_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_

_mental_

2017-04-21 14:21

developer   ~0001506

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

Solus

2017-04-21 17:10

reporter   ~0001508

_mental_ They all crash.
Solus

Solus

2017-04-25 15:33

reporter   ~0001551

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

CrashReport-2.zip (23,872 bytes)
dpJudas

dpJudas

2017-04-26 12:25

developer   ~0001558

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/download/details.aspx?id=8109 ) - if that doesn't fix it I don't know what could be wrong.
Solus

Solus

2017-04-29 13:49

reporter   ~0001585

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

_mental_

2017-04-30 07:50

developer   ~0001602

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.

Issue History

Date Modified Username Field Change
2017-04-18 17:22 Solus New Issue
2017-04-18 17:22 Solus File Added: CrashReport.zip
2017-04-18 19:35 dpJudas Note Added: 0001453
2017-04-19 13:40 Solus Note Added: 0001463
2017-04-19 14:04 _mental_ Note Added: 0001464
2017-04-19 14:06 _mental_ Note Edited: 0001464 View Revisions
2017-04-19 18:38 dpJudas Note Added: 0001466
2017-04-21 13:19 Solus Note Added: 0001505
2017-04-21 13:43 Solus Note Edited: 0001505 View Revisions
2017-04-21 14:21 _mental_ Note Added: 0001506
2017-04-21 17:10 Solus Note Added: 0001508
2017-04-25 15:33 Solus File Added: CrashReport-2.zip
2017-04-25 15:33 Solus Note Added: 0001551
2017-04-26 12:25 dpJudas Note Added: 0001558
2017-04-29 13:49 Solus Note Added: 0001585
2017-04-30 07:50 _mental_ Note Added: 0001602
2017-04-30 07:50 _mental_ Status new => feedback
2017-04-30 13:42 Rachael Assigned To => Rachael
2017-04-30 13:42 Rachael Status feedback => closed