BSOD IRQL not equal to or less than...


  1. annonymorse
    Posts : 1
    Cambridgeshire
       New #1

    BSOD IRQL not equal to or less than...


    Hi,

    I've seen a couple of these threads already and updated a few drivers, but Im kind of stabbing in the dark here so hoped you could help me get a little more specific!

    I've started to use this PC for work so its essential I get this sorted!.. but there doesn't appear to be a pattern to the crashes, they just happen to often!

    I've attached what I think to be the right files and my System spec is:

    Windows 7 Professional x64bit - Full retail
    Itel i7 920 @ 2.67Ghz 2.79Ghz (why is there 2 different numbers?)
    6GB Ram
    Computer can only be 1year to 18 months I guess

    Thanks in adevance, hope you can help!

    Cheers

    Tom
      My Computer
    Quote Quote

  3. writhziden
    Posts : 11,269
    Windows 7 Home Premium 64 Bit
       New #2

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


Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\annonymorse\Windows_NT6_BSOD_jcgriff2\010212-26551-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03411000 PsLoadedModuleList = 0xfffff800`03656670
Debug session time: Mon Jan  2 07:54:22.158 2012 (GMT-7)
System Uptime: 0 days 3:57:03.079
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8a012d97a68, 2, 0, fffff880010ea039}

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

2: 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: fffff8a012d97a68, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880010ea039, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c0100
 fffff8a012d97a68 

CURRENT_IRQL:  2

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`010ea039 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:  fffff88002f8b310 -- (.trap 0xfffff88002f8b310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a012d97a48 rbx=0000000000000000 rcx=fffffa8007417d10
rdx=fffffa80063e5070 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010ea039 rsp=fffff88002f8b4a0 rbp=fffffa8004ae0bf8
 r8=fffffa8007b28a80  r9=fffff88002f8b5b8 r10=fffffa8007417d18
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fltmgr!GetContextFromStreamList+0x99:
fffff880`010ea039 488b4820        mov     rcx,qword ptr [rax+20h] ds:bc50:fffff8a0`12d97a68=fffffa80063e5070
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000348d1e9 to fffff8000348dc40

STACK_TEXT:  
fffff880`02f8b1c8 fffff800`0348d1e9 : 00000000`0000000a fffff8a0`12d97a68 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f8b1d0 fffff800`0348be60 : fffff800`03499cec 00000000`0029e993 fffffa80`05c90a28 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f8b310 fffff880`010ea039 : 00000000`00000000 00000000`00000000 fffff880`02f8b550 fffff880`010e9aae : nt!KiPageFault+0x260
fffff880`02f8b4a0 fffff880`010e9cb3 : fffffa80`07417d10 fffffa80`07417d10 fffffa80`0570a1a0 fffffa80`07b28a80 : fltmgr!GetContextFromStreamList+0x99
fffff880`02f8b520 fffff880`028b1ed9 : fffffa80`07417d10 00000000`00000000 fffff880`02f8b5f8 fffff880`0286c8b4 : fltmgr!FltGetStreamHandleContext+0x43
fffff880`02f8b550 fffffa80`07417d10 : 00000000`00000000 fffff880`02f8b5f8 fffff880`0286c8b4 00000000`00000001 : stflt+0x1ed9
fffff880`02f8b558 00000000`00000000 : fffff880`02f8b5f8 fffff880`0286c8b4 00000000`00000001 fffffa80`0570ccc0 : 0xfffffa80`07417d10


STACK_COMMAND:  kb

FOLLOWUP_IP: 
stflt+1ed9
fffff880`028b1ed9 ??              ???

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
---------
    2. 
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\annonymorse\Windows_NT6_BSOD_jcgriff2\010212-19078-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0340d000 PsLoadedModuleList = 0xfffff800`03652670
Debug session time: Mon Jan  2 09:33:02.973 2012 (GMT-7)
System Uptime: 0 days 0:42:18.894
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8a00580c518, 2, 0, fffff880010bc039}

Unable to load image 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
---------

2: 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: fffff8a00580c518, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880010bc039, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036bc100
 fffff8a00580c518 

