Windows 7 IRQL not less or equal blue screen :(

barbez said:

Hi, since 6 months i've been using windows 7 (64 bit) i've never had a blue screen... Now I cant even use windows normally, after 10 seconds looking at my desktop wallpaper, i get the bsod...
The only thing that changed lately was that i installed a second midipatcher from M-audio. Now i unistalled both devices and the bsod still happens...

so my system:
win 7 64 bit
original install, 6 months old

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 2067

Additional information about the problem:
BCCode: a
BCP1: 0000000000000000
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF80002AC1F0E
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


Please help!!

Hi barbez and welcome

This crash was caused by your Symantec endpoint driver (SRTSPL64.SYS). It is a known problem maker. I would remove it and use Microsoft Security Essentials in its place.

I also noticed many drivers that were old enough to need updating. See the list below.

Code:

fffff880`02c0d000 fffff880`02c1f000   wpsdrvnt wpsdrvnt.sys Fri May 09 19:52:51 2008 (4824E3D3)
fffff880`03e33000 fffff880`03e47000   SRTSPX64 SRTSPX64.SYS Thu Mar 20 13:18:06 2008 (47E29C4E)
fffff880`03ff1000 fffff880`03ff8000   AsIO     AsIO.sys     Mon Dec 17 04:11:49 2007 (47663D55)
fffff880`04a00000 fffff880`04a3d000   teefer2  teefer2.sys  Wed Mar 12 18:19:41 2008 (47D856FD)
fffff880`06c00000 fffff880`06c18000   adfs     adfs.SYS     Thu Jun 26 16:52:37 2008 (48640195)
fffff880`08881000 fffff880`088b7000   SYMEVENT64x86 SYMEVENT64x86.SYS Mon Jan 14 18:32:19 2008 (478BF103)
fffff880`02c0d000 fffff880`02c1f000   wpsdrvnt wpsdrvnt.sys Fri May 09 19:52:51 2008 (4824E3D3)

Let us know if you need further assistance.


Jan

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\072110-31824-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Wed Jul 21 02:19:00.276 2010 (GMT-4)
System Uptime: 0 days 0:02:44.432
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002ac1f0e}

Unable to load image \SystemRoot\System32\Drivers\SRTSPL64.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SRTSPL64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSPL64.SYS
Probably caused by : SRTSPL64.SYS ( SRTSPL64+30f27 )

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

4: 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: 0000000000000001, 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: fffff80002ac1f0e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0d0e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExDeleteResourceLite+ce
fffff800`02ac1f0e 488908          mov     qword ptr [rax],rcx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003369680 -- (.trap 0xfffff88003369680)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ac1f0e rsp=fffff88003369810 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff8800880fb80
r11=0000000000000163 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!ExDeleteResourceLite+0xce:
fffff800`02ac1f0e 488908          mov     qword ptr [rax],rcx ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ad4b69 to fffff80002ad5600

STACK_TEXT:  
fffff880`03369538 fffff800`02ad4b69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`03369540 fffff800`02ad37e0 : fffff880`03369710 fffff880`08818130 00000980`00000000 0000007f`fffffff8 : nt!KiBugCheckDispatch+0x69
fffff880`03369680 fffff800`02ac1f0e : 00000000`0000001c fffffa80`088d6500 ffffffff`80001db0 00000000`00000001 : nt!KiPageFault+0x260
fffff880`03369810 fffff880`08830f27 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000018 : nt!ExDeleteResourceLite+0xce
fffff880`03369870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000018 00000000`00000000 : SRTSPL64+0x30f27


STACK_COMMAND:  kb

FOLLOWUP_IP: 
SRTSPL64+30f27
fffff880`08830f27 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  SRTSPL64+30f27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SRTSPL64

IMAGE_NAME:  SRTSPL64.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  47e29afc

FAILURE_BUCKET_ID:  X64_0xA_SRTSPL64+30f27

BUCKET_ID:  X64_0xA_SRTSPL64+30f27

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

Good advice Jan.

barbez- be sure to use this Semantec removal tool: ftp://ftp.symantec.com/public/englis...moval_Tool.exe

You should still run the removal tool to clean up the leftover registry entries and files that the uninstaller didn't delete.

Your choice, I'm not going to make a big deal of it if you don't want to.