Server task still running after crash + Using different ports ip4 and ip6 ports when restarting

There exists a change that after a server crash occurs, by that I mean the .exe file closes (or system keeps running it is just the program that stops), there is a chance that when rebooting the server both ip4 and ip6 ports will be set to 0, while the port it is supposed to use is "already occupied" by the older server that is no longer running, but because of the crash it never closed the port.

I can submit the server log file in case I find it. But the crash comes down to overloading the server with commands (Basic anti-cheat to prevent things like npc's and command minecarts). The crash was my own fault though. But it comes down to server gets overloaded and crashes leaving the port open.

Is there a way of making it so the port can get closed either by a new server opening and detecting that there is in fact not a server on that port? Al tough I do doubt that is possible myself.

As at this moment the only way to fix it is by rebooting the os. Making it so the crashed program is completely removed from memory/tasklist. And so there is noting accessing the server.

Last note, bug report might be al over the place, but I assume after the crash the server didn't fully shut down, it just kept the task but the console screen closed down. (Reason I suspect that is because I have a script to test if the server task is still running (to reboot server if task has ended), and the script still detected the server hence not opening another instance).