Multiple Win 7 Pro - KERNEL_DATA_INPAGE_ERROR's Blue Screen of Death's...

[jwaters125]

Since I installed Rel 1.8.8-2 and WBPP 1.4.2 I have gotten 3ea KERNEL_DATA_INPAGE_ERRORs Blue Screen of Deaths running WBPP 1.4.2.  I have also gotten 1ea SEGMENTATION_FAULT Blue Screen of Death.  This always happen when memory utilization is maxed out - 16Gbytes.

- Win 7 Pro SP1 w/ all Microsoft Updates and Patches.
- Lenovo E440 Intel Core i7 8 cores
- 16Gbytes Main Memory
- 1TByte SSD
- 512GBytes M.2

I have run extensive main memory tests and stress tested the SSD and M.2 drives.  I swapped out the M.2 drive along with swapping out the SSD with a HDD and still get these errors.  PI is configured to use the M.2 drive for swap and Local Temp space for swap.  I see no swap files in these locations...

WBPP is running the following Canon 6D RAW subs
- 150 BIAS Subs (Full Auto Integration)
- 30 Dark Subs (Full Auto Integration)
- 50 Flat Subs (Full Auto Integration)
- 80 Light Subs (Full Auto Integration) + (Registration Distortion Correction) + (Full Subframe Weighting)

Blue Screens are always towards the end of the WBPP run and always during full memory utilization.  I am not sure where. 'Registered' subs have been created along with Drizzle subs.

What's causing these problems?  Why don't I see swap files?

EDIT - I will try installing PI on a Linux PC with more memory.  It could be another app that's Blue Screening.  I have OutLook, Chrome and McAfee running.  I will try to look at the MiniDump.  UPDATE - MiniDump is empty.

[Juan Conejero]

- A BSOD is always caused by a hardware problem. PixInsight is not causing this problem, although it certainly can stress a machine to the point that a normally hidden hardware problem can become evident.

- ImageIntegration uses most of the available memory with the default parameters used by WBPP. You can be putting your machine through excessive pressure with this task, especially if you are running other applications along with PixInsight. Try disabling integration in WBPP (integration should _never_ be done with WBPP anyway).

- The WBPP script does not cause generation of swap files because it does not generate processing histories, that is, processes that can be undone/redone.

- Windows 7 is not supported.

[jwaters125]

I don't understand this comment..

"Try disabling integration in WBPP (integration should _never_ be done with WBPP anyway)."  Are you saying we should only do Calibration?

I am confident I don't have a HW issue.  I will try upgrading to Win 10.

[pfile]

yes that is what he means...

you can control the memory usage of ImageIntegration by messing with the Buffer Size and Stack Size.

it sounds to me like when your system is under extreme memory pressure eventually something gets paged back in to memory that's been corrupted by the disk. so if you try to avoid thrashing the memory system so hard maybe it will not crash.

its been a while since i've used Prime95 but you might be able to configure it to use more memory than you have and thus trigger the problem.

rob

[jwaters125]

How do you do this within WBPP?

"you can control the memory usage of ImageIntegration by messing with the Buffer Size and Stack Size."

------

If WBPP hits the memory so hard perhaps a warning message needs to be displayed if you do full sub-frame weighting on a very large number of big subs. 

Does Linux get around these issues?

[pfile]

well that is what juan is trying to say - don't integrate with WBPP because not all the controls are exposed to the user; case in point - the memory buffer sizes, etc.

so to my knowledge you can't tweak those knobs from within WBPP. you need to load the c_r / c_d_r files WBPP produced into ImageIntegration and then read the tooltip for the buffer size/stack size and set accordingly, and see what happens. i assume you need to change the weighting mode to FITS keyword and use the keyword that WPBB writes into the header.

rob

[jwaters125]

So if Juan is saying "integration should _never_ be done with WBPP anyway" and we should just "Calibrate" that defeats the purpose of WBPP because Subframe Weighting is disabled.  As I understand it...

These specific ImageIntegration setting need to be made available.  Also; some 'Warning Message' needs to be generated / displayed on low 16GBytes memory PC's or for users that are processing a large number of subs and/or sub size.

My other PC only has 16GBytes of memory  too.  I thought it had more.  For now I will be grading my Light Subs with the SubFrameSelector and using the old BPP script.  For the number of Light Subs I process its not worth the trouble of using WBPP.

[pfile]

no, it does not defeat the purpose of WBPP. see screenshots - bottom line is that along the way WBPP is going to write the WBPPWGHT keyword to the registered files if you tick the box highlighted in the screenshot. so in ImageIntegration, you load your registered frames, and set ImageIntegration to weight by the FITS keyword WBPPWGHT.

rob

[jwaters125]

I think understand now.  Thanks for taking the time to explain it to me Rob.

[pfile]

no problem!

[jwaters125]

pfile - Quick question about the FITS Keyword WBPPWGHT.  If I am processing Canon CR2 images does the keyword change?  Thx

[pfile]

do you mean does the keyword's name change from WBPPWGHT to something else?

i don't know but i wouldn't expect it to. i havent yet used WBPP for any project, plus i don't use a DSLR anymore...

rob