# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"11/29/2023" Time:"00:00:32.3467478" # Scanned Hardware Computer: BaseBoard Manufacturer:"LENOVO" BIOS Mode:"Legacy" BIOS Version/Date:"LENOVO KMCN19WW , 09/20/2023 12:00 AM" CD or DVD:"Not Available" Embedded Controller Version:"1.19" Platform Role:"Mobile" Processor:"12th Gen Intel(R) Core(TM) i7-12700H , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"3.3" Sound Card:"Realtek High Definition Audio(SST)" System Manufacturer:"LENOVO" System Model:"82VB" System SKU:"LENOVO_MT_82VB_BU_idea_FM_Slim 7 16IAH7" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"Not Available" - "Intel(R) Arc(TM) A370M Graphics" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Internal" Adapter RAM:"1.00 GB" Availability:"Offline" Bits Per Pixel:"Not Available" - "Caption":"Intel(R) Arc(TM) A370M Graphics" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Arc+A370M+Graphics" CoInstallers:"oem144.inf,iDG2DH_w10_DS,Internal,Intel(R) Arc(TM) A370M Graphics Family" Color Table Entries:"Not Available" Dedicated Video Memory:"Not Available" Driver:"igdkmdnd64.sys" Driver Date:"06/15/2023 03:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdkmdnd64.sys" Driver Provider:"Intel Corporation" Driver Version:"31.0.101.4502" INF:"oem144.inf" INF Section:"iDG2DH_w10_DS" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12umd64.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 3, device 0, function 0" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"Not Available" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_5693&SUBSYS_384217AA&REV_05\6&24D5ABFE&0&00080030" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"Not Available" Refresh Rate - Maximum:"Not Available" Refresh Rate - Minimum:"Not Available" Resolution:"Not Available" Scan Mode:"Not Available" Service Name:"igfxnd" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) Arc(TM) A370M Graphics Family" - "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:"oem155.inf,iADLPD_w10_DS,Internal,Intel(R) Iris(R) Xe Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmdn64.sys" Driver Date:"06/15/2023 03:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdkmdn64.sys" Driver Provider:"Intel Corporation" Driver Version:"31.0.101.4502" INF:"oem155.inf" INF Section:"iADLPD_w10_DS" Install Date:"Not Available" Installed Drivers:"<>,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\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_46A6&SUBSYS_380B17AA&REV_0C\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"60 Hz" Refresh Rate - Maximum:"75 Hz" Refresh Rate - Minimum:"23 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):"25.78 GB" Physical Memory (Installed):"32 GB" Physical Memory (Total):"31.73 GB" - "BANK 0" Capacity:"4 GB" Channel:"Controller0-ChannelA" Configured Clock Speed:"4800 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"First position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKCKC@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 0" Capacity:"4 GB" Channel:"Controller1-ChannelA" Configured Clock Speed:"4800 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"First position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKCKC@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 1" Capacity:"4 GB" Channel:"Controller0-ChannelB" Configured Clock Speed:"4800 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Second position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKCKC@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 1" Capacity:"4 GB" Channel:"Controller1-ChannelB" Configured Clock Speed:"4800 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Second position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKCKC@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 2" Capacity:"4 GB" Channel:"Controller0-ChannelC" Configured Clock Speed:"4800 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKCKC@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 2" Capacity:"4 GB" Channel:"Controller1-ChannelC" Configured Clock Speed:"4800 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKCKC@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 3" Capacity:"4 GB" Channel:"Controller0-ChannelD" Configured Clock Speed:"4800 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKCKC@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 3" Capacity:"4 GB" Channel:"Controller1-ChannelD" Configured Clock Speed:"4800 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKCKC@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"KMCN19WW, LENOVO - 1" Caption:"Motherboard" Chipset:"Not Available" Date:"09/20/2023 03:00 AM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"LENOVO" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"LNVNB161216" Serial Number:"YX04DN2V" Status:"OK" Version:"SDK0T76461 WIN" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "AVG Secure VPN Wintun Adapter" Availability:"Running or Full Power" Caption:"AVG Secure VPN Wintun Adapter" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"No" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"avgWintun.sys" Driver Date:"10/03/2022 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\avgWintun.sys" Driver Provider:"AVG Technologies" Driver Version:"0.14.1.60" Index:"0013" INF:"oem76.inf" INF Section:"avgWintun.Install" 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:"11/29/2023 12:21 PM" Location:"Not Available" MAC Address:"Not Available" Manufacturer:"AVG Technologies" Media Type: Net Connection ID:"Secure VPN" NetCfgInstanceId:"{3C0CF1B8-285A-42D1-BC5F-37DEB0288DF6}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0000" 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:"AVG Secure VPN Wintun Adapter" Service Name:"avgWintun" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Not Available" - "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: - "Bluetooth Device (Personal Area Network)" Availability:"Running or Full Power" Caption:"Bluetooth Device (Personal Area Network)" 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:"bthpan.sys" Driver Date:"06/21/2006 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\bthpan.sys" Driver Provider:"Microsoft" Driver Version:"10.0.19041.3636" Index:"0003" INF:"bthpan.inf" INF Section:"BthPan.Install" 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:"11/29/2023 12:21 PM" Location:"Not Available" MAC Address:"C4:03:A8:49:BF:A5" Manufacturer:"Microsoft" Media Type: Net Connection ID:"Bluetooth Network Connection" NetCfgInstanceId:"{A0392A97-E234-4F56-B285-C1E10FB5CEEF}" Number of VLANs:"0" PNP Device ID:"BTH\MS_BTHPAN\6&B16FD5A&0&2" 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:"Bluetooth Device (Personal Area Network)" Service Name:"BthPan" 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: - "Intel(R) Wi-Fi 6E AX211 160MHz" Access Point:"b8:bc:1b:42:9b:83" Authentication:"WPA2-Personal" Availability:"Running or Full Power" - "Caption":"Intel(R) Wi-Fi 6E AX211 160MHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Wi+Fi+6E+AX211+160MHz" Channel:"11" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Auto Connect" Default IP Gateway:"192.168.1.1" DHCP Enabled:"Yes" DHCP Lease Expires:"03/11/1915 05:53 AM" DHCP Lease Obtained:"11/29/2023 12:21 PM" DHCP Server:"192.168.1.1" Driver:"Netwtw12.sys" Driver Date:"08/07/2023 12:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\netwtw6e.inf_amd64_cc3a2460c42c06f6\Netwtw12.sys" Driver Provider:"Intel" Driver Version:"22.250.1.2" Index:"0001" INF:"oem95.inf" INF Section:"Install_GEN_SLR_GfP2_211_AX_6G_2x2_WinT" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.1.20;fe80::9481:a078:80f7:302" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"11/29/2023 12:21 PM" Location:"PCI bus 0, device 20, function 3" MAC Address:"C4:03:A8:49:BF:A1" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{ACDD9126-AC0F-4EBE-A3C1-AF5DCC15CBF6}" Network Name:"SeaTac" Network Type:"Infrastructure" Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_51F0&SUBSYS_00948086&REV_01\3&11583659&0&A3" 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:"Intel(R) Wi-Fi 6E AX211 160MHz" Profile:"SeaTac" Radio Type:"802.11n" Receive Rate:"270 Mbps" Service Name:"Netwtw12" Signal Strength:"95%" State:"connected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate:"270 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" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" ChannelWidth6:Channel Width for 6GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac/ax Wireless Mode:"4. 802.11ax (3)" Is6GhzBandSupported:Ultra High Band (6GHz):"Enabled (1)" MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)" RoamAggressiveness:Roaming Aggressiveness:"3. Medium (2)" RoamingPreferredBandType:Preferred Band:"1. No Preference (0)" ThroughputBoosterEnabled:Throughput Booster:"Disabled (0)" uAPSDSupport:U-APSD support:"Disabled (0)" WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)" - "Operating System" .Net Framework Version:"4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Locale:"United States" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Home" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"4.75 GB" Physical Memory (Available):"25.79 GB" Physical Memory (Installed):"32 GB" Physical Memory (Total):"31.73 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.19045 Build 19045" Virtual Memory (Available):"29.99 GB" Virtual Memory (Total):"36.48 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [7/26/2023]" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [7/26/2023]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [7/26/2023]" KB2467173:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [7/26/2023]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [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 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [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]" KB4562830:"Update [10/6/2022]" KB5003791:"Update [10/6/2021]" KB5005699:"Security Update [10/6/2021]" KB5007401:"Update [10/6/2022]" KB5011048:"Update [7/2/2023]" KB5012170:"Security Update [10/7/2022]" KB5015684:"Update [2/1/2023]" KB5016705:"Update [10/6/2022]" KB5018506:"Update [11/11/2022]" KB5020372:"Update [12/14/2022]" KB5022924:"Update [3/15/2023]" KB5023794:"Update [3/26/2023]" KB5025315:"Update [5/10/2023]" KB5026879:"Update [6/19/2023]" KB5027122:"Update [6/19/2023]" KB5028318:"Update [7/20/2023]" KB5028380:"Update [8/14/2023]" KB5029709:"Update [9/13/2023]" KB5031539:"Update [10/25/2023]" KB5031540:"Update [11/7/2023]" KB5032005:"Update [11/15/2023]" KB5032189:"Security Update [11/15/2023]" KB5032392:"Update [11/15/2023]" KB982573:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [7/26/2023]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [7/26/2023]" Microsoft ASP.NET Core 7.0.14 - Shared Framework (x64):".NET [11/15/2023]" Microsoft ASP.NET Core 7.0.7 - Shared Framework (x64):".NET [11/23/2023]" 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" - "12th Gen Intel(R) Core(TM) i7-12700H" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 154 Stepping 3" - "Chipset Name":"12th Gen Intel(R) Core(TM) i7-12700H" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=12th+Gen++Core+i7+12700H" CPU Speed:"2.30 GHz" Current Voltage:"1.8 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.3636" Ext. Family:"Not Available" Family:"Intel Core™ i7-2760QM" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"14 x 288 KB" Level 2 Cache:"14 x 4096 KB" Level 3 Cache:"24 MB" Load:"3%" Manufacturer:"GenuineIntel" Model:"154" Name:"12th Gen Intel(R) Core(TM) i7-12700H" Number of Cores:"14" Number of Cores Enabled:"14" Number of Logical Processors:"20" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000906A3" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"3" Version:"Not Available" - "Storage" - "SAMSUNG MZVLB1T0HBLR-000L2" Capablities:"Random Access, Supports Writing" Caption:"SAMSUNG MZVLB1T0HBLR-000L2" Cylinder - Total:"124519" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.19041.3636" Error Code:"Device is working properly" Firmware Revision:"3L1QEXF7" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"SAMSUNG MZVLB1T0HBLR-000L2" Name:"\\.\PHYSICALDRIVE0" Partitions:"3" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_SAMSUNG_MZVLB1T0\5&260CFC16&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"2000397735" Serial Number:"0025_388C_11B8_4B54." Size:"953.86 GB" Size – Available:"512.08 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"31752345" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Windows-SSD" Serial Number:"4447BD60" Size:"951.65 GB" Size – Available:"512.10 GB" Status:"Not Available" Volume Dirty:"No" - "Seagate BUP BL SCSI Disk Device" Capablities:"Random Access, Supports Writing" Caption:"Seagate BUP BL SCSI Disk Device" Cylinder - Total:"486401" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.19041.3636" Error Code:"Device is working properly" Firmware Revision:"0304" Heads - Total:"255" Index:"2" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"Seagate BUP BL SCSI Disk Device" Name:"\\.\PHYSICALDRIVE2" Partitions:"1" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_SEAGATE&PROD_BUP_BL\6&2BB7D25B&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"3" Sectors - Per Track:"63" Sectors - Total:"7814032065" Serial Number:"NA7TN8AN" Size:"3.64 TB" Size – Available:"2.11 TB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"124032255" - "F:" Availability:"Not Available" Caption:"F:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"SeaGate 4TB" Serial Number:"9E564D83" Size:"3725.90 GB" Size – Available:"2162.80 GB" Status:"Not Available" Volume Dirty:"No" - "Seagate BUP Slim SL SCSI Disk Device" Capablities:"Random Access, Supports Writing" Caption:"Seagate BUP Slim SL SCSI Disk Device" Cylinder - Total:"243201" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.19041.3636" Error Code:"Device is working properly" Firmware Revision:"0302" Heads - Total:"255" Index:"1" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"Seagate BUP Slim SL SCSI Disk Device" Name:"\\.\PHYSICALDRIVE1" Partitions:"1" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_SEAGATE&PROD_BUP_SLIM_SL\6&34F192E6&1&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"2" Sectors - Per Track:"63" Sectors - Total:"3907024065" Serial Number:"NA7L91YM" Size:"1.82 TB" Size – Available:"234.40 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"62016255" - "E:" Availability:"Not Available" Caption:"E:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Sea-Gate 2TB" Serial Number:"90E078AB" Size:"1863.02 GB" Size – Available:"234.40 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.3636_neutral_neutral_cw5n1h2txyewy!App.AppXw3qcpc7p849541dp39vvqd01bn7z9ybh.mca 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. ------------------------------------------------------------------- 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 Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel Corporation - Display - 31.0.101.4575. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- 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 4DF9E0F8.Netflix_6.98.1805.0_x64__mcm4njqhnhss8!Netflix.App.wwa 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Intel(R) OPROM FW Update Service service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: {GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffffe3871026b010, 0xfffff805b73f6b00, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: daa34636-5c74-47d1-855a-99c1f82a9c92. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 11:59:56 AM on ‎11/‎28/‎2023 was unexpected. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- 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 netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- 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_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38f89 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- 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_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- 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: {E48EDA45-43C6-48E0-9323-A7B2067D9CD5} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38f89 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 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: {9E175B68-F52A-11D8-B9A5-505054503030} ------------------------------------------------------------------- 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 WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WSearch with arguments "Unavailable" in order to run the server: {B52D54BB-4818-4EB9-AA80-F9EACD371DF8} ------------------------------------------------------------------- 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 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 netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- 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 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 netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- 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 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_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38f89 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- 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_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- 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 WpnUserService_38f89 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_38f89 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- 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 netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- 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} ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The NlaSvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The IKEEXT service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The LanmanWorkstation service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The AVG Tools service depends on the AVG Antivirus service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The AVG Antivirus service depends on the avgMonFlt service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dnscache service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The WlanSvc service depends on the Wcmsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The Wcmsvc service depends on the nsi service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The nsi service depends on the nsiproxy service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- The Dhcp service depends on the AFD service which failed to start because of the following error: A device attached to the system is not functioning. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: {GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The LenovoVantageService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80351738037, 0xffff81025ad52cc8, 0xffff81025ad52500). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 48157738-8b04-422e-9244-2373123adf71. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 5:35:00 PM on ‎11/‎27/‎2023 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: {GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- 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 device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} 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. ------------------------------------------------------------------- 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff807ad5e8037, 0xffff800af8347cc8, 0xffff800af8347500). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9f7b63cd-e731-4edf-be9f-067930026cfe. ------------------------------------------------------------------- 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 5:08:25 PM on ‎11/‎24/‎2023 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80784548037, 0xffffee8f48132cc8, 0xffffee8f48132500). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 50202db3-a6e6-4113-9e07-c8e72982bb70. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 3:08:04 PM on ‎11/‎23/‎2023 was unexpected. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The User Energy Server Service queencreek service terminated with the following error: {GUID Substitution} During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found. A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended. ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 2 time(s). ------------------------------------------------------------------- The LenovoVantageService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff801951d8037, 0xffffdb0c1b55acc8, 0xffffdb0c1b55a500). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00f7d158-e24e-40f7-83ba-fea371686f2f. ------------------------------------------------------------------- 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 3:53:32 PM on ‎11/‎20/‎2023 was unexpected. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000010e (0x0000000000000017, 0xffffcc863d1b0000, 0x0000000000000000, 0xffffffffc00002b6). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 530e1e89-3ace-41ce-b84b-ce8ca4ebf976. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 11:54:38 PM on ‎11/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80642748037, 0xffffd885e5f2acc8, 0xffffd885e5f2a500). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 65c60f1d-70f0-459d-a06e-d91b0fc582fb. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 5:27:22 PM on ‎11/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Windows Hello Face Software Device (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The device Windows Hello Face Software Device (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The device Windows Hello Face Software Device (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The AVG AntiTrack Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- The device Windows Hello Face Software Device (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Intel(R) Dynamic Tuning Technology Device Extension Component (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The AVG Driver Updater service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The certificate received from the remote server was issued by an untrusted certificate authority. Because of this, none of the data contained in the certificate can be validated. The TLS connection request has failed. The attached data contains the server certificate. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The server {DC6EFB56-9CFA-464D-8880-44885D7DC193} 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. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {DC6EFB56-9CFA-464D-8880-44885D7DC193} 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {8AB635F8-9A67-4698-AB99-784AD929F3B4} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffff938bbac09460, 0xfffff8054e586e30, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: baaa996f-de31-45f2-bb67-266ede4bece7. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 10:00:23 PM on ‎11/‎11/‎2023 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- 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 2:38:45 PM on ‎11/‎10/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 LenovoVantageService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Push Notifications User Service_1d3f57 service to connect. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff801448474b7, 0xffffd10659575cd8, 0xffffd10659575510). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3497be44-cd5a-43a8-bfa4-46e3fa25cedc. ------------------------------------------------------------------- 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 1:43:52 PM on ‎11/‎8/‎2023 was unexpected. ------------------------------------------------------------------- Database Table(L_IntelligenceEvents) Insertion Failed ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 AdobeUpdateService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- Database Table(L_AppDomainStatistics) Insertion Failed ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.3570_neutral_neutral_cw5n1h2txyewy!App.AppXw3qcpc7p849541dp39vvqd01bn7z9ybh.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff801701874b7, 0xffffeb0f68f7acd8, 0xffffeb0f68f7a510). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d8917a78-8cfa-4167-9ddc-cef720e77636. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 1:25:21 PM on ‎11/‎5/‎2023 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The Background Intelligent Transfer Service service terminated with the following service-specific error: A system shutdown is in progress. ------------------------------------------------------------------- The BITS service failed to start. Error 0x8007045B. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The AVG AntiTrack Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service Intel Connectivity Network Service with arguments "Unavailable" in order to run the server: {BF2E3B84-9D7F-4DA7-9EDC-104BDCC37727} ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- An error was detected. Error message: Entering error state, will request WDF to reset the driver ------------------------------------------------------------------- An error was detected. Error message: Changing state to Power State Error, Message: Failed to exit RTD3 ------------------------------------------------------------------- An error was detected. Error message: Error code: 0xF1, Sub error code: 0x1C2 ------------------------------------------------------------------- An error was detected. Error message: Error code: 0x145, Sub error code: 0x1CC ------------------------------------------------------------------- An error was detected. Error message: Error code: 0x145, Sub error code: 0xAB ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service BITS with arguments "Unavailable" in order to run the server: {4991D34B-80A1-4291-83B6-3328366B9097} ------------------------------------------------------------------- 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 {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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4NNS1-Microsoft.DesktopAppInstaller. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {94269C4E-071A-4116-90E6-52E557067E4E} 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. ------------------------------------------------------------------- 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 {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel(R) Dynamic Tuning Technology Telemetry Service 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, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has encountered an internal error and has failed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel(R) Dynamic Tuning Technology Telemetry Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- 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 TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Network Setup Service service terminated with the following error: Network Setup Service is not a valid Win32 application. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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} ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel(R) Dynamic Tuning Technology Telemetry Service 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, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXx4zfy1ffv3wctgdz2vypnybzjkh27jhw.mca 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {71DCE5D6-4B57-496B-AC21-CD5B54EB93FD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {71DCE5D6-4B57-496B-AC21-CD5B54EB93FD} 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. ------------------------------------------------------------------- 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The AVG AntiTrack Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- The server {8AB635F8-9A67-4698-AB99-784AD929F3B4} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8AB635F8-9A67-4698-AB99-784AD929F3B4} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 {8AB635F8-9A67-4698-AB99-784AD929F3B4} 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} 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: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The server ReaderNotificationClient_1.0.4.0_x86__e1rzdqpraam7r!App.AppX0kb1wv51yacfv58jnrprgtyj3c0t775x.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppXryc2qd338f5728r9gzzazav8206ba77s.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.Search_1.14.10.19041_neutral_neutral_cw5n1h2txyewy!CortanaUI.AppX49we79s9ab0xp8xpjb6t6g31ep03r71y.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.YourPhone_1.23052.123.0_x64__8wekyb3d8bbwe!App.AppX3vhsrrrr4az9vb3h5mjdzkhtshkg5v0x.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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 {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. ------------------------------------------------------------------- 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 AVG AntiTrack Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has encountered an internal error and has failed. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 Windows Push Notifications User Service_96a05 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The Lenovo Intelligent Sensing Service service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Windows Push Notifications User Service_21e05d9 service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {71DCE5D6-4B57-496B-AC21-CD5B54EB93FD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The AVG AntiTrack Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.19041.1023_neutral_neutral_cw5n1h2txyewy!App.AppX447jn8wbjb1qsw3jxkndb19cwgsrtrkk.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9P105T65H4Z5-Microsoft.WindowsAppRuntime.1.3. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the WpnUserService_3a130 service to connect. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff8068e7a800c, 0xfffffa0489b4fd48, 0xfffffa0489b4f580). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 30a3b5f5-d840-4d0f-89d6-0c463beb311e. ------------------------------------------------------------------- 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 12:20:19 PM on ‎6/‎2/‎2023 was unexpected. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff801c118800c, 0xfffff302c5717d48, 0xfffff302c5717580). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5c1afcf3-a3fa-4267-a465-62e3a656fe26. ------------------------------------------------------------------- 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 12:07:39 PM on ‎6/‎2/‎2023 was unexpected. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffff980aceb20050, 0xfffff8057fe16850, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 04776e7c-829f-4a65-8fed-9411e97b3944. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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:52:40 AM on ‎6/‎2/‎2023 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The Windows Media Player Network Sharing Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Auto Time Zone Updater service terminated with the following error: Auto Time Zone Updater is not a valid Win32 application. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (8c:de:e6:7d:06:78) failed. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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 9:01:12 AM on ‎5/‎2/‎2023 was unexpected. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The master browser has received a server announcement from the computer AKAYTOSHIBA that believes that it is the master browser for the domain on transport NetBT_Tcpip_{ACDD9126-AC0F-4EBE-A3C1-AF5DCC15CBF6}. The master browser is stopping or an election is being forced. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {9C695035-48D2-4229-8B73-4C70E756E519} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {B91D5831-B1BD-4608-8198-D72E155020F7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The activation of the CLSID {8A1A8BB1-242F-431A-9F5B-254BA754631C} timed out waiting for the service UsoSvc to stop. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} 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. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 name "WORKGROUP :1d" could not be registered on the interface with IP address 192.168.1.20. The computer with the IP address 192.168.1.34 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {354FF91B-5E49-4BDC-A8E6-1CB6C6877182} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {354FF91B-5E49-4BDC-A8E6-1CB6C6877182} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {354FF91B-5E49-4BDC-A8E6-1CB6C6877182} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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 4:39:30 PM on ‎3/‎13/‎2023 was unexpected. ------------------------------------------------------------------- The name "WORKGROUP :1d" could not be registered on the interface with IP address 192.168.1.20. The computer with the IP address 192.168.1.34 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- The name "WORKGROUP :1d" could not be registered on the interface with IP address 192.168.1.20. The computer with the IP address 192.168.1.34 did not allow the name to be claimed by this computer. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {628ACE20-B77A-456F-A88D-547DB6CEEDD5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {628ACE20-B77A-456F-A88D-547DB6CEEDD5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {00020827-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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. ------------------------------------------------------------------- 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 #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Intel Provider Data Helper Service service terminated with the following error: The operation attempted is not supported. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 AVG Antivirus service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {354FF91B-5E49-4BDC-A8E6-1CB6C6877182} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {354FF91B-5E49-4BDC-A8E6-1CB6C6877182} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {354FF91B-5E49-4BDC-A8E6-1CB6C6877182} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, 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 {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. ------------------------------------------------------------------- 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 {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {84F66100-FF7C-4FB4-B0C0-02CD7FB668FE} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {156b646e-eb06-4601-9593-f3d04dc209e7}, had event Fatal error: The miniport has failed a power transition to operational power ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 11/29/2023, 12:23:27 Machine name: HASANLENOVO Machine Id: {F6587BC5-B7D3-4B92-B6DB-92142AC95D68} Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406) Language: English (Regional Setting: English) System Manufacturer: LENOVO System Model: 82VB BIOS: KMCN19WW (type: UEFI) Processor: 12th Gen Intel(R) Core(TM) i7-12700H (20 CPUs), ~2.3GHz Memory: 32768MB RAM Available OS Memory: 32494MB RAM Page File: 6681MB used, 30676MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Supported DirectX Database Version: 1.4.7 DxDiag Version: 10.00.19041.3636 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Display Tab 2: No problems found. Sound Tab 1: No problems found. Sound Tab 2: 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_46A6&SUBSYS_380B17AA&REV_0C 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: 16374 MB Dedicated Memory: 128 MB Shared Memory: 16246 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: External Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.637695,0.333984), Green(0.308594,0.626953), Blue(0.153320,0.073242), 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: 2D FHD LG TV Monitor Id: GSM59C6 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: HDMI 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_41d82e9a7c892f34\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd12umd64.dll Driver File Version: 31.00.0101.4502 (English) Driver Version: 31.0.101.4502 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:True Declarative:True Driver Attributes: Final Retail Driver Date/Size: 6/15/2023 3:00:00 AM, 4722728 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-05E6-11CF-8C65-6E18A3C2D235} Vendor ID: 0x8086 Device ID: 0x46A6 SubSys ID: 0x380B17AA Revision ID: 0x000C Driver Strong Name: oem155.inf:5f63e5343e91ba36:iADLPD_w10_DS:31.0.101.4502:PCI\VEN_8086&DEV_46A6&SUBSYS_380B17AA Rank Of Driver: 00CF0001 Video Accel: 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} {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} {036DFF40-94A6-45B3-A0B3-71F0CDF35129} {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: {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 {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_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive D3D9 Overlay: Not 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_38c4a6addf46dd28\iigd_ext.inf Driver Version: 31.0.101.4502 Driver Date: 06/15/2023 Driver Provider: Intel Corporation Catalog Attributes: Universal:True Declarative:True Component Drivers: Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A Card name: Intel(R) Arc(TM) A370M Graphics Manufacturer: Intel Corporation Chip type: Intel(R) Arc(TM) A370M Graphics Family DAC type: Internal Device Type: Render-Only Device Device Key: Enum\PCI\VEN_8086&DEV_5693&SUBSYS_384217AA&REV_05 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: 20264 MB Dedicated Memory: 4018 MB Shared Memory: 16246 MB Current Mode: Unknown HDR Support: Unknown Display Topology: Unknown Display Color Space: Unknown Color Primaries: Unknown Display Luminance: Unknown Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12umd64.dll Driver File Version: 31.00.0101.4502 (English) Driver Version: 31.0.101.4502 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: Discrete Power P-states: Not Supported Virtualization: Paravirtualization Block List: DISABLE_HWSCH Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 6/15/2023 3:00:00 AM, 2393352 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: Unknown Vendor ID: 0x8086 Device ID: 0x5693 SubSys ID: 0x384217AA Revision ID: 0x0005 Driver Strong Name: oem144.inf:5f63e5347e8a9c72:iDG2DH_w10_DS:31.0.101.4502:PCI\VEN_8086&DEV_5693&SUBSYS_384217AA Rank Of Driver: 00CF0001 Video Accel: Unknown DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_IDCT DXVA2_ModeWMV9_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} {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} {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} {8FF8A3AA-C456-4132-B6EF-69D9DD72571D} {C23DD857-874B-423C-B6E0-82CEAA9B118A} {5B08E35D-0C66-4C51-A6F1-89D00CB2C197} {0E4BC693-5D2C-4936-B125-AEFE32B16D8A} {2F08B5B1-DBC2-4D48-883A-4E7B8174CFF6} {5467807A-295D-445D-BD2E-CBA8C2457C3D} {AE0D4E15-2360-40A8-BF82-028E6A0DD827} 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} {49761BEC-4B63-4349-A5FF-87FFDF088466} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {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} {B8B28E0C-ECAB-4217-8C82-EAAA9755AAF0} {8732ECFD-9747-4897-B42A-E534F9FF2B7A} {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} {8090A09C-6FC5-48EF-9F40-65BF37F7ACC4} {0EEA5B11-88C0-4A9F-81AC-B10FD66B22EA} {50925B7B-E931-4978-A12A-586630F095F9} {3325F221-DB34-47B6-8308-46095447114E} Deinterlace Caps: n/a D3D9 Overlay: Unknown DXVA-HD: Unknown DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 0 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported Extension Drivers: Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext_d.inf_amd64_1fbd43231a8fc169\iigd_ext_d.inf Driver Version: 31.0.101.4502 Driver Date: 06/15/2023 Driver Provider: Intel Corporation Catalog Attributes: Universal:True Declarative:True Component Drivers: Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A ------------- Sound Devices ------------- Description: 2D FHD LG TV (HD Audio Driver for Display Audio) Default Sound Playback: Yes Default Voice Playback: No Hardware ID: HDAUDIO\SUBFUNC_01&VEN_8086&DEV_281C&NID_0001&SUBSYS_00000000&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: AcxHdAudio.sys Driver Version: 31.0.101.4972 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 11/17/2023 3:00:00 AM, 526848 bytes Other Files: Driver Provider: Intel Corporation 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 Description: Speakers (Realtek High Definition Audio(SST)) Default Sound Playback: No Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0257&SUBSYS_17AA39FE&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.9579.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 9/19/2023 3:00:00 AM, 6352344 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 --------------------- --------------------- Video Capture Devices Number of Devices: 3 --------------------- FriendlyName: Integrated Camera Category: Camera SymbolicLink: \\?\usb#vid_13d3&pid_5419&mi_00#6&17d116b8&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 Manufacturer: Realtek HardwareID: USB\VID_13D3&PID_5419&REV_2003&MI_00,USB\VID_13D3&PID_5419&MI_00 DriverDesc: Integrated Camera DriverProvider: Realtek DriverVersion: 10.0.22000.20294 DriverDateEnglish: 8/25/2023 00:00:00 DriverDateLocalized: 8/25/2023 12:00:00 AM 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 Camera Parent: USB\VID_13D3&PID_5419\0000 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \FileSystem\avgSnx,\Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {f66fa674-f2be-4d19-98c5-d132329c642f} MFT0: n/a DMFT: n/a CustomCaptureSource: n/a DependentStillCapture: False EnablePlatformDMFT: True DMFTChain: {09824200-9A44-4B06-8C74-92D99E09B435},{D8AF2BBF-356C-4079-AEA7-2D80D7904E8E} EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 FriendlyName: Integrated IR Camera Category: Sensor SymbolicLink: \\?\usb#vid_13d3&pid_5419&mi_02#6&17d116b8&0&0002#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\global Location: Front Rotation: 0 Manufacturer: Realtek HardwareID: USB\VID_13D3&PID_5419&REV_2003&MI_02,USB\VID_13D3&PID_5419&MI_02 DriverDesc: Realtek DMFT - IR DriverProvider: Realtek DriverVersion: 10.0.22000.20294 DriverDateEnglish: 8/25/2023 00:00:00 DriverDateLocalized: 8/25/2023 12:00:00 AM 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 IR Camera Parent: USB\VID_13D3&PID_5419\0000 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {f66fa674-f2be-4d19-98c5-d132329c642f} MFT0: n/a DMFT: n/a CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: {09824200-9A44-4B06-8C74-92D99E09B435} EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 FriendlyName: AvStream Media Device Category: Sensor Group SymbolicLink: \\?\swd#sgdevapi#4d9fae23a0faf824cfeba42577c0bfb4f2a6bdfedbd0910966c3eadbb590a07c#{669c7214-0a88-4311-a7f3-4e79820e33bd}\4d9fae23a0faf824cfeba42577c0bfb4f2a6bdfedbd0910966c3eadbb590a07c DeviceSymbolicLinks: \\?\USB#VID_13D3&PID_5419&MI_00#6&17d116b8&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global,\\?\USB#VID_13D3&PID_5419&MI_02#6&17d116b8&0&0002#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\global ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 ------------------- 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: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04F3, 0x2F18 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x06CB, 0xCE44 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, 0xCE44 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04F3, 0x2F18 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: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04F3, 0x2F18 FF Driver: n/a Device Name: 2.4G Keyboard Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x062A, 0x4101 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: 2.4G Keyboard Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x062A, 0x4101 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: 2.4G Keyboard Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x062A, 0x4101 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: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E 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: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04F3, 0x2F18 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: Intel(R) HID Event Filter Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x8087, 0x0A1E 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 Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x51ED | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 11/7/2023 19:31:50, 648576 bytes | +-+ USB Composite Device | | Vendor/Product ID: 0x062A, 0x4101 | | Location: Port_#0007.Hub_#0002 | | Matching Device ID: USB\COMPOSITE | | Service: usbccgp | | Driver: usbccgp.sys, 11/7/2023 19:31:50, 190440 bytes | | | +-+ USB Input Device | | | Vendor/Product ID: 0x062A, 0x4101 | | | Location: 0000.0014.0000.007.000.000.000.000.000 | | | Matching Device ID: USB\Class_03&SubClass_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 11/7/2023 19:31:50, 44032 bytes | | | Driver: hidclass.sys, 11/7/2023 19:31:50, 233472 bytes | | | Driver: hidparse.sys, 11/7/2023 19:31:50, 46080 bytes | | | | | +-+ HID Keyboard Device | | | | Vendor/Product ID: 0x062A, 0x4101 | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | Service: kbdhid | | | | Driver: kbdhid.sys, 12/7/2019 12:07:56, 46592 bytes | | | | Driver: kbdclass.sys, 12/7/2019 12:07:56, 71480 bytes | | | | +-+ USB Input Device | | | Vendor/Product ID: 0x062A, 0x4101 | | | Location: 0000.0014.0000.007.000.000.000.000.000 | | | Matching Device ID: USB\Class_03&SubClass_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 11/7/2023 19:31:50, 44032 bytes | | | Driver: hidclass.sys, 11/7/2023 19:31:50, 233472 bytes | | | Driver: hidparse.sys, 11/7/2023 19:31:50, 46080 bytes | | | | | +-+ HID-compliant mouse | | | | Vendor/Product ID: 0x062A, 0x4101 | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | Service: mouhid | | | | Driver: mouhid.sys, 12/7/2019 12:07:56, 35328 bytes | | | | Driver: mouclass.sys, 12/7/2019 12:07:56, 67600 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + HID Keyboard Device | Vendor/Product ID: 0x8087, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 12/7/2019 12:07:56, 46592 bytes | Driver: kbdclass.sys, 12/7/2019 12:07: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 12:07:56, 46592 bytes | Driver: kbdclass.sys, 12/7/2019 12:07:56, 71480 bytes | + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 12/7/2019 12:07:56, 118272 bytes | Driver: kbdclass.sys, 12/7/2019 12:07:56, 71480 bytes | + HID-compliant mouse | Vendor/Product ID: 0x06CB, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 12/7/2019 12:07:56, 35328 bytes | Driver: mouclass.sys, 12/7/2019 12:07:56, 67600 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 524.4 GB Total Space: 974.5 GB File System: NTFS Model: SAMSUNG MZVLB1T0HBLR-000L2 Drive: E: Free Space: 240.0 GB Total Space: 1907.7 GB File System: NTFS Model: Seagate BUP Slim SL SCSI Disk Device Drive: F: Free Space: 2214.7 GB Total Space: 3815.3 GB File System: NTFS Model: Seagate BUP BL SCSI Disk Device -------------- System Devices -------------- Name: Intel(R) PCI Express Root Port #6 - 51BD Device ID: PCI\VEN_8086&DEV_51BD&SUBSYS_383217AA&REV_01\3&11583659&0&E0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 478688 bytes Name: Intel(R) PEG60 - 464D Device ID: PCI\VEN_8086&DEV_464D&SUBSYS_381117AA&REV_02\3&11583659&0&30 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 478688 bytes Name: Intel(R) LPC Controller - 5182 Device ID: PCI\VEN_8086&DEV_5182&SUBSYS_383717AA&REV_01\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 21480 bytes Name: Performance Monitor Device ID: PCI\VEN_8086&DEV_467D&SUBSYS_381B17AA&REV_01\3&11583659&0&50 Driver: n/a Name: Intel(R) GNA Scoring Accelerator module Device ID: PCI\VEN_8086&DEV_464F&SUBSYS_381517AA&REV_02\3&11583659&0&40 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\gna.inf_amd64_04d4eecc5838a558\gna.sys, 3.00.0000.1457 (English), 12/6/2022 19:24:28, 88784 bytes Name: Intel(R) Integrated Sensor Solution Device ID: PCI\VEN_8086&DEV_51FC&SUBSYS_72708086&REV_01\3&11583659&0&90 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ish.inf_amd64_206ab8df50dd8cd2\ISH.sys, 3.01.0000.4589 (English), 2/6/2023 08:25:16, 175232 bytes Name: Intel(R) Innovation Platform Framework Processor Participant Device ID: PCI\VEN_8086&DEV_461D&SUBSYS_381217AA&REV_02\3&11583659&0&20 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipf_lf.sys, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 484448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipf_cpu.sys, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 85600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipf_umdf2.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 1223264 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipf_uf.exe, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 3002464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\dsp.dv, 10/25/2023 05:32:02, 502818 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ppm.dv, 10/25/2023 05:32:02, 241532 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\upe_capi.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 64096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\upe_wwan.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 153184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\upe_wifi.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 77408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\upe_nvme.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 124000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\upe_battery.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 74848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\upe_nvapi.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 104648 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\upe_socwc.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 231520 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\upe_hwpf.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 78944 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipf_helper.exe, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 627808 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipf_cmp.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 143568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipfcore.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 706656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipfipc.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 595656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_b25cc008923a9297\ipfsrv.dll, 1.00.11401.39039 (English), 10/25/2023 05:32:02, 782432 bytes Name: Standard NVM Express Controller Device ID: PCI\VEN_144D&DEV_A808&SUBSYS_A801144D&REV_00\4&3F1686E&0&0032 Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:50, 165248 bytes Name: PCI Express Root Port Device ID: PCI\VEN_8086&DEV_466E&SUBSYS_382217AA&REV_02\3&11583659&0&38 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 478688 bytes Name: Intel(R) USB 3.10 eXtensible Host Controller - 1.20 (Microsoft) Device ID: PCI\VEN_8086&DEV_51ED&SUBSYS_382F17AA&REV_01\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.3636 (English), 11/7/2023 19:31:50, 625536 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.3636 (English), 11/7/2023 19:31:50, 143136 bytes Name: PCI Express Upstream Switch Port Device ID: PCI\VEN_8086&DEV_4FA1&SUBSYS_00000000&REV_01\4&258C995B&0&0030 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\pci.inf_amd64_4ad32a9219c0549a\pci.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 478688 bytes Name: Intel(R) Iris(R) Xe Graphics Device ID: PCI\VEN_8086&DEV_46A6&SUBSYS_380B17AA&REV_0C\3&11583659&0&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdkmdn64.sys, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 50603472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxsn64.vp, 11/22/2023 18:02:14, 5425 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10iumd64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 4722728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd11dxva64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 4238136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd12dxva64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 3222824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igddxvacommon64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 19219704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\media_bin_64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:18, 31367816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd12umd64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 1116720 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10um64xe.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 26709584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10umt64xe.dll, 11/22/2023 18:02:10, 20581736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10mg64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 2536608 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd12um64xel.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 16143504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdgmm64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 4561440 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igfxcmrt64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 246016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igfx11cmrt64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 248064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdumdim64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 2393200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd9trinity32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 19016272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd9trinity64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 20553352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdail64.dll, 11/22/2023 18:02:12, 297472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd9dxva64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 20885976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iga64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:08, 3003896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igc64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 67050296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\DnnlPlugin.dll, 11/22/2023 18:02:08, 19660360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\XeFX.dll, 0.02.0263.0000 (English), 11/22/2023 18:02:08, 162960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igxess.dll, 0.04.0263.0000 (English), 11/22/2023 18:02:16, 89688576 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\UniversalAdapter64.dll, 11/22/2023 18:02:08, 383104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igmlsblob64xel.dll, 0.01.0046.0000 (English), 11/22/2023 18:02:14, 3136792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igmlsblob64xeh.dll, 0.01.0046.0000 (English), 11/22/2023 18:02:14, 6046520 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\opencl-clang64.dll, 2.00.0009.0000 (English), 11/22/2023 18:02:20, 68147200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdfcl64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 1208224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdmd64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 16369600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdml64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 1456664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdde64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 452992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdinfo64.dll, 11/22/2023 18:02:12, 187160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdext64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 336776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10iumd32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 4621144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd11dxva32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 3572304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd12dxva32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 2683016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\media_bin_32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:18, 31173720 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igddxvacommon32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 18239512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd12umd32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 1053504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10um32xe.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 24945800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10umt32xe.dll, 11/22/2023 18:02:10, 18989448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd10mg32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 2454040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd12um32xel.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 15699160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdgmm32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 3488184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdumdim32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 2574264 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdail32.dll, 11/22/2023 18:02:12, 266240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igd9dxva32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 19702544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igfxcmrt32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 202288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igfx11cmrt32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 203312 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iga32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:08, 2423592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igc32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:10, 60021040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\UniversalAdapter32.dll, 11/22/2023 18:02:08, 325120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\opencl-clang32.dll, 2.00.0009.0000 (English), 11/22/2023 18:02:18, 49784984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdfcl32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 1125840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdmd32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 12049104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdml32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 1102464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdde32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 376144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdinfo32.dll, 11/22/2023 18:02:12, 162816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdext32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:12, 275336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libigd12dxva64.so, 11/22/2023 18:02:16, 24085536 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libigd12umd64.so, 11/22/2023 18:02:16, 43248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libigd12um64xel.so, 11/22/2023 18:02:16, 6617624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libigc.so, 11/22/2023 18:02:16, 42414752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libLLVM-9.so, 11/22/2023 18:02:16, 25507352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libigdgmm_w.so.12, 11/22/2023 18:02:16, 2325160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libUniversalAdapter64.so, 11/22/2023 18:02:16, 518232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libigdfcl.so, 11/22/2023 18:02:16, 1051392 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libopencl-clang.so.9, 11/22/2023 18:02:18, 81366600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libwsl_compute_helper.so, 11/22/2023 18:02:18, 555088 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxo64.vp, 11/22/2023 18:02:14, 42513 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxc64.vp, 11/22/2023 18:02:14, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxg64.vp, 11/22/2023 18:02:14, 43760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxo64_dev.vp, 11/22/2023 18:02:14, 43143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxc64_dev.vp, 11/22/2023 18:02:14, 43214 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxg64_dev.vp, 11/22/2023 18:02:14, 43732 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxa64.vp, 11/22/2023 18:02:14, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\iglhxa64.cpa, 11/22/2023 18:02:14, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\cp_resources.bin, 11/22/2023 18:02:08, 2572396 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igxelpicd64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 17925112 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igxelpicd32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 14815224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\OSSCOPYRIGHT.txt, 11/22/2023 18:02:08, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igvk64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 18680096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igvk64.json, 11/22/2023 18:02:14, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\VulkanRT-EULA.txt, 11/22/2023 18:02:08, 4008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igvk32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 17422376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igvk32.json, 11/22/2023 18:02:14, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igvkMedia64.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 1383104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igvkMedia32.dll, 31.00.0101.4502 (English), 11/22/2023 18:02:14, 1070368 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\vulkan-1-64.dll, 1.03.0239.0000 (English), 11/22/2023 18:02:20, 1506768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\vulkaninfo-64.exe, 1.03.0239.0000 (English), 11/22/2023 18:02:20, 2209232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\vulkan-1-32.dll, 1.03.0239.0000 (English), 11/22/2023 18:02:20, 1239504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\vulkaninfo-32.exe, 1.03.0239.0000 (English), 11/22/2023 18:02:20, 1643472 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.03.0261.0001 (English), 11/17/2023 23:14:52, 1285824 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.03.0261.0001 (English), 11/17/2023 23:14:58, 1653952 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0261.0001 (English), 11/17/2023 23:14:52, 1285824 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0261.0001 (English), 11/17/2023 23:14:58, 1653952 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.03.0261.0001 (English), 11/17/2023 23:14:56, 1443520 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.03.0261.0001 (English), 11/17/2023 23:14:58, 2095696 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.03.0261.0001 (English), 11/17/2023 23:14:56, 1443520 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0261.0001 (English), 11/17/2023 23:14:58, 2095696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 11/22/2023 18:02:08, 398248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdrcl32.dll, 23.20.0101.4502 (English), 11/22/2023 18:02:14, 6102480 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 11/22/2023 18:02:08, 535496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\ze_loader.dll, 1.11.0000.0000 (English), 11/22/2023 18:02:20, 462840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\ze_validation_layer.dll, 1.11.0000.0000 (English), 11/22/2023 18:02:20, 313256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\ze_tracing_layer.dll, 1.11.0000.0000 (English), 11/22/2023 18:02:20, 522704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\IntelControlLib.dll, 1.00.0148.0000 (English), 11/22/2023 18:02:08, 605472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\IntelControlLib32.dll, 1.00.0148.0000 (English), 11/22/2023 18:02:08, 521640 bytes Driver: C:\WINDOWS\SysWow64\IntelControlLib32.dll, 1.00.0148.0000 (English), 11/22/2023 18:02:08, 521640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\igdrcl64.dll, 23.20.0101.4502 (English), 11/22/2023 18:02:14, 7061968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\ze_intel_gpu64.dll, 1.03.26370.0000 (English), 11/22/2023 18:02:20, 8557520 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 2.02.0008.0000 (English), 11/22/2023 18:02:08, 398248 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 2.02.0008.0000 (English), 11/22/2023 18:02:08, 535496 bytes Driver: C:\WINDOWS\system32\ze_loader.dll, 1.14.0000.0000 (English), 11/17/2023 23:15:12, 466624 bytes Driver: C:\WINDOWS\system32\ze_validation_layer.dll, 1.14.0000.0000 (English), 11/17/2023 23:15:16, 307392 bytes Driver: C:\WINDOWS\system32\ze_tracing_layer.dll, 1.14.0000.0000 (English), 11/17/2023 23:15:14, 518848 bytes Driver: C:\WINDOWS\system32\ControlLib.dll, 1.00.0171.0000 (English), 11/17/2023 23:12:36, 295000 bytes Driver: C:\WINDOWS\SysWow64\ControlLib32.dll, 1.00.0171.0000 (English), 11/17/2023 23:12:38, 242312 bytes Driver: C:\WINDOWS\SysWow64\libmfxhw32.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 737776 bytes Driver: C:\WINDOWS\SysWow64\mfxplugin32_hw.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 20707792 bytes Driver: C:\WINDOWS\system32\libmfxhw64.dll, 23.06.0021.0536 (English), 11/17/2023 23:18:46, 943216 bytes Driver: C:\WINDOWS\system32\mfxplugin64_hw.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 27983784 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:16, 621712 bytes Driver: C:\WINDOWS\system32\libvpl.dll, 2.09.0000.0000 (English), 11/22/2023 18:02:20, 549728 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:16, 480624 bytes Driver: C:\WINDOWS\SysWow64\libvpl.dll, 2.09.0000.0000 (English), 11/22/2023 18:02:20, 488928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfxplugin64_hw.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 27983784 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfxplugin64_av1e_gacc.dll, 3.11.0005.0020 (English), 11/22/2023 18:02:18, 12681048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\intel_gfx_api-x64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:16, 621712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfxplugin32_hw.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 20707792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfxplugin32_av1e_gacc.dll, 3.11.0005.0020 (English), 11/22/2023 18:02:18, 8706776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\intel_gfx_api-x86.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:16, 480624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_h264ve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 2568632 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_mjpgvd_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 2429904 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_h265ve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 2581184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_vp9ve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 2576016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_encrypt_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 2430352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_av1hve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 2577088 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\c_32.cpa, 11/22/2023 18:02:08, 1361159 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\cpa_32.vp, 11/22/2023 18:02:08, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\dev_32.vp, 11/22/2023 18:02:08, 57143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\he_32.vp, 11/22/2023 18:02:08, 75569 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mj_32.vp, 11/22/2023 18:02:18, 71117 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\h265e_32.vp, 11/22/2023 18:02:08, 77121 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\vp9e_32.vp, 11/22/2023 18:02:20, 76708 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_av1hve_32.vp, 11/22/2023 18:02:18, 76773 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_h264ve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 3121512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_mjpgvd_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 2951584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_h265ve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 3141000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_vp9ve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 3135152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_encrypt_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 2952936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_av1hve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 3136792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\c_64.cpa, 11/22/2023 18:02:08, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\cpa_64.vp, 11/22/2023 18:02:08, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\dev_64.vp, 11/22/2023 18:02:08, 56359 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\he_64.vp, 11/22/2023 18:02:08, 13235 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mj_64.vp, 11/22/2023 18:02:18, 12959 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\h265e_64.vp, 11/22/2023 18:02:08, 13803 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\vp9e_64.vp, 11/22/2023 18:02:20, 13654 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\mfx_mft_av1hve_64.vp, 11/22/2023 18:02:18, 13623 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libmfx64-gen.dll, 23.06.0002.0002 (English), 11/22/2023 18:02:16, 23621616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\libmfx32-gen.dll, 23.06.0002.0002 (English), 11/22/2023 18:02:16, 21972920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\enctools32.dll, 11/22/2023 18:02:08, 7861664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\enctools64.dll, 11/22/2023 18:02:08, 8998864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\IntelCpHDCPSvc.exe, 31.00.0101.4502 (English), 11/22/2023 18:02:08, 363512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\clangFEWrapper.dll, 11/22/2023 18:02:08, 33734152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_41d82e9a7c892f34\clangFEWrapper32.dll, 11/22/2023 18:02:08, 26877680 bytes Name: Intel(R) SPI (flash) Controller - 51A4 Device ID: PCI\VEN_8086&DEV_51A4&SUBSYS_383C17AA&REV_01\3&11583659&0&FD Driver: n/a Name: Intel(R) Wi-Fi 6E AX211 160MHz Device ID: PCI\VEN_8086&DEV_51F0&SUBSYS_00948086&REV_01\3&11583659&0&A3 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_cc3a2460c42c06f6\Netwtw12.sys, 22.250.0001.0002 (English), 8/14/2023 12:13:24, 5334952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_cc3a2460c42c06f6\netwfw12.dat, 8/14/2023 11:00:12, 33125432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_cc3a2460c42c06f6\IntelIHVRouter12.dll, 22.12240.0001.0001 (English), 8/14/2023 12:13:14, 1475496 bytes Name: Intel� Smart Sound Technology BUS Device ID: PCI\VEN_8086&DEV_51C8&SUBSYS_389317AA&REV_01\3&11583659&0&FB Driver: C:\WINDOWS\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_799c962c58e6bfeb\IntcAudioBus.sys, 10.29.0000.9677 (English), 8/31/2023 02:28:30, 331768 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 97792 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 388608 bytes Name: BayHubTech Integrated MMC/SD controller Device ID: PCI\VEN_1217&DEV_8621&SUBSYS_388317AA&REV_01\4&B1E1E99&0&00E0 Driver: C:\WINDOWS\system32\DRIVERS\bhtsddr.sys, 2.01.0101.10570 (English), 3/9/2022 17:00:30, 174272 bytes Driver: C:\WINDOWS\system32\bhtv5Icon.dll, 1.00.0000.0006 (English), 3/9/2022 17:00:32, 1889232 bytes Driver: C:\WINDOWS\sysWoW64\bhtv5Icon.dll, 1.00.0000.0006 (English), 3/9/2022 17:00:32, 1889232 bytes Name: Intel(R) SMBus - 51A3 Device ID: PCI\VEN_8086&DEV_51A3&SUBSYS_384117AA&REV_01\3&11583659&0&FC Driver: n/a Name: Intel(R) Host Bridge/DRAM Registers - 4641 Device ID: PCI\VEN_8086&DEV_4641&SUBSYS_380E17AA&REV_02\3&11583659&0&00 Driver: n/a Name: Intel(R) Shared SRAM - 51EF Device ID: PCI\VEN_8086&DEV_51EF&SUBSYS_383417AA&REV_01\3&11583659&0&A2 Driver: n/a Name: Thunderbolt(TM) Controller - 463E Device ID: PCI\VEN_8086&DEV_463E&SUBSYS_72708086&REV_02\3&11583659&0&6A Driver: C:\WINDOWS\system32\DRIVERS\TbtBusDrv.sys, 1.41.1379.0000 (English), 8/16/2023 15:47:22, 3237720 bytes Driver: C:\WINDOWS\TbtP2pShortcutService.exe, 1.41.1379.0000 (English), 8/16/2023 15:47:22, 256856 bytes Name: Intel(R) Arc(TM) A370M Graphics Device ID: PCI\VEN_8086&DEV_5693&SUBSYS_384217AA&REV_05\6&24D5ABFE&0&00080030 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdkmdnd64.sys, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 50603592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxsnd64.vp, 11/22/2023 18:09:22, 5426 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10iumd64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 4722728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd11dxva64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 4238136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12dxva64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 3222816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igddxvacommon64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 19219848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\media_bin_64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:26, 31367808 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12umd64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 1116760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10um64xe.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 26709688 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10umt64xe.dll, 11/22/2023 18:09:18, 20581736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10mg64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 2536648 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12um64xel.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 16143544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12um64xeh.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 16988440 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdgmm64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 4561480 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igfxcmrt64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 246056 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igfx11cmrt64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 248208 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdumdim64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 2393352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd9trinity32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 19016416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd9trinity64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 20553392 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdail64.dll, 11/22/2023 18:09:20, 297584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd9dxva64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 20886016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iga64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:16, 3003888 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igc64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 67050448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\DnnlPlugin.dll, 11/22/2023 18:09:16, 19660464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\XeFX.dll, 0.02.0263.0000 (English), 11/22/2023 18:09:16, 163112 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igxess.dll, 0.04.0263.0000 (English), 11/22/2023 18:09:24, 89688616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\UniversalAdapter64.dll, 11/22/2023 18:09:16, 383256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igmlsblob64xel.dll, 0.01.0046.0000 (English), 11/22/2023 18:09:22, 3136944 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igmlsblob64xeh.dll, 0.01.0046.0000 (English), 11/22/2023 18:09:22, 6046672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\opencl-clang64.dll, 2.00.0009.0000 (English), 11/22/2023 18:09:28, 68147352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdfcl64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 1208264 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdmd64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 16369752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdml64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 1456712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdde64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 453032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdinfo64.dll, 11/22/2023 18:09:20, 187304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdext64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 336816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10iumd32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 4621248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd11dxva32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 3572304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12dxva32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 2683056 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\media_bin_32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:26, 31173760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igddxvacommon32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 18239656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12umd32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 1053544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10um32xe.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 24945952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10umt32xe.dll, 11/22/2023 18:09:18, 18989440 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd10mg32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 2454040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12um32xel.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 15699200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd12um32xeh.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 16565848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdgmm32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 3488224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdumdim32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 2574304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdail32.dll, 11/22/2023 18:09:20, 266360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igd9dxva32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 19702696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igfxcmrt32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 202440 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igfx11cmrt32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 203464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iga32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:16, 2423696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igc32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:18, 60021032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\UniversalAdapter32.dll, 11/22/2023 18:09:16, 325272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\opencl-clang32.dll, 2.00.0009.0000 (English), 11/22/2023 18:09:26, 49785024 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdfcl32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 1126008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdmd32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 12049144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdml32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 1102608 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdde32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 376184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdinfo32.dll, 11/22/2023 18:09:20, 162960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdext32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:20, 275376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libigd12dxva64.so, 11/22/2023 18:09:24, 24085536 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libigd12umd64.so, 11/22/2023 18:09:24, 43248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libigd12um64xel.so, 11/22/2023 18:09:24, 6617624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libigd12um64xeh.so, 11/22/2023 18:09:24, 7305272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libigc.so, 11/22/2023 18:09:24, 42414752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libLLVM-9.so, 11/22/2023 18:09:24, 25507352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libigdgmm_w.so.12, 11/22/2023 18:09:24, 2325160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libUniversalAdapter64.so, 11/22/2023 18:09:24, 518232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libigdfcl.so, 11/22/2023 18:09:24, 1051392 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libopencl-clang.so.9, 11/22/2023 18:09:26, 81366600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libwsl_compute_helper.so, 11/22/2023 18:09:26, 555088 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\UMED.dll, 11/22/2023 18:09:16, 174184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxo64.vp, 11/22/2023 18:09:22, 42513 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxc64.vp, 11/22/2023 18:09:22, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxg64.vp, 11/22/2023 18:09:22, 43760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxo64_dev.vp, 11/22/2023 18:09:22, 43143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxc64_dev.vp, 11/22/2023 18:09:22, 43214 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxg64_dev.vp, 11/22/2023 18:09:22, 43732 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxa64.vp, 11/22/2023 18:09:22, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\iglhxa64.cpa, 11/22/2023 18:09:22, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\cp_resources.bin, 11/22/2023 18:09:16, 2572396 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igxehpgicd64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 18570800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igxehpgicd32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 15121968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\OSSCOPYRIGHT.txt, 11/22/2023 18:09:16, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igvk64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 18680136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igvk64.json, 11/22/2023 18:09:22, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\VulkanRT-EULA.txt, 11/22/2023 18:09:16, 4008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igvk32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 17422416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igvk32.json, 11/22/2023 18:09:22, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igvkMedia64.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 1383144 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igvkMedia32.dll, 31.00.0101.4502 (English), 11/22/2023 18:09:22, 1070408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\vulkan-1-64.dll, 1.03.0239.0000 (English), 11/22/2023 18:09:28, 1506824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\vulkaninfo-64.exe, 1.03.0239.0000 (English), 11/22/2023 18:09:28, 2209288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\vulkan-1-32.dll, 1.03.0239.0000 (English), 11/22/2023 18:09:28, 1239664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\vulkaninfo-32.exe, 1.03.0239.0000 (English), 11/22/2023 18:09:28, 1643528 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.03.0261.0001 (English), 11/17/2023 23:14:52, 1285824 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.03.0261.0001 (English), 11/17/2023 23:14:58, 1653952 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0261.0001 (English), 11/17/2023 23:14:52, 1285824 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0261.0001 (English), 11/17/2023 23:14:58, 1653952 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.03.0261.0001 (English), 11/17/2023 23:14:56, 1443520 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.03.0261.0001 (English), 11/17/2023 23:14:58, 2095696 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.03.0261.0001 (English), 11/17/2023 23:14:56, 1443520 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0261.0001 (English), 11/17/2023 23:14:58, 2095696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 11/22/2023 18:09:16, 398408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdrcl32.dll, 23.20.0101.4502 (English), 11/22/2023 18:09:22, 6102640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 11/22/2023 18:09:16, 535552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\ze_loader.dll, 1.11.0000.0000 (English), 11/22/2023 18:09:28, 462896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\ze_validation_layer.dll, 1.11.0000.0000 (English), 11/22/2023 18:09:28, 313304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\ze_tracing_layer.dll, 1.11.0000.0000 (English), 11/22/2023 18:09:28, 522760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\IntelControlLib.dll, 1.00.0148.0000 (English), 11/22/2023 18:09:16, 605512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\IntelControlLib32.dll, 1.00.0148.0000 (English), 11/22/2023 18:09:16, 521688 bytes Driver: C:\WINDOWS\SysWow64\IntelControlLib32.dll, 1.00.0148.0000 (English), 11/22/2023 18:02:08, 521640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igdrcl64.dll, 23.20.0101.4502 (English), 11/22/2023 18:09:22, 7062128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\ze_intel_gpu64.dll, 1.03.26370.0000 (English), 11/22/2023 18:09:28, 8557576 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 2.02.0008.0000 (English), 11/22/2023 18:02:08, 398248 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 2.02.0008.0000 (English), 11/22/2023 18:02:08, 535496 bytes Driver: C:\WINDOWS\system32\ze_loader.dll, 1.14.0000.0000 (English), 11/17/2023 23:15:12, 466624 bytes Driver: C:\WINDOWS\system32\ze_validation_layer.dll, 1.14.0000.0000 (English), 11/17/2023 23:15:16, 307392 bytes Driver: C:\WINDOWS\system32\ze_tracing_layer.dll, 1.14.0000.0000 (English), 11/17/2023 23:15:14, 518848 bytes Driver: C:\WINDOWS\system32\ControlLib.dll, 1.00.0171.0000 (English), 11/17/2023 23:12:36, 295000 bytes Driver: C:\WINDOWS\SysWow64\ControlLib32.dll, 1.00.0171.0000 (English), 11/17/2023 23:12:38, 242312 bytes Driver: C:\WINDOWS\SysWow64\libmfxhw32.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 737776 bytes Driver: C:\WINDOWS\SysWow64\mfxplugin32_hw.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 20707792 bytes Driver: C:\WINDOWS\system32\libmfxhw64.dll, 23.06.0021.0536 (English), 11/17/2023 23:18:46, 943216 bytes Driver: C:\WINDOWS\system32\mfxplugin64_hw.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:18, 27983784 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:16, 621712 bytes Driver: C:\WINDOWS\system32\libvpl.dll, 2.09.0000.0000 (English), 11/22/2023 18:02:20, 549728 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 23.05.0008.0534 (English), 11/22/2023 18:02:16, 480624 bytes Driver: C:\WINDOWS\SysWow64\libvpl.dll, 2.09.0000.0000 (English), 11/22/2023 18:02:20, 488928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfxplugin64_hw.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 27983832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfxplugin64_av1e_gacc.dll, 3.11.0005.0020 (English), 11/22/2023 18:09:26, 12681096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\intel_gfx_api-x64.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:24, 621752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfxplugin32_hw.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 20707952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfxplugin32_av1e_gacc.dll, 3.11.0005.0020 (English), 11/22/2023 18:09:26, 8706776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\intel_gfx_api-x86.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:24, 480664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_h264ve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2568672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_mjpgvd_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2429960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_h265ve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2581224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_vp9ve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2576056 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_encrypt_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2430344 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_av1hve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2577088 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\c_32.cpa, 11/22/2023 18:09:16, 1361159 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\cpa_32.vp, 11/22/2023 18:09:16, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\dev_32.vp, 11/22/2023 18:09:16, 57143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\he_32.vp, 11/22/2023 18:09:16, 75569 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mj_32.vp, 11/22/2023 18:09:26, 71117 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\h265e_32.vp, 11/22/2023 18:09:16, 77121 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\vp9e_32.vp, 11/22/2023 18:09:28, 76708 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_av1hve_32.vp, 11/22/2023 18:09:26, 76773 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_h264ve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 3121552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_mjpgvd_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2951640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_h265ve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 3141040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_vp9ve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 3135296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_encrypt_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2952928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_av1hve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 3136832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\c_64.cpa, 11/22/2023 18:09:16, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\cpa_64.vp, 11/22/2023 18:09:16, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\dev_64.vp, 11/22/2023 18:09:16, 56359 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\he_64.vp, 11/22/2023 18:09:16, 13235 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mj_64.vp, 11/22/2023 18:09:26, 12959 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\h265e_64.vp, 11/22/2023 18:09:16, 13803 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\vp9e_64.vp, 11/22/2023 18:09:28, 13654 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_av1hve_64.vp, 11/22/2023 18:09:26, 13623 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_av1ve_32.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 2578664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_av1ve_32.vp, 11/22/2023 18:09:26, 76784 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_av1ve_64.dll, 23.05.0008.0534 (English), 11/22/2023 18:09:26, 3136880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\mfx_mft_av1ve_64.vp, 11/22/2023 18:09:26, 13622 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libmfx64-gen.dll, 23.06.0002.0002 (English), 11/22/2023 18:09:24, 23621656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\libmfx32-gen.dll, 23.06.0002.0002 (English), 11/22/2023 18:09:24, 21972960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\enctools32.dll, 11/22/2023 18:09:16, 7861768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\enctools64.dll, 11/22/2023 18:09:16, 8998968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\clangFEWrapper.dll, 11/22/2023 18:09:16, 33734256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\clangFEWrapper32.dll, 11/22/2023 18:09:16, 26877784 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\fw\dg2_gfx_fwupdate_SOC2.bin, 11/22/2023 18:09:16, 2101248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\fw\dg2_gfx_fwupdate_A0_SOC2.bin, 11/22/2023 18:09:16, 2101248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\fw\dg2_gfx_fwupdate_B0_SOC1.bin, 11/22/2023 18:09:16, 2101248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\fw\dg2_gfx_fwupdate_SOC1.bin, 11/22/2023 18:09:16, 2101248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\fw\dg2_gfx_fwupdate_SOC3.bin, 11/22/2023 18:09:16, 2101248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\IntelGFXFWupdateTool.exe, 4.02.0004.0000 (English), 11/22/2023 18:09:16, 247816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\igsc.dll, 0.08.0004.0000 (English), 11/22/2023 18:09:22, 253288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch_d.inf_amd64_2ba2ee264e0d46f3\oprom\dg1_c_oprom.rom, 11/22/2023 18:09:28, 1048576 bytes Name: PCI Express Downstream Switch Port Device ID: PCI\VEN_8086&DEV_4FA4&SUBSYS_4FA48086&REV_00\5&2096DA6A&1&080030 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\pci.inf_amd64_4ad32a9219c0549a\pci.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 478688 bytes Name: Intel(R) PEG62 - 463D Device ID: PCI\VEN_8086&DEV_463D&SUBSYS_383917AA&REV_02\3&11583659&0&32 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.19041.3636 (English), 11/7/2023 19:31:49, 478688 bytes Name: Intel(R) Serial IO I2C Host Controller - 51E8 Device ID: PCI\VEN_8086&DEV_51E8&SUBSYS_382517AA&REV_01\3&11583659&0&A8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_e736c048ca307ed2\iaLPSS2_I2C_ADL.sys, 30.100.2237.0026 (English), 10/24/2022 06:50:52, 220224 bytes Name: Intel(R) Serial IO I2C Host Controller - 51E9 Device ID: PCI\VEN_8086&DEV_51E9&SUBSYS_381817AA&REV_01\3&11583659&0&A9 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_e736c048ca307ed2\iaLPSS2_I2C_ADL.sys, 30.100.2237.0026 (English), 10/24/2022 06:50:52, 220224 bytes Name: Intel(R) USB 3.20 eXtensible Host Controller - 1.20 (Microsoft) Device ID: PCI\VEN_8086&DEV_461E&SUBSYS_382617AA&REV_02\3&11583659&0&68 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.3636 (English), 11/7/2023 19:31:50, 625536 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.3636 (English), 11/7/2023 19:31:50, 143136 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_51E0&SUBSYS_382E17AA&REV_01\3&11583659&0&B0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_96cd661731a25dc4\x64\TeeDriverW10x64.sys, 2334.05.0001.0000 (English), 8/26/2023 17:06:32, 320712 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.19041.3636 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.19041.3636 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.3636 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.19041.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.19041.3636 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.19041.3636 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.19041.3636 DV Muxer,0x00400000,0,0,qdv.dll,10.00.19041.0001 MainConcept MPEG Demultiplexer,0x00800100,1,2,mc_demux_mp2_ds.ax,8.05.0000.5184 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.19041.3636 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.19041.0001 MainConcept AAC Decoder,0x00800000,1,1,mc_dec_aac_ds.ax,8.05.0000.5184 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.19041.3636 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.19041.3636 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.19041.3693 Track1Filter,0x00200000,0,0,Track1Filter.dll,14.00.0000.0000 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.19041.3636 MainConcept MP4 Demultiplexer,0x00800101,1,2,mc_demux_mp4_ds.ax,8.05.0000.5184 MainConcept (Adobe2Demo) MPEG Audio Decoder,0x00000000,0,0,, StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.19041.0001 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.3636 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.19041.3636 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 Track2Filter,0x00200000,0,0,Track2Filter.dll,14.00.0000.0000 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.3636 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.19041.3636 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.3636 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.19041.3636 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.19041.3636 DV Splitter,0x00600000,1,2,qdv.dll,10.00.19041.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.19041.3636 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.19041.3636 MainConcept MPEG Push Demultiplexer,0x00200000,1,2,mc_demuxpush_mp2_ds.ax,8.05.0000.5184 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.19041.3636 Video Renderer,0x00800001,1,0,quartz.dll,10.00.19041.3636 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.3636 Video Renderer,0x00400000,1,0,quartz.dll,10.00.19041.3636 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 MainConcept Dolby Digital Audio Decoder,0x00600000,1,1,mc_dec_dd_ds.ax,7.04.0000.47388 MainConcept AVC/H.264 Video Decoder,0x00800001,1,2,mc_dec_avc_ds.ax,8.05.0000.5184 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.19041.3636 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.19041.3636 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.3636 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.19041.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.19041.3636 MainConcept (Broadcast) AVC/H.264 Video Decoder,0x00800002,1,2,mc_bc_dec_avc_ds.ax,8.05.0000.5184 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.19041.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.19041.3636 Null Renderer,0x00200000,1,0,qedit.dll,10.00.19041.3636 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.3636 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.19041.3636 Dump,0x00000000,0,0,, Wave Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 File stream renderer,0x00400000,1,1,quartz.dll,10.00.19041.3636 MainConcept Stream Parser,0x00400000,1,2,mc_demux_mp2_ds.ax,8.05.0000.5184 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.19041.3636 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.3636 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.19041.3636 File Source (URL),0x00400000,0,1,quartz.dll,10.00.19041.3636 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.19041.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.19041.3636 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.3636 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.19041.3636 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.3636 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.19041.3636 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.19041.3636 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 PCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.19041.3636 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.19041.3636 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.19041.3636 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.19041.3636 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.19041.3693 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.3693 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.3693 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.19041.3636 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.19041.3636 WDM Streaming Capture Devices: ,0x00000000,0,0,, Integrated Camera,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 ,0x00200000,1,1,, Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Realtek HD Audio Mic input with SST,0x00200000,1,2,ksproxy.ax,10.00.19041.3636 WDM Streaming Rendering Devices: Realtek HD Audio output,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Realtek HD Audio 2nd output,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 ACX HD Audio Speaker,0x00000000,0,0,, 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 Camera,0x00200000,1,1,ksproxy.ax,10.00.19041.3636 Intel Virtual Camera,0x00200000,0,1,VirtualCamDevice.dll,1.00.0000.0001 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.3636 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.3636 Audio Renderers: 2D FHD LG TV (HD Audio Driver for Display Audio),0x00200000,1,0,quartz.dll,10.00.19041.3636 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.19041.3636 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.19041.3636 DirectSound: 2D FHD LG TV (HD Audio Driver for Display Audio),0x00200000,1,0,quartz.dll,10.00.19041.3636 DirectSound: Speakers (Realtek High Definition Audio(SST)),0x00200000,1,0,quartz.dll,10.00.19041.3636 Speakers (Realtek High Definition Audio(SST)),0x00200000,1,0,quartz.dll,10.00.19041.3636 ---------------------------- 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.3693 mfreadwrite.dll, 10.00.19041.3636 mfcaptureengine.dll, 10.00.19041.3636 mfsensorgroup.dll, 10.00.19041.3636 windows.media.dll, 10.00.19041.3636 frameserver.dll, 10.00.19041.3636 frameserverclient.dll, 10.00.19041.3636 --------------------------- 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, 23.05.0008.0534 Intel® Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 23.05.0008.0534 Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 23.05.0008.0534 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.19041.3693 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.3636 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.19041.3693 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.19041.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.19041.3636 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.19041.3636 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.19041.3636 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.19041.3636 HEIFImageExtension VP9VideoExtensionDecoder WebpImageExtension Video Encoders: Intel® Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 23.05.0008.0534 Intel® Hardware Accelerated AV1 Encoder MFT, {62C053CE-5357-4794-8C5A-FBEFFEFFB82D}, 0x4, 7, mfx_mft_av1hve_64.dll, 23.05.0008.0534 Intel® Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 23.05.0008.0534 Intel® Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 23.05.0008.0534 Intel� Hardware AV1 Encoder MFT, {F4ECF9A2-36A6-42C4-B284-A05181FD7490}, 0x4, 7, mfx_mft_av1ve_64.dll, 23.05.0008.0534 Intel® Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 23.05.0008.0534 Intel® Hardware Accelerated AV1 Encoder MFT, {62C053CE-5357-4794-8C5A-FBEFFEFFB82D}, 0x4, 7, mfx_mft_av1hve_64.dll, 23.05.0008.0534 Intel® Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 23.05.0008.0534 Intel® Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 23.05.0008.0534 Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 23.05.0008.0534 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 23.05.0008.0534 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 23.05.0008.0534 Intel� Hardware AV1 Encoder MFT, {F4ECF9A2-36A6-42C4-B284-A05181FD7490}, 0x4, 7, mfx_mft_av1ve_64.dll, 23.05.0008.0534 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.19041.3636 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.19041.3636 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.3636 HEIFImageExtension VP9VideoExtensionEncoder Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.19041.3636 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.19041.3636 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.19041.3636 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.19041.3636 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.19041.3636 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.19041.3636 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.19041.3636 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.3636 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.19041.3693 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.19041.3693 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.19041.3693 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.19041.3636 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.19041.3636 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.19041.3636 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.19041.3693 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.3693 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.19041.3693 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.3636 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.19041.3693 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.19041.3693 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.19041.3636 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.19041.3636 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.3636 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.19041.3636 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.3636 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.3636 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.19041.3693 -------------------------------------------- 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 1283657298410371006, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: IntelProviderDataHelperService.exe P2: 3.1023.830.1 P3: 64efa546 P4: IntelProviderDataHelperService.exe P5: 3.1023.830.1 P6: 64efa546 P7: 000000000005bef9 P8: c0000409 P9: 0000000000000007 P10: +++ WER1 +++: Fault bucket 1167345349525151049, type 5 Event Name: WUDFUnhandledException Response: Not available Cab Id: 0 Problem signature: P1: UnhandledException P2: Host P3: c0000005 P4: 29b81 P5: dptf.dll P6: 9.0.10705.25772 P7: (none) P8: (none) P9: 2.31.0 P10: (DumpedSeparately) +++ WER2 +++: Fault bucket , type 0 Event Name: WUDFUnhandledException Response: Not available Cab Id: 0 Problem signature: P1: UnhandledException P2: Host P3: c0000005 P4: 29b81 P5: dptf.dll P6: 9.0.10705.25772 P7: (none) P8: (none) P9: 2.31.0 P10: (DumpedSeparately) +++ WER3 +++: Fault bucket , type 0 Event Name: WUDFUnhandledException Response: Not available Cab Id: 0 Problem signature: P1: UnhandledException P2: Host P3: c0000005 P4: 29b81 P5: dptf.dll P6: 9.0.10705.25772 P7: (none) P8: (none) P9: 2.31.0 P10: (DumpedSeparately) +++ WER4 +++: Fault bucket 1283657298410371006, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: IntelProviderDataHelperService.exe P2: 3.1023.830.1 P3: 64efa546 P4: IntelProviderDataHelperService.exe P5: 3.1023.830.1 P6: 64efa546 P7: 000000000005bef9 P8: c0000409 P9: 0000000000000007 P10: +++ WER5 +++: Fault bucket 1167345349525151049, type 5 Event Name: WUDFUnhandledException Response: Not available Cab Id: 0 Problem signature: P1: UnhandledException P2: Host P3: c0000005 P4: 29b81 P5: dptf.dll P6: 9.0.10705.25772 P7: (none) P8: (none) P9: 2.31.0 P10: (DumpedSeparately) +++ WER6 +++: Fault bucket , type 0 Event Name: WUDFUnhandledException Response: Not available Cab Id: 0 Problem signature: P1: UnhandledException P2: Host P3: c0000005 P4: 29b81 P5: dptf.dll P6: 9.0.10705.25772 P7: (none) P8: (none) P9: 2.31.0 P10: (DumpedSeparately) +++ WER7 +++: Fault bucket , type 0 Event Name: WUDFUnhandledException Response: Not available Cab Id: 0 Problem signature: P1: UnhandledException P2: Host P3: c0000005 P4: 29b81 P5: dptf.dll P6: 9.0.10705.25772 P7: (none) P8: (none) P9: 2.31.0 P10: (DumpedSeparately) +++ WER8 +++: Fault bucket 1167345349525151049, type 5 Event Name: WUDFUnhandledException Response: Not available Cab Id: 0 Problem signature: P1: UnhandledException P2: Host P3: c0000005 P4: 29b81 P5: dptf.dll P6: 9.0.10705.25772 P7: (none) P8: (none) P9: 2.31.0 P10: (DumpedSeparately) +++ WER9 +++: Fault bucket , type 0 Event Name: WUDFUnhandledException Response: Not available Cab Id: 0 Problem signature: P1: UnhandledException P2: Host P3: c0000005 P4: 29b81 P5: dptf.dll P6: 9.0.10705.25772 P7: (none) P8: (none) P9: 2.31.0 P10: (DumpedSeparately) ...#SSU#...