BSOD when attaching IPOD and other occasions since


  1. Posts : 1
    Windows 7 64bit
       #1

    BSOD when attaching IPOD and other occasions since


    Hi there,

    My laptop has recently given me a few BSOD's. The first occured when I attached an iPod to charge and it completely crashed. Then today it has crashed 3 times, all of which occured when I was not doing anything out of the ordinary.

    I have uploaded the SF Diagnostic report as per forum guidelines.

    If anyone can shed some light on the issue for me I would really appreciate it.

    John
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Security App
    Code:
    ENG64.SYS                   Thu Dec 20 15:24:21 2012 (50D2D945)
    ETD.sys                     Wed Apr 13 13:01:46 2011 (4DA54A5A)
    EX64.SYS                    Thu Dec 20 15:22:39 2012 (50D2D8DF)
    ElbyCDIO.sys                Fri Dec 17 04:58:13 2010 (4D0A9985)
    EraserUtilDrv11220.sys      Wed Aug  1 05:36:50 2012 (50186C12)
    EraserUtilRebootDrv.sys     Wed Aug  1 05:36:50 2012 (50186C12)
    HECIx64.sys                 Tue Sep 21 22:59:04 2010 (4C98E458)
    IDSvia64.sys                Wed Aug 29 08:48:40 2012 (503D8308)
    SRTSP64.SYS                 Tue Jul  3 00:20:28 2012 (4FF1E66C)
    SRTSPX64.SYS                Tue Jul  3 00:20:37 2012 (4FF1E675)
    SYMDS64.SYS                 Tue May 17 04:15:03 2011 (4DD1A1E7)
    SYMEFA64.SYS                Sat May 19 07:29:56 2012 (4FB6F794)
    SYMEVENT64x86.SYS           Tue Jan 24 00:57:54 2012 (4F1DADB2)
    SymIMv.sys                  Sun Nov 13 03:08:22 2011 (4EBEE046)
    SYMNETS.SYS                 Sun Nov 13 03:11:53 2011 (4EBEE119)
    Crashes indicate Norton being a possible cause. Remove Norton and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software
    Code:
    SpybotSD TeaTimer	c:\program files (x86)\spybot - search & destroy\teatimer.exe	lovelynewlappy\lovely new lappy	HKU\S-1-5-21-903429074-2643081801-4049092473-1001\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
    If it were my pc I would not use Spybot on windows 7. It is known to corrupt the system.

    Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

    Microsoft Security Essentials, Free antivirus for windows

    Malwarebytes Anti-Malware Free

       Information
    DO NOT start the free trial of MalwareBytes. Deselect the option when prompted.

       Tip
    Make full scans with both separately.

    Scan your system with the following:

    Kaspersky TDSSKiller - How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)

    ESET online scanner - One-time virus scanner free with ESET online scanner

    This tutorial USB Selective Suspend - Turn On or Off may help you:

    To Disable Selective Suspend:

    Code:
    1. open the control panel
    2. go to power options (you may have to set view to small icons)
    3. click change plan settings
    4. in the window that opens:
    5. click change plan settings
    6. click change advanced power settings, expand usb and ensure usb selective suspend is disabled.
    Start up
    Keep less stuff at the start-up. Only anti-virus, this helps avoid driver conflicts and improves time to log in to windows.

    Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista
    How to Change, Add, or Remove Startup Programs in Windows 7

    I would also perform Clean Up Factory Bloatware
    Code:
    Start Menu\Programs\ASUS	Public:Start Menu\Programs\ASUS	Public
    Start Menu\Programs\ASUS\ASUS WebStorage	Public:Start Menu\Programs\ASUS\ASUS WebStorage	Public
    Start Menu\Programs\ASUS\AsusVibe	Public:Start Menu\Programs\ASUS\AsusVibe	Public
    Start Menu\Programs\ASUS Utility	Public:Start Menu\Programs\ASUS Utility	Public
    Start Menu\Programs\ASUS Utility\ASUS Splendid Utility	Public:Start Menu\Programs\ASUS Utility\ASUS Splendid Utility	Public
    Start Menu\Programs\ASUS Utility\SmartLogon	Public:Start Menu\Programs\ASUS Utility\SmartLogon	Public
    Basic checks: Please run these tests and report back the results

    1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
    2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
    3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
    4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
    5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

    That's all for now, good luck.

    BSOD BUGCHECK SUMMARY
    Code:
    Debug session time: Sat May 18 06:35:07.841 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\051713-32604-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 0:31:41.731
    *** WARNING: Unable to verify timestamp for RtsUVStor.sys
    *** ERROR: Module load completed but symbols could not be loaded for RtsUVStor.sys
    Probably caused by : usbhub.sys
    BugCheck 9F, {3, fffffa800c0bd060, fffff800047203d8, fffffa800ee48bd0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Bugcheck code 0000009F
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800c0bd060, Physical Device Object of the stack
    Arg3: fffff800047203d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800ee48bd0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_RtsUVStor_IMAGE_usbhub.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Sat May 18 05:01:21.085 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\051713-33243-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 0:16:12.600
    *** WARNING: Unable to verify timestamp for RtsUVStor.sys
    *** ERROR: Module load completed but symbols could not be loaded for RtsUVStor.sys
    Probably caused by : usbhub.sys
    BugCheck 9F, {3, fffffa800a4cb440, fffff80000b9a3d8, fffffa800aecb3f0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Bugcheck code 0000009F
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800a4cb440, Physical Device Object of the stack
    Arg3: fffff80000b9a3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800aecb3f0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_RtsUVStor_IMAGE_usbhub.sys
    MaxSpeed:     2200
    CurrentSpeed: 2195
    BiosVersion = K53SC.216
    BiosReleaseDate = 09/26/2011
    SystemManufacturer = ASUSTeK Computer Inc.
    SystemProductName = K53SC
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Sat May 18 04:41:25.124 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\051713-24694-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 0 days 20:19:57.014
    *** WARNING: Unable to verify timestamp for RtsUVStor.sys
    *** ERROR: Module load completed but symbols could not be loaded for RtsUVStor.sys
    Probably caused by : usbhub.sys
    BugCheck 9F, {3, fffffa800a302060, fffff80000b9c3d8, fffffa800e05cbd0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Bugcheck code 0000009F
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800a302060, Physical Device Object of the stack
    Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800e05cbd0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_RtsUVStor_IMAGE_usbhub.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Debug session time: Fri May 17 07:16:53.468 2013 (UTC + 6:00)
    Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\051613-31839-01.dmp]
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    System Uptime: 1 days 4:25:19.595
    *** WARNING: Unable to verify timestamp for RtsUVStor.sys
    *** ERROR: Module load completed but symbols could not be loaded for RtsUVStor.sys
    Probably caused by : usbhub.sys
    BugCheck 9F, {3, fffffa800d3fd2f0, fffff80000b9c3d8, fffffa800b624bd0}
    BugCheck Info: DRIVER_POWER_STATE_FAILURE (9f)
    Bugcheck code 0000009F
    Arguments: 
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa800d3fd2f0, Physical Device Object of the stack
    Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa800b624bd0, The blocked IRP
    BUGCHECK_STR:  0x9F
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x9F_3_RtsUVStor_IMAGE_usbhub.sys
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      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 11:49.
Find Us