postgresql 9.6 stopped working out of nowhere

I have postgresql 9.6 running on windows 10.

its accepting ports

pg_hba.conf

host all all 0.0.0.0/0 md5

postgresql.conf

listen_addresses='*'

I have had this DB running for about 6 months now. I am the only user and the last time I changed anything in the settings was months ago. I was using it earlier this morning then out of nowwhere it gave me an error that it was unable to connect

Server doesn't listen
The server doesn't accept connections: the connection library reports 
could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (::1) and accepting TCP/IP connections on port 5432? could not connect to server: Connection refused (0x0000274D/10061) Is the server running on host "localhost" (127.0.0.1) and accepting TCP/IP connections on port 5432? 
If you encounter this message, please check if the server you're trying to contact is actually running PostgreSQL on the given port. Test if you have network connectivity from your client to the server host using ping or equivalent tools. Is your network / VPN / SSH tunnel / firewall configured correctly? 
For security reasons, PostgreSQL does not listen on all available IP addresses on the server machine initially. In order to access the server over the network, you need to enable listening on the address first. 
For PostgreSQL servers starting with version 8.0, this is controlled using the "listen_addresses" parameter in the postgresql.conf file. Here, you can enter a list of IP addresses the server should listen on, or simply use '*' to listen on all available IP addresses. For earlier servers (Version 7.3 or 7.4), you'll need to set the "tcpip_socket" parameter to 'true'. 
You can use the postgresql.conf editor that is built into pgAdmin III to edit the postgresql.conf configuration file. After changing this file, you need to restart the server process to make the setting effective. 
If you double-checked your configuration but still get this error message, it's still unlikely that you encounter a fatal PostgreSQL misbehaviour. You probably have some low level network connectivity problems (e.g. firewall configuration). Please check this thoroughly before reporting a bug to the PostgreSQL community. 

again I made no changes and I am the only user and this was working earlier this morning.

from the pg_log folder here is the messages it gave me when it stopped working

2019-08-05 14:24:02 EDT LOG:  server process (PID 15104) was terminated by exception 0xC0000005
2019-08-05 14:24:02 EDT HINT:  See C include file "ntstatus.h" for a description of the hexadecimal value.
2019-08-05 14:24:02 EDT LOG:  terminating any other active server processes
2019-08-05 14:24:02 EDT WARNING:  terminating connection because of crash of another server process
2019-08-05 14:24:02 EDT DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2019-08-05 14:24:02 EDT HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2019-08-05 14:24:02 EDT WARNING:  terminating connection because of crash of another server process
2019-08-05 14:24:02 EDT DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2019-08-05 14:24:02 EDT HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2019-08-05 14:24:02 EDT LOG:  all server processes terminated; reinitializing
2019-08-05 14:24:02 EDT LOG:  startup process (PID 10536) was terminated by exception 0xC0000005
2019-08-05 14:24:02 EDT HINT:  See C include file "ntstatus.h" for a description of the hexadecimal value.
2019-08-05 14:24:02 EDT LOG:  aborting startup due to startup process failure
2019-08-05 14:24:02 EDT LOG:  database system is shut down

I tried restarting my computer, did not work. Connecting via pgadminIII, I am still able to use the other DB's that are hosted remotely. Very confused on what is happening