BSOD when going to sleep


  1. Posts : 2
    Windows 7 Home Premium 64 bit
       #1

    BSOD when going to sleep


    Hey guys.
    Whenever I put my computer to sleep I get a BSOD.

    Windows declares the following:


    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.768.3
    Locale ID: 1033

    Additional information about the problem:
    BCCode: d1
    BCP1: FFFFF8A0040DE828
    BCP2: 0000000000000002
    BCP3: 0000000000000000
    BCP4: FFFFF88001118039
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 768_1

    Files that help describe the problem:
    C:\Windows\Minidump\082111-7956-01.dmp
    C:\Users\Ben\AppData\Local\Temp\WER-17222-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt


    BlueScreenView says:
    Dump File: 082111-7956-01.dmp
    Crash Time: 8/21/2011 12:44:47 AM
    Bug Check String: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code: 0x000000d1
    Caused By Driver: fltmgr.sys
    Caused By Address: fltmgr.sys+5039
    Processor: x64
    Crash Address: ntoskrnl.exe+7cc40
    Full Path: C:\Windows\Minidump\082111-7956-01.dmp
    Processors Count: 8
    Major Version: 15
    Minor Version: 7601
    Dump File Size: 284,616


    My PC is running Windows 7 Home Premium.
    I'm using an Intel Core 2600-K.
    My motherboard is an Asus P8P67 Pro.
    My graphics card is a GTX Geforce 580.

    I feel like the motherboard plays a role in this because I was installing features + drivers from the disk it came with right around when this started happening.
    I thought it was the motherboard's internal bluetooth that was causing the problem because the drivers wouldn't install completely, so I uninstalled bluetooth. After that, I was actually able to put the computer to sleep multiple times throughout a (maybe) 2 hour period before the BSOD came back.

    I appreciate any assistance you all can give me.

    Thanks,

    Ben
      My Computer


  2. Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       #2

    BSODs caused by Spyware Terminator, please remove this program
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff8a0040de828, 2, 0, fffff88001118039}
    
    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 )
    
    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: fffff8a0040de828, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88001118039, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c7100
     fffff8a0040de828 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    fltmgr!GetContextFromStreamList+99
    fffff880`01118039 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:  fffff80000b9c310 -- (.trap 0xfffff80000b9c310)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8a0040de808 rbx=0000000000000000 rcx=fffffa8009fd1f50
    rdx=fffffa800b105d50 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88001118039 rsp=fffff80000b9c4a0 rbp=fffffa8006a9ede8
     r8=fffffa800b5cc920  r9=fffff80000b9c5b8 r10=fffffa8009fd1f58
    r11=0000000000000011 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    fltmgr!GetContextFromStreamList+0x99:
    fffff880`01118039 488b4820        mov     rcx,qword ptr [rax+20h] ds:fffff8a0`040de828=fffffa8006c35640
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030941e9 to fffff80003094c40
    
    STACK_TEXT:  
    fffff800`00b9c1c8 fffff800`030941e9 : 00000000`0000000a fffff8a0`040de828 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`00b9c1d0 fffff800`03092e60 : fffffa80`096870a0 00000000`00007e31 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c310 fffff880`01118039 : 00000000`00000000 00000000`00000000 fffff800`00b9c550 fffff880`01117aae : nt!KiPageFault+0x260
    fffff800`00b9c4a0 fffff880`01117cb3 : fffffa80`09fd1f50 fffffa80`09fd1f50 00000000`00000002 fffffa80`0b5cc920 : fltmgr!GetContextFromStreamList+0x99
    fffff800`00b9c520 fffff880`06d07ed9 : fffffa80`09fd1f50 00000000`00000000 fffff800`00b9c5f8 fffff800`03608b7f : fltmgr!FltGetStreamHandleContext+0x43
    fffff800`00b9c550 fffffa80`09fd1f50 : 00000000`00000000 fffff800`00b9c5f8 fffff800`03608b7f 00000000`00000000 : stflt+0x1ed9
    fffff800`00b9c558 00000000`00000000 : fffff800`00b9c5f8 fffff800`03608b7f 00000000`00000000 fffffa80`06aa3d30 : 0xfffffa80`09fd1f50
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    stflt+1ed9
    fffff880`06d07ed9 ??              ???
    
    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
    ---------
      My Computer


  3. Posts : 2
    Windows 7 Home Premium 64 bit
    Thread Starter
       #3

    Thank you so much!
    It seems to work perfectly again.
      My Computer


 

  Related Discussions
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 02:18.
Find Us