CURRENT_IRQL:  2

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`010bc039 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:  fffff88002f8b310 -- (.trap 0xfffff88002f8b310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00580c4f8 rbx=0000000000000000 rcx=fffffa8006d35590
rdx=fffffa8006be2770 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880010bc039 rsp=fffff88002f8b4a0 rbp=fffffa8005493d68
 r8=fffffa80076dd6d0  r9=fffff88002f8b5b8 r10=fffffa8006d35598
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fltmgr!GetContextFromStreamList+0x99:
fffff880`010bc039 488b4820        mov     rcx,qword ptr [rax+20h] ds:5c50:fffff8a0`0580c518=fffffa8006be2770
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034891e9 to fffff80003489c40

STACK_TEXT:  
fffff880`02f8b1c8 fffff800`034891e9 : 00000000`0000000a fffff8a0`0580c518 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f8b1d0 fffff800`03487e60 : fffffa80`04da2d80 fffffa80`0637dd88 fffff880`017fd128 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f8b310 fffff880`010bc039 : 00000000`00000000 00000000`00000000 fffff880`02f8b550 fffff880`010bbaae : nt!KiPageFault+0x260
fffff880`02f8b4a0 fffff880`010bbcb3 : fffffa80`06d35590 fffffa80`06d35590 fffffa80`056fd1a0 fffffa80`076dd6d0 : fltmgr!GetContextFromStreamList+0x99
fffff880`02f8b520 fffff880`057d2ed9 : fffffa80`06d35590 00000000`00000000 fffff880`02f8b5f8 fffff880`06ab88b4 : fltmgr!FltGetStreamHandleContext+0x43
fffff880`02f8b550 fffffa80`06d35590 : 00000000`00000000 fffff880`02f8b5f8 fffff880`06ab88b4 00000000`00000001 : stflt+0x1ed9
fffff880`02f8b558 00000000`00000000 : fffff880`02f8b5f8 fffff880`06ab88b4 00000000`00000001 fffffa80`0571a4e0 : 0xfffffa80`06d35590


STACK_COMMAND:  kb

FOLLOWUP_IP: 
stflt+1ed9
fffff880`057d2ed9 ??              ???

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
---------
    3. 
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\annonymorse\Windows_NT6_BSOD_jcgriff2\010212-45895-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03404000 PsLoadedModuleList = 0xfffff800`03649670
Debug session time: Mon Jan  2 09:46:56.802 2012 (GMT-7)
System Uptime: 0 days 0:12:18.723
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8a005514148, 2, 0, fffff8800110e039}

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

2: 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: fffff8a005514148, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800110e039, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b3100
 fffff8a005514148 

CURRENT_IRQL:  2

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`0110e039 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:  fffff88002f8b310 -- (.trap 0xfffff88002f8b310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a005514128 rbx=0000000000000000 rcx=fffffa8004d5aaf0
rdx=fffffa8004d55910 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800110e039 rsp=fffff88002f8b4a0 rbp=fffffa800709d398
 r8=fffffa80079f4d00  r9=fffff88002f8b5b8 r10=fffffa8004d5aaf8
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fltmgr!GetContextFromStreamList+0x99:
fffff880`0110e039 488b4820        mov     rcx,qword ptr [rax+20h] ds:ec50:fffff8a0`05514148=fffffa8004d55910
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034801e9 to fffff80003480c40

STACK_TEXT:  
fffff880`02f8b1c8 fffff800`034801e9 : 00000000`0000000a fffff8a0`05514148 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f8b1d0 fffff800`0347ee60 : fffff800`0348ccec 00000000`00000011 fffffa80`072bffb8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f8b310 fffff880`0110e039 : 00000000`00000000 00000000`00000000 fffff880`02f8b550 fffff880`0110daae : nt!KiPageFault+0x260
fffff880`02f8b4a0 fffff880`0110dcb3 : fffffa80`04d5aaf0 fffffa80`04d5aaf0 fffffa80`0570b1a0 fffffa80`079f4d00 : fltmgr!GetContextFromStreamList+0x99
fffff880`02f8b520 fffff880`011d5ed9 : fffffa80`04d5aaf0 00000000`00000000 fffff880`02f8b5f8 fffff880`016818b4 : fltmgr!FltGetStreamHandleContext+0x43
fffff880`02f8b550 fffffa80`04d5aaf0 : 00000000`00000000 fffff880`02f8b5f8 fffff880`016818b4 fffffa80`05851930 : stflt+0x1ed9
fffff880`02f8b558 00000000`00000000 : fffff880`02f8b5f8 fffff880`016818b4 fffffa80`05851930 fffffa80`07049c10 : 0xfffffa80`04d5aaf0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
stflt+1ed9
fffff880`011d5ed9 ??              ???

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
---------
    4. 
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\annonymorse\Windows_NT6_BSOD_jcgriff2\010312-21091-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03415000 PsLoadedModuleList = 0xfffff800`0365a670
Debug session time: Tue Jan  3 06:36:04.588 2012 (GMT-7)
System Uptime: 0 days 3:51:19.510
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8a00508e618, 2, 0, fffff88001103039}

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

