Video Capture now dropping frames, crashing, HD 9

ZenProAudio wrote on 2/5/2011, 10:55 AM

I have been using Movie Studio HD 9 with 100% success since summer 2010. Now, the program is dropping frames and / or crashing in capture mode. I am on a Win7 64 bit Vaio laptop using a Microsoft Lifecam via USB. Nothing in my setup has changed. I have experimented with changing the capture folder (which shows tons of space available) and making sure other programs aren't running etc. It's not the camera, I just went out and picked up another Lifecam to test if it's a hardware issue, and nothing changes. I went from working to a dead stop in one fell swoop and cannot figure this out on my own.

The error messages I get are pasted below.

Sony Video Capture

Exception 0xC0000005 (access violation) READ:0x4 IP:0x4427B3
In Module 'VidCap60.EXE' at Address 0x400000 + 0x427B3
Thread: GUI ID=0x8FC Stack=0x18C000-0x190000
Registers:
EAX=02a68ed0 CS=0023 EIP=004427b3 EFLGS=00010246
EBX=008ef998 SS=002b ESP=0018cfc8 EBP=0018d434
ECX=00000000 DS=002b ESI=008ef760 FS=0053
EDX=06864a30 ES=002b EDI=02a68ed0 GS=002b
Bytes at CS:EIP:
004427B3: 8B 51 04 89 54 24 48 8B .Q..T: 47 30 8B 48 08 8B 55 08 G0.H..U.
Stack Dump:
0018CFC8: 00000000
0018CFCC: 00A2A610 009A0000 + 8A610
0018CFD0: 76814076 767F0000 + 24076 (USER32.dll)
0018CFD4: 76820155 767F0000 + 30155 (USER32.dll)
0018CFD8: 06FF9C7D 06FD0000 + 29C7D
0018CFDC: 00A78530 009A0000 + D8530
0018CFE0: 76806EC0 767F0000 + 16EC0 (USER32.dll)
0018CFE4: 00000000
0018CFE8: 00000000
0018CFEC: 00000000
0018CFF0: 00000001
0018CFF4: 00000000
0018CFF8: 00000000
0018CFFC: 00000000
0018D000: 008EF998 008E0000 + F998
0018D004: 00010003 00010000 + 3
> > 0018D030: 7680701B 767F0000 + 1701B (USER32.dll)
> > 0018D040: 76807027 767F0000 + 17027 (USER32.dll)
> > 0018D064: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D068: 7284780C 72830000 + 1780C (COMCTL32.dll)
> > 0018D080: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D08C: 76806238 767F0000 + 16238 (USER32.dll)
> > 0018D0A0: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D0B0: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D0BC: 76870230 767F0000 + 80230 (USER32.dll)
> > 0018D0C8: 76806941 767F0000 + 16941 (USER32.dll)
> > 0018D0CC: 76806901 767F0000 + 16901 (USER32.dll)
> > 0018D0FC: 76806899 767F0000 + 16899 (USER32.dll)
> > 0018D100: 76806941 767F0000 + 16941 (USER32.dll)
> > 0018D118: 76820155 767F0000 + 30155 (USER32.dll)
> > 0018D120: 76820155 767F0000 + 30155 (USER32.dll)
> > 0018D12C: 76806901 767F0000 + 16901 (USER32.dll)
> > 0018D130: 7680CD1A 767F0000 + 1CD1A (USER32.dll)
> > 0018D138: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D174: 7682FFD8 767F0000 + 3FFD8 (USER32.dll)
> > 0018D180: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D1A4: 728C5329 72830000 + 95329 (COMCTL32.dll)
> > 0018D1AC: 728C533D 72830000 + 9533D (COMCTL32.dll)
> > 0018D1F0: 76810CFE 767F0000 + 20CFE (USER32.dll)
> > 0018D1F8: 76810D0D 767F0000 + 20D0D (USER32.dll)
> > 0018D224: 76810EAF 767F0000 + 20EAF (USER32.dll)
> > 0018D228: 72847985 72830000 + 17985 (COMCTL32.dll)
> > 0018D250: 7680698B 767F0000 + 1698B (USER32.dll)
> > 0018D258: 76806947 767F0000 + 16947 (USER32.dll)
> > 0018D264: 7680698B 767F0000 + 1698B (USER32.dll)
> > 0018D278: 76820155 767F0000 + 30155 (USER32.dll)
> > 0018D294: 72EC0D73 72EB0000 + 10D73 (uxtheme.dll)
> > 0018D2A0: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D2B4: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D2BC: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D2C8: 76806238 767F0000 + 16238 (USER32.dll)
> > 0018D2DC: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D2F8: 76870230 767F0000 + 80230 (USER32.dll)
> > 0018D304: 76806941 767F0000 + 16941 (USER32.dll)
> > 0018D308: 76806901 767F0000 + 16901 (USER32.dll)
> > 0018D338: 76806899 767F0000 + 16899 (USER32.dll)
> > 0018D33C: 76806941 767F0000 + 16941 (USER32.dll)
> > 0018D35C: 76820155 767F0000 + 30155 (USER32.dll)
> > 0018D368: 76806901 767F0000 + 16901 (USER32.dll)
> > 0018D36C: 76807177 767F0000 + 17177 (USER32.dll)
> > 0018D374: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D38C: 76807182 767F0000 + 17182 (USER32.dll)
> > 0018D3B8: 76820155 767F0000 + 30155 (USER32.dll)
> > 0018D3C4: 76807182 767F0000 + 17182 (USER32.dll)
> > 0018D3C8: 768072F1 767F0000 + 172F1 (USER32.dll)
> > 0018D3D0: 774BF88A 774A0000 + 1F88A (ntdll.dll)
> > 0018D3D4: 76807304 767F0000 + 17304 (USER32.dll)
> > 0018D404: 774B00E6 774A0000 + 100E6 (ntdll.dll)
> > 0018D414: 774B0070 774A0000 + 10070 (ntdll.dll)
> > 0018D42C: 728477CD 72830000 + 177CD (COMCTL32.dll)
> > 0018D430: 774D2472 774A0000 + 32472 (ntdll.dll)
> > 0018D438: 00444356 00400000 + 44356 (VidCap60.EXE)
0018D43C: 00A2A610 009A0000 + 8A610

