BSOD error 0x0000009f, PLEASE HELP


  1. Posts : 4
    Windows 7 Home Premium 64 Bit
       #1

    BSOD error 0x0000009f, PLEASE HELP


    I've been getting a BSOD on my laptop more frequently lately and need to get to the bottom of it.

    The latest error description said this:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa800b235060, 0xfffff800040073d8, 0xfffffa800b747010). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 091013-35193-01.

    A BSOD a week ago gave me this:

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xfffffa800ce80060, 0xfffff8000400d748, 0xfffffa8006eae6c0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090313-19000-01.

    When I try to run SF Diagnostic, I get this error: Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately. Access to path 'C:\Windows\Minidump' is denied.

    When I hit Continue in SF Diagnostic, the program does not complete it's diagnostic.

    PLEASE HELP ME!!!!
      My Computer

  2.    #2

    Please go to this directory:

    Code:
    C:\Windows\Minidump
    Place any dump files into a zipped folder, and then attach in your next post.

    Run the SF_Diagnostic Tool again, but select all the options individually, apart from the Minidump option.
      My Computer


  3. Posts : 4
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #3

    Attached my Minidump files.

    And I seem to getting similar errors for the other options in SF Diagnostic.

    Thank you!
      My Computer

  4.    #4

    Code:
    BugCheck 9F, {3, fffffa800b235060, fffff800040073d8, fffffa800b747010}
    
    Probably caused by : usbhub.sys
    Code:
    0: kd> !irp fffffa800b747010
    Irp is active with 14 stacks 13 is current (= 0xfffffa800b747440)
     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
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa800cfcb060 00000000 00000000-00000000    pending
              Unable to load image \SystemRoot\system32\drivers\AmUStor.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for AmUStor.SYS
    *** ERROR: Module load completed but symbols could not be loaded for AmUStor.SYS
     \Driver\AmUStor
                Args: 00000000 00000001 00000003 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8006e18250    
    
                Args: 00000000 00000000 00000000 00000000
    Code:
    0: kd> lmvm AmUStor
    start             end                 module name
    fffff880`084f4000 fffff880`0850a000   AmUStor  T (no symbols)           
        Loaded symbol image file: AmUStor.SYS
        Image path: \SystemRoot\system32\drivers\AmUStor.SYS
        Image name: AmUStor.SYS
        Timestamp:        Mon May 16 12:31:25 2011 (4DD10B0D)
        CheckSum:         0001EC6E
        ImageSize:        00016000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Your ALCOR Micro SD Card Controller seems to be causing problems, please update the driver from your motherboard support page (if available) or the vendor here - ALCOR MICRO - Storage Product > SD Card Controller
      My Computer


  5. Posts : 4
    Windows 7 Home Premium 64 Bit
    Thread Starter
       #5

    Thank you so much Blue Robot! I did insert an SD card into my laptop a couple weeks ago and didn't realize this could be causing my issues.

    Would it be safe to assume that until I fix the driver issue, not using the SD card slot on my laptop will prevent future related BSODs?
      My Computer

  6.    #6

    I can say with confidence, that it seems to be least part of the problem, I never tend to say the root of the problem because I've seen systems with multiple driver issues, but do not worry about that. I wouldn't see the SD Card Reader, and if it still BSODs then please upload the new dump files and remove that driver from your system.
      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 22:38.
Find Us