Help! WBPP now crashes before registration after computer upgrade

M

mhb1989

Well-known member
I just did a major computer upgrade (128 Ram/I9 14900K processor - other details I will paste below) and though PI runs fine, WBPP (even after I did a full system reset - twice) keep crashing. It makes it right up to Registration and then the entire program closes so I don't think I can get a log? I can't see an error message or anything. the computer does not shut down - PI just closes very quickly. After the first factory reset, I was able to do a small stack of M13, but the Soul Nebula crashes it every time and it's only 6 hours of data so not that much. It's worked flawlessly until the computer upgrade (and the PI update - not sure what the problem is).
Any suggestions? I'll paste my computer specs below - any settings to change? Any way to access a log?
1711480151593.png
 
mhb1989 said:
I just did a major computer upgrade (128 Ram/I9 14900K processor - other details I will paste below) and though PI runs fine, WBPP (even after I did a full system reset - twice) keep crashing. It makes it right up to Registration and then the entire program closes so I don't think I can get a log? I can't see an error message or anything. the computer does not shut down - PI just closes very quickly. After the first factory reset, I was able to do a small stack of M13, but the Soul Nebula crashes it every time and it's only 6 hours of data so not that much. It's worked flawlessly until the computer upgrade (and the PI update - not sure what the problem is).
Any suggestions? I'll paste my computer specs below - any settings to change? Any way to access a log?
View attachment 22549
Click to expand...
I'd try cutting back on the amount of data. Does it crash if you use master frames for your calibration? If so, can you keep reducing the number of lights until it stops crashing? The idea here being to identify whether it's some kind of resource problem, or something odd with the data itself that's causing the issue. Of course, if you still get the crash with just a small number of files, you could upload them and we could try them on different systems.

And even if the PI WBPP log doesn't show the problem (but I'd check), it's possible that something will show in the Windows System or Application logs, which often record abnormal program termination.
 
cloudbait said:
I'd try cutting back on the amount of data. Does it crash if you use master frames for your calibration? If so, can you keep reducing the number of lights until it stops crashing? The idea here being to identify whether it's some kind of resource problem, or something odd with the data itself that's causing the issue. Of course, if you still get the crash with just a small number of files, you could upload them and we could try them on different systems.

And even if the PI WBPP log doesn't show the problem (but I'd check), it's possible that something will show in the Windows System or Application logs, which often record abnormal program termination.
Click to expand...
I did get it (after a factory reset) to do a 3 hour stack of M13. The one that keeps crashing is the Soul NEbula data - 3 hours with HA03, 3 hours with S2HB. it's okay to load all the lights together isn't it if they are labelled? I tried the same data in APP and it stacked just fine (and in like 8 minutes) -so it's not that much data. I also tried to take out Local normalization so it got right up to registration and then shut down. Is there a setting that could cause this? I literally optimized my computer by doubling the ram, getting a bigger graphics processor and new Intel Core - so I'm bummed that the one thing I need it to do as far as stacking isn't working. Plus, I've never had a PI issue with WBPP and I read that another gentleman had the same issue. IT just closes the entire program.
 
mhb1989 said:
I did get it (after a factory reset) to do a 3 hour stack of M13. The one that keeps crashing is the Soul NEbula data - 3 hours with HA03, 3 hours with S2HB. it's okay to load all the lights together isn't it if they are labelled? I tried the same data in APP and it stacked just fine (and in like 8 minutes) -so it's not that much data. I also tried to take out Local normalization so it got right up to registration and then shut down. Is there a setting that could cause this? I literally optimized my computer by doubling the ram, getting a bigger graphics processor and new Intel Core - so I'm bummed that the one thing I need it to do as far as stacking isn't working. Plus, I've never had a PI issue with WBPP and I read that another gentleman had the same issue. IT just closes the entire program.
Click to expand...
Well, try what I suggested. What happens if you use the calibration masters from a previous WBPP run and only 5 or 10 lights?
 
mhb1989 said:
it was too big so I did as a zip file
Click to expand...
Nothing jumps out, other than the abrupt ending. I'd still suggest doing a much reduced run, with masters and just a handful of lights from a single filter. If that crashes, it will be a lot easier to wade through the log and to share the files to see if others have the same issue.
 
