BYN 2.0.1 Exception Errors with D750

[midnight_lightning]

Hi,

 

I have been using 1.0.5 without any issues for several months but yesterday upgraded to the new 2.0.1 version. My D750 was bought in 2015, around a year ago and hasn't been upgraded so I selected the "2015" option on connection.

 

This version crashed twice whilst I was imaging last night, the first time it just crashed BYN, the second time it also crashed the laptop. Unfortunately I didn't think to screenshot the error but it was something about an unmanaged exception error. In at least one case I was using the curves function to examine an image whilst an imaging plan was also running. I also got a memory warning around the same time which may or may not be connected (memory leak?). The laotop is brand new, bought specifically for imaging and has 4GB RAM. It was only running PH2 and Team Viewer in addition to BYN and other than during the problem I never saw it use more than 2.3GB of 4GB - so plenty spare.

 

I uninstalled 2.0.1 and put 1.0.5 back on half way through my imaging session and it worked flawlessly.

 

Any ideas?

 

Thanks

 

Mid

[admin]

1.0.5 and 2.0.1 are almost 100% identical.  The only big difference in the actual Nikon SDK and the way BYN connects to the camera.  If anything 2.0.1 shold be more stable because it only loads the SDK needed for your specific model rather to loading them all like 1.0.5 did.

 

The latest SDK with the latest 2.0.1 should work with your D750.  I would try that for sure and see if you have the same issue.

 

Keep us posted.

 

Regards,

[astroman133]

It is very abnormal that an application would crash the entire machine. Windows is specifically designed to prevent this. On the other hand, a flaky memory module could cause the symptom that you are seeing. You did say that you got a memory warning. The specific wording would be helpful. Is it low memory? 4GB is not a lot for Windows 10! Or is it a memory error? Indicative of bad memory.

 

Did you run BYN 1.0.5 for long enough to be sure that the issue is only with BYN 2.0.1? Do you have any system diagnostics to run? They could rule out the hardware.

 

Guylain, which version of the SDK is the correct choice for the D750?

[admin]

I believe the latest SDK released early 2016 is the correct one for the D750.

 

If there was a memory leak it would have been reported a long time ago.  The prevent this I often run the app for 24 hours taking one image every minute; this is 3600 images in a single run.

 

The memory issue is probably the image memory issue.  I talk about this in the thread.  Hard to say without the log files.

[midnight_lightning]

I'm sure the memory is fine I've not had any other isues, the warning was for "low memory". I hadn't monitored usage before the crash but kept an eye on it after going back to 1.0.5 and as detailed above it was peaking just above 50% usage. I ran for another 2-3 hours on 1.0.5 with no issues.

 

Could the issue be because I connected with the "2015" option rather than the "2016" -  I just followed the guidelines on the page since my camera /firmware is from 2015?

 

What is the SDK, is this another download I need, I only installed 2.0.1?

 

Thanks

Mid

[admin]

BYN is all inclusive, not need to download anything else.

 

Low memory seems odd, do you have virtual memory configured on your computer?  If not I would try this first.

[midnight_lightning]

Virtual memory is too low, only around 740MB if I remember correctly, I was going to increase it at the time but it asked for a reboot and I didn't want to have to recalibrate PHD2 again. But again, I had no issues with 1.0.5 so I don't think its a memory issue. Perhaps I'll try connecting as a 2016 camera. 

[astroman133]

Well, the newer version of BYN does use different SDK libraries, so they could have a larger memory footprint.

 

I would bump your virtual memory up to around 4000MB...The same as your physical memory.  That said if you actually start running out of physical memory and Windows starts to swap out programs the machine will appear to slow down to a crawl. If that happens routinely then you should consider putting more RAM into the laptop.

[midnight_lightning]

Ok, I will try that, it has SSD storage so it's quicker than a HDD, but I still don't think it's a memory issue