Memory Exhaustion Problems

[PieterVuylsteke]

In the incoming version 1.8.8-8 I am making efforts to prevent memory exhaustion issues in some critical tools. One of them is Debayer, which will do a much better job to adapt the number of worker threads to the available physical memory, taking into account predicted per-thread memory requirements. It will also be much faster thanks to an improved noise evaluation routine.

Dear Juan,

Could you please please explain a bit more in detail how that memory exhaustion manifests itself on WIndows 10, 64bit ?

I got a brand new computer with i7-9700K, 2TB and 64GB.

In two days I got with PixInsight THREE crashes with the error message
Bug Check 0xBE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

My new computer underwent a full memcheck, nothing bad was found on it. Today it was the whole day back in the shop, the brave people do not find what is happening with the machine.

Could it be that not the computer is in fault, but that it is PIwith that memory exhaustion ?

Strangely, I do manage to work on those files with my laptop which has more kernels (6*2, the desktop has 8*1), but only 16GB.
That's why I did not think PI was in error, but now I read this message and start to get very worried...

Yes, I was working on a lot of files : 50MB Nikon Z7 transform into half GB files, and if one has 100 or 200, that is a lot of GB.

My PC is still at the shop, they will continue to investigate it. I do not dare to say it, but hopefully you understand its rather an urgency...

 

[fredvanner]

I get on fine with an old i7-8700K with 32GB running Windows 10 Pro (64bit). I've never had a crash or a memory problem. I run with my swap space on my 500GB SDD C: drive, with my image storage on various other much larger (but much slower) drives.
My typical captured images (from an ASI2600 - 6248x4176x16bit) are ~50MB -> 100MB (32bit CFA) -> 300MB(32 bit RGB).

 

[Juan Conejero]

Bug Check 0xBE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

As noted in the other thread where you reported the same, this problem has nothing to do with PixInsight. See this document on Microsoft's website for complete information:

Bug Check 0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORY - Windows drivers

The ATTEMPTED_WRITE_TO_READONLY_MEMORY bug check has a value of 0x000000BE. This is issued if a driver attempts to write to a read-only memory segment.

docs.microsoft.com

So one of the device drivers that you have installed on your machine is causing this. PixInsight is a processor/memory/graphics intensive application prone to expose this type of inconsistencies, but the real cause of the problem is not PixInsight.

 

[PieterVuylsteke]

As noted in the other thread where you reported the same, this problem has nothing to do with PixInsight. See this document on Microsoft's website for complete information:

Bug Check 0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORY - Windows drivers

The ATTEMPTED_WRITE_TO_READONLY_MEMORY bug check has a value of 0x000000BE. This is issued if a driver attempts to write to a read-only memory segment.

docs.microsoft.com

So one of the device drivers that you have installed on your machine is causing this. PixInsight is a processor/memory/graphics intensive application prone to expose this type of inconsistencies, but the real cause of the problem is not PixInsight.

OK, thank you very much for confirming this. I'll send that message to the people who did a fresh reinstall of the machine hours before this started to happen. They did something wrong apparently.

 

[PieterVuylsteke]

Some extra information, one never knows it is of interest to other people :
The desktop went back to the shop and the hardware was extensively tested. Nothing found. However, they changed a thing in the BIOS so that the RAM memory would not run at 2111 but 2666 (ximp or something?)

Yesterday all went fine, no crashes in PixInsight and not in Autostakkert, whilst beforee they crashed all the time. Me happy, temporarily.

This morning I was debayering a lot of files and yes : blue screen.
This time not the 0XBE error, but 0x50 :
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffd485c4da1080, 0x0000000000000000, 0xfffff8017124cbb8, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: d0bd68bb-de4d-466e-812d-2ce0aff9d04c.

Under that line in the event manager, I found also this line :

The propres à l’application permission settings do not grant Local Exécution permission for the COM Server application with CLSID
{7022A3B3-D004-4F52-AF11-E9E987FEE25F}
and APPID
{ADA41B3C-C6FD-4A08-8CC1-D6EFDE67BE7D}
to the user DESKTOP-63RLTA1\Admin SID (S-1-5-21-1275434260-3885244832-1013481107-1001) from address LocalHost (avec LRPC) running in the application container Non disponible SID (Non disponible). This security permission can be modified using the Component Services administrative tool.

The application apparently is called WPN Srumon server. No clue what that is.

I did find these two id's in the regedit (in the CLSID group), and the admin had only READ. But, I could not change it because the owner was TrustedInstaller. So first had to change the owner to admin, and the I could give full access to admin.

After starting debayer again PixInsight crashed directly, every time. So there was some advance, but rather not in the correct direction.

After that I started PixInsight as administrator, and for the moment (until further notice) it runs fine.
A bit bizare as my usercode for windows is the admin.

PS: whilsts typing all of this I debayered 160 files succesfully. Me happy, Temporarily.

 

[sunlover]

Such bugchecks are caused by a buggy device driver. In order to determine which driver is causing this, it is necessary to look at the MEMORY.DMP dump using Windows debugger (WinDbg). Probably people in the shop will be able to do this.

 

[PieterVuylsteke]

Such bugchecks are caused by a buggy device driver. In order to determine which driver is causing this, it is necessary to look at the MEMORY.DMP dump using Windows debugger (WinDbg). Probably people in the shop will be able to do this.

They did not find anything. And yes, it is a big, very well known specialist shop in Geneva.

For the moment it seems to me that the fact that the Admin did not have all full rights and ownership is the cause of the problems. I'll ask more info to the shop.

I just finished the calibration, debayer, staralign en integration of 160 lights (NEF 50MB, debayered 0.5Gig) with no problems... Cross fingers it stays like this