# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"05-28-2021" Time:"00:00:28.6664763" # Scanned Hardware Computer: BaseBoard Manufacturer:"Dell Inc." BIOS Mode:"UEFI" BIOS Version/Date:"Dell Inc. 1.4.0 , 03/17/2021" CD or DVD:"Not Available" Embedded Controller Version:"255.255" Platform Role:"Mobile" Processor:"11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"3.2" Sound Card:"Realtek Audio" Sound Card:"Intel® Smart Sound Technology for Digital Microphones" System Manufacturer:"Dell Inc." System Model:"Inspiron 3501" System SKU:"0A25" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"27.20.100.9466" - "Intel(R) Iris(R) Xe Graphics" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Internal" Adapter RAM:"1.00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" - "Caption":"Intel(R) Iris(R) Xe Graphics" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Iris+Xe+Graphics" CoInstallers:"oem128.inf,iTGLD_w10_DS,Internal,Intel(R) Iris(R) Xe Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmdn64.sys" Driver Date:"03-30-2021 05:30 AM" Driver Path:"C:\Windows\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdkmdn64.sys" Driver Provider:"Intel Corporation" Driver Version:"27.20.100.9466" INF:"oem128.inf" INF Section:"iTGLD_w10_DS" Install Date:"Not Available" Installed Drivers:"C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd12umd64.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 0, device 2, function 0" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_9A49&SUBSYS_0A251028&REV_01\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"59 Hz" Refresh Rate - Maximum:"59 Hz" Refresh Rate - Minimum:"47 Hz" Resolution:"1920 X 1080" Scan Mode:"Noninterlaced" Service Name:"igfxn" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) Iris(R) Xe Graphics Family" - "Memory" Physical Memory (Available):"0.43 GB" Physical Memory (Installed):"4 GB" Physical Memory (Total):"3.73 GB" - "DIMM A" Capacity:"4 GB" Channel:"DIMM A" Configured Clock Speed:"2667 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Not Available" Manufacturer:"80AD00000000" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"HMA851S6DJR6N-XN" Serial Number:"21E2A4EC" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"1.4.0, DELL - 2" Caption:"Motherboard" Chipset:"Not Available" Date:"03-17-2021 05:30 AM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"Dell Inc." Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"0RYXFP" Serial Number:"/9H6C393/CNCMC000BJ09DE/" Status:"OK" Version:"A00" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Qualcomm QCA9377 802.11ac Wireless Adapter" Access Point:"84:d8:1b:69:a1:17" Authentication:"WPA2-Personal" Availability:"Running or Full Power" Caption:"Qualcomm QCA9377 802.11ac Wireless Adapter" Channel:"36" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Auto Connect" Default IP Gateway:"192.168.0.1" DHCP Enabled:"Yes" DHCP Lease Expires:"05-28-2021 12:44 PM" DHCP Lease Obtained:"05-28-2021 10:44 AM" DHCP Server:"192.168.0.1" Driver:"Qcamain10x64.sys" Driver Date:"08-19-2020 12:00 AM" Driver Path:"C:\Windows\system32\drivers\Qcamain10x64.sys" Driver Provider:"Qualcomm Communications Inc." Driver Version:"12.0.0.967" Index:"0002" INF:"oem12.inf" INF Section:"ATHR_DEV_OS63_988x_DE_NFA435_TF_1_1.ndi.NTamd64" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.0.111;fe80::e472:4876:bcb7:9a5e" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05-27-2021 05:01 PM" Location:"PCI bus 2, device 0, function 0" MAC Address:"18:47:3D:F3:1B:69" Manufacturer:"Qualcomm Communications Inc." Media Type: Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{B713BCA2-993F-4DD4-8CE7-0310714AC51B}" Network Name:"Dhanak_House(5G)" Network Type:"Infrastructure" Number of VLANs:"0" PNP Device ID:"PCI\VEN_168C&DEV_0042&SUBSYS_18101028&REV_31\4&CA52D08&0&00E9" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Qualcomm QCA9377 802.11ac Wireless Adapter" Profile:"Dhanak_House(5G)" Radio Type:"802.11ac" Receive Rate:"433.3 Mbps" Service Name:"Qcamain10x64" Signal Strength:"84%" State:"connected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate:"433.3 Mbps" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" D0PCEnable:D0 PacketCoalescing:"Disable (0)" roamPolicy:Roaming aggressiveness:"3.Medium (3)" StaPreferredBand:Preferred Band:"1 - No Preference (1)" StaWirelessMode:Wireless Mode:"12 - 11 a/b/g/n/ac (12)" - "Realtek PCIe GbE Family Controller" Availability:"Running or Full Power" Caption:"Realtek PCIe GbE Family Controller" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"rt640x64.sys" Driver Date:"12-02-2020 12:00 AM" Driver Path:"C:\Windows\system32\drivers\rt640x64.sys" Driver Provider:"Realtek" Driver Version:"10.39.212.2020" Index:"0001" INF:"oem35.inf" INF Section:"RTL8168HTRxOptThrld1k.ndi.NT" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"05-27-2021 05:01 PM" Location:"PCI bus 1, device 0, function 0" MAC Address:"30:D0:42:1F:83:96" Manufacturer:"Realtek" Media Type: Net Connection ID:"Ethernet" NetCfgInstanceId:"{23E84F81-1F69-430B-ACB5-9F8D06D99CC7}" Number of VLANs:"0" PNP Device ID:"PCI\VEN_10EC&DEV_8168&SUBSYS_0A251028&REV_15\01000000684CE00000" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Realtek PCIe GbE Family Controller" Service Name:"rt640x64" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *EEE:Energy-Efficient Ethernet:"Enabled (1)" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Frame:"Disabled (1514)" *LsoV2IPv4:Large Send Offload v2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload v2 (IPv6):"Enabled (1)" *ModernStandbyWoLMagicPacket:Wake on magic packet when system is in the S0ix power state:"Disabled (0)" *NumRssQueues:Maximum Number of RSS Queues:"4 Queues (4)" *PMARPOffload:ARP Offload:"Enabled (1)" *PMNSOffload:NS Offload:"Enabled (1)" *PriorityVLANTag:Priority & VLAN:"Priority & VLAN Enabled (3)" *ReceiveBuffers:Receive Buffers:"512 (512)" *RSS:Receive Side Scaling:"Enabled (1)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"128 (128)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on pattern match:"Enabled (1)" AdvancedEEE:Advanced EEE:"Disabled (0)" AutoDisableGigabit:Auto Disable Gigabit:"Disabled (0)" EnableGreenEthernet:Green Ethernet:"Enabled (1)" GigaLite:Gigabit Lite:"Enabled (1)" PowerSavingMode:Power Saving Mode:"Enabled (1)" S5WakeOnLan:Shutdown Wake-On-Lan:"Enabled (1)" WolShutdownLinkSpeed:WOL & Shutdown Link Speed:"10 Mbps First (0)" - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.8" Boot Device:"\Device\HarddiskVolume3" Locale:"United States" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Home Single Language" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"9.02 GB" Physical Memory (Available):"0.43 GB" Physical Memory (Installed):"4 GB" Physical Memory (Total):"3.73 GB" System Directory:"C:\Windows\system32" Version:"10.0.19043 Build 19043" Virtual Memory (Available):"6.99 GB" Virtual Memory (Total):"12.75 GB" Windows Directory:"C:\Windows" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [19-01-2021]" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [19-01-2021]" KB2467173:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [19-01-2021]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [19-01-2021]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB4534170:"Update [4/20/2020]" KB4537759:"Security Update [4/20/2020]" KB4542335:"Update [11/27/2020]" KB4545706:"Security Update [4/20/2020]" KB4562830:"Update [12/26/2020]" KB4577266:"Security Update [11/27/2020]" KB4577586:"Update [2/17/2021]" KB4580325:"Security Update [12/26/2020]" KB4589212:"Update [3/11/2021]" KB4593175:"Security Update [12/26/2020]" KB4598481:"Security Update [1/13/2021]" KB5000736:"Update [5/19/2021]" KB5003214:"Update [5/26/2021]" KB5003254:"Update [5/26/2021]" KB5003503:"Update [5/26/2021]" KB982573:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [19-01-2021]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [19-01-2021]" SP1:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [Not Available]" SP1:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [Not Available]" - "Processor" - "11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 140 Stepping 1" - "Chipset Name":"11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=11th+Gen++Core+i5+1135G7+" CPU Speed:"2.42 GHz" Current Voltage:"9. volts" Driver:"Not Available" Driver Date:"04-21-2009 12:00 AM" Driver Path:"C:\Windows\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.19041.546" Ext. Family:"Not Available" Family:"Not Available" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"4 x 192 KB" Level 2 Cache:"4 x 5120 KB" Level 3 Cache:"8 MB" Load:"3%" Manufacturer:"GenuineIntel" Model:"140" Name:"11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz" Number of Cores:"4" Number of Cores Enabled:"4" Number of Logical Processors:"8" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000806C1" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"1" Version:"Not Available" - "Storage" - "NVMe KBG40ZNS256G NVMe KIOXIA 256GB" Capablities:"Random Access, Supports Writing, SMART Notification" Caption:"NVMe KBG40ZNS256G NVMe KIOXIA 256GB" Cylinder - Total:"31130" Description:"Disk drive" Driver:"Not Available" Driver Date:"06-21-2006 12:00 AM" Driver Version:"10.0.19041.789" Error Code:"Device is working properly" Firmware Revision:"10410106" Heads - Total:"255" Index:"1" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"NVMe KBG40ZNS256G NVMe KIOXIA 256GB" Name:"\\.\PHYSICALDRIVE1" Partitions:"5" Physical Sector Size:"512" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_KBG40ZNS256G_NVM\4&BD3BB5D&0&030000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"3" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"500103450" Serial Number:"0100_0000_0000_0000_8CE3_8E04_013A_F4AC." Size:"238.47 GB" Size – Available:"138.74 GB" SMART Attributes:"Self-Test: 0 minutes, OK, Short Self-Test: 0 minutes, OK" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"7938150" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"OS" Serial Number:"307FA6C8" Size:"222.07 GB" Size – Available:"138.74 GB" Status:"Not Available" Volume Dirty:"No" - "SMART" 0x05 Reallocated Sector Count:0:"36" 0x09 Power-On Hours:276:"0" 0x0C Power Cycle Count:466:"20" 0xAE Power-off Retract Count:37:"0" 0xBB Uncorrectable Error Count:0:"0" 0xBE Temperature - Current:50° C:"0" 0xBE Temperature - Highest:Not Available:"0" 0xBE Temperature - Lowest:Not Available:"40" 0xE8 Available Reserved Space:0:"0" 0xF1 Total LBAs Written:8564057:"0" 0xF2 Total LBAs Read:26890391:"0" - "ST1000LM035-1RK172" Capablities:"Random Access, Supports Writing, SMART Notification" Caption:"ST1000LM035-1RK172" Cylinder - Total:"121601" Description:"Disk drive" Driver:"Not Available" Driver Date:"06-21-2006 12:00 AM" Driver Version:"10.0.19041.789" Error Code:"Device is working properly" Firmware Revision:"1002" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"ST1000LM035-1RK172" Name:"\\.\PHYSICALDRIVE0" Partitions:"1" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_ATA&PROD_ST1000LM035-1RK1\4&BD3BB5D&0&020000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"2" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"1953520065" Serial Number:"WQ9APBA4" Size:"931.51 GB" Size – Available:"850.48 GB" SMART Attributes:"Self-Test: 158 minutes, OK, Short Self-Test: 1 minutes, OK" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"31008255" - "D:" Availability:"Not Available" Caption:"D:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"DATA" Serial Number:"BE8513C4" Size:"931.39 GB" Size – Available:"850.48 GB" Status:"Not Available" Volume Dirty:"No" - "SMART" 0x01 Raw Read Error Rate:196382814:"6" 0x03 Spin Up Time:0:"0" 0x04 Start/Stop Count:1662:"20" 0x05 Reallocated Sector Count:0:"36" 0x07 Seek Error Rate:8648476:"45" 0x09 Power-On Hours:462:"0" 0x0A Spin Retry Count:0:"97" 0x0C Power Cycle Count:462:"20" 0xB8 End-to-End Error Detection Count:0:"99" 0xBB Uncorrectable Error Count:0:"0" 0xBC Reported Command Timeouts:0:"0" 0xBD High Fly Writes:0:"0" 0xBE Temperature - Current:38° C:"0" 0xBE Temperature - Highest:40° C:"0" 0xBE Temperature - Lowest:31° C:"40" 0xBF G-sense Rate/Servo Tracking:10:"0" 0xC0 Unsafe Shutdown Count:7:"0" 0xC1 Load/Unload Cycle Count:15121:"0" 0xC2 Internal Device Temperature:38° C:"0" 0xC5 Current Pending Errors Count:0:"0" 0xC6 Uncorrectable Sector Count:0:"0" 0xC7 CRC Error Count:0:"0" 0xF0 Head Flying Hours:135:"0" 0xF1 Total LBAs Written:3262448766:"0" 0xF2 Total LBAs Read:3526096912:"0" 0xFE Free Fall Protection:0:"0" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xffffcc0d4c805d40, 0x0000000000000002, 0x0000000000000000, 0xfffff80754de6350). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 20c95c44-08c7-4570-ba42-5e5a3d9abfcc. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:54:58 on ‎27-‎05-‎2021 was unexpected. ------------------------------------------------------------------- The Dell Data Vault Processor service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The Server service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The LanmanServer service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The DNS Client service depends on the Network Store Interface Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHTTP Web Proxy Auto-Discovery Service service depends on the DHCP Client service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- The mpssvc service terminated with the following service-specific error: The parameter is incorrect. ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The Dnscache service depends on the nsi service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {9E175B6D-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {EDAE4045-CAE6-4706-8973-FA69715B8C10} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {EDAE4045-CAE6-4706-8973-FA69715B8C10} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {816A45F9-7406-42BB-B4FA-A655D96F2A8A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {EDAE4045-CAE6-4706-8973-FA69715B8C10} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {BD8A8E7D-E42F-434A-8215-C7ECB6C32786} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {47782907-6A6D-44BC-8872-4E45E994E6F9} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {2557A77E-882D-4633-960E-0C718670C1C7} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {F6976CF5-68A8-436C-975A-40BE53616D59} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {1B48339C-D15E-45F3-AD55-A851CB66BE6B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {F99A566C-42AE-4DE2-AD4D-D297A04C5433} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {5CF41123-E9E6-4AC0-85A7-C4001F513C6A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {A2A6D7C6-ECBD-439E-9244-9E784608439F} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {74FA5D1F-BBD3-4F3E-8776-41EDEFC608D9} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {CC66E708-C687-42EA-806E-83D41C9D1A5F} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {470B9B9B-0E95-4963-B265-5D58E5808C3D} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {434AEC1C-8583-45EC-B88F-750D6F380BC3} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service BthAvctpSvc with arguments "Unavailable" in order to run the server: {6E1F7F3E-760E-45F3-AA8F-5761ABDA272A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {ECC2E0CA-E42A-4DCB-ABE9-40A4E87D484A} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service mccspsvc with arguments "Unavailable" in order to run the server: {8F2BC96B-68C5-40E8-9CE1-368E3ACAC09B} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service EventSystem with arguments "Unavailable" in order to run the server: {1BE1F766-5536-11D1-B726-00C04FB926AF} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38549 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38549 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38549 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38549 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38549 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38549 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.964_neutral_neutral_cw5n1h2txyewy!Windows.Networking.BackgroundTransfer.Internal.NetworkChangeTask.ClassId.1 did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.964_neutral_neutral_cw5n1h2txyewy!App.AppXx4zfy1ffv3wctgdz2vypnybzjkh27jhw.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The Virtual Disk service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:46:53 on ‎22-‎05-‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The SysMain service terminated with the following error: The parameter is incorrect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 15:11:52 on ‎20-‎05-‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 11:31:34 on ‎19-‎05-‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The RzKLService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:44:24 on ‎18-‎05-‎2021 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 11:19:22 on ‎16-‎05-‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 20:00:05 on ‎15-‎05-‎2021 was unexpected. ------------------------------------------------------------------- The Intel(R) HD Graphics Control Panel Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Installer service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Dell Hardware Support service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The Dell Data Vault Processor service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 17:57:13 on ‎03-‎05-‎2021 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 18:44:26 on ‎02-‎05-‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:28:09 on ‎26-‎04-‎2021 was unexpected. ------------------------------------------------------------------- The system could not sucessfully load the crash dump driver. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address :: with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 21:17:20 on ‎23-‎04-‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR5. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR5. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR5. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR5. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Windows Push Notifications User Service_17df0b1 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. ------------------------------------------------------------------- The system detected an address conflict for IP address :: with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 21:14:41 on ‎02-‎04-‎2021 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The system could not sucessfully load the crash dump driver. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffffe28f3ae1f450, 0xfffff8053a083fd0, 0xffffffffc0000001, 0x0000000000000003). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 8c4d6f15-6876-4ca9-a035-a26f6fe778e2. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 21:10:50 on ‎27-‎03-‎2021 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.WindowsCamera_2020.902.20.0_x64__8wekyb3d8bbwe!App did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {B9B05098-3E30-483F-87F7-027CA78DA287} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR8. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR19. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR16. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR15. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system detected an address conflict for IP address :: with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The vgc service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80248007: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR10. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR10. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR10. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The previous system shutdown at 10:48:30 on ‎18-‎02-‎2021 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {94269C4E-071A-4116-90E6-52E557067E4E} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout was reached (60000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 09:31:48 on ‎30-‎01-‎2021 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #6, {15596e81-fbba-4a3b-9704-ce6f432797ef}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0} ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 192.168.0.9 with the system having network hardware address 10-D3-8A-A3-FB-76. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server: {8C9C0DB7-2CBA-40F1-AFE0-C55740DD91A0} ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The Delivery Optimization service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {211EBA3A-EA5A-496B-A021-5C6BEB365E4C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Dell Data Vault Processor service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- A fatal error occurred while creating a TLS client credential. The internal error state is 10013. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #4, {2516df41-7f9e-455c-91bb-23025570d7c1}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9PLFNLNT3G5G-AppUp.IntelGraphicsExperience. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The device (14:01:52:c3:61:13) is trying to distribute an Identity Resolving Key that is already used by a paired device. The pairing was rejected, if the intent was to pair with this device, you may need to first delete the existing pairing information. ------------------------------------------------------------------- The device (14:01:52:c3:61:13) is trying to distribute an Identity Resolving Key that is already used by a paired device. The pairing was rejected, if the intent was to pair with this device, you may need to first delete the existing pairing information. ------------------------------------------------------------------- The device (14:01:52:c3:61:13) is trying to distribute an Identity Resolving Key that is already used by a paired device. The pairing was rejected, if the intent was to pair with this device, you may need to first delete the existing pairing information. ------------------------------------------------------------------- The device (14:01:52:c3:61:13) is trying to distribute an Identity Resolving Key that is already used by a paired device. The pairing was rejected, if the intent was to pair with this device, you may need to first delete the existing pairing information. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NX51W9GBS5T-ScreenovateTechnologies.DellMobileConnect. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: Driver %2 returned invalid ID for a child device (55005300450052005F0045005300520056005F005300560043005F0051005500450045004E0043005200450045004B000000). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Rivet AP Selector Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.423_neutral_neutral_cw5n1h2txyewy!App.AppX447jn8wbjb1qsw3jxkndb19cwgsrtrkk.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Function Discovery Resource Publication service terminated with the following error: The requested address is not valid in its context. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Remote NDIS based Internet Sharing Device, {2f901821-f38a-4bd6-86f3-6df013b52943}, had event Network Interface deleted while PNP Device still exists. Note that this event is provided for informational purpose and might not be an error always (Eg: In case of vSwitch which was recently un-installed or a LBFO team was removed) ------------------------------------------------------------------- The Dell Data Vault Processor service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {61386bf7-d1d5-4404-829c-f144a3afa6de}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Realtek Semiconductor Corp. - Extension - 6.0.9034.1. ------------------------------------------------------------------- The server {209500FC-6B45-4693-8871-6296C4843751} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Function Discovery Resource Publication service terminated with the following error: The requested address is not valid in its context. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 5/28/2021, 11:02:50 Machine name: ARYAN-LAPTOP Machine Id: {6C5CCD8C-74CB-4E2E-8A3F-CFF62DC580BF} Operating System: Windows 10 Home Single Language 64-bit (10.0, Build 19043) (19041.vb_release.191206-1406) Language: English (Regional Setting: English) System Manufacturer: Dell Inc. System Model: Inspiron 3501 BIOS: 1.4.0 (type: UEFI) Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 CPUs), ~2.4GHz Memory: 4096MB RAM Available OS Memory: 3818MB RAM Page File: 5921MB used, 7131MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.0.8 DxDiag Version: 10.00.19041.0928 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. 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: Intel(R) Iris(R) Xe Graphics Manufacturer: Intel Corporation Chip type: Intel(R) Iris(R) Xe Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_9A49&SUBSYS_0A251028&REV_01 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 2037 MB Dedicated Memory: 128 MB Shared Memory: 1909 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Internal Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.589844,0.370117), Green(0.349609,0.554688), Blue(0.155273,0.110352), White Point(0.313477,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: unknown Monitor Id: LGD05F2 Native Mode: 1920 x 1080(p) (59.977Hz) Output Type: Internal Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdumdim64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd12umd64.dll Driver File Version: 27.20.0100.9466 (English) Driver Version: 27.20.100.9466 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.7 Hardware Scheduling: Supported:False Enabled:False Graphics Preemption: Triangle Compute Preemption: Thread group Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: DISABLE_HWSCH Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 30-03-2021 05:30:00, 1459240 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-D909-11CF-6257-412ABAC2D635} Vendor ID: 0x8086 Device ID: 0x9A49 SubSys ID: 0x0A251028 Revision ID: 0x0001 Driver Strong Name: oem128.inf:5f63e5348b96c4a0:iTGLD_w10_DS:27.20.100.9466:PCI\VEN_8086&DEV_9A49 Rank Of Driver: 00CF2001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {9B31316B-F204-455D-8A8C-9345DCA77C01} {AFE4285C-AB63-4B2D-8278-E6BAACEA2CE9} {277DE9C5-ED83-48DD-AB8F-AC2D24B22943} {04C5BA10-4E9A-4B8E-8DBF-4F4B48AFA27C} {0ACEF8BC-285F-415D-AB22-7BF2527A3D2E} {24D19FCA-C5A2-4B8E-9F93-F8F6EF15C890} {353ACA91-D945-4C13-AE7E-469060FAC8D8} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {B8B28E0C-ECAB-4217-8C82-EAAA9755AAF0} {8732ECFD-9747-4897-B42A-E534F9FF2B7A} {E139B5CA-47B2-40E1-AF1C-AD71A67A1836} {056A6E36-F3A8-4D00-9663-7E9430358BF9} {5415A68C-231E-46F4-878B-5E9A22E967E9} {161BE912-44C2-49C0-B61E-D946852B32A1} {D6D6BC4F-D51A-4712-97E8-750917C860FD} {7FEF652D-3233-44DF-ACF7-ECFB584DAB35} {580DA148-E4BF-49B1-943B-4214AB05A6FF} {CEE393AB-1030-4F7B-8DBC-55629C72F17E} {87B2AE39-C9A5-4C53-86B8-A52D7EDBA488} {10E19AC8-BF39-4443-BEC3-1B0CBFE4C7AA} {2DEC00C7-21EE-4BF8-8F0E-773F11F126A2} {C35153A0-23C0-4A81-B3BB-6A1326F2B76B} {A33FD0EC-A9D3-4C21-9276-C241CC90F6C7} {310E59D2-7EA4-47BB-B319-500E78855336} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {E484DCB8-CAC9-4859-99F5-5C0D45069089} {41A5AF96-E415-4B0C-9D03-907858E23E78} {6A6A81BA-912A-485D-B57F-CCD2D37B8D94} {E4E3CF5B-97D2-4658-AACB-366E3EE2CEEE} {FD9D9559-0FD3-4917-A9A7-07E714EE9EF9} {0E4BC693-5D2C-4936-B125-AEFE32B16D8A} {2F08B5B1-DBC2-4D48-883A-4E7B8174CFF6} {5467807A-295D-445D-BD2E-CBA8C2457C3D} {AE0D4E15-2360-40A8-BF82-028E6A0DD827} {8FF8A3AA-C456-4132-B6EF-69D9DD72571D} {C23DD857-874B-423C-B6E0-82CEAA9B118A} {5B08E35D-0C66-4C51-A6F1-89D00CB2C197} {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {68A21C7B-D58F-4E74-9993-E4B8172B19A0} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {1D5C4D76-B55A-4430-904C-3383A7AE3B16} {A7F759DD-5F54-4D7F-8291-42E883C546FE} {F34FA92F-DC79-474C-B0DB-B7BD4522DF77} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {CA44AFC5-E1D0-42E6-9154-B127186D4D40} {F9A16190-3FB4-4DC5-9846-C8751F83D6D7} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466} Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 3 MPO Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) MPO Stretch: 21.000X - 0.334X MPO Media Hints: colorspace Conversion MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM PanelFitter Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) PanelFitter Stretch: 21.000X - 0.334X Extension Drivers: Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_2006a2648a69923b\iigd_ext.inf Driver Version: 27.20.100.9365 Driver Date: 03/10/2021 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_5bb02df78b81cb20\iigd_ext.inf Driver Version: 27.20.100.8853 Driver Date: 10/14/2020 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True Driver Name: C:\Windows\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_1e68bc7f351413eb\iigd_ext.inf Driver Version: 27.20.100.8680 Driver Date: 08/28/2020 Driver Provider: Intel Corporation Catalog Attributes: Universal:N/A Declarative:True Component Drivers: Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A ------------- Sound Devices ------------- Description: Speakers (Realtek(R) Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0236&SUBSYS_10280A25&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.9071.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 24-11-2020 05:30:00, 5954144 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: Microphone Array (Intel� Smart Sound Technology for Digital Microphones) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: IntcDMic.sys Driver Version: 10.29.0.4842 (English) Driver Attributes: Final Retail Date and Size: 27-11-2020 05:30:00, 704880 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 1 --------------------- FriendlyName: Integrated Webcam Category: Camera SymbolicLink: \\?\usb#vid_0c45&pid_671e&mi_00#6&1296259f&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 Manufacturer: Microsoft HardwareID: USB\VID_0C45&PID_671E&REV_8502&MI_00,USB\VID_0C45&PID_671E&MI_00 DriverDesc: USB Video Device DriverProvider: Microsoft DriverVersion: 10.0.19041.964 DriverDateEnglish: 6/21/2006 00:00:00 DriverDateLocalized: 21-06-2006 00:00:00 Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Integrated Webcam Parent: USB\VID_0C45&PID_671E\5&31036e8e&0&6 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {20C94C5C-F402-4F1F-B324-0C1CF0257870} MFT0: n/a DMFT: n/a CustomCaptureSource: n/a DependentStillCapture: True EnablePlatformDMFT: True DMFTChain: n/a EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a ProfileIDs: n/a ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E FF Driver: n/a Device Name: Converted Portable Device Control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0000 FF Driver: n/a Device Name: Converted Portable Device Control device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x0000 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0xCDD6 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0xCDD6 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 12/7/2019 14:37:56, 118272 bytes | Driver: kbdclass.sys, 12/7/2019 14:37:56, 71480 bytes | + HID Keyboard Device | Vendor/Product ID: 0x045E, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 12/7/2019 14:37:56, 46592 bytes | Driver: kbdclass.sys, 12/7/2019 14:37:56, 71480 bytes | + PS/2 Compatible Mouse | Matching Device ID: *PNP0F13 | Service: i8042prt | Driver: mouclass.sys, 12/7/2019 14:37:56, 67600 bytes | Driver: i8042prt.sys, 12/7/2019 14:37:56, 118272 bytes | + HID-compliant mouse | Vendor/Product ID: 0x06CB, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 12/7/2019 14:37:56, 35328 bytes | Driver: mouclass.sys, 12/7/2019 14:37:56, 67600 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 142.1 GB Total Space: 227.4 GB File System: NTFS Model: NVMe KBG40ZNS256G NVMe KIOXIA 256GB Drive: D: Free Space: 870.9 GB Total Space: 953.7 GB File System: NTFS Model: ST1000LM035-1RK172 -------------- System Devices -------------- Name: PCI standard host CPU bridge Device ID: PCI\VEN_8086&DEV_9A14&SUBSYS_0A251028&REV_01\3&11583659&0&00 Driver: n/a Name: Intel(R) Serial IO I2C Host Controller - A0E8 Device ID: PCI\VEN_8086&DEV_A0E8&SUBSYS_0A251028&REV_20\3&11583659&0&A8 Driver: C:\Windows\System32\DriverStore\FileRepository\ialpss2_i2c_tgl.inf_amd64_ab87bf17a571e523\iaLPSS2_I2C_TGL.sys, 30.100.2031.0002 (English), 8/9/2020 18:42:26, 197272 bytes Name: Intel(R) Dynamic Tuning Processor Participant Device ID: PCI\VEN_8086&DEV_9A03&SUBSYS_0A251028&REV_01\3&11583659&0&20 Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\esif_lf.sys, 8.07.10600.20700 (English), 3/17/2021 13:40:36, 423064 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\dptf_cpu.sys, 8.07.10600.20700 (English), 3/17/2021 13:40:34, 73368 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\esif_uf.exe, 8.07.10600.20700 (English), 3/17/2021 13:40:38, 2301592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\esif_umdf2.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:38, 1011352 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\Dptf.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:10, 2490008 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyRfim.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:26, 813720 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyActive.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:10, 826520 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyActive2.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:12, 1008808 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyEnergyPerformanceOptimizer.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:16, 882840 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyAdaptiveUserPresence.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:14, 1046696 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyAdaptivePerformance.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:12, 1203368 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyCritical.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:14, 803992 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyIntelligentThermalManagement.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:16, 974488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPassive.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:18, 1136296 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPassive2.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:18, 1084072 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPid.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:20, 983704 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPowerBoss.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:22, 1419928 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyVirtualSensor.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:28, 982168 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPowerShare.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:22, 967832 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicyPowerShare2.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:24, 986264 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\DptfPolicySystemConfiguration.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:26, 772248 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_wwan.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:46, 133272 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_wifi.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:46, 67224 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_nvme.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:44, 114840 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_battery.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:42, 71832 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_socwc.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:44, 225432 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\upe_hwpf.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:42, 74392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\dptf_helper.exe, 8.07.10600.20700 (English), 3/17/2021 13:40:34, 549016 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\esif_cmp.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:36, 138392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\ipftcs.dll, 8.07.10600.20700 (English), 3/17/2021 13:40:40, 1686408 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\dsp.dv, 3/17/2021 13:31:00, 894845 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_1da48d5885266bb7\ppm.dv, 3/17/2021 13:31:00, 7608 bytes Name: Intel(R) Management Engine Interface Device ID: PCI\VEN_8086&DEV_A0E0&SUBSYS_0A251028&REV_20\3&11583659&0&B0 Driver: C:\Windows\System32\DriverStore\FileRepository\heci.inf_amd64_ca966d63ef47a7ed\x64\TeeDriverW10x64.sys, 2023.15.0000.1249 (English), 7/27/2020 06:29:42, 302592 bytes Name: Intel(R) LPC Controller/eSPI Controller (U Premium) - A082 Device ID: PCI\VEN_8086&DEV_A082&SUBSYS_0A251028&REV_20\3&11583659&0&F8 Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 10.00.19041.0001 (English), 12/7/2019 14:37:54, 20280 bytes Name: Intel(R) SPI (flash) Controller - A0A4 Device ID: PCI\VEN_8086&DEV_A0A4&SUBSYS_0A251028&REV_20\3&11583659&0&FD Driver: n/a Name: PCI standard RAM Controller Device ID: PCI\VEN_8086&DEV_A0EF&SUBSYS_0A251028&REV_20\3&11583659&0&A2 Driver: n/a Name: Intel(R) USB 3.10 eXtensible Host Controller - 1.20 (Microsoft) Device ID: PCI\VEN_8086&DEV_A0ED&SUBSYS_00000000&REV_20\3&11583659&0&A0 Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.0662 (English), 12/26/2020 19:28:08, 602440 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.0662 (English), 12/26/2020 19:28:08, 137936 bytes Name: Intel(R) PCI Express Root Port #9 - A0B0 Device ID: PCI\VEN_8086&DEV_A0B0&SUBSYS_0A251028&REV_20\3&11583659&0&E8 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.0964 (English), 4/29/2021 09:00:43, 469304 bytes Name: Intel(R) Tigerlake Telemetry Aggregator Driver Device ID: PCI\VEN_8086&DEV_9A0D&SUBSYS_0A251028&REV_01\3&11583659&0&50 Driver: C:\Windows\system32\DRIVERS\IntelTA.sys, 10.00.19041.0546 (English), 12/26/2020 19:28:08, 26608 bytes Name: Intel(R) Serial IO I2C Host Controller - A0E9 Device ID: PCI\VEN_8086&DEV_A0E9&SUBSYS_0A251028&REV_20\3&11583659&0&A9 Driver: C:\Windows\System32\DriverStore\FileRepository\ialpss2_i2c_tgl.inf_amd64_ab87bf17a571e523\iaLPSS2_I2C_TGL.sys, 30.100.2031.0002 (English), 8/9/2020 18:42:26, 197272 bytes Name: Qualcomm QCA9377 802.11ac Wireless Adapter Device ID: PCI\VEN_168C&DEV_0042&SUBSYS_18101028&REV_31\4&CA52D08&0&00E9 Driver: C:\Windows\system32\DRIVERS\Qcamain10x64.sys, 12.00.0000.0967 (English), 8/24/2020 00:19:16, 2443016 bytes Driver: C:\Windows\system32\DRIVERS\qca9377_2_0.bin, 8/24/2020 00:08:46, 1143296 bytes Driver: C:\Windows\system32\DRIVERS\Data9377_2_0.msc, 8/24/2020 00:08:46, 97202 bytes Driver: C:\Windows\system32\DRIVERS\eeprom_qca9377_1p1_NFA435_olpc.bin, 4/27/2020 02:58:56, 8124 bytes Driver: C:\Windows\system32\DRIVERS\eeprom_qca9377_1p1_NFA435_olpc_DE_P87G.bin, 8/25/2020 05:56:04, 8124 bytes Driver: C:\Windows\system32\DRIVERS\eeprom_qca9377_1p1_NFA435_olpc_DE_P88G.bin, 8/25/2020 05:56:04, 8124 bytes Driver: C:\Windows\system32\DRIVERS\eeprom_qca9377_1p1_NFA435_olpc_DE_089C.bin, 8/25/2020 05:56:04, 8124 bytes Driver: C:\Windows\system32\DRIVERS\eeprom_qca9377_1p1_NFA435_olpc_DE_P130G.bin, 4/27/2020 02:58:56, 8124 bytes Driver: C:\Windows\system32\DRIVERS\QcomWlanSrvx64.exe, 1.00.0000.0001 (English), 8/24/2020 00:19:16, 191752 bytes Name: Intel(R) Iris(R) Xe Graphics Device ID: PCI\VEN_8086&DEV_9A49&SUBSYS_0A251028&REV_01\3&11583659&0&10 Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdkmdn64.sys, 27.20.0100.9466 (English), 5/14/2021 10:54:02, 28296088 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxsn64.vp, 5/14/2021 10:24:42, 5407 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd10iumd64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:00, 19079088 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd11dxva64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:06, 79015880 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd12dxva64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:14, 78918480 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd12umd64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:16, 9678120 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdgmm64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:36, 3393256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igfxcmrt64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:58, 214040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igfx11cmrt64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:56, 217176 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdumdim64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:52, 1459240 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdail64.dll, 5/14/2021 10:53:58, 193944 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd9dxva64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:24, 78663056 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iga64.dll, 5/14/2021 10:53:52, 2922720 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igc64.dll, 27.20.0100.9466 (English), 5/14/2021 10:53:58, 46357992 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\SPIRVDLL.dll, 5/14/2021 10:55:32, 3777944 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\UniversalAdapter64.dll, 5/14/2021 10:55:56, 323336 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\opencl-clang64.dll, 2.00.0008.0000 (English), 5/14/2021 10:55:52, 103150784 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdfcl64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:34, 1035184 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdmd64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:42, 11452616 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdml64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:48, 4212240 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdde64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:26, 417808 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdinfo64.dll, 5/14/2021 10:54:38, 155736 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdext64.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:32, 277192 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd10iumd32.dll, 27.20.0100.9466 (English), 5/14/2021 10:53:58, 14828024 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd11dxva32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:04, 77611704 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd12dxva32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:10, 77511160 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd12umd32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:14, 9473224 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdgmm32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:34, 2526160 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdumdim32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:50, 1294568 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdail32.dll, 5/14/2021 10:53:56, 158104 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igd9dxva32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:20, 77274672 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igfxcmrt32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:56, 170816 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igfx11cmrt32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:54, 172864 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iga32.dll, 5/14/2021 10:53:48, 2344760 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igc32.dll, 27.20.0100.9466 (English), 5/14/2021 10:53:56, 39895472 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\SPIRVDLL32.dll, 5/14/2021 10:55:32, 2903960 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\UniversalAdapter32.dll, 5/14/2021 10:55:54, 268568 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\opencl-clang32.dll, 2.00.0008.0000 (English), 5/14/2021 10:55:48, 83702408 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdfcl32.dll, 27.20.0100.9466 (English), 5/14/2021 10:53:58, 956824 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdmd32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:40, 8826096 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdml32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:46, 3264424 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdde32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:24, 338544 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdinfo32.dll, 5/14/2021 10:54:36, 130000 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdext32.dll, 27.20.0100.9466 (English), 5/14/2021 10:54:28, 221256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\UMED.dll, 5/14/2021 10:55:54, 141696 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxo64.vp, 5/14/2021 10:24:42, 42513 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxc64.vp, 5/14/2021 10:24:42, 44194 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxg64.vp, 5/14/2021 10:24:42, 43760 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxo64_dev.vp, 5/14/2021 10:24:42, 43143 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxc64_dev.vp, 5/14/2021 10:24:42, 43214 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxg64_dev.vp, 5/14/2021 10:24:42, 43732 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxa64.vp, 5/14/2021 10:24:42, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\iglhxa64.cpa, 5/14/2021 10:24:42, 1376256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\IntelCpHDCPSvc.exe, 27.20.0100.9466 (English), 5/14/2021 10:54:38, 356744 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\cp_resources.bin, 5/14/2021 10:24:16, 2415596 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\ig12icd64.dll, 27.20.0100.9466 (English), 5/14/2021 10:53:46, 16029592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\ig12icd32.dll, 27.20.0100.9466 (English), 5/14/2021 10:53:46, 12979624 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\OSSCOPYRIGHT.txt, 5/14/2021 10:24:48, 1372 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igvk64.dll, 27.20.0100.9466 (English), 5/14/2021 10:55:08, 17295112 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igvk64.json, 5/14/2021 10:24:42, 135 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\VulkanRT-EULA.txt, 5/14/2021 10:24:48, 4008 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igvk32.dll, 27.20.0100.9466 (English), 5/14/2021 10:55:06, 15439200 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igvk32.json, 5/14/2021 10:24:42, 135 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\vulkan-1-64.dll, 1.02.0162.0001 (English), 5/14/2021 10:55:36, 1093712 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\vulkaninfo-64.exe, 1.02.0162.0001 (English), 5/14/2021 10:55:40, 1851288 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\vulkan-1-32.dll, 1.02.0162.0001 (English), 5/14/2021 10:55:36, 947792 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\vulkaninfo-32.exe, 1.02.0162.0001 (English), 5/14/2021 10:55:38, 1431952 bytes Driver: C:\Windows\SysWow64\vulkan-1.dll, 1.02.0162.0001 (English), 5/14/2021 10:55:36, 947792 bytes Driver: C:\Windows\SysWow64\vulkaninfo.exe, 1.02.0162.0001 (English), 5/14/2021 10:55:38, 1431952 bytes Driver: C:\Windows\SysWow64\vulkan-1-999-0-0-0.dll, 1.02.0162.0001 (English), 5/14/2021 10:55:36, 947792 bytes Driver: C:\Windows\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.02.0162.0001 (English), 5/14/2021 10:55:38, 1431952 bytes Driver: C:\Windows\system32\vulkan-1.dll, 1.02.0162.0001 (English), 5/14/2021 10:55:36, 1093712 bytes Driver: C:\Windows\system32\vulkaninfo.exe, 1.02.0162.0001 (English), 5/14/2021 10:55:40, 1851288 bytes Driver: C:\Windows\system32\vulkan-1-999-0-0-0.dll, 1.02.0162.0001 (English), 5/14/2021 10:55:36, 1093712 bytes Driver: C:\Windows\system32\vulkaninfo-1-999-0-0-0.exe, 1.02.0162.0001 (English), 5/14/2021 10:55:40, 1851288 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 5/14/2021 10:54:52, 361880 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdrcl32.dll, 23.20.0100.9466 (English), 5/14/2021 10:54:08, 4098456 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 5/14/2021 10:54:56, 499096 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\ze_loader.dll, 1.02.0003.0000 (English), 5/14/2021 10:55:44, 421288 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\ze_validation_layer.dll, 1.02.0003.0000 (English), 5/14/2021 10:55:46, 137112 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\ze_tracing_layer.dll, 1.02.0003.0000 (English), 5/14/2021 10:55:46, 605592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\ControlLib.dll, 1.00.0008.0000 (English), 5/14/2021 10:53:24, 330664 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\igdrcl64.dll, 23.20.0100.9466 (English), 5/14/2021 10:54:12, 4694416 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\ze_intel_gpu64.dll, 5/14/2021 10:55:42, 4226456 bytes Driver: C:\Windows\SysWow64\OpenCL.dll, 2.02.0008.0000 (English), 5/14/2021 10:54:52, 361880 bytes Driver: C:\Windows\system32\OpenCL.dll, 2.02.0008.0000 (English), 5/14/2021 10:54:56, 499096 bytes Driver: C:\Windows\system32\ze_loader.dll, 1.02.0003.0000 (English), 5/14/2021 10:55:44, 421288 bytes Driver: C:\Windows\system32\ze_validation_layer.dll, 1.02.0003.0000 (English), 5/14/2021 10:55:46, 137112 bytes Driver: C:\Windows\system32\ze_tracing_layer.dll, 1.02.0003.0000 (English), 5/14/2021 10:55:46, 605592 bytes Driver: C:\Windows\system32\ControlLib.dll, 1.00.0011.0000 (English), 5/20/2021 12:01:50, 346632 bytes Driver: C:\Windows\SysWow64\libmfxhw32.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:18, 246280 bytes Driver: C:\Windows\SysWow64\mfxplugin32_hw.dll, 1.21.0003.0004 (English), 5/14/2021 10:54:58, 13487512 bytes Driver: C:\Windows\system32\libmfxhw64.dll, 11.21.0004.0014 (English), 5/20/2021 12:03:38, 299024 bytes Driver: C:\Windows\system32\mfxplugin64_hw.dll, 1.21.0003.0004 (English), 5/14/2021 10:55:02, 26659752 bytes Driver: C:\Windows\system32\intel_gfx_api-x64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:10, 162992 bytes Driver: C:\Windows\SysWow64\intel_gfx_api-x86.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:10, 138504 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfxplugin64_hw.dll, 1.21.0003.0004 (English), 5/14/2021 10:55:02, 26659752 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfxplugin64_av1e_gacc.dll, 5/14/2021 10:55:16, 5514408 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\intel_gfx_api-x64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:10, 162992 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfxplugin32_hw.dll, 1.21.0003.0004 (English), 5/14/2021 10:54:58, 13487512 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfxplugin32_av1e_gacc.dll, 5/14/2021 10:55:14, 4528568 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\intel_gfx_api-x86.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:10, 138504 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_h264ve_32.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:36, 2603816 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_mjpgvd_32.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:04, 2459544 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_h265ve_32.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:38, 2616848 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_vp9ve_32.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:44, 2612168 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_encrypt_32.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:32, 2444352 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_av1hve_32.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:24, 2613688 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\c_32.cpa, 5/14/2021 10:24:16, 1361159 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\cpa_32.vp, 5/14/2021 10:24:16, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\dev_32.vp, 5/14/2021 10:24:16, 57143 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\he_32.vp, 5/14/2021 10:24:16, 71873 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mj_32.vp, 5/14/2021 10:24:44, 67137 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\h265e_32.vp, 5/14/2021 10:24:16, 73525 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\vp9e_32.vp, 5/14/2021 10:24:48, 73056 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_av1hve_32.vp, 5/14/2021 10:24:44, 73101 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_h264ve_64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:38, 3215944 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_mjpgvd_64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:06, 3043224 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_h265ve_64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:42, 3236856 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_vp9ve_64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:44, 3230200 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_encrypt_64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:34, 3010248 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_av1hve_64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:30, 3232232 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\c_64.cpa, 5/14/2021 10:24:16, 1376256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\cpa_64.vp, 5/14/2021 10:24:16, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\dev_64.vp, 5/14/2021 10:24:16, 56359 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\he_64.vp, 5/14/2021 10:24:16, 13665 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mj_64.vp, 5/14/2021 10:24:44, 13409 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\h265e_64.vp, 5/14/2021 10:24:16, 14257 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\vp9e_64.vp, 5/14/2021 10:24:48, 14120 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\mfx_mft_av1hve_64.vp, 5/14/2021 10:24:44, 14089 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\libmfxhw64.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:14, 25413192 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_90af7db2c816ac7b\libmfxhw32.dll, 11.21.0003.0004 (English), 5/14/2021 10:55:12, 23903000 bytes Name: Intel(R) PCI Express Root Port #10 - A0B1 Device ID: PCI\VEN_8086&DEV_A0B1&SUBSYS_0A251028&REV_20\3&11583659&0&E9 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.0964 (English), 4/29/2021 09:00:43, 469304 bytes Name: Intel RST VMD Managed Controller 09AB Device ID: PCI\VEN_8086&DEV_09AB&SUBSYS_00000000&REV_00\3&11583659&0&B8 Driver: n/a Name: Intel(R) SMBus - A0A3 Device ID: PCI\VEN_8086&DEV_A0A3&SUBSYS_0A251028&REV_20\3&11583659&0&FC Driver: n/a Name: Realtek PCIe GbE Family Controller Device ID: PCI\VEN_10EC&DEV_8168&SUBSYS_0A251028&REV_15\01000000684CE00000 Driver: C:\Windows\system32\DRIVERS\rt640x64.sys, 10.39.0212.2020 (English), 5/20/2020 15:42:24, 1162848 bytes Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_A0C8&SUBSYS_0A251028&REV_20\3&11583659&0&FB Driver: C:\Windows\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_8c64c6214ca63c3c\IntcAudioBus.sys, 10.30.0000.4842 (English), 12/1/2020 19:22:26, 297328 bytes Driver: C:\Windows\system32\DRIVERS\drmk.sys, 10.00.19041.0746 (English), 1/13/2021 12:04:20, 97792 bytes Driver: C:\Windows\system32\DRIVERS\portcls.sys, 10.00.19041.0746 (English), 1/13/2021 12:04:20, 388608 bytes Name: Intel RST VMD Controller 9A0B Device ID: PCI\VEN_8086&DEV_9A0B&SUBSYS_0A251028&REV_00\3&11583659&0&70 Driver: C:\Windows\system32\DRIVERS\iaStorVD.sys, 18.01.0006.1039 (English), 2/25/2021 09:07:16, 1480048 bytes Driver: C:\Windows\system32\DRIVERS\iaStorAfs.sys, 18.01.0006.1039 (English), 2/25/2021 09:02:40, 73096 bytes Driver: C:\Windows\system32\iaStorAfsService.exe, 18.01.0006.1039 (English), 2/25/2021 09:03:14, 2965896 bytes Driver: C:\Windows\system32\iaStorAfsNative.exe, 18.01.0006.1039 (English), 2/25/2021 09:03:12, 219504 bytes Driver: C:\Windows\system32\OptaneEventLogMsg.dll, 18.01.0006.1039 (English), 2/25/2021 09:07:22, 23400 bytes Driver: C:\Windows\system32\Optane.dll, 18.01.0006.1039 (English), 2/25/2021 09:07:20, 119664 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iastorvd.inf_amd64_3d154b973973bd49\RstMwService.exe, 18.01.0006.1039 (English), 2/25/2021 09:07:42, 1916808 bytes Driver: C:\Windows\system32\RstMwEventLogMsg.dll, 18.01.0006.1039 (English), 2/25/2021 09:07:32, 27528 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.19041.0508 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.19041.0508 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.19041.0001 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.19041.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.19041.0450 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.19041.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.19041.0928 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.19041.0001 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.19041.0001 DV Muxer,0x00400000,0,0,qdv.dll,10.00.19041.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.19041.0746 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.19041.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.19041.0746 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.19041.0746 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.19041.1023 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.19041.0329 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.19041.0001 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.0746 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.19041.0746 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.0746 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.19041.0329 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.19041.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.0001 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.19041.0746 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.19041.0746 DV Splitter,0x00600000,1,2,qdv.dll,10.00.19041.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.19041.0746 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.19041.0001 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.19041.0746 Video Renderer,0x00800001,1,0,quartz.dll,10.00.19041.0746 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.19041.0001 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.19041.0746 Video Renderer,0x00400000,1,0,quartz.dll,10.00.19041.0746 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.19041.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.19041.0001 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax, File writer,0x00200000,1,0,qcap.dll,10.00.19041.0001 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.19041.0746 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.19041.0746 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.0001 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.19041.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.19041.0329 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.19041.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.19041.0746 Null Renderer,0x00200000,1,0,qedit.dll,10.00.19041.0746 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.19041.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.19041.0001 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.19041.0001 Smart Tee,0x00200000,1,2,qcap.dll,10.00.19041.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.0746 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.19041.0746 Wave Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.19041.0746 File stream renderer,0x00400000,1,1,quartz.dll,10.00.19041.0746 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.19041.0001 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.19041.0001 AVI Mux,0x00200000,1,0,qcap.dll,10.00.19041.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.19041.0746 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.19041.0746 File Source (URL),0x00400000,0,1,quartz.dll,10.00.19041.0746 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.19041.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.19041.0546 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.19041.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.19041.0746 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.19041.0867 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.19041.0001 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.19041.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.19041.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.19041.0746 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.19041.0508 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.19041.0508 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 PCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.0746 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.19041.0746 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.19041.0746 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.19041.0746 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.19041.0746 Audio Capture Sources: Microphone Array (Intel� Smart Sound Technology for Digital Microphones),0x00200000,0,0,qcap.dll,10.00.19041.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.19041.0746 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.0746 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.0746 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.19041.0746 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.19041.0746 WDM Streaming Capture Devices: Realtek HD Audio Mic input with SST,0x00200000,1,2,ksproxy.ax,10.00.19041.0746 ,0x00000000,0,0,, Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 ,0x00000000,0,0,, Integrated Webcam,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Intel� Smart Sound Technology DMIC Microphone,0x00200000,1,5,ksproxy.ax,10.00.19041.0746 WDM Streaming Rendering Devices: Realtek HD Audio output with SST,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 Realtek HD Audio 2nd output with SST,0x00200000,2,2,ksproxy.ax,10.00.19041.0746 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.19041.0001 Video Capture Sources: Integrated Webcam,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.0746 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.19041.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.19041.0001 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.0746 Audio Renderers: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.19041.0746 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.19041.0746 DirectSound: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.19041.0746 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] MEDIASUBTYPE_DVD_LPCM_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_VIDEO, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS {78766964-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_mp4s, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {58564944-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {5634504D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_MP4S, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject {44495658-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mpg4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_h264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_H264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_MP43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMV2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS2, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_M4S2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WVP2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_AVC1, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_MPEG_LOAS, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG_ADTS_AAC, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_WMAUDIO_LOSSLESS, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_WMAUDIO3, WMAudio Decoder DMO, CLSID_CWMADecMediaObject WMMEDIASUBTYPE_WMAudioV8, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS WMMEDIASUBTYPE_MP3, MP3 Decoder DMO, CLSID_CMP3DecMediaObject MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec {6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec {20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject --------------------------- Media Foundation File Versions --------------------------- mfcore.dll, 10.00.19041.1023 mfreadwrite.dll, 10.00.19041.0746 mfcaptureengine.dll, 10.00.19041.0906 mfsensorgroup.dll, 10.00.19041.0964 windows.media.dll, 10.00.19041.1023 frameserver.dll, 10.00.19041.0964 frameserverclient.dll, 10.00.19041.0964 --------------------------- Media Foundation Transforms --------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms] : , , , [, ], Video Decoders: Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 11.21.0003.0004 Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 11.21.0003.0004 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.19041.1023 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.19041.0001 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.19041.0450 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.19041.1023 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.19041.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.19041.0928 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.19041.0329 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.19041.0001 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.19041.0001 WebpImageExtension HEVCVideoExtension MPEG2VideoExtension HEIFImageExtension VP9VideoExtensionDecoder Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 11.21.0003.0004 Intel� Hardware Accelerated AV1 Encoder MFT, {62C053CE-5357-4794-8C5A-FBEFFEFFB82D}, 0x4, 7, mfx_mft_av1hve_64.dll, 11.21.0003.0004 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 11.21.0003.0004 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 11.21.0003.0004 Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 11.21.0003.0004 Intel� Hardware Accelerated AV1 Encoder MFT, {62C053CE-5357-4794-8C5A-FBEFFEFFB82D}, 0x4, 7, mfx_mft_av1hve_64.dll, 11.21.0003.0004 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 11.21.0003.0004 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 11.21.0003.0004 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.19041.0964 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.19041.0867 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.19041.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.19041.0001 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.19041.0001 HEVCVideoExtensionEncoder HEIFImageExtension VP9VideoExtensionEncoder Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.19041.0746 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.19041.0867 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.19041.0746 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.19041.0746 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.19041.0867 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.19041.0789 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.19041.1023 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.19041.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.19041.0508 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.19041.0867 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.19041.1023 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.19041.1023 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.19041.0508 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.19041.0746 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.19041.1023 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.19041.0867 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.19041.0001 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.19041.1023 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.19041.1023 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.19041.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.19041.0746 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.19041.1023 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.19041.0746 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.19041.1023 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.19041.0746 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.19041.0508 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.19041.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.19041.0001 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.19041.0508 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.19041.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.19041.0746 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.19041.0001 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.19041.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.19041.0001 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.19041.1023 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.19041.1023 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableEncoders = 1 EnableDecoders = 1 ------------------------------------- Media Foundation Byte Stream Handlers ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] .3g2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .ac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .adt, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .am?, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler .amr, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler, Preferred .asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred .dvr-ms, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler .dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred .ec3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred .m2t, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m2ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mk3d, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mka, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mks, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mkv, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mov, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp2v, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mpg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .nsc, {B084785C-DDE0-4D30-8CA8-05A373E185BE}, NSC Byte Stream Handler, Preferred .sami, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .smi, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .tod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .uvu, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .vob, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred .weba, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wtv, {65964407-A5D8-4060-85B0-1CCD63F768E2}, WTV Byte Stream Handler, Preferred audio/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/aacp, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/eac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/L16, {3FFB3B8C-EB99-472B-8902-E1C1B05F07CF}, LPCM Byte Stream Handler, Preferred audio/mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/MP4A-LATM, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/vnd.dlna.adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/vnd.dolby.dd-raw, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred audio/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred audio/x-aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/x-flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/x-m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred audio/x-mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-ms-wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred audio/x-wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred video/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/vnd.dece.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/vnd.dlna.mpeg-tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred video/x-m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred video/x-ms-asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred -------------------------------- Media Foundation Scheme Handlers -------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] file:, {477EC299-1421-4BDD-971F-7CCB933F21AD}, File Scheme Handler, Preferred http:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler http:, {9EC4B4F9-3029-45AD-947B-344DE2A249E2}, Urlmon Scheme Handler http:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpd:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler, Preferred https:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpsd:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcast:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcrecv:, {FA6D33D4-9405-4BA5-9983-12604AC8E77A}, Miracast Sink Scheme Handler, Preferred mms:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ms-appdata:, {CFC81939-3886-4ACF-9692-DA58037AE716}, MsAppData Scheme Handler, Preferred ms-appx-web:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppxWeb Scheme Handler, Preferred ms-appx:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppx Scheme Handler, Preferred ms-winsoundevent:, {F79A6BF9-7415-4CF3-AE10-4559509ABC3C}, Sound Event Scheme Handler, Preferred rtsp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtsps:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred sdp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ------------------------------------- Preferred Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred] , [, ] {EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B} {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905} MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9} {00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} {0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A} {00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} {00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B} {00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC} {00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE} KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514} {00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786} KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject ------------------------------------- Disabled Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse] ------------------------ Disabled Media Sources ------------------------ [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse] --------------- EVR Power Information --------------- Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket 1579942207045792414, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: IGCC.exe P2: 1.100.3325.0 P3: 10.0.19043.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER1 +++: Fault bucket 1253138703961848035, type 5 Event Name: RADAR_PRE_LEAK_WOW64 Response: Not available Cab Id: 0 Problem signature: P1: t6sp.exe P2: 1.0.0.1 P3: 10.0.19043.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER2 +++: Fault bucket 81635134371, type 5 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: setup.tmp P2: 51.1052.0.0 P3: 506a75b5 P4: botva2.dll_unloaded P5: 0.9.7.151 P6: 2a425e19 P7: 00005514 P8: c0000005 P9: 00000008 P10: +++ WER3 +++: Fault bucket 2077032431876899057, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: cls-lolly_x64.exe P2: 0.0.0.0 P3: 10.0.19043.2.0.0 P4: P5: P6: P7: P8: P9: P10: +++ WER4 +++: Fault bucket AV_vgk!Egg, type 0 Event Name: BlueScreen Response: Not available Cab Id: 98f5ae58-e703-4ae2-a538-f703e0e45101 Problem signature: P1: a P2: ffffcc0d4c805d40 P3: 2 P4: 0 P5: fffff80754de6350 P6: 10_0_19043 P7: 0_0 P8: 768_1 P9: P10: +++ WER5 +++: Fault bucket LKD_0x1A8_LONG_POWER_PRESS_GraphicsUnknown_Intel_dxgkrnl!DISPLAYSTATECHECKER::CreateBlackScreenLiveDump, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 76018c60-b822-4ad6-9351-2eee62acc37d Problem signature: P1: 1a8 P2: 8 P3: 0 P4: 0 P5: 0 P6: 10_0_19043 P7: 0_0 P8: 768_1 P9: P10: +++ WER6 +++: Fault bucket LKD_0x141_Tdr:6_IMAGE_igdkmdn64.sys_GEN12LP_DX12_BBHANG, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 82d47675-c3f0-46fe-b5d5-b83500d5f6e2 Problem signature: P1: 141 P2: ffffc6078dabd010 P3: fffff8049e0857f0 P4: 0 P5: 1b48 P6: 10_0_19043 P7: 0_0 P8: 768_1 P9: P10: +++ WER7 +++: Fault bucket LKD_0x141_Tdr:6_IMAGE_igdkmdn64.sys_GEN12LP_DX12_BBHANG, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: e47dd748-4821-4f62-82b1-cf5fb7ceef3f Problem signature: P1: 141 P2: ffffc60790099050 P3: fffff8049e0857f0 P4: 0 P5: 760 P6: 10_0_19043 P7: 0_0 P8: 768_1 P9: P10: +++ WER8 +++: Fault bucket LKD_0x1A8_LONG_POWER_PRESS_OSDwmNotVisible_dxgkrnl!DISPLAYSTATECHECKER::CreateBlackScreenLiveDump, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 0f930a48-4cbe-4948-b137-1529e832a47d Problem signature: P1: 1a8 P2: 8 P3: 0 P4: 0 P5: 0 P6: 10_0_19043 P7: 0_0 P8: 768_1 P9: P10: +++ WER9 +++: Fault bucket LKD_0x1B8_Intel_Blackscreen_Blackbox_dxgkrnl!DxgCreateLiveDumpWithDriverBlob, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 5396a0cc-9eda-4aeb-aec0-bc2e7763c399 Problem signature: P1: 1b8 P2: 8 P3: 0 P4: 0 P5: 0 P6: 10_0_19043 P7: 0_0 P8: 768_1 P9: P10: ...#SSU#...