The WDM Video Capture Driver causes reboot problem with windows XP

  • Thread starter Thread starter Geofrey van Hecke
  • Start date Start date
G

Geofrey van Hecke

Hi,

When I select my Hercules smart TV2 as capture device in several software
(i.e VideoLan) and I try to start the capture, my Windows xp reboot...

I have analysed (with the use of the Windbg tool) the dump file produced by
windows ... and my investigations lead to the following conclusions...

The error occured in the Pv848.sys file which is the "WDM Video Capture
Driver" from Microsoft". The error description is the following:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are.

I'm looking for a solution. Is there any newer version of this driver (the
current i used is version 5.0.0.272) ?

I would be please if someone can help me.
 
Hi Geofrey,

It is possible that another driver is really at fault. Since you have
been able to find the .dmp file and analyze it in WinDBG I would recommend
that you enable Driver Verifier and make certain that driver is really at
fault. It is possible another driver has overwritten some memory that
belonged to Pv848.sys so that later when it crashes it looks to be at fault.
Here is how to enable Driver Verifier. If you want to send me the dmp from
verifier you can.


Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me (remove "online") back. Good Luck,
 
Back
Top