How to fix 0xC0000005 exception in Postgres 9.0

Hi!

Every time when user tries to log on from same virtual computer where
Postgreql resides, Postgres terminates with 0xC0000005 exception. Log is
below.

About 65 users are accessing this server over VPN. They can use server
normally.
Logging from localhost using pgadmin 4 with user postgres also works.

Only any attempt to log on from localhost with user dbadmin from psqlODBC
client causes this exception.

It has worked normally for many years but now suddenly stopped working for
localhost.

How to fix this ?

Server:

PostgreSQL 9.0.4, compiled by Visual C++ build 1500, 64-bit

OS:

Windows server 2008 R2
Version 6.1 Build 7601

Andrus.

Postgres log:

2020-02-20 15:44:51 EET LOG: server process (PID 3788) was terminated by
exception 0xC0000005
2020-02-20 15:44:51 EET HINT: See C include file "ntstatus.h" for a
description of the hexadecimal value.
2020-02-20 15:44:51 EET LOG: terminating any other active server
processes
2020-02-20 15:44:51 EET andrus mydatabase WARNING: terminating connection
because of crash of another server process
2020-02-20 15:44:51 EET andrus mydatabase 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.
2020-02-20 15:44:51 EET andrus mydatabase HINT: In a moment you should be
able to reconnect to the database and repeat your command.
2020-02-20 15:44:51 EET kati mydatabase WARNING: terminating connection
because of crash of another server process
2020-02-20 15:44:51 EET kati mydatabase 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.
2020-02-20 15:44:51 EET kati mydatabase HINT: In a moment you should be
able to reconnect to the database and repeat your command.
2020-02-20 15:44:51 EET julia mydatabase WARNING: terminating connection
because of crash of another server process
2020-02-20 15:44:51 EET julia mydatabase 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.
2020-02-20 15:44:51 EET julia mydatabase HINT: In a moment you should be
able to reconnect to the database and repeat your command.
2020-02-20 15:44:51 EET reinpuu mydatabase WARNING: terminating connection
because of crash of another server process
2020-02-20 15:44:51 EET reinpuu mydatabase 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.
2020-02-20 15:44:51 EET reinpuu mydatabase HINT: In a moment you should be
able to reconnect to the database and repeat your command.
2020-02-20 15:44:51 EET kokka mydatabase WARNING: terminating connection
because of crash of another server process
2020-02-20 15:44:51 EET kokka mydatabase 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.
2020-02-20 15:44:51 EET kokka mydatabase HINT: In a moment you should be
able to reconnect to the database and repeat your command.
2020-02-20 15:44:51 EET myll mydatabase WARNING: terminating connection
because of crash of another server process
2020-02-20 15:44:51 EET myll mydatabase 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.
2020-02-20 15:44:51 EET myll mydatabase HINT: In a moment you should be
able to reconnect to the database and repeat your command.
2020-02-20 15:44:51 EET WARNING: terminating connection because of crash
of another server process
2020-02-20 15:44:51 EET 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.
2020-02-20 15:44:51 EET HINT: In a moment you should be able to reconnect
to the database and repeat your command.
2020-02-20 15:44:51 EET dbadmin mydatabase FATAL: the database system is in
recovery mode
2020-02-20 15:44:51 EET LOG: all server processes terminated;
reinitializing
2020-02-20 15:45:01 EET FATAL: pre-existing shared memory block is still
in use
2020-02-20 15:45:01 EET HINT: Check if there are any old server processes
still running, and terminate them.