Games won't launch

[Bro Bike]

Hi there,

Today Killing Floor 2 and DOOM Eternal won't start. Both would end up with Steam telling me the game is running but task bar and task manager shows nothing.

I think it has something to do with the last Steam update. Only Quake Live would start and launch.

Nothing on my PC has changed since 2 days ago, no new programs no new driver updates.

[fireplankg]

:D

[crunchyfrog]

Go to your Task Manager.
Don't just look at processes, but also go into finer detailby looking at details and services - you should find the legacy thing that's causing this in there.

[Bro Bike]

crunchyfrog の投稿を引用：

Go to your Task Manager.
Don't just look at processes, but also go into finer detailby looking at details and services - you should find the legacy thing that's causing this in there.

What is the legacy thing name?

[The Giving One]

Looks like you are on Windows 11 :

https://steamcommunity.com/app/232090/discussions/1/5144805327263461243/

Please post the rest of your system specs like this :

Go to "Help" in the top of Steam, then "System Information" in the drop down.

In the new window, right click, "select all", then "copy" and "paste" all that here, please.

[Bro Bike]

I played some StarCraft 2 and L4D2 and then 2 hours after I decided to try again Killing Floor 2 which launched without problems. This is very weird.


Computer Information:
Manufacturer: ASUS
Model: System Product Name
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: 12th Gen Intel(R) Core(TM) i5-12600K
CPU Family: 0x6
CPU Model: 0x97
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 3686 Mhz
16 logical processors
10 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:
Windows 11 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0

