SharpCap Forums

Hi,

Operating System: Windows 7
Camera: ZWO 174mm
Sharpcap version: 3.1

Here is the error message:

Problem Event Name: APPCRASH
Application Name: SharpCap.exe
Application Version: 3.1.5219.0
Application Timestamp: 5b465dfd
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b83c8a
Exception Code: c06d007e
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Hi,

what stage are you at when the program crashes? Starting the application? Opening the camera?

cheers,

Robin

Hi

Oder of occurrence:

1 - the colorful small window with Jupiter, a cmos chip, and the word "Sharpcap" appears
2 - then the main window appears with the top menu bar and white screen
3 - finally, a smaller window with the message "SharpCap has stopped working" appears

Ok, thanks.

The error code in the initial log and your description both point at a DLL file being missing on your system. The interesting bit is working out which one and why It doesn't show a name for the missing DLL in the error message or the system event log does it?

cheers,

Robin

Hi,

there are two messages in the event log:

first:

Log Name: Application
Source: .NET Runtime
Date: 8/7/2018 7:53:30 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: MININT-0971DCL
Description:
Application: SharpCap.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c06d007e, exception address 7525C41F

followed by:

Log Name: Application
Source: Application Error
Date: 8/7/2018 7:53:31 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MININT-0971DCL
Description:
Faulting application name: SharpCap.exe, version: 3.1.5219.0, time stamp: 0x5b465dfd
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
Exception code: 0xc06d007e
Fault offset: 0x0000c41f
Faulting process id: 0xaa0
Faulting application start time: 0x01d42ea9c6d9efce
Faulting application path: C:\Program Files (x86)\SharpCap 3.1\SharpCap.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: 16354be4-9a9d-11e8-9cea-e318919528bd

Thanks for checking - unfortunatly neither of these tell me what the missing DLL is - I think the only way to track this down is to use ProcMon (https://docs.microsoft.com/en-us/sysint ... ds/procmon) to track all the file access that SharpCap is attempting - near the end of the procmon log we will see lots of attempts to find [something].dll in various different folders, all of which fail - then we know that [something] is the missing dll.

What you need to do is...

1) Download Procmon from the link above
2) Unpack and run it
3) In the filter window that pops up select 'Process Name', 'Contains', 'SharpCap' and then press the 'Add' button, then 'OK' (see image below)
4) Leaving procmon running, run SharpCap and let it crash
5) You should see lots of lines of text appear in the procmon window
6) Press the save button in procmon - choose options as shown in second image below and press OK
7) send me the PML file created (attach it to a reply here of PM me for an email address).

cheers,

Robin

Ah, one more thing...

close down Procmon when you are done. If you leave it running it will gradually use up all your memory until everything else slows to a crawl. Been caught like that myself a few times.

cheers,

Robin

Thanks Robin.

when I attempted to attach the "pml" file, I received a message "invalid file extension.

When I tried to attach it as a comma-separated file, the message said "too large"

any suggestions?

Cheers

Conrad

Just to let you know I sent you a PM with an email address to send the pml file to.

cheers,

Robin

A way round the 'invalid file extension' for the .pml is to zip the file and then try attaching. Many systems are picky about attachments - this technique is usually used with .exe files.

Zipping would also help with the .csv 'file too large' problem. A .csv (or any text file such as a log file) would shrink significantly when zipped.

Dave