BSOD issues

[marcgohin]

hi there,

I have a brand new laptop (less than a month old) and I keep getting this blue screen thing come up. My daughter directed me to this forum, and I really hope you can help me out.

Windows 7 home premium 32bit
its the original OS, not changed anything
the whole thing was bought less than a month ago

is it fixable, or should I return it to the shop? your help would be much appreciated.

 

[yowanvista]

A ZoneAlarm software/Firewall was the cause, please remove such software
Turn off driver verifier http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html
Remove AVG and use MSE

AVGIDSDriver.Sys        fffff880`08707000    fffff880`08732000    0x0002b000    0x4da72aa9    14/04/2011 21:11:05                
AVGIDSEH.Sys        fffff880`01ad5000    fffff880`01adf000    0x0000a000    0x4d634838    22/02/2011 09:23:04                
AVGIDSFilter.Sys        fffff880`05636000    fffff880`05641000    0x0000b000    0x4d5370b9    10/02/2011 08:59:37                
avgldx64.sys        fffff880`01b77000    fffff880`01bc6000    0x0004f000    0x4d269857    07/01/2011 08:36:39                
avgmfx64.sys        fffff880`0425c000    fffff880`0426b000    0x0000f000    0x4d6ce5ab    01/03/2011 16:25:15                
avgrkx64.sys        fffff880`01ac9000    fffff880`01ad5000    0x0000c000    0x4d80c3ea    16/03/2011 18:06:34                
avgtdia.sys        fffff880`04320000    fffff880`04380000    0x00060000    0x4d9a3e1b    05/04/2011 01:54:35

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

Use !analyze -v to get detailed debugging information.

BugCheck C4, {91, 2, fffff80002ff5cc0, 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 )


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: fffff80002ff5cc0
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 fffff80002ec8ada to fffff80002e6c580

STACK_TEXT:  
fffff800`00b96fc8 fffff800`02ec8ada : 00000000`000000c4 00000000`00000091 00000000`00000002 fffff800`02ff5cc0 : nt!KeBugCheckEx
fffff800`00b96fd0 fffff800`02e13e45 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4814
fffff800`00b97010 fffff800`02e14209 : fffff800`00b97000 fffff800`00b9d000 00000000`00000000 00000000`00000000 : nt!RtlEnoughStackSpaceForStackCapture+0x15
fffff800`00b97040 fffff800`02f32ccb : 00000000`00000001 fffffa80`08965f10 fffff800`00b97170 00000000`00000000 : nt!RtlWalkFrameChain+0x59
fffff800`00b97070 fffff880`02e9825c : fffffa80`08965f00 fffff880`02eeb110 00000000`00000002 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x4b
fffff800`00b970a0 fffffa80`08965f00 : fffff880`02eeb110 00000000`00000002 00000000`00000000 00000000`00000000 : vsdatant+0x1125c
fffff800`00b970a8 fffff880`02eeb110 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`08965f00
fffff800`00b970b0 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vsdatant+0x64110
fffff800`00b970b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2


STACK_COMMAND:  kb

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

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
---------

 

[marcgohin]

Thank you very much for your help. I am going to start doing all that. Hoping it will fix the issue.