Problem signature:
Problem Event Name: APPCRASH
Application Name: VidCap60.EXE
Application Version: 6.0.0.1000
Application Timestamp: 473b36dd
Fault Module Name: VidCap60.EXE
Fault Module Version: 6.0.0.1000
Fault Module Timestamp: 473b36dd
Exception Code: c0000005
Exception Offset: 000427b3
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033
Additional Information 1: b4c3
Additional Information 2: b4c35959030b076d1d0dce7885317eed
Additional Information 3: 72b3
Additional Information 4: 72b31fc234236cf6812cb50af0688455

Warren Dent
ZenPro Audio

Comments

Steve Grisetti wrote on 2/5/2011, 1:27 PM

If it used to work but suddenly doesn't, the most likely culprit is spyware or fragmentation on your capture drive. But it could also be a Microsoft update or interference from your antivirus (especially if it's McAfee or Norton).

Or it could be that you need to update the driver on your Lifecam or even your video card (directly from the ATI or nVidia site).

But it's likely worth checking out your background processes first. Ctrl+Alt+Del to open your Task Manager. How many background processes are running?

ZenProAudio wrote on 2/5/2011, 6:10 PM

I don't use any antivirus, this laptop and webcam / software combo I actually bought in lieu of having a dedicated camera, since the quality was good enough and kept everything together. I never do anything on the computer but make videos, and connect to YouTube to upload them.

My son has a Win7 64 bit laptop that I just tried it with, as well as the same copy of HD 9 installed. Exact same problem, could it be Microsoft "updating" the driver...? Also, I ran out and bought the new 1080p HD version of this Lifecam today in case it was the camera, and it has the exact same issue.

I just noticed that at this moment, only really running this HD program, it still reports 70 processes running. I ended a few of them named "svchost.exe" that were showing usage about the same size as HD 9 being open. After closing some of them, I was able to just now capture some video without a crash, but still with dropped frames.

Does having all these identically named processes open mean possible virus?

Thanks so much for your response!

Warren

ZenProAudio wrote on 2/5/2011, 6:11 PM

Also, I defragmented the drive as soon as this started happening, and it did not help this.

Warren

Steve Grisetti wrote on 2/5/2011, 7:03 PM

BTW, I would very much recommend you get an antivirus program on that computer as soon as possible!

In fact, if you've been running it with no antivirus, you could well be overrun with viruses, spyware and other malware. And that could well account for your problems!

Microsoft Security Essentials is absolutely free and can be downloaded from the Microsoft site. As soon as you install it, do a complete system scan.

You may also want to install Spybot S&D and do a thorough scan with it too.

No PC should ever go anywhere near the internet without protection! I don't care which version of the operating system you're running!

ZenProAudio wrote on 2/6/2011, 3:36 PM

Thanks for the advice, I installed and scanned it and it showed no issues.

Turns out the issue is the Lifecam itself. When asking it to do some of its AUTO features, or when using ZOOM, causes the camera to interact with its software constantly, and eats up bandwidth as a result. I assumed ZOOM (which was the only one I was using) was a physical zoom of the lens, but it must be DSP "cropping" instead.

I turned off all of those features (which I never used before, which is why it suddenly stopped) and I'm back to zero dropped frames.

Warren