Webcam crashes

  • Thread starter Thread starter victor
  • Start date Start date
V

victor

Hello,
On my MSI K7T Pro2 mobo, no webcam is willing to function!
Tried several models, all crashed the system with the following fault
code: 40000 0080, params 1..4: all zeroes.

Anybody knows something?

Thanks,
victor
 
Hello,
On my MSI K7T Pro2 mobo, no webcam is willing to function!
Tried several models, all crashed the system with the following fault
code: 40000 0080, params 1..4: all zeroes.

Anybody knows something?

Thanks,
victor
Click to expand...

It crashes when, exactly?

What shows this fault code?

We need lots of specifics, only you know this system or can
see the monitor.

If you'd only tried one software, try some others.
Are they showing up ok in Device Manager?
Does the software have prerequisites, try the help file or
readme, or FAQ on their website.
 
Kony, thanks for replying.
I'll try to be as specific as possible:
Processor is a Duron-700MHz on the mobo with a VIA KT133 chipset. OS =
XP_Pro/SP2.
I've tried two different systems: Logitech and TechSolo webcams; both
shows the same symptoms: installation is OK, device is listed in the
DeviceMgr list and is 'running OK'.
After running for 20-30 secs it suddenly freezes the image, a lot of
disk activities and followed by a (auto-) reboot!
The error msg is taken from the EventViewer logging entry. Can't
figure it out .... .
Also tried to juggle with the BIOS settings (already d'loaded the
latest one), like modifying IRQ's enabling/disabling PnP-OS etc., all
to no avail.
My guess is that it has something todo with another resource conflict,
but what? I only have two cards in it: AGP-video and a network card.

Hope this will give you some clues.
greetz, victor.

------------------------------------------------------------------------------------
 
Kony, thanks for replying.
I'll try to be as specific as possible:
Processor is a Duron-700MHz on the mobo with a VIA KT133 chipset. OS =
XP_Pro/SP2.
I've tried two different systems: Logitech and TechSolo webcams; both
shows the same symptoms: installation is OK, device is listed in the
DeviceMgr list and is 'running OK'.
After running for 20-30 secs it suddenly freezes the image, a lot of
disk activities and followed by a (auto-) reboot!
Click to expand...

Disable windows auto-reboot feature. Next time it happens
if you get an error message, write down the main text and
error code.

What are you "running"? What software/application/etc is
being used? A webcam is just a twain device, the key here
seems to be what is accessing that twain device. I'm not
certain that's the only possibility but is one area to
cover. Do you ever have problems with any other USB
devices? Does it always seem to run for exactly the same
period of time?

The error msg is taken from the EventViewer logging entry. Can't
figure it out .... .
Click to expand...

What error msg? I mean, what does it say?
The disk activity might be a log creation, see if you can
find a new log.

Also tried to juggle with the BIOS settings (already d'loaded the
latest one), like modifying IRQ's enabling/disabling PnP-OS etc., all
to no avail.
My guess is that it has something todo with another resource conflict,
but what? I only have two cards in it: AGP-video and a network card.
Click to expand...


I'd suspect a problem with windows (don't know what,
insufficienit information and I don't know what to ask to
get any), or the specific software. Whatever this software
is have you checked for a newer version or patch?

Are you running WinXP SP2? I'd also wonder if SP2 might be
problematic. If you aren't using but one piece of software
to view the webcam, try something else, another software.
 
