BSOD, nearly certainly linked to SD Card usage.


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

    BSOD, nearly certainly linked to SD Card usage.


    Hello, I am using a three-ish year-old laptop (Gateway MD2419u) and have not, until a couple of days ago, used an SD Card in it at all. I bought an SD Card recently and decided to start storing files on it, but my computer has been Blue Screening on me, only when the card is plugged in. As it's only been a few days, I can't be sure that the SD Card is the issue, but I suspect that it is. I hope that I post this properly, as it's my first time on this site. Thank you very much for any help provided.
      My Computer


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

    All your dumps are consistent of this error:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8002467050, fffff80000b9c518, fffffa80023b6e10}
    
    Probably caused by : disk.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8002467050, Physical Device Object of the stack
    Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa80023b6e10, The blocked IRP
    
    Debugging Details:
    ------------------
    
    
    DRVPOWERSTATE_SUBCODE:  3
    
    DEVICE_OBJECT: fffffa80045c84c0
    
    DRIVER_OBJECT: fffffa8002ea8560
    
    IMAGE_NAME:  disk.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc11d
    
    MODULE_NAME: disk
    
    FAULTING_MODULE: fffff880018c0000 disk
    
    IRP_ADDRESS:  fffffa80023b6e10
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`034fb8c2 : 00000000`0000009f 00000000`00000003 fffffa80`02467050 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`0349684c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`00b9c570 fffff800`034966e6 : fffff800`0363bf20 00000000`00fd538c 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c5e0 fffff800`034965ce : 0000025b`03bd3e2c fffff800`00b9cc58 00000000`00fd538c fffff800`0360a408 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`034963b7 : 0000007b`d3e4f9c1 0000007b`00fd538c 0000007b`d3e4f913 00000000`0000008c : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`0348390a : fffff800`03606e80 fffff800`03614cc0 00000000`00000000 fffff880`0439bdb0 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_disk.sys
    
    BUCKET_ID:  X64_0x9F_3_IMAGE_disk.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa80023b6e10
    Irp is active with 4 stacks 2 is current (= 0xfffffa80023b6f28)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa80045c84c0 00000000 fffff88000e45f50-00000000 Success Error Cancel pending
    	       \Driver\Disk	partmgr!PmPowerCompletion
    			Args: 00000000 00000001 00000004 00000000
     [ 16, 2]   0 e1 fffffa8002636a30 00000000 00000000-00000000    pending
    	       \Driver\partmgr
    			Args: 00000000 00000001 00000004 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa80026527b0    
    
    			Args: 00000000 00000000 00000000 00000000
    Hard Drive/Storage

    Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition

    How to Upload and Post a Screenshot and File in Seven Forums

    Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

    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

    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

    Have you checked for a BIOS updates? Yours is like 5 years old.
    Code:
    BIOS Version/Date	Phoenix Technologies LTD 9A.30, 10/14/2008
    Let us know the results.
      My Computer


  3. Posts : 1,454
    Windows 7 ultimate x64
       #3

    Hi

    Are you having problems with using the SD card in any other system ??

    Are you getting the BSOD while copying or just plugging it in ??

    Are you getting the BSOD error while the computer reads the SD card ??


    Answer the above and in any case here is what you need to do

    This is the support page for your model... Use the Hardware Vendor Detection Tool to see if you have any update... I dont think you will have much to update ... but its worth a try.

    Second the Bios version for your Model Series is 9A30b.... Update if possible from the link above

    Third... You are using 2 Antivirus... AVG 2013 and MSC.... I would really suggest you remove AVG 2013...Use the removal tool to do that... There are cases of BSOD when you use both at the same time

    Do these and let me know
      My Computer


  4. Posts : 6,830
    Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
       #4

    Driver for the Card Reader


    Download

      My Computer


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

    I really appreciate all this help; I am currently updating drivers and working on all that was suggested. I will reply as soon as I finish everything and figure out whether or not it worked.
      My Computer


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

    Also, I am getting the error after the card has been in for a while. I am using it with Readyboost as extra RAM, so it's constantly in use while it's plugged in.
      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 06:18.
Find Us