Crash BSOD trying on startup Windows 10 64bit

Report bugs and errors to the digiCamControl development team.
FlightRisk
Posts: 7
Joined: Fri Nov 22, 2019 8:10 am

Crash BSOD trying on startup Windows 10 64bit

Post by FlightRisk » Fri Nov 22, 2019 8:19 am

I have an HP Laptop running Windows 10 Professional 64bit. I had a very old version of Digicam working just fine and tried to upgrade to the version the software asked me to use, 2.1.1.0. Every time I try to run the program, it crashes. I see people posting logs, but not sure where they are getting them. I don't have anything related to logitech in my list of programs that I can uninstall. How can I debug the crash and what is the best older version to use? I see references to 2.1.0.0, but the sticky threads are 2 much older versions.

Crash BSOD trying on startup Windows 10 64bit

Advertisment
 

admin
Site Admin
Posts: 111
Joined: Tue Sep 15, 2015 8:33 pm

Re: Crash BSOD trying on startup Windows 10 64bit

Post by admin » Fri Nov 22, 2019 1:39 pm

Try to delete the c:\ProgramData\digiCamControl folder

FlightRisk
Posts: 7
Joined: Fri Nov 22, 2019 8:10 am

Re: Crash BSOD trying on startup Windows 10 64bit

Post by FlightRisk » Tue Nov 26, 2019 4:34 pm

I tried everything I know how. I deleted the folder. Didn't help. Manually deleted every folder I could find and registry entries. Installed all the latest windows 10 64 bit updates. Re-installed. Still crashes. I see "kmode exception" in "clwvd.sys". Took a lot of effort to find the actual driver name, the writing is too small on the BSOD and it goes away after a few seconds. Looks like this is a driver for "Youcam", so I will research that. I'll try again. Is there are more stable version than 2.1.1.0?

FlightRisk
Posts: 7
Joined: Fri Nov 22, 2019 8:10 am

Re: Crash BSOD trying on startup Windows 10 64bit

Post by FlightRisk » Tue Nov 26, 2019 5:51 pm

It seems there is an issue with the webcam support code. Obviously, it shouldn't give a BSOD fo, even if there is an issue with 3rd party drivers. But now instead of crashing it just sits at the loading screen. It doesn't seem to be locked, task manager shows activity.

admin
Site Admin
Posts: 111
Joined: Tue Sep 15, 2015 8:33 pm

Re: Crash BSOD trying on startup Windows 10 64bit

Post by admin » Tue Nov 26, 2019 6:36 pm


FlightRisk
Posts: 7
Joined: Fri Nov 22, 2019 8:10 am

Re: Crash BSOD trying on startup Windows 10 64bit

Post by FlightRisk » Tue Nov 26, 2019 7:44 pm

I was just going to post that I tried each version backwards until I got to 1.1.0 and it seems to work fine. Going to check this version.

FlightRisk
Posts: 7
Joined: Fri Nov 22, 2019 8:10 am

Re: Crash BSOD trying on startup Windows 10 64bit

Post by FlightRisk » Tue Nov 26, 2019 7:51 pm

Well, this version loaded right away. I was encouraged. But then I tried to change the theme to a dark one and it wouldn't change. So I exited the software and now it won't load at all. It doesn't even show a loading screen.

FlightRisk
Posts: 7
Joined: Fri Nov 22, 2019 8:10 am

Re: Crash BSOD trying on startup Windows 10 64bit

Post by FlightRisk » Tue Nov 26, 2019 7:59 pm

Nothing much works on this version other than it loads once. File/Exit won't work, you have to click the "x" in the upper right of the window. That leaves the software still loaded in memory. You have to manually terminate the process in task manager in order to load it again. So progress of a sort :)

FlightRisk
Posts: 7
Joined: Fri Nov 22, 2019 8:10 am

Re: Crash BSOD trying on startup Windows 10 64bit

Post by FlightRisk » Wed Nov 27, 2019 2:19 am

I appreciate the help. I am a code myself so understand what is involved in writing good software. The .1.1.3 version you had me try seems to be hard coded to look to drive D. I don't have a drive D, but that error may be pointing to your development system and your C# settings source file. So this version does load, but does not allow me to do anything. I do NOT have a camera connected. I am just testing to see if I can get the software to run and execute functions that don't require the camera. I see null reference exceptions. Here is the pertinent portion of the log:

Code: Select all

2019-11-26 19:07:29,266 [1]DEBUG DCC [(null)] - Init : _pipeServer
2019-11-26 19:07:30,951 [4]DEBUG DCC [(null)] - Error find photo session 
System.NullReferenceException: Object reference not set to an instance of an object.
   at CameraControl.Core.Classes.Settings.<>c__DisplayClass358_0.<GetSession>b__0(PhotoSession photoSession) in D:\devel\vs2010\CameraControl\CameraControl.Core\Classes\Settings.cs:line 1380
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   at CameraControl.Core.Classes.Settings.GetSession(String name) in D:\devel\vs2010\CameraControl\CameraControl.Core\Classes\Settings.cs:line 1380
2019-11-26 19:07:31,181 [1]DEBUG DCC [(null)] - Logo file not foundC:\Program Files (x86)\digiCamControl\Plugins\CameraControl.Plugins\logo.png
2019-11-26 19:07:31,184 [1]DEBUG DCC [(null)] - Loading plugin dll: C:\Program Files (x86)\digiCamControl\Plugins\CameraControl.Plugins\CameraControl.Plugins.dll
2019-11-26 19:07:33,395 [1]DEBUG DCC [(null)] - Loading plugin dll: C:\Program Files (x86)\digiCamControl\Plugins\Plugin.DeviceControlBox\Plugin.DeviceControlBox.dll
2019-11-26 19:07:34,382 [1]ERROR DCC [(null)] - Error to load plugins 
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at CameraControl.ViewModel.CameraPropertyViewModel.Init() in D:\devel\vs2010\CameraControl\CameraControl\ViewModel\CameraPropertyViewModel.cs:line 61
   at CameraControl.ViewModel.CameraPropertyViewModel..ctor() in D:\devel\vs2010\CameraControl\CameraControl\ViewModel\CameraPropertyViewModel.cs:line 52

admin
Site Admin
Posts: 111
Joined: Tue Sep 15, 2015 8:33 pm

Re: Crash BSOD trying on startup Windows 10 64bit

Post by admin » Thu Nov 28, 2019 11:01 pm

Can you upload the full log file also you can try delete again the c:\ProgramData\digiCamControl folder
I think this error is related to the webcamera support

Post Reply