Hi there,
'Think I've got a (tiny) clue:
First, to answer your question: I'm still at the stage of running
'their' own image capture apps (from TechSolo and Logitech).
I'm now experiencing the following: after modifying the value of the
clock rate (BIOS item) from 'default' to '7' - to match the processor
700MHz rate, it suddenly runs for more than an hour !!
Haven't seen this before. But then ....: after coming out for the n-th
time of the screen-save mode, the image suddenly stayed black and ...
a reboot follows ! (@$#!X^!!!)
Anyway, I'm hoping that this trail is something - I'll shut off the
screensaver and see how long it will stay on.

BTW: how do you disable the auto-reboot?

I'm shutting off the conversation for now, it's two in the morning (!)
- thank you for your co-thinking.
I'll continue tomorrow if there are some new results (or to see if you
come up with other idea's).

g'nite, victor
--------------
 
Hi there,
'Think I've got a (tiny) clue:
First, to answer your question: I'm still at the stage of running
'their' own image capture apps (from TechSolo and Logitech).
I'm now experiencing the following: after modifying the value of the
clock rate (BIOS item) from 'default' to '7' - to match the processor
700MHz rate, it suddenly runs for more than an hour !!
Click to expand...

? You mean the webcam now does or the whole system?

I'm now wondering if your system is instable besides the
webcam problem, do you have other problems too?
If so, you might double-check all bios settings and test
memory stability (memtest86) and CPU stablity (Prime95's
Torture Test).

Haven't seen this before. But then ....: after coming out for the n-th
time of the screen-save mode, the image suddenly stayed black and ...
a reboot follows ! (@$#!X^!!!)
Click to expand...

Has this been happening before or only after installing this
webcam? If only after the webcam, are you using a driver
from the webcam CD? If so, check the manufacturer's website
for a newer driver.

Anyway, I'm hoping that this trail is something - I'll shut off the
screensaver and see how long it will stay on.

BTW: how do you disable the auto-reboot?
Click to expand...

I had assumed you were running WinXP, but with a system that
age I should ask, "What OS are you running?" It would seem
to be at least win2k or XP to have it reboot as you
described so if that's true see the following page and the
section titled "Recovery Settings"

http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/russel_02may13.mspx

You're wanting to clear the "automatically restart" checkbox
as that page describes.
 
Kony,
'back again at my PC-puzzle. An update: it is still running OK now ..!
Confuse, confusing it is!
FYI: indeed, the HW is (quite-) outdated (with enough memory though),
but the OS is rather current: XP-SP2. The machine itself have been
running for several years with no trouble whatsoever. It is just that
it is now getting another 'function', and has to be equipped with a
webcam. Here the trouble started.
Memtest86 didn't reveal any flaws.
As for the moment, I've got several ideas:
I've noticed that, during the debugging course, whenever the system is
not yet 'steady' (after power-on for example), the crash-problem
re-occured. If I wait awhile, waiting for the disk activity to cease,
the webcam doesn't crash. Add to this the symptom that it crashes
after a while, when getting out of the screensaver mode co-inciding
with a screen power-off event, then I guess you maybe right pointing
to 'a system that age'. Although ... a Duron at 700MHz should be
capable of driving a simple webcam, can it?
The drivers are the latest - taken from their home site.

About my first 'super-trick': modifying the clock-rate factor from
"default" to the value of "7" (matching my Duron spec), resulting in a
suddenly 'healthy' webcam .... well, I can't be sure that this *IS*
the cause of the problem, because of the situations where the crash
still occurs as I've described above.
The main difference it has established is that it does not crash
immediately after activating the imaging app.
To assess this I actually have to reset that value and see what
happens ...., but, I'm kind of tired of the whole thing and happy that
it runs now!

The MS article is interesting - thank you for your time and knowledge
sharing.

cheers, victor
=============
 
then I guess you maybe right pointing
to 'a system that age'. Although ... a Duron at 700MHz should be
capable of driving a simple webcam, can it?
The drivers are the latest - taken from their home site.
Click to expand...

Had nothing to do with a webcam or age as a reliability
factor, only what OS was expected on it as was current in
that era.

Merely operating a webcam, any old system (including Pentium
1) can do fine providing the system used an overlay and had
stable video driver. You might see if you can upgrade your
video driver, and perhaps chipset driver as well,
particularly if it's a Via chipset based board as they had
some PCI issues in that era. Likewise, leaving no stone
unturned it might be useful to have a motherboard bios
update. I would not expect the bios update to help but if
the manufacturer provides bios notes, you can see for
yourself what they've addressed.

About my first 'super-trick': modifying the clock-rate factor from
"default" to the value of "7" (matching my Duron spec), resulting in a
suddenly 'healthy' webcam .... well, I can't be sure that this *IS*
the cause of the problem, because of the situations where the crash
still occurs as I've described above.
The main difference it has established is that it does not crash
immediately after activating the imaging app.
To assess this I actually have to reset that value and see what
happens ...., but, I'm kind of tired of the whole thing and happy that
it runs now!
Click to expand...

I wonder if manually setting it is causing other bios
settings to change as well, since as you noted that is the
correct, should be same, multiplier the board was already
using.
 
Kony,

sighhhh ...., back to square one!!
Turned out that it "works" now, but in a kind of 'delayed execution':
after idling for a while or while working with the cam, the dreadful
BSOD is there.
Yes, I followed your advise and turned off the auto-reboot; now I can
see what happens:
on two BSOD occasions, there are two different files complaining: the
first time it was the "KS.SYS" file and the second time it is the
"USBPORT.SYS" file.

'Have done the mobo BIOS upgrade - didn't help.
Video driver also latest one (Matrox Millennium II) - didn't help.

Didnot tried the VIA chipset yet - maybe, hopefully.

:-(( victor
 
Kony,

sighhhh ...., back to square one!!
Turned out that it "works" now, but in a kind of 'delayed execution':
after idling for a while or while working with the cam, the dreadful
BSOD is there.
Yes, I followed your advise and turned off the auto-reboot; now I can
see what happens:
on two BSOD occasions, there are two different files complaining: the
first time it was the "KS.SYS" file and the second time it is the
"USBPORT.SYS" file.

'Have done the mobo BIOS upgrade - didn't help.
Video driver also latest one (Matrox Millennium II) - didn't help.

Didnot tried the VIA chipset yet - maybe, hopefully.
Click to expand...

I"m running out of ideas... maybe reinstall DirectX 9c,
check on newer USB drivers for your motherboard. I assume
you had the updated Via chipset driver?
 
I"m running out of ideas... maybe reinstall DirectX 9c,
check on newer USB drivers for your motherboard. I assume
you had the updated Via chipset driver?
Click to expand...

There is some less than clever software in this world.
When it comes to imaging stuff on the screen, double
buffering is a popular method. Good software would
throw frames away, if the processor was not able to
keep up with the flow of data. The user would notice
the dropped frames and generally crappy performance, but
at least there would be no crashes. It could be that
in this case, the software assumes an "infinite" processor,
and the software doesn't know how to handle "falling behind".

Since the problem happens so quickly, it is probably not a
memory leak. You can watch memory consumption in the Task
Manager.

If there was a spare disk available, then a clean reinstall
of the OS, with minimal software installed on the disk,
would be a way to test the configuration with fewer pieces
of interfering software being present. It could just be the
sheer number of bloated tasks running on the machine (like
AV software), that leaves no processing power left for the
webcam.

Just a theory,
Paul
 
Paul, Kony (and maybe other thread readers),

A short reaction to Paul's idea: yes, I've monitored this leakage
possibility and saw nothing strange; I've also tried the other cam, a
Logitech one, same problems - no leaks.

Next:
This is, I hope so, the final soution of my situation!
After installing the latest VIA chipset driver and still no result, I
kind of want to give up .... .
The next day though, while doing a last-hope-google-search, I stumbled
into the tale of 'raspyni-ga'. The article is on "Google Answers",
titled 'Computer Shuts Off by Itself When Using Skype and USB Webcam'.
Well, it's almost exactly the same condition as mine - the only
difference is the crash behavior: his'/her's does not restart by
itself but just switches itself off.
Making a long story short, his solution turned out to be a faulty
power supply! Problem solved.
Well, unfortunately this was not the case with me - but, triggered by
this event and discussions at work, the path led to try out a USB2-PCI
add-on card.

And .... IT WORKED !! (two days full testing, hours online, no crashes
anymore)
Took card out - crashed again!

Conclusao: somehow the On-board USB port drivers had a flaw, what kind
.... 'don't know. The most probable thing is that it didn't provide
enough 'juice' to drive the cam. Those 'old day boards' can have those
'early-USB' problems.

I hope this thread helps somebody someday.

Thank you all for your co-thinking!
regards, victor.
==========================================================
 
Back
Top