2: 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: fffff8a00508e618, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001103039, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036c4100
 fffff8a00508e618 

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Bridge.exe

TRAP_FRAME:  fffff88002f92540 -- (.trap 0xfffff88002f92540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00508e5f8 rbx=0000000000000000 rcx=fffffa8007ab3d20
rdx=fffffa8007a74a20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001103039 rsp=fffff88002f926d0 rbp=fffffa800533b3c8
 r8=fffffa8007b3d750  r9=fffff88002f927e8 r10=fffffa8007ab3d28
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
fltmgr!GetContextFromStreamList+0x99:
fffff880`01103039 488b4820        mov     rcx,qword ptr [rax+20h] ds:10e0:fffff8a0`0508e618=fffffa8007a74a20
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034911e9 to fffff80003491c40

STACK_TEXT:  
fffff880`02f923f8 fffff800`034911e9 : 00000000`0000000a fffff8a0`0508e618 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f92400 fffff800`0348fe60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f92540 fffff880`01103039 : 00000000`00000000 00000000`00000000 fffff880`02f92780 fffff880`01102aae : nt!KiPageFault+0x260
fffff880`02f926d0 fffff880`01102cb3 : fffffa80`07ab3d20 fffffa80`07ab3d20 fffffa80`0570b1a0 fffffa80`07b3d750 : fltmgr!GetContextFromStreamList+0x99
fffff880`02f92750 fffff880`0389fed9 : fffffa80`07ab3d20 00000000`00000000 fffff880`02f92828 fffff880`0385a8b4 : fltmgr!FltGetStreamHandleContext+0x43
fffff880`02f92780 fffffa80`07ab3d20 : 00000000`00000000 fffff880`02f92828 fffff880`0385a8b4 00000000`00000001 : stflt+0x1ed9
fffff880`02f92788 00000000`00000000 : fffff880`02f92828 fffff880`0385a8b4 00000000`00000001 fffffa80`057294e0 : 0xfffffa80`07ab3d20


STACK_COMMAND:  kb

FOLLOWUP_IP: 
stflt+1ed9
fffff880`0389fed9 ??              ???

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
---------
    5. 
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\annonymorse\Windows_NT6_BSOD_jcgriff2\010612-18018-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03459000 PsLoadedModuleList = 0xfffff800`0369e670
Debug session time: Fri Jan  6 11:48:51.887 2012 (GMT-7)
System Uptime: 0 days 1:09:31.808
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8a001cce048, 2, 0, fffff8800104a039}

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

2: 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: fffff8a001cce048, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800104a039, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003708100
 fffff8a001cce048 

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  Photoshop.exe

TRAP_FRAME:  fffff88002f92540 -- (.trap 0xfffff88002f92540)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a001cce028 rbx=0000000000000000 rcx=fffffa8005afcd70
rdx=fffffa80054aaf20 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800104a039 rsp=fffff88002f926d0 rbp=fffffa80061bb1c8
 r8=fffffa8005c48d00  r9=fffff88002f927e8 r10=fffffa8005afcd78
r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
fltmgr!GetContextFromStreamList+0x99:
fffff880`0104a039 488b4820        mov     rcx,qword ptr [rax+20h] ds:d210:fffff8a0`01cce048=fffffa80073a4af0
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034d51e9 to fffff800034d5c40

STACK_TEXT:  
fffff880`02f923f8 fffff800`034d51e9 : 00000000`0000000a fffff8a0`01cce048 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f92400 fffff800`034d3e60 : fffffa80`070d2480 fffff880`017dbede 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f92540 fffff880`0104a039 : 00000000`00000000 00000000`00000000 fffff880`02f92780 fffff880`01049aae : nt!KiPageFault+0x260
fffff880`02f926d0 fffff880`01049cb3 : fffffa80`05afcd70 fffffa80`05afcd70 fffffa80`057051a0 fffffa80`05c48d00 : fltmgr!GetContextFromStreamList+0x99
fffff880`02f92750 fffff880`02909ed9 : fffffa80`05afcd70 00000000`00000000 fffff880`02f92828 fffff880`028c48b4 : fltmgr!FltGetStreamHandleContext+0x43
fffff880`02f92780 fffffa80`05afcd70 : 00000000`00000000 fffff880`02f92828 fffff880`028c48b4 00000000`00000001 : stflt+0x1ed9
fffff880`02f92788 00000000`00000000 : fffff880`02f92828 fffff880`028c48b4 00000000`00000001 fffffa80`05707cc0 : 0xfffffa80`05afcd70


STACK_COMMAND:  kb

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

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
---------
    You blue screen crashes were all Probably caused by : stflt.sys ( stflt+1ed9 ). I am unable to find any information on what this driver controls. Recommend going into C:\Windows\System32\Drivers and renamed stflt.sys to stflt.sys.bak and see what programs/hardware are affected and then report back.

    Update the following drivers using information from Driver Reference and Drivers and Downloads.
    Code:
    i1display_x64	fffff880`04c9d000	fffff880`04c9ee80	Tue Oct 04 10:43:03 2005 (4342b117)	0000242d		i1display_x64.sys
speedfan	fffff880`01965000	fffff880`0196c000	Sun Sep 24 07:26:48 2006 (45168798)	00005062		speedfan.sys
adfs	fffff880`05472000	fffff880`0548a000	Thu Jun 26 14:52:37 2008 (48640195)	00024203		adfs.SYS
      My Computer
    Quote Quote

 

  Related Discussions
Bsod- irql not less or equal
in BSOD Help and Support

BCCode: a BCP1: 0000000000000008 BCP2: 0000000000000002 BCP3: 0000000000000001 BCP4: FFFFF80002E84438 OS Version: 6_1_7601 Service Pack: 1_0
BSOD - IRQL not less than equal
in BSOD Help and Support

I have been getting this message on and off for a while whenever I play any recent-ish games for 10 minutes or more. Usually I just stop playing and don't really mind but Rome II just came out and I want to play it...lol. Anyway I have uploaded my crash dump, any help will be much appreciated.
BSOD IRQL Not Less Than or Equal
in BSOD Help and Support

Hi, After waking from sleep, my computer seems to cycle through a number of BSOD with the error message IRQL Not Less Than or Equal. While I've received this message with BSODs off and on for the past couple of months, it seems to be increasing in frequency and I'm not sure what the cause is....
BSOD IRQL NO LESS OR Equal
in BSOD Help and Support

Here is the info from the minidump file: 091012-47671-01.dmp 9/10/2012 4:57:27 PM IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x00000000 0x00000002 0x00000001 0x830befb9 TDI.SYS TDI.SYS+60e0 TDI Wrapper Microsoft® Windows® Operating System Microsoft Corporation...
Bsod irql not less or equal
in BSOD Help and Support

Hi everybody, This is my first post and I usually speak french, so sorry if my english isn't really good. I have a BSOD at start up. Sometime, I am able to start windows in Safe mode but not always. My computer is a Gateway and I have the windows that came already in it. My computer is...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 06:28.
Find Us