Hang at Launch (OpenGL only, fallback to D3D9 doesn't happen)

[KatherineFtw]

What happens?
I launch it, and windows basically stops until it's closed. I've tried both 1.4.2 and 1.5.4, both installer and zip, both cause this issue. Can't even open the debugger for a log file, it's that bad.

• Problem details -
  Problem signature
  Problem Event Name: AppHangB1
  Application Name: PPSSPPWindows64.exe
  Application Version: 1.5.4.0
  Application Timestamp: 5a26acd0
  Hang Signature: 334c
  Hang Type: 134217728
  OS Version: 10.0.16299.2.0.0.768.101
  Locale ID: 1033
  Additional Hang Signature 1: 334c6b321bb203e931b3c5865c5127a1
  Additional Hang Signature 2: 1348
  Additional Hang Signature 3: 1348ccb9c2ab6d5bece49268e52481fd
  Additional Hang Signature 4: 334c
  Additional Hang Signature 5: 334c6b321bb203e931b3c5865c5127a1
  Additional Hang Signature 6: 1348
  Additional Hang Signature 7: 1348ccb9c2ab6d5bece49268e52481fd

What should happen?
IDK, it opens and doesn't nearly crash windows? I last used PPSSPP years ago on my old PC.

What hardware and operating system are you running PPSSPP on? GPU might matter if it's a graphical issue.
Dell Insperion 7559
Intel-i5 6300 HQ
Nvidia GTX-960M
8GB of RAM
Western Digital 2 TB External Hard Drive

[hrydgard]

Weird, this is not happening for many people so must be something specific to your setup. Two things that may be interesting to try:

• Upgrade your NVIDIA drivers to the latest version
• Go into memstick/PSP/SYSTEM/ppsspp.ini and change GPUBackend to 0, 1, 2, and 3, and see if any of those work.

[KatherineFtw]

System is empty. The whole of Memstick is.

[KatherineFtw]

Update: Deleated PPSSPP, attempting the ZIP of 1.5.4 again.

[KatherineFtw]

And, again.

Problem signature
Problem Event Name: AppHangB1
Application Name: PPSSPPWindows64.exe
Application Version: 1.5.4.0
Application Timestamp: 5a26acd0
Hang Signature: db44
Hang Type: 134217728
OS Version: 10.0.16299.2.0.0.768.101
Locale ID: 1033
Additional Hang Signature 1: db44db06cf72c887e5d965642ec2cfcf
Additional Hang Signature 2: ad62
Additional Hang Signature 3: ad62c0317070d9bb923f0e666b6def71
Additional Hang Signature 4: db44
Additional Hang Signature 5: db44db06cf72c887e5d965642ec2cfcf
Additional Hang Signature 6: ad62
Additional Hang Signature 7: ad62c0317070d9bb923f0e666b6def71

Here's literally my folder.
https://drive.google.com/open?id=1gUBBIXsisIQYS8r2SHn_qXAx4-sKwbEA

[unknownbrackets]

Can you try much older versions, such as 1.0.1? Just wondering if any version works.

https://github.com/hrydgard/ppsspp/releases/tag/v1.0.1

-[Unknown]

[KatherineFtw]

Problem signature
Problem Event Name: AppHangB1
Application Name: PPSSPPWindows64.exe
Application Version: 1.0.1.0
Application Timestamp: 54ef8192
Hang Signature: db44
Hang Type: 134217728
OS Version: 10.0.16299.2.0.0.768.101
Locale ID: 1033
Additional Hang Signature 1: db44db06cf72c887e5d965642ec2cfcf
Additional Hang Signature 2: 7c9c
Additional Hang Signature 3: 7c9cdcf1bdb3e667e59fa7366cd8ab80
Additional Hang Signature 4: db44
Additional Hang Signature 5: db44db06cf72c887e5d965642ec2cfcf
Additional Hang Signature 6: 7c9c
Additional Hang Signature 7: 7c9cdcf1bdb3e667e59fa7366cd8ab80

I'll keep trying 1.0.1.

Edit: (Attempt with 32-Bit Executable)
Problem signature
Problem Event Name: AppHangB1
Application Name: PPSSPPWindows.exe
Application Version: 1.0.1.0
Application Timestamp: 54ef8206
Hang Signature: 5694
Hang Type: 134217728
OS Version: 10.0.16299.2.0.0.768.101
Locale ID: 1033
Additional Hang Signature 1: 5694614c0c04801851c06f66b6106f8f
Additional Hang Signature 2: 483b
Additional Hang Signature 3: 483b4d53cf79bc8bc7f497343a39aec7
Additional Hang Signature 4: 5694
Additional Hang Signature 5: 5694614c0c04801851c06f66b6106f8f
Additional Hang Signature 6: 483b
Additional Hang Signature 7: 483b4d53cf79bc8bc7f497343a39aec7

[KatherineFtw]

Attempt with v0.9.5.

Well first off, I got the debug console open, not too much to report though.............

Problem signature
Problem Event Name: AppHangB1
Application Name: PPSSPPWindows64.exe
Application Version: 0.0.9.5
Application Timestamp: 527393b8
Hang Signature: eca0
Hang Type: 134217728
OS Version: 10.0.16299.2.0.0.768.101
Locale ID: 1033
Additional Hang Signature 1: eca02242278a6f8fa2ad3f43ddd75196
Additional Hang Signature 2: 3057
Additional Hang Signature 3: 3057384488d384f8a71184efd4df4e51
Additional Hang Signature 4: eca0
Additional Hang Signature 5: eca02242278a6f8fa2ad3f43ddd75196
Additional Hang Signature 6: 3057
Additional Hang Signature 7: 3057384488d384f8a71184efd4df4e51

[KatherineFtw]

I have an idea if nothing else. Can you upload the default memstick files for me to put in there and see if it hangs?

[TehPlayer14]

Perhaps try to clean boot and try to run PPSSPP no idea if that would work but its worth a shot or even in safe mode

[KatherineFtw]

We found the issue I guess. Booted in Safe Mode. OpenGL was the issue according to this. No issues with DX9.

Edit: No problems with DX11 either. Going to test a few games.

[hrydgard]

OK, good. Unfortunate that we failed to fall back automatically to D3D...

Hopefully if anyone else has this problem they'll end up here when googling. To force another GPU backend on first boot, start PPSSPP from the command line (or a shortcut) with the argument --graphics=directx9 or --graphics=directx11 or --graphics=vulkan.

By the way, you might want to try to download the latest drivers for your GPU from NVIDIA, that might also have solved it.

[KatherineFtw]

I have the latest drivers, the issue is that memstick doesn't load properly either. I had to go into safe mode before this occurred.

[TehPlayer14]

Make sure the dedicated gpu gets picked to render job for ppsspp because you might've integrated graphics

[hrydgard]

@KatherineFtw OK, that's very weird.

@TehPlayer14 We already use NVIDIA's recommended hack to get it to use the dedicated GPU if there are two.

[TehPlayer14]

Permission issues then perhaps try to run PPSSPP as administrator? or moving the folder somewhere else or erasing memstick

[unknownbrackets]

Does this still happen in the latest git and with the latest drivers?

-[Unknown]

[KatherineFtw]

Hold on, I'll try a fresh install.

[KatherineFtw]

No issue, auto sets to Vulkin without problem. Not even using latest Nvidia Drivers yet. Don't know if if me having already fixed the issue affects this at all though.

[unknownbrackets]

Ah - we default to Vulkan now in 1.6.x, maybe that's just effectively worked around this problem. But if it's a driver bug and it supports Vulkan anyway, that might be the best we can do.

-[Unknown]

[hrydgard]

I'm gonna close this, not clear what we can do...