blackscreen after fullscreen -> hard reset

Need help running G/Q/ZDoom/ECWolf/Zandronum/3DGE/EDuke32/Raze? Did your computer break? Ask here.

Moderator: GZDoom Developers

Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!

If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.

We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.
bomse1
Posts: 7
Joined: Fri Jan 19, 2018 4:50 am

blackscreen after fullscreen -> hard reset

Post by bomse1 »

hello folks,

i was searching all over the net to find answers without success. so iam writing this thread.

iam running the newest brutal doom v21 + hell on mars starter pack with the latest gzdoom and zdl launcher. everything works perfectly fine until switching to fullscreen ingame. screen goes black, no error messages, no response at all, no tabbing out possible anymore. i have to hard-reset my computer. starting up the game again results in the same crash over and over again, no matter how i try to start it up (switching wads and pk3s, erasing and reinstalling, trying out zdoom, etc.) so there's no way for me to get to the ingame options anymore.

from what i read online i presume that it has something to do with hardware acceleration or monitor refreshing rates maybe..?

please advise!

greetings
bomse
User avatar
Rachael
Posts: 13542
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her
Contact:

Re: blackscreen after fullscreen -> hard reset

Post by Rachael »

This is clearly an issue with your driver and/or kernel, which is outside the scope of what GZDoom can control.

What you can try is turning off fullscreen mode, and then using borderless mode, instead.

Simply start gzdoom with "gzdoom +set fullscreen false +set win_borderless true" and try that.
bomse1
Posts: 7
Joined: Fri Jan 19, 2018 4:50 am

Re: blackscreen after fullscreen -> hard reset

Post by bomse1 »

hello Rachael,

thanks for your input. are these command line arguments? iam not sure were to put them.

greetings
User avatar
Rachael
Posts: 13542
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her
Contact:

Re: blackscreen after fullscreen -> hard reset

Post by Rachael »

Yes they are. When you have the GZDoom folder open you can simply type the command into your address bar.
bomse1
Posts: 7
Joined: Fri Jan 19, 2018 4:50 am

Re: blackscreen after fullscreen -> hard reset

Post by bomse1 »

ok i did that but with the same outcome.
User avatar
Rachael
Posts: 13542
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her
Contact:

Re: blackscreen after fullscreen -> hard reset

Post by Rachael »

It's likely a problem with your driver then. We'll need full system specs in order to help, here.
Guest

Re: blackscreen after fullscreen -> hard reset

Post by Guest »

Betriebssystemname Microsoft Windows 7 Professional
Version 6.1.7601 Service Pack 1 Build 7601
Zusätzliche Betriebssystembeschreibung Nicht verfügbar
Betriebssystemhersteller Microsoft Corporation
Systemname BOMSE-PC
Systemhersteller MSI
Systemmodell MS-7751
Systemtyp x64-basierter PC
Prozessor Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, 3400 MHz, 4 Kern(e), 4 logische(r) Prozessor(en)
BIOS-Version/-Datum American Megatrends Inc. V1.5, 17.07.2012
SMBIOS-Version 2.7
Windows-Verzeichnis C:\Windows
Systemverzeichnis C:\Windows\system32
Startgerät \Device\HarddiskVolume4
Gebietsschema Deutschland
Hardwareabstraktionsebene Version = "6.1.7601.23403"
Benutzername bomse-PC\bomse
Zeitzone Mitteleuropäische Zeit
Installierter physikalischer Speicher (RAM) 8,00 GB
Gesamter realer Speicher 7,95 GB
Verfügbarer realer Speicher 5,35 GB
Gesamter virtueller Speicher 15,9 GB
Verfügbarer virtueller Speicher 12,9 GB
Größe der Auslagerungsdatei 7,95 GB
Auslagerungsdatei C:\pagefile.sys


maybe this will help?
User avatar
wildweasel
Posts: 21706
Joined: Tue Jul 15, 2003 7:33 pm
Preferred Pronouns: He/Him
Operating System Version (Optional): A lot of them
Graphics Processor: Not Listed
Contact:

Re: blackscreen after fullscreen -> hard reset

Post by wildweasel »

