so, i've been able to use byond just fine for a while. stopped playing for a bit, and i tried playing a couple days ago. it'll start loading, close but still be active, as i can see it in task manager, and when i try opening it again it's just completely white. then either after about 5-10 seconds, or just immediately sometimes, it'll give me 'BYOND is not responding'
it'll occasionally let me login, but that's all i can interact with.

i've tried multiple things i've seen suggested on other posts.

changing the userpath
reinstalling internet explorer
deleting all byond folders then reinstalling byond
changing antivirus settings
installing in different locations
running as administrator
renaming the cfg folder
restarting my computer
cleared the cache (manually went to the folder, since i cant interact with byond at all.)
did some of these multiple times, as well.

using windows 10, 64 bit, locale is english (united states), no cyrillic in the user name

i have zero clue why it's suddenly not working, so help would be greatly appreciated.

edit: i've noticed byond also tends to freeze one or two applications i have open, preventing me from interacting with them as well until i close it out, which is kinda weird. it doesn't make them not respond, just unable to be interacted with.

edit 2: been a while, huh?
anyway, decided to try again after all this time of not getting any response, and i opened up the event viewer when i did. this time it actually gave me an error. it always shows up, even after a complete reinstall.

Faulting application name: byond.exe, version: 5.0.513.1542, time stamp: 0x601349b9
Faulting module name: d3d10warp.dll, version: 10.0.18362.1049, time stamp: 0x6aabfaf4
Exception code: 0xc0000005
Fault offset: 0x0038b446
Faulting process id: 0x86c
Faulting application start time: 0x01d71f174fedf0f9
Faulting application path: C:\Program Files (x86)\BYOND\bin\byond.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d10warp.dll
Report Id: e939c5dd-7506-4e75-817e-23be9956eaf3
Faulting package full name:
Faulting package-relative application ID:

figured this would help someone figure out the problem.