BSoD problem w/video

[BeeDee]

I am now getting BSoD when watching videos.
That seems to be the initiating factor. (also when using Wifi adapter for Internet access -- separate (seemingly known) issue)
Both YouTube in Firefox and non-browser viewing and NetFlix.
It seems to be any type of video format or player.
It used to work fine.
I haven't been able to figure out if it started after any certain software install or
Windows Update upgrade.
Note: uploaded BSoD.zip was a .7Z file, renamed.
Thanks.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? 64bit
- the original installed OS on the system? original
- an OEM or full retail version? Full retail as purchased
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer

- What is the age of system (hardware)? About a year
- What is the age of OS installation (have you re-installed the OS?) Original

 

[fimble]

Hi BeeDee and Welcome.

Your dump files all give a stop error of 0x7F. Its a stop error that ZoneAlarm firewall gives frequently. You have two (?) options:

ZoneAlarm Security and Firewall is known to be a cause of BSOD's on many Windows 7 systems. Download the ZoneAlarm Remover. Uninstall ZoneAlarm through Programs and Features. Boot to safe mode and run the ZoneAlarm Remover. Reboot. Make sure that Windows Firewall is enabled.
Alternatively
Try this Microsoft hotfix if you wish to keep ZoneAlarm: Stop Error 0x07F when you run applications that transfer data using the UDP protocol in Win Server 2008 R2/Win 7" which I can neither verify or discount. It may work, it may not.

Bugcheck Analysis

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002cdc05f

Debugging Details:
------------------

BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002cd5ca9 to fffff80002cd6740

STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02cd4172 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
---------

0: kd> lmvm [COLOR=red][B]vsdatant[/B][/COLOR]
start             end                 module name
fffff880`03b1a000 fffff880`03baf000   vsdatant   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\vsdatant.sys
    Image name: vsdatant.sys
    Timestamp:        Sun May 09 17:28:58 2010 (4BE6E2CA)
    CheckSum:         0007FD21
    ImageSize:        00095000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Old and outdated drivers can cause problems that do not point directly to them and should be updated.
I'll check your latest dump file for any other outdated drivers that may cause future problems.

 

[fimble]

Outdated Drivers:

DKbFltr.sys Thu Mar 26 03:15:42 2009 Dritek Keyboard Filter driver

iaStor.sys Fri Jun 05 02:53:40 2009 Intel Storage.

k57nd60a.sys Thu Aug 06 12:44:32 2009 Broadcom Ethernet

NTIDrvr.sys Wed Mar 25 03:09:39 2009 NTI CD-ROM Filter Drivers by NewTech. See OEM
UBHelper.sys Mon Apr 27 09:48:19 2009 NTI CD-ROM or NTI Backup NOW! See OEM

PxHlpa64.sys Thu Mar 13 01:58:17 2008 Sonic CD/DVD driver. Used by many different programs. See OEM

 

[BeeDee]

Thank you

Is Windows Firewall safe to use?

 

[BeeDee]

It seems to have fixed the problem. Thank you.

Is this the same problem that was occurring when I was trying to use the WiFi Internet connection?

 

[DeanP]

Is Windows Firewall safe to use?

Yes

 

[Maguscreed]

It seems to have fixed the problem. Thank you.

Is this the same problem that was occurring when I was trying to use the WiFi Internet connection?

It could have been ZA it could be the outdated drivers, but yes, it's very likely the problems were related to the above information.