this was from a smaller stack (and just darks and lights).
again, stopped and shut down
 

Attachments

  • 20240327020335.zip
    92.1 KB · Views: 13
mhb1989 said:
this was from a smaller stack (and just darks and lights).
again, stopped and shut down
Click to expand...
There are still 128 lights there! Can you do it with only your MASTER calibration frames (so no bias, dark, or flat subs at all) and just 10 lights?

Also, is T: an external drive?
 
T is my internal hard drive (not the main c drive but a dedicated one for astrophotos) - I think it's 4 TB. I will try a smaller one today with 10 lights and let you know. also planning a clean install on Friday so it may take me a few days to respond back but THANK YOU so much as I need to resolve this as the main reason I upgraded was for PI and stacking!!
 
Okay, I tried to stack 10 light frames of Bodes (which I had previously stacked in January) with NO other frames. It shut down the program and then crashed the whole computer - here is the log file - thank you!
 

Attachments

  • newlog.zip
    13.9 KB · Views: 16
mhb1989 said:
Okay, I tried to stack 10 light frames of Bodes (which I had previously stacked in January) with NO other frames. It shut down the program and then crashed the whole computer - here is the log file - thank you!
Click to expand...
That log shows that it made it through registration, unlike the previous logs. Does the system log show a different process causing the crash?
 
The previous system shutdown at 9:29:52 AM on ‎3/‎27/‎2024 was unexpected.
Dump file creation failed due to error during dump creation.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000006, 0x0000000000000000, 0xffffd681c037c180, 0x0000000000000008). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
 
interesting - I tried stacking 10 light frames RIGHT FROM THE USB drive instead of the 4TB drive (and saving to the 4TB drive) and that stack went through!
 
mhb1989 said:
interesting - I tried stacking 10 light frames RIGHT FROM THE USB drive instead of the 4TB drive (and saving to the 4TB drive) and that stack went through!
Click to expand...
Your issues do seem to point to a hardware or maybe driver problem of some kind.
 
we ran a full test of the 4TB drive and it came out with no problems. Then, I tried to stack 30 lights from my SSD drive and once again, it shut down PI. So now I can't say that it works from the SSD either. Whether I stack from the SSD or the 4TB drive, it crashes - here is the log from this last test. Thanks so much for looking.
 

Attachments

  • newtest.zip
    23.1 KB · Views: 14
mhb1989 said:
we ran a full test of the 4TB drive and it came out with no problems. Then, I tried to stack 30 lights from my SSD drive and once again, it shut down PI. So now I can't say that it works from the SSD either. Whether I stack from the SSD or the 4TB drive, it crashes - here is the log from this last test. Thanks so much for looking.
Click to expand...
My guess is that you have a damaged operating system because of the way that your upgrade was performed, and the fix is to do a clean install of W11 and then a clean install of PI (and any other apps you use).
 
Well, you still use T:\
Loading the files from D:\, I assume this is your SSD but then suddenly the cache files go to T:\

Code: 
[2024-03-28 03:40:19] Cache saved with key D:/ASIAIR/Autorun/Light/Ngc7822/Light_Ngc7822_300.0s_Bin1_2600MC_Trgb_gain100_20240221-193204_-19.6C_0001.fit
[2024-03-28 03:40:19] [cache] - set LMD [15d1886230b0c0a9c0804fd89556846a4a8cab6a] Light_Ngc7822_300.0s_Bin1_2600MC_Trgb_gain100_20240221-193204_-19.6C_0001_d.xisf: 2024-03-28T03:39:47.000Z
[2024-03-28 03:40:19] Cache saved with key LMD_15d1886230b0c0a9c0804fd89556846a4a8cab6aT:/AstroPics/BodesJan21/test pixstack/debayered/Light_BIN-1_6248x4176_EXPOSURE-300.00s_FILTER-Trgb_CFA/Light_Ngc7822_300.0s_Bin1_2600MC_Trgb_gain100_20240221-193204_-19.6C_0001_d.xisf
[2024-03-28 03:40:19] Cache saved with key T:/AstroPics/BodesJan21/test pixstack/debayered/Light_BIN-1_6248x4176_EXPOSURE-300.00s_FILTER-Trgb_CFA/Light_Ngc7822_300.0s_Bin1_2600MC_Trgb_gain100_20240221-193204_-19.6C_0001_d.xisf
Something is wrong.
You may should make a clean installation of Windows 11.

