having chased this error several times over the last 20 years, if its not windows update, AV update, firewall config change, UAC or a driver update it is nearly impossible to to figure out what is causing it.
One can try to run sysinternal app such as process explorer or depends to look over the files see if there are recent changes
Process explorer i have seen crash postgresql when it tries to monitor the internal workings so it can be very dangerous to use,
I have learned if the root of the problem can not be quickly identified in an hour or two, its faster to just start from scratch, format the server, install windows, and recover from backups. That is how frustrating this error can be to track ..
On Thu, Feb 20, 2020 at 6:17 PM Ron <ronljohnsonjr@xxxxxxxxx> wrote:
On 2/20/20 4:50 PM, Adrian Klaver wrote:
On 2/20/20 2:48 PM, Ron wrote:
On 2/20/20 4:35 PM, Adrian Klaver wrote:
On 2/20/20 2:29 PM, Andrus wrote:
Hi!
>Then what changes were done recently, in particular ODBC-related.
Same psqlODBC driver 09.00.0101 has worked 10 years.
Previously I logged into this server long time ago and then it worked.
Windows update history shows lot of updates all called
Security Intelligence Update for Microsoft Endpoint Protection - KB 2461484
with different version numbers.
So did the issue show up after the above updates?
What is ntstatus.h? Would looking there for 0xC0000005 give a clue to the problem (and thus solution)?
https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-erref/596a1078-e883-4972-9bbc-49e60bebca55
Good luck on gaining any useful information:)
The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
If he recently patched Windows, that might be the cause.
--
Angular momentum makes the world go 'round.
