Windows 7 Home Premium BSODs

Welcome!

It looks a lot like your anti-virus ZoneAlarm is causing the problem. I strongly recommend uninstalling the program completely, using the free program Revo Uninstaller.

You still need a good anti-virus though. I recommend the free A/V Microsoft Security Essentials.

   Note

You may need to uninstall ZoneAlarm in Safe Mode, if you can't do it in normal mode. If you need to do a system restore, do one, and immediately uninstall.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\031210-22916-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c16000 PsLoadedModuleList = 0xfffff800`02e53e50
Debug session time: Thu Mar 11 19:39:24.250 2010 (GMT-5)
System Uptime: 0 days 0:06:06.918
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffff80002e0ec40, 0}

Unable to load image \SystemRoot\system32\DRIVERS\vsdatant.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+10997 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
    the operating system. The only supported way to extend a kernel
    mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000002
Arg3: fffff80002e0ec40
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002cde8fa to fffff80002c87f00

STACK_TEXT:  
fffff800`00b96e68 fffff800`02cde8fa : 00000000`000000c4 00000000`00000091 00000000`00000002 fffff800`02e0ec40 : nt!KeBugCheckEx
fffff800`00b96e70 fffff800`02c26575 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4944
fffff800`00b96eb0 fffff800`02c26929 : fffff800`00b97000 fffff800`00b9d000 00000000`00000000 00000000`00000000 : nt!RtlEnoughStackSpaceForStackCapture+0x15
fffff800`00b96ee0 fffff800`02d49bcb : 00000000`00000001 fffffa80`05da4190 fffff800`00b96fc0 00000000`00000000 : nt!RtlWalkFrameChain+0x59
fffff800`00b96f10 fffff880`03b52997 : 00000000`00000001 fffff880`03ba4110 fffff800`00b97c50 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x4b
fffff800`00b96f40 00000000`00000001 : fffff880`03ba4110 fffff800`00b97c50 00000000`00000000 00000000`00000000 : vsdatant+0x10997
fffff800`00b96f48 fffff880`03ba4110 : fffff800`00b97c50 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1
fffff800`00b96f50 fffff800`00b97c50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vsdatant+0x62110
fffff800`00b96f58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`00b97c50


STACK_COMMAND:  kb

FOLLOWUP_IP: 
vsdatant+10997
fffff880`03b52997 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  vsdatant+10997

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vsdatant

IMAGE_NAME:  vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b09cb48

FAILURE_BUCKET_ID:  X64_0xc4_91_vsdatant+10997

BUCKET_ID:  X64_0xc4_91_vsdatant+10997

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

Thanks, I've took ZoneAlarm off. I only had that as my firewall though, been using avast free for AV. Am I ok to just use avast with windows firewall instead of getting MSE? Don't like to put all my eggs in one basket if you know what i mean...


edit: Also was wondering could it be that it's because something is trying to get through the firewall that was causing the BSOD?

Either way you put it, ZoneAlarm is crashing your computer. Who knows exactly what was happening, but the bottom line is it was.

Feel free to use Avast. I was just giving my personal favorite.

I've heard Comodo is a good free firewall, if you're interested. Personally, I just use the Windows firewall, though.