Did you delete the Cache file in WBPP or better reset WBPP?

And I asked before to provide the filesize of the files in %AppData%\Pleiades.


Cheers
Tom
 
tom886 said:
Well, you still use T:\
Loading the files from D:\, I assume this is your SSD but then suddenly the cache files go to T:\

Code: 
[2024-03-28 03:40:19] Cache saved with key D:/ASIAIR/Autorun/Light/Ngc7822/Light_Ngc7822_300.0s_Bin1_2600MC_Trgb_gain100_20240221-193204_-19.6C_0001.fit
[2024-03-28 03:40:19] [cache] - set LMD [15d1886230b0c0a9c0804fd89556846a4a8cab6a] Light_Ngc7822_300.0s_Bin1_2600MC_Trgb_gain100_20240221-193204_-19.6C_0001_d.xisf: 2024-03-28T03:39:47.000Z
[2024-03-28 03:40:19] Cache saved with key LMD_15d1886230b0c0a9c0804fd89556846a4a8cab6aT:/AstroPics/BodesJan21/test pixstack/debayered/Light_BIN-1_6248x4176_EXPOSURE-300.00s_FILTER-Trgb_CFA/Light_Ngc7822_300.0s_Bin1_2600MC_Trgb_gain100_20240221-193204_-19.6C_0001_d.xisf
[2024-03-28 03:40:19] Cache saved with key T:/AstroPics/BodesJan21/test pixstack/debayered/Light_BIN-1_6248x4176_EXPOSURE-300.00s_FILTER-Trgb_CFA/Light_Ngc7822_300.0s_Bin1_2600MC_Trgb_gain100_20240221-193204_-19.6C_0001_d.xisf
Something is wrong.
You may should make a clean installation of Windows 11.

Did you delete the Cache file in WBPP or better reset WBPP?

And I asked before to provide the filesize of the files in %AppData%\Pleiades.


Cheers
Tom
Click to expand...
yes, I both purged the cache each time and did "factory reset" for WBPP. Can you give me "idiot" directions for this: nd I asked before to provide the filesize of the files in %AppData%\Pleiades - I have no idea what that means - sorry. I'm not very adept at computers. My computer tech guy is going to run some tests today on the windows system and failing that, we will do a clean install of windows tomorrow....
 
mhb1989 said:
Can you give me "idiot" directions for this: nd I asked before to provide the filesize of the files in %AppData%\Pleiades - I have no idea what that means - sorry.
Click to expand...
You are not the only one who might have problems with this. I'll talk it through on Windows 10 Pro; hopefully, Windows 11 won't be too different!
PixInsight stores its files in two places. All the application installation files are stored on the Windows system disc (usually C: ) in a set of folders on the path "C:\Program Files\PixInsight".

Quite separately, the licence file, the saved settings file and some application cache files are stored, also on the system disc, in the "user" space of the current user, at a path of the form "C:\Users\<username>\AppData\Roaming\Pleiades", where <username> is your username. The string "%AppData%" is the name of a Windows environment variable that contains the current user application data path ("C:\Users\<username>\AppData\Roaming"); it is recognised as part of a file path name in Windows file explorer (so it can save you typing the full name). It can also save you from the problem that Windows usually hides the AppData folder by default. You can avoid this by checking "Hidden items" in the file explorer "View" tab "Show/hide" settings; I would also recommend that you check "File name extension", so all extensions are displayed.
1711634685845.png

If you enter either the full path or the %AppData%\Pleiades path into your Windows file explorer, you should find a set of files something like:
1711635025843.png

The sizes in the "Size" column are what @cloudbait is asking for.
 
You must log in or register to reply here.
Back
Top