Intermittent Blue Screens

[BeastPanda]

Hi,
I have recently installed new ram (which passed memtest86+ on both sticks and in parallel operation) but now I am plagued with seemingly intermittent blue screens. I'm not sure if the problem is the new ram or if coincidentally something else is popping up as a result of the installation. The guys at G.Skill are convinced their ram is not at fault so I thought I would post over here and see if anyone has any suggestions.

My windows 7 is 64 bit and is not the original OS installed on this system. The system is about 3 years old and the OS installation is about 1 year old.

I have attached the files as instructed.

Awesome. Thanks for all the help!

 

[zigzag3143]

Hi,
I have recently installed new ram (which passed memtest86+ on both sticks and in parallel operation) but now I am plagued with seemingly intermittent blue screens. I'm not sure if the problem is the new ram or if coincidentally something else is popping up as a result of the installation. The guys at G.Skill are convinced their ram is not at fault so I thought I would post over here and see if anyone has any suggestions.

My windows 7 is 64 bit and is not the original OS installed on this system. The system is about 3 years old and the OS installation is about 1 year old.

I have attached the files as instructed.

Awesome. Thanks for all the help!

Doing the ten now.


Right off the bat I spotted one huge problem

1-ASACPI.sys

ASACPI.sys        fffff880`03e5d000    0x00008000    3/27/2005 21:30:36            0x42476c4c    fffff880`03e55000

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

2-vfilter.sys -- part of your vpn client. Replace or re-install at least.

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\111610-22343-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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02814000 PsLoadedModuleList = 0xfffff800`02a51e50
Debug session time: Tue Nov 16 22:20:20.739 2010 (GMT-5)
System Uptime: 0 days 0:40:35.411
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 0, fffff800028888b6}

Unable to load image \SystemRoot\system32\DRIVERS\vfilter.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for vfilter.sys
[COLOR=Red][B]Probably caused by : vfilter.sys ( vfilter+29a6 )[/B][/COLOR]

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800028888b6, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002abc0e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeSetEvent+226
fffff800`028888b6 488b09          mov     rcx,qword ptr [rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  fffff88006fa0c60 -- (.trap 0xfffff88006fa0c60)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800657d898 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800028888b6 rsp=fffff88006fa0df0 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe cy
nt!KeSetEvent+0x226:
fffff800`028888b6 488b09          mov     rcx,qword ptr [rcx] ds:0002:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002883ca9 to fffff80002884740

STACK_TEXT:  
fffff880`06fa0b18 fffff800`02883ca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`06fa0b20 fffff800`02882920 : fffff800`02a13bc0 fffffa80`0657d890 00000000`00000000 fffff880`0140ae00 : nt!KiBugCheckDispatch+0x69
fffff880`06fa0c60 fffff800`028888b6 : fffff880`06fa0e60 fffff880`02d59b0e 00000000`0000004f fffff880`06fa0ee0 : nt!KiPageFault+0x260
fffff880`06fa0df0 fffff880`02d599a6 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0657d880 : nt!KeSetEvent+0x226
fffff880`06fa0e60 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0657d880 00000000`00000000 : vfilter+0x29a6
fffff880`06fa0e68 00000000`00000000 : 00000000`00000000 fffffa80`0657d880 00000000`00000000 fffff880`02d5942b : 0xfffffa80`00000000


STACK_COMMAND:  kb

FOLLOWUP_IP: 
vfilter+29a6
fffff880`02d599a6 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  vfilter+29a6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vfilter

IMAGE_NAME:  vfilter.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b048bff

FAILURE_BUCKET_ID:  X64_0xA_vfilter+29a6

BUCKET_ID:  X64_0xA_vfilter+29a6

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

3-NETIO.SYS--- Often when this causes crashes it is from Zone Alarm. If ZAP is installed remove and replace with Microsoft Security Essentials and the win 7 firewall.

http://download.zonealarm.com/bin/free/support/cpes_clean.exe

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

 

[BeastPanda]

Hello,
I believe I have implemented the changes suggested in the previous post. I have not had a random blue screen crash but I have had one instance of windows 7 not starting properly and getting stuck on the "starting windows" screen. I restarted and I did not have any problems after that. I thought I would post over here again and see if anyone has any suggestions.

I have attached the files again.

Thanks!

 

[BeastPanda]

And.. I lied. I got another blue screen today.
I have attached the most recent mini dump.
Any help will be appreciated! Thanks!

 

[Jonathan_King]

Hello,

Try removing ShrewSoft VPN Client, and see how things go.

...Summary of the dumps

[FONT=lucida console]Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Nov 22 22:32:43.197 2010 (UTC - 5:00)
System Uptime: 0 days 2:44:27.916
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xA_vfilter+29a6
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]