1.8.9.2 build 1605 repeatedly crashes on M1Max
- Thread starter andyc67
- Start date
Not at all. 1605 works perfectly on the MacBook Pro M1 Max / 64 GB where I am writing this.
Ok great thanks for checking. I wonder why it crashes on my computer, it's essentially identical to the one you are using. I am running WBPP off of an external hard drive where I keep my data, I wonder if that has anything to do with it. Is there a log that I can refer to when I have a crash?
Marcelofig
Well-known member
I use WBPP all the time on my Mac mini M1 using an external drive without any problems.
Does this happen all the time with any set of frames or just a specific one and how many are they, which camera are they from? If you're trying to process 5000 fullframe frames at once, maybe it's too much for the MB, even with 64GB of RAM.
Does this happen all the time with any set of frames or just a specific one and how many are they, which camera are they from? If you're trying to process 5000 fullframe frames at once, maybe it's too much for the MB, even with 64GB of RAM.
I was processing 87 light frames with the ASI 6200 mono plus 45 flat frames. At the third try WBPP went through without issues.
This is the first time that this happens. I think that without a log it will be impossible to determine what caused the crash.
I also have the ASI461 and I have never had a crash processing the same amount of frames, or even more, with that camera but that was with a previous build.
This is the first time that this happens. I think that without a log it will be impossible to determine what caused the crash.
I also have the ASI461 and I have never had a crash processing the same amount of frames, or even more, with that camera but that was with a previous build.
I was just going to post - I just upgraded my computer (Windows) and now WBPP crashes right before registration
cloudbait
Well-known member
What does "upgraded my computer" mean? What does "WBPP crashes" mean?
WBPP starts out fine - it gets up to Local Normalization (or when I didn't check that, registration) and all of a sudden that window closes and the entire PI shuts down. Like super fast.
Upgraded my computer: Kept the hard drives and updated graphics card, then new motherboard, Intel processer (I listed on the other post) 128 of RAM from 64, etc... - my computer guy did it - I'm not a computer person so let me know what other info would be helpful
Upgraded my computer: Kept the hard drives and updated graphics card, then new motherboard, Intel processer (I listed on the other post) 128 of RAM from 64, etc... - my computer guy did it - I'm not a computer person so let me know what other info would be helpful
cloudbait
Well-known member
Oh, and make sure that the motherboard doesn't have overclocking enabled. Seems to be a trend these days with some new motherboards to have that as a default, and there are numerous reports of it crashing PI due to overheating.
here are the notes from the error:
Faulting application name: PixInsight.exe, version: 1.8.9.2, time stamp: 0x65fb42b4
Faulting module name: ImageRegistration-pxm.dll, version: 0.0.0.0, time stamp: 0x65fb2602
Exception code: 0xc0000005
Fault offset: 0x000000000000573c
Faulting process id: 0x0xFC0
Faulting application start time: 0x0x1DA7FAE40A643CB
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\Program Files\PixInsight\bin\ImageRegistration-pxm.dll
Report Id: 99a61db7-1038-4482-b50c-33a9cc0cda22
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: PixInsight.exe, version: 1.8.9.2, time stamp: 0x65fb42b4
Faulting module name: ImageRegistration-pxm.dll, version: 0.0.0.0, time stamp: 0x65fb2602
Exception code: 0xc0000005
Fault offset: 0x000000000000573c
Faulting process id: 0x0xFC0
Faulting application start time: 0x0x1DA7FAE40A643CB
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\Program Files\PixInsight\bin\ImageRegistration-pxm.dll
Report Id: 99a61db7-1038-4482-b50c-33a9cc0cda22
Faulting package full name:
Faulting package-relative application ID:
cloudbait
Well-known member
You could try taking the files from your 'cosmetized' folder, which should be the ones that WBPP feeds to StarAlignment, and run them manually through that process and see if it fails. If it does, see if it's related to just one problematic image by reducing and selecting the images you use.
cloudbait
Well-known member
AWCC is a Dell service for managing Alienware boxes. From the description of your system, it makes no sense that it's even present. Did you do a clean install of Windows 11 after your hardware upgrades?
yea, my computer guy may have used an Alienware mouse while he was doing the rebuild -- he just deleted that program (uninstalled). that was a different error. As for Windows, he said "we moved the SSD to the new system and updated drivers" if that answers the "new install" question?
that is beyond my knowledge base but I'm going to try another object (Bodes) to see
cloudbait
Well-known member
I would say that there's a high probability that simply moving an old Windows installation to a system with as many changes as you made, especially the motherboard, and simply updating drivers, would result in a low quality, low reliability installation. That may or may not be your problem, but I wouldn't trust a system that had been upgraded in that fashion.
cloudbait
Well-known member
What file path error? I don't see that in the above information.
is t his it? i'm not a computer person:
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\Program Files\PixInsight\bin\ImageRegistration-pxm.dll