SKJM Forum
Support => iCam Support => : paulmccutcheon October 11, 2010, 09:27:57 PM
-
"iCamSource.exe has stopped working..."
This error occurs as soon as it is launched, within 1 second and never even see the app. Running the latest iCamSource version on Win7 Ultimate x64. It started after a recent Windows update; not sure exactly which one because I didn't have to reboot right away. I would say it was an update within the last 2 weeks.
Has anyone seen this same issue?
Thanks, Paul
-
Do you know if the Auto-Start option is enabled in iCamSource? The application doesn't do very much when it's first launched, unless the Auto-Start option is enabled.
Please try disabling the Auto-Start option. To do that, download and run (double-click) this file: http://skjm.com/icam/DeleteAS.reg
Then re-launch iCamSource.
If the program launches, but it crashes when you hit the Start button, please send me a screenshot of the iCamSource window (before it crashes) so I can verify the settings.
If it still crashes as soon as you launch it, that indicates there's an issue with Windows. Please make sure that Windows is fully updated through Windows Update.
Also, there are two prerequisites that must be installed in order for iCamSource to run properly, the Visual Studio Redistributable Package(vcredist_x86.exe) and the .Net framework.
Please download the vcredist_x86.exe installer from here: http://skjm.com/icam/vcredist_x86.exe and run it. After you run vcredist_x86.exe, please reboot your computer. Then try iCamSource to see if the problem has been resolved.
If that does not resolve your problem, please update .Net. The .Net updater is available here: http://www.microsoft.com/downloads/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en
-
I did all of your recommendations, and nothing changed. I checked the version I had installed in Control Panel and it said 2.1.1. I removed it, rebooted and reinstalled version 2.1.3 and it seems to be working fine right now.
-
I have the same problem. I have tried the solutions here to no avail. I managed to run iCamSource on another machine -- the camera is wireless, but it is far from a good solution because the usb camera is attached to my Windows 7 64-bit machine. I must say I have had endless problems, and not just with iCamSource, since the most recent Windows auto-update.
-
Have you checked your version of icamsource? Paul mentioned that he upgraded from 2.1.1 to 2.1.3...and that fixed his problems. There is also a 2.1.4 version of icamsource if 2.1.3 doesn't work for you. From the sound of it, Paul was also using Windows 7 64-bit.
-
I have the same problem. Win7 64 bit. Just tried version 2.1.5 and within 1 second I get the "has stopped working" box.
-
@Blitz - Have you tried using the iCamSource Registry Cleaner? - http://skjm.com/icam/CleaniCamKey.reg
If you download and double-click that file it should reset your iCamSource registry settings. The next time you run the iCamSource you will need to re-enter your info, but hopefully it will not crash.
-
Worked! Thanks!
-
I had the same problem and the resetting the registry did the trick, thanks.
-
Hi there, having a similar problem but the problem can cause a blue screen on the pc and is shut down - manual reboot is essential.
Tracked it down to a cam with a long USB active lead connected to one of the cams in iCam.
Looks like iCam can only handle USB leads up to 10m without causing a iCam crash and a complete fatal system crash.
Unfortunatley I have to use Jumicam to view the cam with a long active lead which is 20m to the front door cam.
Question is - If Jumicam can work flawlessly with the longer USB lead, any chance of making iCam work so I don't have to use 2 programs to view all cams?
-
The issue is actually with your computer's USB bus and the instability that a long USB extension cable introduces to your system.
The difference between iCam and Jumicam is that Jumicam only "engages" the webcam when you connect to view it, whereas the iCamSource is constantly monitoring the webcam's video stream to send push notifications and record motion events when motion is detected.
-
rottoruss,
I have 2 USB cameras connected to my main Windows 7 computer. One is connected via 4 hubs and a total of about 60 feet. The other is connected via a single hub at 50 feet (the 50 foot run degrades the USB 2 to USB 1). Both work fine although my audio drops out after about 12-24 hours.
I have 2 more USB cameras connected to an old XP computer that use 1 hub and both have about 20 foot runs.
When I first hooked them up, I had various instability problems and had to try different combinations of hubs, ports on my PC and wire lengths.
-
Hey Twink, thanks for the info.. I'll experiment and try to find a work around
Might try the new USB over power cams and see what happens.
Would be good if iCam did sound for the IP cameras.. May solve a few issues.
-
I believe that PC Tools Registry Mechanic is causing this problem. I had mine fixed and registry mechanic ran last night and it was not working again this morning and I had to rerun the program to reset the registry. It is working fine right now. I will have to keep an eye on Registry Mechanic as it may be having a problem with one of the entrys.
-
The issue is actually with your computer's USB bus and the instability that a long USB extension cable introduces to your system.
The difference between iCam and Jumicam is that Jumicam only "engages" the webcam when you connect to view it, whereas the iCamSource is constantly monitoring the webcam's video stream to send push notifications and record motion events when motion is detected.
Well, mine worked for about a week and then quit again. I can take the USB variable out -- I connect via WiFi. There was an error message with codes, and I cleared it before I thought to take a screenshot. I do use registry booster, to add another variable.
-
Well, mine worked for about a week and then quit again. I can take the USB variable out -- I connect via WiFi. There was an error message with codes, and I cleared it before I thought to take a screenshot. I do use registry booster, to add another variable.
Did the iCamSource crash? Or did you see an error message underneath the video preview in the iCamSource Preferences window? What is the make and model of camera that you are using?
-
I'm having a recurring problem with iCamSource.exe halting after about a day of operation. Here is info from the Windows event log:
Faulting application iCamSource.exe, version 0.0.0.0, time stamp 0x4cbc7028, faulting module MSVCR90.dll, version 9.0.30729.4148, time stamp 0x4a594c79, exception code 0xc0000417, fault offset 0x0006ccb5, process id 0x1280, application start time 0x01cb7980745b5f9c.
I've got a watchdog process to restart it, but this is getting annoying.
-
Are you running the latest version of the iCamSource, 2.1.5? How many webcams and / or network IP cameras are you connecting to? Is the computer going to sleep or into standby mode?
-
Version 2.1.5 with a single wi-fi Swann camera on Windows Vista. Computer is not going into standby or sleep mode. It was stopped again today.
Here's some additional information I collected after windows gave the "iCamSource.exe has stopped working" dialog. Its status reported as "running" seems a bit contradictory, but I imagine that just means the application had surrendered its memory, etc... yet.
Image Name PID Session Name Session# Mem Usage Status CPU Time
iCamSource.exe 5772 Console 1 66,472 K Running 3:45:15 N/A
So it was using a reasonable amount of memory -- eliminating memory leak as a cause.
-
What is the model number of your Wi-Fi camera? Also, what is the MJPEG or JPEG URL that you are using to connect to it in the iCamSource?
-
URL is http://192.168.2.10/cgi/mjpg/mjpeg.cgi. The model is IP-3G ConnectCam 1000.
-
I am assuming that you have the MJPEG radio button chosen on the iCamSource as opposed to JPEG? What is the % CPU usage in the task manager when the iCamSource is running? Also, what is the video frame rate that you have set for your camera?
-
Yes, the MJPEG radio button is selected. CPU usage is about 6-8%. Frame rate is 5 fps. Resolution is VGA high quality. Things were more stable under iCamSource 1.x. I'll experiment by dropping the video quality and rate even further.
-
Your CPU and frame rate numbers look reasonable.
Do you know if the iCamSource is crashing when you connect to it from iCam (either via WiFi or 3G)? Or is it just crashing after running for a while?
-
Not sure, but I suspect it's when I try to connect. A typical scenario is that I receive notification of a motion event when I'm away from home, and then find that I can't connect. When I get home I see the "has stopped working" dialog. Of course, other items I get the notification and can connect fine, so it's pretty hit or miss.
-
This is just an idea...not sure if it will fix your problem.
I had similar crashes (especially with multiple cameras) when trying to connect because the ports were not being forwarded correctly. To fix it, I had to set up manual port fowarding...and all of my problems went away. Granted, this was icamsource 1.4 or before...when there was no uPNP feature. It would be worth checking and making sure that the minimum number of ports (I think they recommend 6 or 7 ports per camera feed) are, in fact, open...and that your router is forwarding to those ports correctly (uPNP is enabled, etc). And while it might be a pain, it might be worth setting up manual port forwarding. This is more secure and more consistent in terms of performance anyway. Hope this helps.
-
@stuart_k_rogers - You might try connecting via both WiFi and 3G to see if either way causes a crash.
OUAnthony is correct in that port forwarding does simplify what iCam and the iCamSource have to navigate through to make the connection, and if it is a lesser-travelled logic path that is causing the crash then that might be a solution. (He is also right in that trying the Auto-Config Router would be easier than to do the full-on manual port forwarding ... If your router supports it, of course.)
-
rottoruss,
I have 2 USB cameras connected to my main Windows 7 computer. One is connected via 4 hubs and a total of about 60 feet. The other is connected via a single hub at 50 feet (the 50 foot run degrades the USB 2 to USB 1). Both work fine although my audio drops out after about 12-24 hours.
I have 2 more USB cameras connected to an old XP computer that use 1 hub and both have about 20 foot runs.
When I first hooked them up, I had various instability problems and had to try different combinations of hubs, ports on my PC and wire lengths.
Any resolution to the audio issue ??
-
I am having the same issues - running win7 with 4 skyipcam 747w on wifi
runs for about 12 hours then crashes - here is the debug report
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: Unknown error (0x8)
at System.Drawing.BufferedGraphicsContext.CreateCompatibleDIB(IntPtr hdc, IntPtr hpal, Int32 ulWidth, Int32 ulHeight, IntPtr& ppvBits)
at System.Drawing.BufferedGraphicsContext.CreateBuffer(IntPtr src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
at System.Drawing.BufferedGraphicsContext.AllocBuffer(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.AllocBufferInTempManager(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.Allocate(IntPtr targetDC, Rectangle targetRectangle)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
WiniCamSource
Assembly Version: 1.0.3943.14548
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/iCamSource/iCamSource.exe
----------------------------------------
msvcm90
Assembly Version: 9.0.30729.4926
Win32 Version: 9.00.30729.4926
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_508ed732bcbc0e5a/msvcm90.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
-
mrz500 - Does it still crash if you only run one camera in iCamSource?
Are you using the MJPEG or JPEG mode in iCamSource? Please try switching to the other mode on all of the cameras to see if that has any effect.
-
running mjpeg, will try and switch to jpeg but not sure if those airlink cams have that option. Also I upgraded to 2.16 and the issues is still happening after so many hours but also now it crashes instantly if I connect via icam-iphone through wifi, but 3G it does not. this happens with 1 or 4 cams connected.
-
You don't need to change anything on the camera. Just use the same URL in iCamSource, but check the JPEG checkbox instead of the MJPEG checkbox. The JPEG mode will work with MJPEG URLs as well, it just requests the data differently.
Have you rebooted your computer since the crashing first occurred? If not, please try rebooting.