Access Violation when accessing hard drive-Win10-Dell Inspiron -PI 1.08.04.1171

[cgalavis]

Hi Juan,
Thanks for the update, I applied it but unfortunately the issue did not go away
It does seem to be related to disk access, when either the "Open" or "Load Project" dialog is brought up the application crashes, the dialog does pop-up but doesn't show any files, it shows "Working on it..." instead.

I have attached a screen shoot, not much there unfortunately. If you don't mine compiling with debug symbols I could run it and send you the call stack.

Though not universal, it does seem to be affecting Dell computers only, could it be coincidence? maybe but it seems unlikely, it could be something affecting only newer models, or the latest drivers. It would be interesting to see what those reporting the issue have in common.

-Carlos

[rhaynes]

Hello Juan and all,

I am the one that started this thread and have an update with good news. A couple weeks ago my Dell prompted me with a notification there were new drivers available to download with the graphics card being one of them. I downloaded and installed and today decided to try installing PI-1171 again. It seems to be working flawlessly now so in my case the problem was due to the graphics driver that came with the laptop. My HD 5500 driver version is now 10.18.15.4256 not sure what it was previously. I think it would be worthwhile for anyone experiencing this issue to look into updating the graphics driver.

[cgalavis]

Glad to hear it is working for you, and thanks for sharing.
I followed your lead and went to the dell website to check for new drivers. The auto driver test indicated that no updates where available so I manually downloaded all the latest update and install them, testing PixInsight after every installation, at the end the issue did not go away

I updated first the BIOS, then the Chipset drivers, then the SATA drivers. I downloaded the NVIDIA drivers from Dell, that update did not work so I download it directly from NVIDIA and installed them successfully, but still no solution to the issue.

At this point I am out of ideas, I guess I will need to wait for the next release of PixInsight and hope that it fixes the problem.

-Carlos

[cgalavis]

Incidentally, is there a way to convert the 1.8.4 projects to version 1.8.3?

[bmhjr]

Hello,

I tried the above procedure and it seems to have corrected my issue, at first glance.  I have not done extensive testing but I can now open a file without PI crashing.  This is good news!

Dell XPS 13
Windows 10
PI 1.8.4 with above replacement files.

Thanks!
Bill

[rhaynes]

I have used PI 1.08.04.1171 extensively including batch scripts since updating the graphic driver and have not had any issues at all.

[WesChilton]

I have tried on 3 separate occasions to move to 1.8.4, but I still cannot open a file without crashing... Dell Inspiron 7458

[Renan]

No luck with the procedure recomended by Juan Conejero.

As I mentioned a few messages ago, I also have problems running PI 1.8.4 in my notebook (high resolution screen)

I tried the following:
- Replace de Pixinsight/bin files in accordance with Juan Conejero's instructions
- Updated all my notebook's drivers
- Tried it with Win 8.1 and Win 10

but the problem is still there.

Hopefully the new release will solve this problem.

Regards
Renan

[Juan Conejero]

Hopefully the new release will solve this problem.

I hope so. I have just released version 1.8.4.1185.

[WesChilton]

Unfortunately, I have to report I still have the same problem...
https://www.dropbox.com/s/kyre2yd526n3915/Screenshot%202015-10-09%2011.51.44.png?dl=0


back to 1.8.3 again..   

[Juan Conejero]

We can't reproduce this problem on any machine. Version 1.8.4.1185 has been thoroughly tested on Windows 8.1 and Windows 10, and this does not happen under normal working conditions.

Try with multiplatform file dialogs: EDIT > Global Preferences > File I/O Settings > Use native file dialogs (disable). Press F6 or click Apply Global. With this option disabled the application will not use Windows file dialogs, but its own platform-independent implementation. Hopefully this will help with this specific issue. However, This looks like you have a device driver conflict or incompatibility in your machine. Have you upgraded from Windows 8.1 to Windows 10? I would recommend a clean Windows 10 installation.