Share via

Bugcheck 0x0000009f dump file suggesting uaspstor.sys at fault

Anonymous
2019-02-01T19:58:14+00:00

Hi everyone, 

I have been having an issue resulting in a BSOD "Bugcheck 0x0000009f" occur on my Windows 10 setup.  I have a bit of a convoluted setup here: firstly I am running on a MacBook with bootcamp installed.  It is running perfectly other than when I have my USB devices connected, now comes the complicated part, and I am hoping that you may be able to offer me advice in how to better configure this setup:

Firstly, I have an eGPU connected to the MacBook via a Thunderbolt 3 cable, which is working fine and I haven't had any problems with (all drivers are up-to-date, etc).

This is where I believe the problem resides -- Second device I have connected to one of the Thunderbolt 3 ports is a USB-C 10 port externally powered USB-3.0 hub, that currently has 9 devices plugged into it.  

  • 2 Devices are gamepads
  • 1 Device is a keyboard
  • 1 Device is a mouse
  • 1 Device is a Samsung T5 SSD
  • 1 Device is a WD External HDD
  • 1 Device is an inateck 2 slot Internal HDD adapter with 2 HDDs installed (has its own dedicated power supply)
  • 1 Device is an internal to external (USB) NVMe adapter with a 960 Evo installed
  • 1 Device is an external pad / cooling station for the MacBook

Here is a link to the dump (.dmp) file if anyone is interested: 

https://1drv.ms/u/s!AuO36xP9HQjxjgtMyTBXZSArLftG

After I briefly glanced at it, it appears that uaspstor.sys is the culprit.  

If there is anything apparently wrong with this setup please let me know.  I am thinking that maybe (even though the hub is externally powered) I have too many demanding devices connected to it.  Otherwise please let me know what you think.  Any help is appreciated, 

Thanks!

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

8 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-02-02T00:54:56+00:00

    Thanks for the reply!  

    Since I am on bootcamp I want to avoid running the driver check (since the macOS portion likes to take over during restarts) until it is the last measure.  

    Auggy seems to have found from the dump file that the issue stems from the JMicron drive (my USB 3.1 NVMe enclosure with a 960 Evo inside).  I recently formatted the drive using the Microsoft Disk Management Utility, could I have formatted it wrong?  I'm also wondering if it could be the enclosure itself that's caused this problem, it was a fairly cheap enclosure from amazon: 

    USB 3.1 NVMe Adapter

    Is it possible that the device was being controlled by the Windows power management utility and entered a no-power state due to inactivity, causing the BSOD?  

    Since I have removed the device so far my system seems to be okay (its been about 5+ hours), last night it only lasted about 3-4 hours before the BSOD occurred (with the NVMe adapter attached).  

    Thanks again for the help!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-02-01T20:59:21+00:00

    It was the NVMe enclosure / adapter.  I have unplugged it for now to see whether or not the problem arises again, do you by chance know any more specifics as to why it may have occurred on that drive?  Honestly, it was a fairly cheap adapter that I purchased on amazon (https://www.amazon.com/gp/product/B07K6M4L8Q/ref=ppx\_yo\_dt\_b\_asin\_title\_o04\*\*\*\*\_s00?ie=UTF8&psc=1) for my 960 Evo that I used in my old computer, so I could access my files from that PC, but upon installing it on the new setup it wasn't being detected and I ended up having to format it so the computer could just use it as additional space.  

    Do you think the problem may have been caused by lack of power to the device (since so many are plugged into the externally powered hub) or is it just that the device is inherently dysfunctional?  If you look at related items for that product on amazon, you'll find that they appear to be the same exact product and multiple reviews claimed that it would malfunction etc.  I'm thinking I may have made a mistake in purchasing that, and at this point I should just sell the 960 Evo and use the money to purchase another Samsung T5.

    I'll keep monitoring my PC and checking to see if the problem arises again, I'll update after I wait a bit.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-02-01T20:48:32+00:00

    Thank you for the response!  

    I am looking to see which one that is now... I remember seeing that name specifically in my device manager and I suspect it is the USB internal NVMe drive adapter.  I'll let you know when I find out which one it is.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-02-01T20:35:42+00:00

    Hi,

    The potentially problematic device appears to be identified as a JMicron device:

    !DevNode ffffde862e1db6a0 :

    DeviceInst is "SCSI\Disk&Ven_JMicron&Prod_Tech\000000"

    Any device (USB) showing up in the Device Manager as a JMicron device?

    If so try unplugging that device and see if the error still occurs.

    Was this answer helpful?

    0 comments
  5. Vijay A. Verma 104.8K Reputation points Volunteer Moderator
    2019-02-01T20:16:37+00:00

    Hi Dashton,

    I am Vijay, an Independent Advisor. I am here to work with you on this problem.

    A. Analysis Results

    File Name: 020119-13515-01.dmp

    DRIVER_POWER_STATE_FAILURE (9f)

    IMAGE_NAME: uaspstor.sys

    B. Third Party Drivers

    None

    C. Recommendations

    1. Create a system restore point so that if something wrong happens you can revert.

    Type restore point in Cortana Search > Create a Restore point > Check whether against your drive, Protection is ON or not. If not ON, click Configure button below to Make it ON > Now press Create to create a restore point

    1. uaspstor.sys is a Windows driver not a third party driver. Windows driver is rarely actual cause. Most of the time, third party drivers are the cause of BSODs. To know if a driver is one of the causes - Enable Driver Verifier and generate dump files and upload to Onedrive and share the link here (Don't forget to turn off Driver Verifier after the job is done). Do read the instructions carefully particularly how to get back into Windows when you get the crash.

    https://www.tenforums.com/tutorials/5470-enable...

    Do let me know if you require any further help on this. Will be glad to help you.

    Disclaimer - This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

    Was this answer helpful?

    0 comments