<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-15">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
a strange error is happening to some of our customers.<br>
They all have a Windows 10 installation on their machines with our
application and, of course, PostgreSQL 9.1 installed (migration to
9.5 upcoming in late summer/fall, but not applicable by now)<br>
<br>
While working, suddenly PostgreSQL stops working, and log reports<br>
<br>
2016-05-05 10:36:19 CEST LOG: server process (PID 5920) was
terminated by exception 0xC0000018<br>
2016-05-05 10:36:19 CEST HINT: See C include file "ntstatus.h" for
a description of the hexadecimal value.<br>
2016-05-05 10:36:19 CEST LOG: terminating any other active server
processes<br>
2016-05-05 10:36:19 CEST WARNING: terminating connection because of
crash of another server process<br>
2016-05-05 10:36:19 CEST 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.<br>
2016-05-05 10:36:19 CEST HINT: In a moment you should be able to
reconnect to the database and repeat your command.<br>
[... above three lines repeated a bunch of times...]<br>
2016-05-05 10:36:19 CEST LOG: all server processes terminated;
reinitializing<br>
2016-05-05 10:36:29 CEST FATAL: pre-existing shared memory block is
still in use<br>
2016-05-05 10:36:29 CEST HINT: Check if there are any old server
processes still running, and terminate them.<br>
<br>
ntstatus.h refers to exception code as<br>
<p><i>0xC0000018</i></p>
<i> </i>
<p><i>STATUS_CONFLICTING_ADDRESSES</i></p>
<i> </i>
<p><i>{Conflicting Address Range} The specified address range
conflicts with the address space.</i></p>
Googling I found many applications failing with that error and how
to fix them by setting a value in Registry, but these are not the
cases.<br>
All I found in common of these machines (except Windows 10 and our
app :-) ) was ClassicShell. Uninstalling it seemed to resolve the
problem... until 2 hours ago, when one of them submitted us the same
crash with same error.<br>
<br>
Trying to google deeper did not help for me.<br>
<br>
This issue seems to be present on Windows 10 machines.<br>
<br>
Any idea/thought/suggestion?<br>
<br>
Thanks in advance,<br>
Moreno.-<br>
</body>
</html>