This helps with everything but your video hardware - do you know what GPU you have, and what its driver version is? DXDIAG can help you get this information.
Guest

Re: blackscreen after fullscreen -> hard reset

Post by Guest »

oh my. i posted this last night when beeing a little bit boozed and didnt entirely check it. iam really sorry.

here it is, straight out of the extracted txt-file.

Card name: NVIDIA GeForce GTX 660
Manufacturer: NVIDIA
Chip type: GeForce GTX 660
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_11C0&SUBSYS_354E1458&REV_A1
Display Memory: 1707 MB
Dedicated Memory: 1988 MB
Shared Memory: 3814 MB
Current Mode: 1920 x 1080 (32 bit) (60Hz)
Monitor Name: PnP-Monitor (Standard)
Monitor Model: E2242
Monitor Id: GSM58BF
Native Mode: 1920 x 1080(p) (60.000Hz)
Output Type: DVI
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 23.21.0013.8871 (English)
Driver Version: 23.21.13.8871
DDI Version: 11
Driver Model: WDDM 1.1
Driver Attributes: Final Retail
Driver Date/Size: 12/16/2017 01:21:27, 18208784 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
Device Identifier: {D7B71E3E-5280-11CF-4F55-43151BC2DA35}
Vendor ID: 0x10DE
Device ID: 0x11C0
SubSys ID: 0x354E1458
Revision ID: 0x00A1
Driver Strong Name: oem31.inf:NVIDIA_Devices.NTamd64.6.1:Section030:23.21.13.8871:pci\ven_10de&dev_11c0
Rank Of Driver: 00E62001
Video Accel: ModeMPEG2_A ModeMPEG2_C ModeVC1_C ModeWMV9_C
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled


it's running the 388.71 nvidia driver. i think its the newest.
bomse1
Posts: 7
Joined: Fri Jan 19, 2018 4:50 am

Re: blackscreen after fullscreen -> hard reset

Post by bomse1 »

in addidtion: i have the "hell on earth" starter pack seperately and standalone in one folder and it works absolutely fine, even in fullscreen mode.
_mental_
 
 
Posts: 3812
Joined: Sun Aug 07, 2011 4:32 am

Re: blackscreen after fullscreen -> hard reset

Post by _mental_ »

The starter pack of "the best mod" uses pretty old build of GZDoom (g2.1.pre-1231) and moreover the configuration file is bundled with it.
You can try to use gzdoom.ini from it with the latest release to see if the problem is caused by particular combination of settings.
This may not help though. Fixing such issues is purely a guess game without a direct access to affected PC.
bomse1
Posts: 7
Joined: Fri Jan 19, 2018 4:50 am

Re: blackscreen after fullscreen -> hard reset

Post by bomse1 »

thank you _mental_. iam grateful for any advise. you are right, its pretty difficult from the distance.

i tried to copy the .ini but it didnt work. still crashing. that is so frustrating :(
bomse1
Posts: 7
Joined: Fri Jan 19, 2018 4:50 am

Re: blackscreen after fullscreen -> hard reset

Post by bomse1 »

i need to add something: its not the system thats crashing. music is still playing and the monitor options are still accessable.

it feels like the monitor isnt "triggered" correctly anymore. somehow. i suppose its a graphics card problem. dunno.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49066
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: blackscreen after fullscreen -> hard reset

Post by Graf Zahl »

Try so edit the .ini manually and set vid_fps to 60. GZDoom will always try the best refresh rate it can find for a given resolution and there have been rare occurences where this failed.
bomse1
Posts: 7
Joined: Fri Jan 19, 2018 4:50 am

Re: blackscreen after fullscreen -> hard reset

Post by bomse1 »

heureka, i managed to make it work again! switching to fullscreen still crashes but i found a way to reset.
i tried severel things at once, so iam not so sure what it was: either changing the resolution from 1920x1080 to another one for once or (and thats more likely it in my eyes)
the 'register' and 'identify' buttons in the monitor-resolution-screen
plus
erasing the .ini in the gzdoom folder.

but fullscreen problem still existing.

thanks graf zahl for your tip!
Post Reply

Return to “Technical Issues”