PixInsight Forum (historical)
PixInsight => General => Topic started by: wisetrout on 2018 December 17 22:14:25
-
During the past two years I never experienced a PI crash. Release 1.8.6 is not stable on my computer. I have uninstalled and reinstalled twice. Is anybody else having difficulties?
-
not on OSX - you'll have to provide more details. windows? linux?
is there any crashdump information available?
rob
-
I am running Windows 8.1. I get a message window from "Windows" stating there has been an error, and the program must close. No other information. The program runs for about 15 to 30 minutes then the error occurs. It happens every time I run the program. In two years of using the earlier version, I never had it happen.
Thanks for your help.
-
you might need to look in the error reporter and see if there's any info about the crash:
https://www.cyberlink.com/support/faq-content.do?id=10449
without this info juan can't do anything. since there are not an avalanche of people posting here with similar problems, it may be something specific to your system.
rob
-
I have similar problems on Windows 10. Never had with 1.8.5.
Always the same memory access violation errors with subsequent application crash.
These during an Image Integration processing:
(http://i66.tinypic.com/2nalevn.png)
-
I cannot reproduce these problems on any platform. What memory access violations? What hardware? Any repeatable pattern? A reduced data set where I can reproduce the issue?
-
Just modified my post with some images.
-
This cannot be reproduced on any of our working and testing machines.
On Windows, these exceptions can be caused sometimes as a result of severe exhaustion of RAM resources; for example if you are trying to integrate a huge set of images that cannot be loaded incrementally (for example, digital camera raw images) and you don't have enough memory to load them at once.
Another possible cause is a defective OpenGL implementation, but if you have been using version 1.8.5 before this is unlikely.
Anyway, can you please upload a data set where this can be reproduced? If you can use something like Dropbox to upload a project, that would be of great help.
-
I'm also noticing that 1.8.6 is unstable as compared to previous versions. I am seeing 3 specific behaviors that I've never seen before installing the current version.
For reference, I am running Windows 10 version 1709, build 16299.611, with a Surface Book with Core-i7 processor and 16GB of RAM. Here are the things that I'm seeing:
1) When I am using a process with a real-time preview window, sometimes the preview window does not close the first time I click on the 'X' in the corner of the window. It always closes on the second click. This is a small thing and it doesn't happen all the time, but I've seen it enough times that it's noticeable.
2) Sometimes when I select a process that's not open yet, I get the following error dialog with the text. I have seen it on multiple processes and if I exit and restart PI, then it works normally:
CreateSpinBox(): Low-Level API Function
error (0x0001): Unknown error
3) Twice now, I've had version 1.8.6 go unresponsive while running a process or script. According to the resource monitor, when this happens the CPU goes to maximum clock speed and the pixinsight.exe process consumes 100% CPU for about 5 seconds and then goes idle for about 5 seconds, repeatedly. I've seen this happen when running the PSFImage script from www.skypixels.at. I initially attributed it to the script, but I've also seen it happen with TGVDenoise and MultiscaleMedianTransform. Once when I saw it, I left the computer for two hours and it never returned to a responsive state. Clicking on the Abort button in the Process Console for the two built-in processes did not return the PI to a responsive state. In all cases, terminating the pixinsight.exe process and then restarting it returned things to normal (with the loss of any unsaved work). In the new PixInsight instance, all of the processes ran as expected.
In addition to CPU, I've monitored memory consumption. The pixinsight.exe process was consuming about 1.5GB of RAM in the cases where the CPU spun, and total memory usage on the machine never exceeded 65% of the total available.
Unfortunately, I cannot reproduce any of the above behaviors and have not found any pattern to them. I've taken to doing frequent saves of my project to avoid losing too much work. Again, this is all on a machine that has been rock solid stable on previous PI versions.
If there is something I can do to collect more information, please let me know.
Thanks,
-Wade
-
Warren, from the beta tester team reporting in. I've had no problems with my desktop and Windows 10. When I get home tomorrow from my PixInsight teaching trip, I will install 1.8.6 on my Windows 10 laptop and report back in.
-
is todays release with the QT dll included intended to fix this problem?
rob
-
Warren, from the beta tester team reporting in. I've had no problems with my desktop and Windows 10. When I get home tomorrow from my PixInsight teaching trip, I will install 1.8.6 on my Windows 10 laptop and report back in.
Likewise, the beta versions and the final release have been stable for me on a desktop system (AMD Threadripper, Windows 10 Home) and a laptop (Dell XPS15, Windows 10 Pro.)
Cheers,
Rick.
-
This cannot be reproduced on any of our working and testing machines.
On Windows, these exceptions can be caused sometimes as a result of severe exhaustion of RAM resources; for example if you are trying to integrate a huge set of images that cannot be loaded incrementally (for example, digital camera raw images) and you don't have enough memory to load them at once.
Another possible cause is a defective OpenGL implementation, but if you have been using version 1.8.5 before this is unlikely.
Anyway, can you please upload a data set where this can be reproduced? If you can use something like Dropbox to upload a project, that would be of great help.
I'm doing further tests. Now crashed on applying a crop process in a image container of 20 images not 200 ...
I'm gonna to send you project file if further tests go wrong.
-
As promised, I have installed the very latest .1448 on my Windows 10 ASUS laptop and ran a quick BPP LRGB run w/ CosmeticCorrection with no issues at all. The only thing I saw was a red checksum error in the Process Console when I tried to open an instance of BPP from a new instance icon that had been saved in 1.8.5. 1.8.6.1448 working well in Windows 10 on a desktop and a laptop.
-
Hi Warren,
Thank you so much for your report. The checksum mismatch error is normal if you are executing BPP (or any other script for that matter) from an icon previously saved with version 1.8.5. The checksums don't match because we have modified the script in this version. As you know, you can run the icon after deleting the MD5 checksum manually on the Script tool.
By the way, users sometimes ask why this happens when we change a script. I'll take advantage of this opportunity to answer. This happens because scripts are intrinsically dangerous in PixInsight. A script can be altered very easily, since its entire source code is necessarily available when it is going to be executed. A malicious modification made to one of the scripts distributed with PixInsight would easily pass unnoticed, but could do extremely harmful things, considering the power available in our JavaScript runtime.
By associating a cryptographic checksum (MD5 in this case) to each executed instance of a script, we can ensure that the icon you are going to launch will run exactly the same source code that was executed previously, when you saved the icon. This rules out the possibility of a malicious modification applied to a process icon, and/or to the associated script, which would lead you to run altered code without your knowledge. When you delete the MD5 checksum on the Script tool, you are assuming the entire responsibility for what happens next :)
In a future version of the core application, I plan on implementing a secure system for authentication of scripts. This will include the necessity to sign scripts with a developer's certificate, just as we do now with standard PixInsight modules.
-
Hello!
I am running a Win10 64-bit, Intel i7 6700K, 64Gb RAM, GTX-1080-6GB, Samsung evo 960 SSD with a 256Gb pagefile. I have been running PixInsight 1.8.5 with no issues whatsoever apart occasional crash (once or twice in one year).
I am very sorry to say but I am encountering many issues with build 1448.
I am still using old subframeselector script and it crashes very often with the same error.
There are two types of crashes, one were PI just closes and one with the same message as others:
PCL Win32 System Exception
At address 00007FFF63495470 with exception code C0000005:
Access violation: invalid memory read operation at address 0000000000000008
Also after some time it seems all js files fail to run. Typical errors are like:
*** Error [000]: C:/Program Files/PixInsight/include/pjsr/NumericControl.jsh, line 153: Error: At address 00007FFAFD1A5470 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008
I have uninstalled and reinstalled both pixinsight and my nvidia drivers (including clean install) and it didn't help.
I have tried running PI with QT rendering in both software and rasterized, unfortunately with no success. So I reverted back to opengl.
I noticed subframeselector started working good again after I freed some space on my ssd (had 100gb free and freed an additional 300gb). But it only worked for a day or two. When I reached 250gb free space issues occurred again. I freed another 150gb but it still fails.
PI temp folder is currently 135Gb, which seems a bit higher than running 1.8.5.
I have also often encountered the following issue: If I switch to anther window and let PI sit for a few minutes in the background doing nothing it very often crashes when switching back to it.
After using PI for sometime it slows down at some point. I especially notice it in DrizzleIntegration as it slows down by a factor of ~50 but I believe it is generalized. Also when this happens my process icons starts flickering. Most of the time restarting PI is sufficient to fix, but sometimes a reboot is required.
When a reboot is required I notice GUI refresh is very slow upon reopening.
Build 1457 crashes far more often for me, and no matter what I am doing, it is very painful as when it starts failing I cannot save my progress.
Message is now only printed in console (At address 00007FFF63495470 with exception code C0000005) rather than a message box. But the issue iust that after a minute or two PI becomes unresponsive and crashes.
I will conduct more testing on build 1457, I am sorry if I am reporting fixed issues.
Those issues seems quite random and I haven't been able to reproduce on demand. Though switching between windows and desktops while PI is processing seems to make it worse. And as being a developer myself I know this is the worst situation because you cannot reproduce and while you cant reproduce you cant fix...
My personal feeling (because of the flickering, the free space and the js script crashing when trying to set GUI field) is that it might have something to do with QT/GUI and the hard disk access. But its only a gut feeling, I got no strong evidence for that ;-)
Let me know if I can provide anything, I will be glad to help!
I still noticed a very good overhall perfomance improvement and I believe it is an excellent release. Looking forward for a new build :-)
-
Hello,
So after more thorough testing, as promised, here are my results:
1 - Subframe selector script crashes as often as for build 1448, however errors are now only printed to the console and not in a modal interrupting message box. I have this issue no matter the files I use (even ones that worked fine either with v1.8.5 or v1.8.6).
Sometimes it happens after 3 files have been measured, sometimes after hundreds. Sometimes it is only a single file, sometimes it is a bunch of them in a row or close to each other. I fail to find any pattern other than the more files you add to the list the more probable it will occur.
I am convinced it is not linked to the data, as sometimes a particular file will work sometimes it won't, but if you wish let me know and I'll be happy to provide you my files.
My tests were conducted prior the module update I noticed today. But as I am using the script I believe my tests should still be valid, unless there are any dependencies with the module. Please let me know, and I will re-conduct tests if needed.
2 - About general use it seems crashes happen especially when I use Star mask module several times (on a small image, details attached).
I have a difficult picture with nebulosity that gets picked up and I am doing trial and error with star mask parameters. So I end up generating a lot of new views (I close them as I generate new ones tho).
After sometime it systematically crashes on my setup with the same error I reported in my previous post (after maybe 20 or 30 star masks have been generated).
I notice it crashes when I try to move new star mask window and it doesn't (instead error is printed in console). If I try closing it, each time I try the same error gets printed on the console after about 10 tries PI shuts down non gracefully.
I found a workaround for this! I believe this might help you pinpoint the exact issue, and help others experiencing the issue...
Interestingly, if instead of left click, I right click on the close button it works. The faulty view is closed with no errors and I can resume work without having to restart PI.
3 - For the performance sudden drop, It is still present but I have measured it a bit more precisely. I would say the slow down factor is closer to 25 times rather than 50.
With build 1457 restarting PI is not sufficient as a workaround but a reboot works all the time.
4 - The bug about opening PI and letting it sit in the background leading to a crash has never occurred on build 1457.
I also wanted to share more information about my system/usage of PI:
A - In PI I make use of 3 workspaces and have tens of process icons on each of them.
Upon opening a project with only process icons and no images, each process dialog appears and disappears. Looking like flickering and is slow to open even-though I have it set on workspace 4 containing no process icons.
This might be normal or already happening in v1.8.5, sorry I don't remember. But I didn't want to discard any information that might help you.
B - In my last post I didn't precise that my SSD is an M.2 2TB drive.
It is partioned in two disks, one containing OS, and one PI data, temp folder and pagefile.
Maybe somehow it could have an impact.
C - I also forgot to precise that all my drives have been trimmed, error checked and have windows indexing disabled.
D - PI swap storage folder is not a system temporary folder.
E - My motherboard is an ASUS Z170 PRO GAMING with latest BIOS installed.
Please kindly let me know if I can provide further help.
Looking forward for your response.
Cheers.
-
Hi,
I am very sorry to know that PixInsight 1.8.6 is performing so badly for you. However, none of the issues you are reporting can be reproduced under normal working conditions on a variety of Linux distributions and desktops, macOS 10.11, 10.12 and 10.14, and Windows 10. In all of our tests, which include severe stress tests with many gigabytes of data, version 1.8.6.1457 is stable under normal working conditions on all supported platforms.
Unfortunately, If I can't reproduce a nontrivial problem, I am unable to understand and fix it. The kind of issues you are reporting are most likely being caused by hardware-specific conditions, faulty device drivers, wrong operating system components, or conflicts with installed software utilities running as background processes. Windows is intrinsically a problematic platform, mainly because of bad design principles, the vast variety of uncontrolled interactions between software and hardware components, the proliferation of malware and bloatware, and also, unfortunately, because of problematic and even buggy system updates.
Assuming the obvious fact that you want to continue using Windows, my only recommendation in such a situation is a complete, clean reinstall of Windows 10. Please don't install a vendor provided copy of Windows, but an original copy downloaded directly from Microsoft servers. Make sure you install up-to-date device drivers. Do not install any bloatware. Perform a minimal software configuration that you always should keep as pure as possible. This is more or less what we call normal working conditions.
Sorry for not having more constructive advice to offer.
-
Palmito, you're not alone on this. I too have been running into memory issues on 1.8.6 that were not present with 1.8.5. Same type of error messages that you posted. I'm using a high-end Windows 10 Pro system also. Notably the issues occur when I end up using a process like PCC, StarMask or repeated process instances to a preview. This may not be considered normal operation as I'm trying to perfect the usage of some of these processes and will repeat iterations for over thirty minutes or more. At some point (and not repeatable) PI will report the crash error. As there seems to be no apparent fix as this is difficult to pinpoint, my only workaround is to save the PI project often so I can recover after I shutdown the PI project instance that's failing. This is not a show-stopper for me as I really enjoy the product but just an added nuisance. Maybe it will work itself out with future updates.
-
I too get repeated crashes on W7 with 01.08.06.1457 after never seeing them on previous releases. My crashes always occur when I go to expand an options box and this can happen immediately after starting PixInsight. I most often see it with Image Integration when I expand Pixel Rejection (1). But if I change Scale Estimater from the default of "Iterative k-sigma..." to "Average absolute deviation..." then it does not happen. Then if I change it back to "Iterative k-sigma..." it's still okay to open and close the Pixel Rejection(1). The details are:
Problem Event Name: APPCRASH
Application Name: PixInsight.exe
Application Version: 1.8.6.1457
Application Timestamp: 5c472890
Fault Module Name: StackHash_34cf
Fault Module Version: 6.1.7601.24358
Fault Module Timestamp: 5c5e1dff
Exception Code: c0000374
Exception Offset: 00000000000bf302
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 34cf
Additional Information 2: 34cf7b3675121a09fd72c5e6172c6f07
Additional Information 3: 9e0c
Additional Information 4: 9e0c6839d118692b0cb17798b34a9e74
Also the same crash happens with Pixmath when I expand the Destination options. The details are:
Problem Event Name: APPCRASH
Application Name: PixInsight.exe
Application Version: 1.8.6.1457
Application Timestamp: 5c472890
Fault Module Name: StackHash_ce1e
Fault Module Version: 6.1.7601.24358
Fault Module Timestamp: 5c5e1dff
Exception Code: c0000374
Exception Offset: 00000000000bf302
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: ce1e
Additional Information 2: ce1e0dbc49f315cc4a1a3875da369dd0
Additional Information 3: 2bb2
Additional Information 4: 2bb2b08292fcfa513ad09e3b24ef60e3
I'm running with W7 on a i7 6700 CPU with 16GB memory. It's a Shuttle DH110 computer.
-
I will also add that these crashes occur when running PI as the first process immediately after a clean reboot.
-
And in addition, Windows Memory Diagnostic shows no errors and I can successfully run image integrations and drizzle integrations of up to 660 images without issue if I work around these option window expansion issues.
-
Just wanted to chime in and say I too have issues where the longer PI is open and the more I work in it, it continuously slows down.
This is particularly evident with the flashing process windows as noted above, something I've never had happen until the update. I thought it was some weird one off thing but it has been progressively getting on my nerves having to constantly restart PI or my computer to bring PI back to life. Figured I would google it, and sure enough, others were having this issue.
Weird. I would add more to this topic, but I feel as though it's already been explained in greater detail by others. Just wanted to chime in and say it IS an issue.
Connor
-
This cannot be reproduced on any of our working and testing machines.
On Windows, these exceptions can be caused sometimes as a result of severe exhaustion of RAM resources; for example if you are trying to integrate a huge set of images that cannot be loaded incrementally (for example, digital camera raw images) and you don't have enough memory to load them at once.
Another possible cause is a defective OpenGL implementation, but if you have been using version 1.8.5 before this is unlikely.
Anyway, can you please upload a data set where this can be reproduced? If you can use something like Dropbox to upload a project, that would be of great help.
Juan,
with respect ... I would like to help... but simply blaming these issues on windows 10, drivers or memory are not going to help
both my machines have far more ram than needed and my server in fact as 512GB of ram so its not the issue
both machines are opengl 4.5 and all up to date ... all have the latest drivers for their cards and until 1.8.8 NEVER had an issue with pix
Now you have multiple people reporting the same memory errors across a variety of PC's - the common issue ... 1.8.6 and beyond upgrades
I have also suffered locked and crashed pixinsight during processing apart from image integration in the latest weeks
there is no pattern - its happened during WBPP at differing times/steps .. it leaves no trace in the log but windows throws the memory error
my server can handle anything pix can ever offer it ... dual cpu 48 core 3ghz xeon and 512GB ram so its not related to loading of images into memory and running out ...
this is something that went in with 1.8.8 - where these memory errors started - last crash for me was star aligning in WBPPP - previous crashed at debayer ... other times its at actually writing a file
no pattern - only root cause 1.8.8 - I know its clearly not everyone ... and prob an edge case but theres enough it now makes 1.8.8 unusuable for me so much I have now reverted on machine back to 1.8.5
and its not just on here there are issues - people on the pixinsight for beginners FB also report it the same memory errors
there is a problem - now how can we help find the cause it we can't find the log info - windows does not report the error and it appears in diff ways
just because your machine does not have the issue doesn't mean there isnt one - theres enough of us who do seems to now have issues since 1.8.8 to suggest something a little more than 'bad drivers'
I say that from experience as I am both an Agile Certified Practioner and software development project manager.
So .. how we can help - but i know i paid a lot of money for pix and I'd like to keep using it and helping create a better product - what can we do to help find the error???
thanks
Simon
-
Hi,
I am very sorry to know that PixInsight 1.8.6 is performing so badly for you. However, none of the issues you are reporting can be reproduced under normal working conditions on a variety of Linux distributions and desktops, macOS 10.11, 10.12 and 10.14, and Windows 10. In all of our tests, which include severe stress tests with many gigabytes of data, version 1.8.6.1457 is stable under normal working conditions on all supported platforms.
Unfortunately, If I can't reproduce a nontrivial problem, I am unable to understand and fix it. The kind of issues you are reporting are most likely being caused by hardware-specific conditions, faulty device drivers, wrong operating system components, or conflicts with installed software utilities running as background processes. Windows is intrinsically a problematic platform, mainly because of bad design principles, the vast variety of uncontrolled interactions between software and hardware components, the proliferation of malware and bloatware, and also, unfortunately, because of problematic and even buggy system updates.
Assuming the obvious fact that you want to continue using Windows, my only recommendation in such a situation is a complete, clean reinstall of Windows 10. Please don't install a vendor provided copy of Windows, but an original copy downloaded directly from Microsoft servers. Make sure you install up-to-date device drivers. Do not install any bloatware. Perform a minimal software configuration that you always should keep as pure as possible. This is more or less what we call normal working conditions.
Sorry for not having more constructive advice to offer.
today after some extensive testing I am narrowing this down
I dropped back to 1.8.7 and WBPP 1.4.0
it crashed 3 times in a row everytime at image integration
* Integrating channel 1 of 3:
Integrating pixel rows: 0 -> 2821: 36%
*** PCL Win32 System Exception: At address 00007FFBB01BA839 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000000
<* failed *>
same issue ...
now today I did capture this
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: PixInsight.exe (16320) consumed 13120978944 bytes, chrome.exe (15684) consumed 825663488 bytes, and chrome.exe (2564) consumed 794980352 bytes.
so ... is it something that is allowing pix to simply eat all the memory to a point that it simply crashed windows?
i will try again now without chrome running and only pix running
-
so I can reproduce this again again ......
WBPP - 100 x 300s lights - 50 flats 2sec 50 flat darks 2 sec and 50 darks 300s
runs all processes until it gets to integration
it then crashes out within the first few % .... eats all the memory it can and the PC crashes
same on my server eventually
it causes the whole PC to screw up and requires a reboot
now this is with 1.8.7 and WBPP 1.4.0
later in the week I will install 1.8.5 and do the same
-
I get very similar issues with the Win32 error and C00000005. In my case nearly always it is the use of scripts that causes it. Image Integration also can cause it. I also see lots of API errors in the console randomly when I click on execute. I have done extensive memory and CPU torture tests and the HW is fine. I also use this machine for Adobe CC apps such as Premiere, Photoshop and After Effects and all those work perfectly. I run python and Visual C++ IDE and they are all fine.
I never had any issues on this same machine prior to 1.8.6. Since 1.8.6 I have these issues and I no longer trust PI like I did and have to do a save project every 5 minutes or else risk losing my work.
I am persevering with PI nonetheless since it is so good when it works. But my confidence is shaken a bit.
-
in another thread juan said that he found a problem with the javascript interpreter's garbage collection algorithm (this is part of the interpreter's memory management system) which was leading to these sporadic crashes on 1.8.8-1. i don't know if the same bug is in the JS interpreter bundled in 1.8.7 or 1.8.6, but if you are having crashes running scripts on 1.8.8-1 then the update to 1.8.8-2 will probably fix the problem.
rob
-
As Rob has pointed out, we have found a complex bug that has been causing problems during script execution in version 1.8.8-1. I'll release version 1.8.8-2 later today, which fixes these problems. Note that this bug was not present in 1.8.8 and older versions.
However, the problems caused by this bug are clearly identifiable, very specific and, although with some difficulty, reproducible:
https://pixinsight.com/forum/index.php?topic=14283.0
Besides this, there are other Windows-specific issues that we cannot reproduce. Some graphics drivers on Windows are causing problems that we cannot solve because are not under our control. This mainly applies to some Intel HD graphics drivers, which provide poor OpenGL implementations incompatible with recent versions of PixInsight. Outdated versions of NVIDIA drivers can also cause problems on Windows.
-
There are two types of crashes, one were PI just closes and one with the same message as others:
PCL Win32 System Exception
At address 00007FFF63495470 with exception code C0000005:
Access violation: invalid memory read operation at address 0000000000000008
Also after some time it seems all js files fail to run. Typical errors are like:
*** Error [000]: C:/Program Files/PixInsight/include/pjsr/NumericControl.jsh, line 153: Error: At address 00007FFAFD1A5470 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008
Today we have been able to reproduce this same problem on a Dell laptop with an NVIDIA graphics card running Windows 10 Pro (see attached screenshot). The access violation error has happened during execution of a long WBPP task with 120 CFA light frames.
I am very sorry to say that we currently have no solution to this problem. The access violation does not happen in our code. We have to investigate this problem further, but it seems to be an incompatibility of recent NVIDIA graphics drivers for Windows with the versions of Qt used by PixInsight 1.8.6 and later (Qt 5.12.2, 5.12.5 and 5.13.2). Other than this problem PixInsight runs very well on the same machine. We have repeated the same procedure with no errors, so this issue seems to be sporadic and, to our knowledge, completely unpredictable.
This does not happen on other Windows 10 machines with AMD graphics cards, where the latest version 1.8.8-2 of PixInsight runs without any problems during extremely intensive tests. Of course, this does not happen with the FreeBSD, Linux and macOS versions of PixInsight.
I apologize for this problem, even if we are not directly responsible. I'll try to do my best to find a solution.
-
I have installed 1.8.8.2 and so far, good. No crashes.
-
Hi Steve,
I have installed 1.8.8.2 and so far, good. No crashes.
I am glad to read that. Please let me know if it continues working well for you. I am trying to do my best to find causes and solutions to these issues.
-
We have important news on this issue.
Yesterday I reported a verified reproduction of the problem being described here (read access violation at address 8 on Windows 10) on a Dell laptop with dual Intel HD integrated + NVIDIA discrete graphics cards.
We have solved this problem on the same machine by simply updating graphics drivers to their latest versions available for Windows 10. Now we have repeated the same WBPP task 6 times without any problems. Everything has worked perfectly and PixInsight 1.8.8-2 runs absolutely stable on this laptop. So far we have repeated many stress tests with zero problems.
Here is the procedure to update your graphics drivers on Windows 10:
- From the Start menu, select Control Panel.
- On Control Panel, select System and Security.
- Select System.
- Select Advanced System Settings (left panel)
- Select the Hardware tab.
- Click on Device Manager.
- Pull down the Display adapters item.
- Right click on the item for your graphics adapter. Select Update driver.
- Click on Search automatically for updated driver software. Windows will look for new drivers online, and if new drivers exist for your graphics card, they will be downloaded and installed.
If you have several display adapters on your machine (e.g. an integrated Intel HD graphics adapter and an NVIDIA or AMD discrete card), repeat the same procedure for each of them from Device Manager.
I hope this helps. These weird access violation errors are definitely being caused by wrong or incompatible graphics drivers on Windows. They are machine-specific issues beyond our control, but at least we have managed to solve them by updating graphics drivers on the only machine where we have been able to reproduce them.
-
Hi Juan,
I am not so sure about your conclusions here..... I have seen the same PI locks ups with the COOOOO5 Win32 issue on three different Windows 10 PC hardware machines, all with very different graphics, CPUs etc. I never see the problem on OSX. It is definitely IMO something to do with PI on Windows 10.
That said, I have not seen any issue since 1.8.8.2 update you posted.
Regards, Steve
-
Hi Steve,
I am not so sure about your conclusions here.....
Well, these conclusions are based on our own experience with several PixInsight installations on Windows 10, with different AMD, NVIDIA and Intel graphics cards. We can only speak about what we can reproduce under normal working conditions.
Glad to know 1.8.8-2 is working well for you.
-
1.8.8.2 has not caused any further issues so far on my desktop
now to update the server
-
Nope. It's at it again. All OS fixes and latest NVida Drivers 441.41.
I am going to remove, reinstall and not install any third party scripts from 3rd party repositories.
This morning, to get the below errors, all I did from PI startup was Blink and Image Integration tool, loading in 50 BIAS frames
*** PCL Win32 System Exception: At address 00007FFC70B5E320 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008
*** PCL Win32 System Exception: At address 00007FFC70B5E320 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008
*** PCL Win32 System Exception: At address 00007FFC70B5E320 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008
*** PCL Win32 System Exception: At address 00007FFC70B5E320 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008
*** PCL Win32 System Exception: At address 00007FFC70B5E320 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008