-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Black Screen Crash on Launch #2784
Comments
Which Windows 10 version is this, what GPUs do you have in your machine (integrated and discrete)? When does it crash, after a bit of launch or rather immediately at startup during the green console or showing the window? |
Windows 10 version 20H2, OS Build 19041.928 Running GeForce GTX1070 8GB card, no integrated GPU showing on my system information. All software/drivers is up to date. Freeze/lock up occurs right after the initial green console screen vanishes and the PoB window opens. It opens as a black screen with the top bar blank, only showing the minimize/window/close buttons there. It does not seem to correlate with any specific tasks that I can identify, as the console has already finished its sequence/update process. It only occurs if the window has been closed and then relaunched on my secondary display, and seems to not occur as long as I never move it off my primary after a reinstall (tested this a few more times this morning since submitting issue.) |
Could you try this variant of SimpleGraphic.dll, temporarily replacing the one in your PoB folder? It's going to be annoying and try to redownload the old one as an "update" every time you run but I'm curious if the changes I've made to the graphics backend make any difference. |
works for me, thanks! |
@Neclony Ooh, that's interesting. Could you describe how your PoB was behaving prior to testing this DLL, please also mention what hardware and Windows version you are on? |
After the small green window(I believe this window opened on the primary monitor) it opened the actual window in black on the secondary monitor. It constantly had a bit, maybe 10-20% CPU usage and not responding in Task Manager. I left it like that maybe for a minute but nothing more happened other than when I tried to close it that Windows wrote that it crashed with the typical popup to end the process. Last time working I closed it maximized on the secondary monitor so I couldn't even "restore" it to a smaller window to move it to the primary(no key combination or option worked). I had to turn off the secondary monitor to launch it again without a problem. I should mention that it works on the secondary without a problem if it opened on the primary, so closing it on the primary is necessary(Windows cached window position). 2 monitor setup, with too many peripheral devices ^^ |
oh and it also crashes like this in a normal window when it launches on the secondary monitor and I can even move it to the primary but Windows does not remember the position of the "crashed" window when closed. |
@Neclony It should be fine for you to continue using this reworked DLL, the only bug I currently know about in it is that it once failed to completely exit for me when closing the program. Thanks for the information on the problem and your setup, it'll help to evaluate how safe it is to integrate the changes into the main Path of Building runtime. It sounds like you're indeed in the same problem category as the original poster. |
Hi, i have the same problem the green screen open and after a few second it close the main windows. My spec : I9-9900k Nom de l’application défaillante Path of Building.exe, version : 0.0.0.0, horodatage : 0x606d1b4c
|
FYI - Mine was crashing (is crashing) and i changed the compatibility to Win 8...And this time it stopped with an error (instead of just crashing). Error: In update thread [string "#@...":110: attempt to index a nil value stack traceback: [string "#@..."-:110: in main chunk...press f5 to restart app |
I also have this issue. When I open PoB it flashes the green console, and then hangs on a black screen in the main window, have to force close it due to 'not responding.' I used to be able to fix this by uninstalling and then reinstalling PoB, but that doesn't work anymore. |
When launching in Windows 10, PoB is freezing on the main screen and forcing windows to close it. When this started to manifest, it would resolve if the software was reinstalled. It no longer fixes the issue.
I haven't been able to recover any crash files to help diagnose this but am open to trying other ways to capture this data. A screen capture will only show a blank, black screen.
I use PoB religiously while playing PoE and I am finding this very difficult to navigate/deal with.
The issue appears to occur when the software is launched in my second monitor.
The text was updated successfully, but these errors were encountered: