BSOD on sleep


  1. Posts : 8,679
    Windows 10 Pro x64
       #1

    BSOD on sleep


    Hello people,this dump file is not mine,it's from one member from Macedonian forum. So if BSOD Squad can help him... :)

    Attachment 177403

    User has do sfc/scannow and no errors were found. Also he has reinstalled latest Realtek drivers for NIC.

    Cheers, StalkeR.
      My Computer


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

    The Realtek NIC driver is the cause, it should be updated
    Realtek

    Old Driver, incompatible with Windows 7
    Code:
    TVicHW64.sys        fffff880`09978000    fffff880`09980000    0x00008000    0x43489764    09/10/2005 08:07:00
    The software/device using it should be removed


    Any CD virtualization programs such as Daemon Tools and Alcohol 120% should be removed. They use a driver, found in the dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
    MagicDisc can be used as an alternative.
    Code:
    sptd.sys        fffff880`010b8000    fffff880`011de000    0x00126000    0x4ad24632    12/10/2009 00:55:14
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8003acb060, fffff80000b9c4d8, fffffa800418fe10}
    
    *** WARNING: Unable to verify timestamp for Rt64win7.sys
    *** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
    Probably caused by : Rt64win7.sys
    
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver is causing an inconsistent power state.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8003acb060, Physical Device Object of the stack
    Arg3: fffff80000b9c4d8, Functional Device Object of the stack
    Arg4: fffffa800418fe10, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IRP_ADDRESS:  fffffa800418fe10
    
    DEVICE_OBJECT: fffffa8005f3e050
    
    DRIVER_OBJECT: fffffa8005f40060
    
    IMAGE_NAME:  Rt64win7.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4df1baab
    
    MODULE_NAME: Rt64win7
    
    FAULTING_MODULE: fffff880044f7000 Rt64win7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002aebcd2 to fffff80002a7dc40
    
    STACK_TEXT:  
    fffff800`00b9c488 fffff800`02aebcd2 : 00000000`0000009f 00000000`00000003 fffffa80`03acb060 fffff800`00b9c4d8 : nt!KeBugCheckEx
    fffff800`00b9c490 fffff800`02a895fc : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`00b9c530 fffff800`02a89496 : fffff800`02c28f00 00000000`00023ec1 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c5a0 fffff800`02a8937e : 00000005`5a52644a fffff800`00b9cc18 00000000`00023ec1 fffff800`02bf7aa8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cbf0 fffff800`02a89167 : 00000001`dda8f5c1 00000001`00023ec1 00000001`dda8f525 00000000`000000c1 : nt!KiTimerExpiration+0x1be
    fffff800`00b9cc90 fffff800`02a7596a : fffff800`02bf3e80 fffff800`02c01cc0 00000000`00000000 fffffa80`039970a0 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys
    
    BUCKET_ID:  X64_0x9F_IMAGE_Rt64win7.sys
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 8,679
    Windows 10 Pro x64
    Thread Starter
       #3

    Thanks for answering Yowan. I send this info to the member and we'll see what will he do. :)
    Thanks,StalkeR
      My Computer


  4. Posts : 8,679
    Windows 10 Pro x64
    Thread Starter
       #4

    I also said that with the Realteck driver,I checked the dump file before,but I want to check some whos much better in that from me. :)

    Today I got PM from that member,and he said that haved again BSOD when he put pc on sleep. He told me then when he check the dump file with Blue Screen View it says that its caused by ntoskrnl.exe.

    Here is the file.
    Attachment 178264
      My Computer


  5. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #5

    Boshko,

    This crash is the same as the last one & is related to Rt64win7.sys 8101E/8168/8169 NDIS 6.20 64-bit Driver from Realtek Corporation.
    I suggest it be re-installed with the newest version available.


    These drivers need updating
    Code:
    RTCore64.sys    5/25/2005 5:39:12 PM        fffff880`09eac000    fffff880`09eb2000    0x00006000    0x42941d90                        
    TVicHW64.sys    10/9/2005 3:07:00 PM        fffff880`09978000    fffff880`09980000    0x00008000    0x43489764                        
    ElRawDsk.sys    7/27/2008 4:59:09 AM        fffff880`043e5000    fffff880`043ef000    0x0000a000    0x488b65ed                        
    MTiCtwl.sys    11/4/2008 6:40:50 PM        fffff880`019a8000    fffff880`019b1000    0x00009000    0x490ffc82                        
    ALSysIO64.sys    4/20/2009 6:41:04 AM        fffff880`09ea4000    fffff880`09eac000    0x00008000    0x49eb7e50                        
    intelsmb.sys    5/13/2009 6:31:00 PM        fffff880`03ed0000    fffff880`03edf880    0x0000f880    0x4a0a7734                        
    SaiMini.sys    6/3/2009 9:09:18 PM        fffff880`04f21000    fffff880`04f24e80    0x00003e80    0x4a264bce                        
    SaiBus.sys    6/3/2009 9:09:19 PM        fffff880`042e8000    fffff880`042f2900    0x0000a900    0x4a264bcf
    How To Find Drivers:
    - search Google for the name of the driver
    - compare the Google results with what's installed on your system to figure out which device/program it belongs to
    - visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
    - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
    - - The most common drivers are listed on this page: Driver Reference Driver Reference
    - - Driver manufacturer links are on this page: Drivers and Downloads
      My Computer


  6. Posts : 8,679
    Windows 10 Pro x64
    Thread Starter
       #6

    Jan,thanks for answering on thread. I send this post to the member,and I'm now waiting for reply. When he will answer to my I'll post it here.
      My Computer


  7. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #7

    Noted.
    Thanks!
      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 08:12.
Find Us