The driver is storport, and it seems that if I IoReportDetectedDevices, storport won’t see the device. As you indicate, it might on the next boot, but I’m network booting off the root enumerated device (or trying to), and all changes will be thrown away on reboot so there is no “next time”. ROOT ENUMERATED DRIVER FOR WINDOWS DOWNLOAD - We're no longer immediately blocked but need to eventually figure it out. Doron Holan xxxxxx microsoft. The most complete answer I have found is here.
Look, I have had a ton of issue with my computer of late, and the last thing to fix is my AMD drivers. However, I cannot install it when in regular Windows mode, as it causes the crash 'THREAD STUCK IN DEVICE DRIVER'. This error also occurs without attempting to install, thus my need to update the drivers. I am using Windows 10, and can start in Safe Mode with Networking, however it refuses to find the hardware when I attempt to install it during Safe Mode.
Below is my System Information
------------------
Time of this report: 11/28/2016, 10:38:00
Machine name: BOLAND-PC
Machine Id: {D15043F7-25BA-4899-A062-28921007DBE4}
Operating System: Windows 10 Home 64-bit (10.0, Build 14393) (14393.rs1_release.160715-1616)
Language: English (Regional Setting: English)
System Manufacturer: To be filled by O.E.M.
System Model: To be filled by O.E.M.
BIOS: BIOS Date: 06/26/15 18:42:03 Ver: 04.06.05
Processor: AMD FX(tm)-6300 Six-Core Processor (6 CPUs), ~3.5GHz
Memory: 8192MB RAM
Available OS Memory: 8090MB RAM
Page File: 1424MB used, 14856MB available
Windows Dir: C:WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.14393.0000 64bit Unicode
------------
DxDiag Notes
------------
Display Tab 1: No problems found.
Sound Tab 1: This computer cannot play audio because the Windows Audio service is not enabled. Use the Sounds and Devices Properties control panel to enable audio. No sound card was found. If one is expected, you should install a sound driver provided by the hardware manufacturer.
Input Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (retail)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: Microsoft Basic Display Driver
Manufacturer: (Standard display types)
Chip type: AMD ATOMBIOS
DAC type: (C) 1988-2010, Advanced Micro D
Device Type: Display-Only Device
Device Key: EnumROOTBASICDISPLAY
Device Status: 4180000B [DN_ROOT_ENUMERATED|DN_DRIVER_LOADED|DN_STARTED|DN_NT_ENUMERATOR|DN_NT_DRIVER|DN_NO_SHOW_IN_DM]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 4044 MB
Dedicated Memory: 0 MB
Shared Memory: 4044 MB
Current Mode: 1366 x 768 (32 bit) (64Hz)
Driver Name: Unknown
Driver File Version: Unknown (Unknown)
Driver Version: 10.0.14393.0
DDI Version: 11.2
Feature Levels: 11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 1.3
Graphics Preemption: DMA
Compute Preemption: DMA
Miracast: Not Supported by Graphics driver
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Driver Attributes: Final Retail
![Livesuit pack version Livesuit pack version](/uploads/1/2/6/3/126346794/922404511.jpg)
Driver Date/Size: 21-Jun-06 10:00:00 AM, 0 bytes
WHQL Logo'd: No
WHQL Date Stamp: None
Device Identifier: {D7B71AF4-43CC-11CF-B063-3918AFC2C735}
Vendor ID: 0x1414
Device ID: 0x008C
SubSys ID: 0x00000000
Revision ID: 0x0000
Driver Strong Name: basicdisplay.inf:1080904755d1bda1:MSBDD_Fallback:10.0.14393.0:ROOTBasicDisplay
Rank Of Driver: 00FB0000
Video Accel:
DXVA2 Modes: Unknown
page_type | description | languages | products |
---|---|---|---|
Demonstrates how a UMDF version 2 driver can implement F-state-based power management. |
|
This solution demonstrates how a User-Mode Driver Framework (UMDF) version 2 driver can implement F-state-based power management. The SingleComp project demonstrates how a UMDF version 2 driver can implement F-state-based power management for a device that has only a single component.
Universal Windows Driver Compliant
This sample builds a Universal Windows Driver. It uses only APIs and DDIs that are included in OneCoreUAP.
Related technologies
KMDF Power Framework (PoFx) Sample.
Run the sample
The computer where you install the driver is called the target computer or the test computer. Typically this is a separate computer from where you develop and build the driver package. The computer where you develop and build the driver is called the host computer.
The process of moving the driver package to the target computer and installing the driver is called deploying the driver. You can deploy a driver sample automatically or manually.
![Install Install](/uploads/1/2/6/3/126346794/578464060.jpg)
Automatic deployment (root enumerated)
Before you automatically deploy a driver, you must provision the target computer. For instructions, see Provision a computer for driver deployment and testing.
After you have provisioned the target computer, continue with these steps:
- On the host computer, in Visual Studio, in Solution Explorer, right click package (lower case), and choose Properties. Navigate to Configuration Properties > Driver Install > Deployment.
- Check Enable deployment, and check Remove previous driver versions before deployment. For Target Computer Name, select the name of a target computer that you provisioned previously. Select Hardware ID Driver Update, and enter rootSingleComponentSingleState for the hardware ID. Click OK.
- On the Build menu, choose Build Solution.
Manual deployment (root enumerated)
Before you manually deploy a driver, you must turn on test signing and install a certificate on the target computer. You also need to copy the DevCon tool to the target computer. For instructions, see Preparing a Computer for Manual Driver Deployment.
After you have prepared the target computer for manual deployment, continue with these steps:
- Copy all of the files in your driver package to a folder on the target computer (for example, c:PoFx).
- On the target computer, open a Command Prompt window as Administrator. Navigate to your driver package folder, and enter the following command:
devcon install SingleComponentSingleStateUm.inf rootSingleComponentSingleState
View the root enumerated driver in Device Manager
On the target computer, in a Command Prompt window, enter devmgmt to open Device Manager. In Device Manager, on the View menu, choose Devices by type. In the device tree, locate UMDF 2.0 Single Component Single State Device (for example, this might be under the Sample Device node).
In Device Manager, on the View menu, choose Devices by connection. Locate UMDF 2.0 Single Component Single State Device as a child of the root node of the device tree.
Build the sample using MSBuild
As an alternative to building the driver sample in Visual Studio, you can build it in a Visual Studio Command Prompt window. In Visual Studio, on the Tools menu, choose Visual Studio Command Prompt. In the Visual Studio Command Prompt window, navigate to the folder that has the solution file, PoFx.sln. Use the MSBuild command to build the solution. Here is an example:
msbuild /p:configuration='Release' /p:platform='Win32' PoFx.sln
For more information about using MSBuild to build a driver package, see Building a Driver with Visual Studio and the WDK.