Video Card:
Driver: NVIDIA GeForce GTX 1080 Ti
DirectX Driver Name: nvldumd.dll
Driver Version: 30.0.15.1179
DirectX Driver Version: 30.0.15.1179
Driver Date: 2 10 2022
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 360 Hz
DirectX Card: NVIDIA GeForce GTX 1080 Ti
VendorID: 0x10de
DeviceID: 0x1b06
Revision: 0xa1
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 21.38" x 11.89" (24.45" diag)
54.3cm x 30.2cm (62.1cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 11263 MB
Supported MSAA Modes: 2x 4x 8x

Sound card:
Audio device: Speakers (Realtek(R) Audio)

Memory:
RAM: 16125 MB

VR Hardware:
VR Headset: None detected

Miscellaneous:
UI Language: English
Media Type: Undetermined
Total Hard Disk Space Available: 4783242 MB
Largest Free Hard Disk Block: 1036954 MB
OS Install Date: janv. 20 2022
Game Controller: None detected
MAC Address hash: e47dc8578051f20be452601c4d28654ef594cdcb

Storage:
Disk serial number hash: 0
Number of SSDs: 0
Number of HDDs: 0

[crunchyfrog]

Bro Bike の投稿を引用：

crunchyfrog の投稿を引用：

Go to your Task Manager.
Don't just look at processes, but also go into finer detailby looking at details and services - you should find the legacy thing that's causing this in there.

What is the legacy thing name?

Now that's something you're going to have to work out from reading the data to see what the programs relate to.

We can't say as it entirely depends on the program and what it's running.

[crunchyfrog]

Bro Bike の投稿を引用：

I played some StarCraft 2 and L4D2 and then 2 hours after I decided to try again Killing Floor 2 which launched without problems. This is very weird.


Computer Information:
Manufacturer: ASUS
Model: System Product Name
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: 12th Gen Intel(R) Core(TM) i5-12600K
CPU Family: 0x6
CPU Model: 0x97
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 3686 Mhz
16 logical processors
10 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:
Windows 11 (64 bit)
NTFS: Supported
Crypto Provider Codes: Supported 311 0x0 0x0 0x0

Video Card:
Driver: NVIDIA GeForce GTX 1080 Ti
DirectX Driver Name: nvldumd.dll
Driver Version: 30.0.15.1179
DirectX Driver Version: 30.0.15.1179
Driver Date: 2 10 2022
OpenGL Version: 4.6
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 360 Hz
DirectX Card: NVIDIA GeForce GTX 1080 Ti
VendorID: 0x10de
DeviceID: 0x1b06
Revision: 0xa1
Number of Monitors: 1
Number of Logical Video Cards: 1
No SLI or Crossfire Detected
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 21.38" x 11.89" (24.45" diag)
54.3cm x 30.2cm (62.1cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 11263 MB
Supported MSAA Modes: 2x 4x 8x

Sound card:
Audio device: Speakers (Realtek(R) Audio)

Memory:
RAM: 16125 MB

VR Hardware:
VR Headset: None detected

Miscellaneous:
UI Language: English
Media Type: Undetermined
Total Hard Disk Space Available: 4783242 MB
Largest Free Hard Disk Block: 1036954 MB
OS Install Date: janv. 20 2022
Game Controller: None detected
MAC Address hash: e47dc8578051f20be452601c4d28654ef594cdcb

Storage:
Disk serial number hash: 0
Number of SSDs: 0
Number of HDDs: 0

Not really.

As I said it's those tricky little legacy programs that get left open. Unless you find out what they are and kill them they can stay open.

It's just likely that when you tried playing one of those other games, it luckily killed it for you.

Just a quick question for the future - do you use sleep mode at all, and not shut your PC down fully? If you do, you should avoid doing that as that can ezxacerbate this issue.

[Bro Bike]

Restarting the PC did not fix it (first thing I tried), yes I have sleep mode activated on this desktop PC.

[crunchyfrog]

Bro Bike の投稿を引用：

Restarting the PC did not fix it (first thing I tried), yes I have sleep mode activated on this desktop PC.

Well don't do that. Always shut down the PC properly, and do not have settings wheere drive go to sleep after a period of lack of use. That really loves to screw up how Steam works and cause issues like this.

[Bro Bike]

crunchyfrog の投稿を引用：

Bro Bike の投稿を引用：

Restarting the PC did not fix it (first thing I tried), yes I have sleep mode activated on this desktop PC.

Well don't do that. Always shut down the PC properly, and do not have settings wheere drive go to sleep after a period of lack of use. That really loves to screw up how Steam works and cause issues like this.

I shut down the PC properly, in the Steam interface I always clicked "close game" before doing anything. I have an NVMe SSD and I do not wish to turn off the auto PC sleep mode after 15mn. My problem has nothing to do with this I think.

[crunchyfrog]

Bro Bike の投稿を引用：

crunchyfrog の投稿を引用：

Well don't do that. Always shut down the PC properly, and do not have settings wheere drive go to sleep after a period of lack of use. That really loves to screw up how Steam works and cause issues like this.

I shut down the PC properly, in the Steam interface I always clicked "close game" before doing anything. I have an NVMe SSD and I do not wish to turn off the auto PC sleep mode after 15mn. My problem has nothing to do with this I think.

Maybe, but all I'm saying is that if you do use sleep mode or such things it WILL mess with Steam and it is notorious for this behaviour.

[Bro Bike]

Shouldn't affect Steam on cold start. Anyway thanks for letting me know.

[crunchyfrog]

Bro Bike の投稿を引用：

Shouldn't affect Steam on cold start. Anyway thanks for letting me know.

No it doesn't that's not the point really.

Its' that when you start steam and let it run it all goes fine, say. But if you have power saving settings, things like hard drives and such will power down after a given period. This confuses steam completely, and you will typically find your library starts disappearing and it can be a bit of a pain.

That's AFTER starting normally. You should try to keep things running at all times and then fully off when you need to. That's the point - hope it's clearer.

[Bro Bike]

crunchyfrog の投稿を引用：

Bro Bike の投稿を引用：

Shouldn't affect Steam on cold start. Anyway thanks for letting me know.

No it doesn't that's not the point really.

Its' that when you start steam and let it run it all goes fine, say. But if you have power saving settings, things like hard drives and such will power down after a given period. This confuses steam completely, and you will typically find your library starts disappearing and it can be a bit of a pain.

That's AFTER starting normally. You should try to keep things running at all times and then fully off when you need to. That's the point - hope it's clearer.

I have an NVMe SSD they don't go into sleep mode I think, the problem I had was happening right after starting the PC, no sleep mode were engagaed.

[crunchyfrog]

Bro Bike の投稿を引用：

crunchyfrog の投稿を引用：

No it doesn't that's not the point really.

Its' that when you start steam and let it run it all goes fine, say. But if you have power saving settings, things like hard drives and such will power down after a given period. This confuses steam completely, and you will typically find your library starts disappearing and it can be a bit of a pain.

That's AFTER starting normally. You should try to keep things running at all times and then fully off when you need to. That's the point - hope it's clearer.

I have an NVMe SSD they don't go into sleep mode I think, the problem I had was happening right after starting the PC, no sleep mode were engagaed.

Ah if that's the case, then we can try to hone in on it to prevent it happening again?

Or monitor it to see if it crops up again? Commonly it's general power savings settings like letting drives go dormant after a period of no use, but it can also be USB sockets powering down, or any of the other little things. The biggest problem tends to be anything drive realted as it the doesn't see the storage and gets confused.

But that's not the only thing of course.

So let us know if it persists and I'll happily have a closer bash at it.