Windows 7: Random BSOD, DRIVER_IRQL_NOT_LESS_OR_EQUAL fltmgr.sys and ntoskrnl.exe

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


Loading Dump File [D:\Users\SP1\Desktop\121011-28485-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`0324f670
Debug session time: Sat Dec 10 03:30:51.734 2011 (UTC - 5:00)
System Uptime: 1 days 6:20:07.123
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8a01683dac8, 2, 0, fffff88001326039}

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

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff8a01683dac8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001326039, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b9100
 fffff8a01683dac8 

CURRENT_IRQL:  2

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`01326039 488b4820        mov     rcx,qword ptr [rax+20h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800311b420 -- (.trap 0xfffff8800311b420)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a01683daa8 rbx=0000000000000000 rcx=fffffa80084dd3c0
rdx=fffffa8004c8ef20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001326039 rsp=fffff8800311b5b0 rbp=fffffa8004c79638
 r8=fffffa800971eb90  r9=fffff8800311b6c8 r10=fffffa80084dd3c8
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fltmgr!GetContextFromStreamList+0x99:
fffff880`01326039 488b4820        mov     rcx,qword ptr [rax+20h] ds:0002:fffff8a0`1683dac8=fffffa8004c8ef20
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030861e9 to fffff80003086c40

STACK_TEXT:  
fffff880`0311b2d8 fffff800`030861e9 : 00000000`0000000a fffff8a0`1683dac8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0311b2e0 fffff800`03084e60 : 00000000`00000001 fffff800`03093241 fffff880`019fb128 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0311b420 fffff880`01326039 : 00000000`00000000 00000000`00000000 fffff880`0311b660 fffff880`01325aae : nt!KiPageFault+0x260
fffff880`0311b5b0 fffff880`01325cb3 : fffffa80`084dd3c0 fffffa80`084dd3c0 fffffa80`04c79530 fffffa80`0971eb90 : fltmgr!GetContextFromStreamList+0x99
fffff880`0311b630 fffff880`08270ed9 : fffffa80`084dd3c0 00000000`00000000 fffff880`0311b708 fffff880`0311b708 : fltmgr!FltGetStreamHandleContext+0x43
fffff880`0311b660 fffffa80`084dd3c0 : 00000000`00000000 fffff880`0311b708 fffff880`0311b708 00000000`00000000 : stflt+0x1ed9
fffff880`0311b668 00000000`00000000 : fffff880`0311b708 fffff880`0311b708 00000000`00000000 fffff800`0308cfda : 0xfffffa80`084dd3c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
stflt+1ed9
fffff880`08270ed9 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  stflt+1ed9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: stflt

IMAGE_NAME:  stflt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c2b57fc

FAILURE_BUCKET_ID:  X64_0xD1_stflt+1ed9

BUCKET_ID:  X64_0xD1_stflt+1ed9

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