View Single Post
26 May 2011  
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by jc210 View Post
Hi,

Run into a problem recently on a relatively new laptop suddenly blue screening and restarting, seems to work fine after restarting, but it did happen twice in an afternoon. Seems to have started since I began bringing it into work and might have something to do with installing a wireless authentication program (SecureW2).

Other than that I don't know. Please help.

If you need any more info, let me know.

Thanks

These were driver verified and related to Zone Alarm. I would remove it and use Microsoft Security Essentials and the win 7 firewall.


http://download.zonealarm.com/bin/fr...cpes_clean.exe

http://www.microsoft.com/security_essentials/


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\052611-18189-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`0364b000 PsLoadedModuleList = 0xfffff800`03888e50
Debug session time: Thu May 26 05:39:00.649 2011 (GMT-4)
System Uptime: 0 days 1:20:20.038
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffffa80042a2060, 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+1125c )

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: fffffa80042a2060
Arg4: 0000000000000000

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


BUGCHECK_STR:  0xc4_91

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000371032a to fffff800036bb700

STACK_TEXT:  
fffff800`00b9ce88 fffff800`0371032a : 00000000`000000c4 00000000`00000091 00000000`00000002 fffffa80`042a2060 : nt!KeBugCheckEx
fffff800`00b9ce90 fffff800`0365b579 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4894
fffff800`00b9ced0 fffff800`0365b95d : fffff880`0d0b7000 fffff880`0d0be000 00000000`00000000 00000000`00000000 : nt!RtlEnoughStackSpaceForStackCapture+0x15
fffff800`00b9cf00 fffff800`0377eb2b : 00000000`00000001 fffffa80`06c30090 fffff800`00b9d030 00000000`00000000 : nt!RtlWalkFrameChain+0x59
fffff800`00b9cf30 fffff880`02eb325c : fffffa80`06c30080 fffff880`02f06110 00000000`00000002 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x4b
fffff800`00b9cf60 fffffa80`06c30080 : fffff880`02f06110 00000000`00000002 00000000`00000000 00000000`00000000 : vsdatant+0x1125c
fffff800`00b9cf68 fffff880`02f06110 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`06c30080
fffff800`00b9cf70 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vsdatant+0x64110
fffff800`00b9cf78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
vsdatant+1125c
fffff880`02eb325c ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  vsdatant+1125c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vsdatant

IMAGE_NAME:  vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4be6e2ca

FAILURE_BUCKET_ID:  X64_0xc4_91_vsdatant+1125c

BUCKET_ID:  X64_0xc4_91_vsdatant+1125c

Followup: MachineOwner
---------
My System SpecsSystem Spec