# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"01/07/2022" Time:"00:01:08.9625878" # Scanned Hardware Computer: BaseBoard Manufacturer:"ASUSTeK COMPUTER INC." BIOS Mode:"UEFI" BIOS Version/Date:"American Megatrends International, LLC. X513EA.308 , 07/27/2021" CD or DVD:"Not Available" Embedded Controller Version:"255.255" Platform Role:"Mobile" Processor:"11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"3.3" Sound Card:"Realtek High Definition Audio" System Manufacturer:"ASUSTeK COMPUTER INC." System Model:"VivoBook_ASUSLaptop X513EA_S513EA" System SKU:"Not Available" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"Not Available" - "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:"oem0.inf,iTGLD_w10_DS,Internal,Intel(R) Iris(R) Xe Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmdn64.sys" Driver Date:"09/30/2021 01:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdkmdn64.sys" Driver Provider:"Intel Corporation" Driver Version:"30.0.100.9929" INF:"oem0.inf" INF Section:"iTGLD_w10_DS" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12umd64.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 0, device 2, function 0" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_9A49&SUBSYS_14321043&REV_01\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:"59 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):"7.86 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.69 GB" - "BANK 0" Capacity:"8 GB" Channel:"Controller0-ChannelA" Configured Clock Speed:"3200 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"First position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"M471A1G44AB0-CWE" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 0" Capacity:"8 GB" Channel:"Controller1-ChannelA-DIMM0" Configured Clock Speed:"3200 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Second position" Manufacturer:"SK Hynix" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"HMA81GS6DJR8N-XN" Serial Number:"236B3815" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"X513EA.308, _ASUS_ - 1072009" Caption:"Motherboard" Chipset:"Not Available" Date:"07/27/2021 01:00 AM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"ASUSTeK COMPUTER INC." Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"X513EA" Serial Number:"M727NBCV008TWXMB" Status:"OK" Version:"1.0" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Intel(R) Wi-Fi 6 AX201 160MHz" Access Point:"44:ad:b1:c8:71:69" Authentication:"WPA2-Personal" Availability:"Running or Full Power" - "Caption":"Intel(R) Wi-Fi 6 AX201 160MHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Wi+Fi+6+AX201+160MHz" Channel:"48" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Auto Connect" Default IP Gateway:"192.168.1.1;fe80::46ad:b1ff:fec8:716b" DHCP Enabled:"Yes" DHCP Lease Expires:"01/08/2022 07:33 PM" DHCP Lease Obtained:"01/07/2022 07:33 PM" DHCP Server:"192.168.1.1" Driver:"Netwtw10.sys" Driver Date:"09/27/2021 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\Netwtw10.sys" Driver Provider:"Intel" Driver Version:"22.90.0.5" Index:"0001" INF:"oem86.inf" INF Section:"Install_GEN_QSR_HrP_201_AX_2x2_WinT" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.1.182;fe80::28f8:d739:2336:ce4c;fdaa:bbcc:ddee:0:31ec:df8d:f967:bd0d;fdaa:bbcc:ddee:0:28f8:d739:2336:ce4c" IP Subnet:"255.255.255.0;64;128;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/07/2022 11:50 AM" Location:"PCI bus 0, device 20, function 3" MAC Address:"EC:63:D7:32:1F:AE" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"WiFi" NetCfgInstanceId:"{ED1A994E-4647-4E00-84A3-56FD1FE9C58C}" Network Name:"TALKTALKC8716B" Network Type:"Infrastructure" Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_A0F0&SUBSYS_00748086&REV_20\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 6 AX201 160MHz" Profile:"TALKTALKC8716B" Radio Type:"802.11ac" Receive Rate:"866.7 Mbps" Service Name:"Netwtw10" Signal Strength:"86%" State:"connected" Status:"Enabled" Team Name:"Not in a team" Temperature: Transmit Rate:"866.7 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)" BgScanGlobalBlocking:Global BG Scan blocking:"Never (0)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"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)" 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:"2.0,3.0,3.5,4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Locale:"United Kingdom" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 11 Pro" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"2.38 GB" Physical Memory (Available):"7.87 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.69 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.22000 Build 22000" Virtual Memory (Available):"9.69 GB" Virtual Memory (Total):"18.06 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [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 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB5004567:"Update [10/12/2021]" KB5007292:"Update [11/29/2021]" KB5007414:"Update [12/9/2021]" KB5008215:"Security Update [12/14/2021]" KB5008295:"Update [11/6/2021]" - "Processor" - "11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 140 Stepping 1" - "Chipset Name":"11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=11th+Gen++Core+i5+1135G7+" CPU Speed:"2.42 GHz" Current Voltage:"7. 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.22000.1" Ext. Family:"Not Available" Family:"Not Available" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"4 x 192 KB" Level 2 Cache:"4 x 5120 KB" Level 3 Cache:"8 MB" Load:"15%" Manufacturer:"GenuineIntel" Model:"140" Name:"11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz" Number of Cores:"4" Number of Cores Enabled:"4" Number of Logical Processors:"8" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000806C1" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"1" Version:"Not Available" - "Storage" - "NVMe INTEL SSDPEKNW512G8" Capablities:"Random Access, Supports Writing, SMART Notification" - "Caption":"NVMe INTEL SSDPEKNW512G8" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=NVMe+INTEL+SSDPEKNW512G8" Cylinder - Total:"62260" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.22000.1" Error Code:"Device is working properly" - "Firmware Revision":"004C" Link:"http://www.intel.com/content/www/us/en/support/solid-state-drives/000017245.html?wapkw=ssd+firmware" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"NVMe INTEL SSDPEKNW512G8" Name:"\\.\PHYSICALDRIVE0" Partitions:"4" Physical Sector Size:"512" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_INTEL_SSDPEKNW51\4&4E4E240&0&030000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"3" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"1000206900" Serial Number:"0000_0000_0100_0000_E4D2_5C1C_3640_5401." Size:"476.94 GB" Size – Available:"348.05 GB" SMART Attributes:"Self-Test: 0 minutes, OK, Short Self-Test: 0 minutes, OK" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"15876300" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"OS" Serial Number:"E01185C8" Size:"475.45 GB" Size – Available:"348.05 GB" Status:"Not Available" Volume Dirty:"No" - "SMART" 0x05 Reallocated Sector Count:0:"0" 0x09 Power-On Hours:1129:"0" 0x0C Power Cycle Count:117:"0" 0xAE Power-off Retract Count:8:"0" 0xBB Uncorrectable Error Count:0:"0" 0xBE Temperature - Current:33° C:"0" 0xBE Temperature - Highest:Not Available:"0" 0xBE Temperature - Lowest:Not Available:"23" 0xE8 Available Reserved Space:0:"10" 0xF1 Total LBAs Written:121.36 TB:"0" 0xF2 Total LBAs Read:138.95 TB:"0" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The WerSvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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 RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityUsage ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityUsage ------------------------------------------------------------------- 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_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 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 netprofm with arguments "Unavailable" in order to run the server: {A47979D2-C419-11D9-A5B4-001185AD2B89} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service LicenseManager with arguments "Unavailable" in order to run the server: {22F5B1DF-7D7A-4D21-97F8-C21AEFBA859C} ------------------------------------------------------------------- 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: {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 ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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 UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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: {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: {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 RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- 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.Management.CapabilityUsage ------------------------------------------------------------------- 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.Management.CapabilityUsage ------------------------------------------------------------------- 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 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_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f8d1 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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 WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- 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 WpnUserService_2f8d1 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service 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 RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- Bootmgr failed to obtain the BitLocker volume master key from the TPM. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} 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 server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5250E46F-BB09-D602-5891-F476DC89B700} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server microsoft.windowscommunicationsapps_16005.14326.20544.0_x64__8wekyb3d8bbwe!microsoft.windowslive.mail did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {B9B05098-3E30-483F-87F7-027CA78DA287} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff808a7e29d360, 0xffff808a7ed2aaa0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6af56001-b3bc-4334-9463-445c71efa1f2. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 19:56:44 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe40deaabc360, 0xffffe40e044b2520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d3bf64d9-9cd4-41ef-bc4e-0a13e35e35d2. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 18:33:45 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffbb093237b060, 0xffffbb094c124010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a6258b7c-66a9-4d29-8168-95ddfb0143d8. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 18:21:26 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff9c0775843360, 0xffff9c078f1609a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6f6a5b55-159e-4ed8-a0fd-ed1af17f17b0. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 18:09:06 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffda8f81c37360, 0xffffda8f9c1ef8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 085cef89-f6de-4ba5-8ead-e16c40fa6172. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 17:56:46 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff9d8d9f69d360, 0xffff9d8db8d928a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5d008e21-4083-48a9-9184-332f84808ccf. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 17:44:20 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd70fe88cb060, 0xffffd70ff1f29010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 30ae55a6-fa31-4126-984e-6b5365beba87. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 17:32:02 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffba84216e7060, 0xffffba843e746050, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a94a7f67-a336-4873-a7c3-084fe9cd7e1f. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 17:19:42 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb18cb2c1c060, 0xffffb18ccd01d8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 069199f4-30e0-498e-baf8-067fc9c6dc61. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 17:07:22 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff9a0872a45360, 0xffff9a088be088a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: de97fc9f-5b35-4be2-98b3-c93cc087de24. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 16:55:02 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff828c462ae360, 0xffff828c5dba81e0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9282d83f-917c-42de-9a8d-ca707cd68edf. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 16:42:42 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa68be7665060, 0xffffa68bffec1aa0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 18524dbb-9c65-4b4d-9bcf-335060aadf8e. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 16:30:24 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe30f0da40060, 0xffffe30f2630c010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e04b5539-7291-4f8f-92d1-0e84eaf92869. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 16:18:04 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff998a49e7d360, 0xffff998a63797aa0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 22457d29-e1cf-447c-9fa5-e9e04adf7766. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 16:05:45 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff930f65577360, 0xffff930f7f59b520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0f7b90a1-c7e3-45f0-a562-1452c65faf5d. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 15:53:25 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 15:41:05 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffae8985a86360, 0xffffae899ec592c0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0aece8b7-9298-4aec-a5cb-f1e434113ecb. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 15:28:46 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd786b2875360, 0xffffd786cb6c4a30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a9ee8912-1ef9-46d5-b05f-e08514407a44. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 15:16:26 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff87017b104060, 0xffff870195fa9730, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 296fc1c8-3461-49a1-ac5c-4dd171697740. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 15:04:09 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd5063ac9b060, 0xffffd50656d9c010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e24e7819-1055-4700-a6d0-a5162e70716e. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:51:48 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe70b3f282060, 0xffffe70b57bb1a30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8b00a681-71b3-4add-a310-b2bdfefa6439. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:39:29 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff930278a2c360, 0xffff930291e959a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 28583f8e-91ca-4038-a90b-443f296a208a. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:27:08 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffcd836ec05060, 0xffffcd838877a010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 97b274da-2eb2-4048-baa4-5047301cb5de. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:14:50 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa808c5c67360, 0xffffa808e0564010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c780f7f5-a253-4f04-b019-12c17a7d7bd2. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:02:30 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb6011188a060, 0xffffb6012acfb8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 1b5e7016-3405-4f42-a7cb-f7e06dbacbfe. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 13:50:11 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe30e7f711360, 0xffffe30e98546520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e1ce9fdd-a929-4a8b-a54c-5f2f719779c9. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 13:37:51 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe78828887360, 0xffffe78841577520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7add6936-44ac-4e6e-8255-7e0b153478cc. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 13:25:33 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff8c8539ab8060, 0xffff8c855242a010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e7bee5f0-d822-4146-81fe-6689101acdb6. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 13:13:13 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff960d5d387360, 0xffff960d7af1e600, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e7af4538-5a59-4c64-b02e-310831be996a. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 12:55:23 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd08b60a33060, 0xffffd08b7fc51700, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 281da2ca-a2ca-4403-9380-dcdcc8c7d975. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 12:12:05 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa606c568b360, 0xffffa606deb4a010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b10c635b-b818-42ba-9635-5f0e9a3ad067. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 11:40:08 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb3898f0b9060, 0xffffb389a74d08a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ef2d86b7-55f5-473c-95e8-4f589f9404c9. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 10:54:11 on ‎06/‎01/‎2022 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 driver detected a controller error on \Device\Harddisk1\DR15. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The HvHost service terminated with the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff800f83204360, 0xffff800f83e0a520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 72dbabc0-83b1-4698-a8a3-4fd8fc2028f4. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 06:31:29 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb00691076360, 0xffffb006a804e8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ab538734-1a14-497a-892f-c8006ace1e48. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 06:19:10 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 06:06:56 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 192.168.1.181 with the system having network hardware address 44-AD-B1-C8-71-6B. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd9814a2d7060, 0xffffd98161c10a30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: cfc9d884-dd9c-4055-859e-06e2a9da6410. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 05:54:39 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 05:42:22 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 05:30:05 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 05:17:48 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff800ea544d060, 0xffff800ebd2dc670, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 08f73950-eb0e-46cb-8084-2203c4e03a75. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 05:05:31 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa70f64013060, 0xffffa70f7b17d8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7c6a0747-8f69-43b8-acb7-8e33a629755b. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 04:53:15 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb60f8d632360, 0xffffb60fa6583750, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 83afc9b2-f6a5-4a88-a287-9a76eb0d5929. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 04:40:58 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffba0c27698060, 0xffffba0c3fcf6830, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 1e8082c6-62d0-46d4-86f6-b448fea1f9bb. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 04:28:41 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb90a8c381360, 0xffffb90aa9d9a9e0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9c45e43a-ef6a-406a-97e1-9019ddc2426d. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 04:16:25 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe407584aa060, 0xffffe40770925a30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 84bb41e3-ec44-4754-9339-f8a1bc25be92. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 04:04:08 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd38f2557e360, 0xffffd38f3dd099b0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: dd925362-6031-430f-9c80-077c3c45af97. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 03:51:53 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 192.168.1.168 with the system having network hardware address 44-AD-B1-C8-71-6B. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff820741e60060, 0xffff82075bd7d520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5062e72a-16d9-4658-b007-15cb309be3be. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 03:39:35 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa98a347e8360, 0xffffa98a4dd3d010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8ac82d83-a155-4b58-ae9b-5b72128c91f6. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 03:27:18 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffaa052c811060, 0xffffaa0545b11aa0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 2bfe1e1b-ee20-4291-a26e-809fd30492d6. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 03:15:02 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd0099721a060, 0xffffd009af46f4d0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 52b5d154-4e2c-445d-bb7e-83db168da850. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 03:02:46 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff998848655360, 0xffff9988619928a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 98915cc4-8ea7-4ea7-ac51-94a4351f5b9b. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 02:50:29 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffab0af0cd1060, 0xffffab0b0a2db520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: fd7a5eae-3826-4ecd-8057-ff1f57629d5d. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 02:38:12 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffdc042f9df360, 0xffffdc0448a5c010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 254eebad-7ba0-4d4c-9ab7-d27c2881c895. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 02:25:57 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff870946cc8360, 0xffff870960296aa0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 2dbf9f02-9e94-4159-8f48-c74781a9dc59. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 02:13:41 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff99854d69d360, 0xffff998566bd5010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: bfbeab13-e821-441c-a78e-56bb75aa88fa. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 02:01:23 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffbc0af877b360, 0xffffbc0b11c0c8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: babdbe08-9c66-4adf-a921-829a07d726d8. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 01:49:06 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa58af1d7f360, 0xffffa58b0b80f7c0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e7cc2bc4-c666-4da5-9791-6ec95eb25145. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 01:36:51 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa98ae0c44360, 0xffffa98afa2dba20, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6316080a-bd38-474e-b325-9e11f41aad36. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 01:24:29 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd605b46ba360, 0xffffd605cca3da30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9c8562e3-bfe5-4277-8207-11b8ed5cc5ab. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 01:12:12 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff8006dce55060, 0xffff8006f62f83d0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 20b35c82-f01a-4321-9f68-6c5352adbfb6. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 00:59:55 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd30de58b9060, 0xffffd30dfecdf8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: be6ea220-0ec2-45d6-82dd-57c806c44dcc. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 00:47:39 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff948d2fc1d360, 0xffff948d4951e850, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0701a15e-7a98-48f4-9b02-0ff9d2c4ba08. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 00:35:24 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb805f9782360, 0xffffb80611d83520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a0d36fd0-9fe9-40fa-9f09-04fafbb57680. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 00:23:07 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff9404b6279360, 0xffff9404b65e2ae0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9ac17188-745d-4c60-a76c-597c1ccb9d3c. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 00:10:49 on ‎20/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffbc039bf77360, 0xffffbc03b5ea1010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9ba98014-400a-411d-a466-2ccbe95b5586. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 23:54:31 on ‎19/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffcf01669e2360, 0xffffcf017f37a920, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 02b1a03c-113a-458a-971d-d4cc53b54f5a. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 23:27:58 on ‎19/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} 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 could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd609e0bf1360, 0xffffd609fa250520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 2fbcb681-af5d-4e4f-b2b3-87b4182bccda. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 23:18:21 on ‎18/‎12/‎2021 was unexpected. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240016: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.355.485.0). ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa10b304ec360, 0xffffa10b47da2010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a7636317-89cb-4234-a4c9-94f52b1819d6. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 22:45:35 on ‎18/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The ASUS Software Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff8001c9a48360, 0xffff8001e22968a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 68e5de0f-cd0b-4ee3-8351-db01090f6a6b. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 15:10:56 on ‎17/‎12/‎2021 was unexpected. ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff918fa65e0360, 0xffff918fbed83560, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 6fde7be3-7c35-457d-b3cb-93da1a283077. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 21:31:36 on ‎16/‎12/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- 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: 9WZDNCRFJ3PR-MICROSOFT.WINDOWSALARMS. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- 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: 9N7R5S6B0ZZH-B9ECED6F.ASUSPCAssistant. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJ3PR-MICROSOFT.WINDOWSALARMS. ------------------------------------------------------------------- The server B9ECED6F.ASUSPCAssistant_3.0.32.0_x64__qmba6cd70vzyy!App.AppX47adpsjmq9ecaqg4s11c48ptg0e3pwyt.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server MicrosoftWindows.Client.CBS_1000.22000.376.0_x64__cw5n1h2txyewy!Global.Accounts.AppXczw5m0gs1v24mkf1zqkkpebvayhcn73d.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server B9ECED6F.ASUSPCAssistant_3.0.32.0_x64__qmba6cd70vzyy!App.AppX0na3apzfvbmp03c3d8pf3nkeg10ggpyf.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7EAD5C10-8B3F-11E6-AE22-56B6B6499611} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7EAD5C10-8B3F-11E6-AE22-56B6B6499611} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7EAD5C10-8B3F-11E6-AE22-56B6B6499611} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR5. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ASUSSystemAnalysis service. ------------------------------------------------------------------- The default transaction resource manager on volume D: encountered a non-retryable error and could not start. The data contains the error code. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Virtual Disk service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Virtual Disk service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Network Setup Service service terminated with the following error: Network Setup Service is not a valid Win32 application. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {AB93B6F1-BE76-4185-A488-A9001B105B94} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 19:38:44 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffbe022a241360, 0xffffbe024264fa30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 83b24a6b-b7e9-40d9-9689-6adb3ff04cca. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 18:05:29 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa10802e24360, 0xffffa1081d358010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: c825b085-3ef4-47af-8960-1873506a8c9b. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 17:47:14 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd28f7aa70060, 0xffffd28f93d6f520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: dc15b67c-ba43-441c-8113-45071ff1569d. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 17:20:58 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} 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 could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe1028141b060, 0xffffe102998988a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: de01c38c-3f9b-45a0-aee3-4e4beba83ad2. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 10:17:49 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd687e00c9360, 0xffffd687f73c5a30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 785d7cc6-120f-42fd-98ae-4ebc6201245e. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 10:05:33 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffda04c6da7060, 0xffffda04e1215520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e66c7c08-bb59-41d9-860d-a93a1a825afa. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 09:53:18 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff850f67871060, 0xffff850f80c25a30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5646f4d9-2c06-4e31-907e-ea5826264d5c. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 09:41:01 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa68d7e01f360, 0xffffa68d954ea010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e348fc86-12b1-4acf-ba69-d72e1504b393. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 09:08:45 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff9d86dfbcf360, 0xffff9d86fa20fa30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ac4f0b9e-9deb-4b07-b4c0-d5a59418f2b6. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 08:56:29 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff808aec47f360, 0xffff808b04514010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 4fa6ea82-270f-4b33-829f-da1efa34b610. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 08:44:12 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe78fb9454360, 0xffffe78fd1a98520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8eaa8283-9e63-499b-9841-ee762e8742ad. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 08:31:56 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff9b8c2f848360, 0xffff9b8c47ecf010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: dadab2df-2bc3-41c4-9897-cd49896e526d. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 08:19:40 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffbf06236d7060, 0xffffbf063bc49670, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7d7b733d-82a4-4906-a1e7-eea3575cbabf. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 08:07:23 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff90810337d360, 0xffff90811bd7ea70, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 15e1ab98-e214-43a6-a80f-4bd84658a972. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 07:54:41 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe60b7a4be360, 0xffffe60b929748a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 9a7e41df-b1f5-4966-a0ab-eda424728290. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 07:38:22 on ‎30/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR1. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The ASUS Software Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The ASUS Software Manager service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9N7R5S6B0ZZH-B9ECED6F.ASUSPCAssistant. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attached data contains the server certificate. The SSPI client process is svchost[WpnService] (PID: 4900). ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attached data contains the server certificate. The SSPI client process is svchost[WpnService] (PID: 4900). ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attached data contains the server certificate. The SSPI client process is svchost[WpnService] (PID: 4900). ------------------------------------------------------------------- The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is client.wns.windows.com. The TLS connection request has failed. The attached data contains the server certificate. The SSPI client process is svchost[WpnService] (PID: 4900). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk1\DR13. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {005A3A96-BAC4-4B0A-94EA-C0CE100EA736} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR10. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The shadow copies of volume D: were aborted during detection because a critical control file could not be opened. ------------------------------------------------------------------- The shadow copies of volume D: were aborted during detection. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb50cf944a360, 0xffffb50d10cfaab0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a06b255c-e996-4b4e-b28c-a89443e20979. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 20:43:06 on ‎20/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Encrypted volume check: Volume information on D: cannot be read. ------------------------------------------------------------------- Encrypted volume check: Volume information on D: cannot be read. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Encrypted volume check: Volume information on D: cannot be read. ------------------------------------------------------------------- Encrypted volume check: Volume information on D: cannot be read. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff8202c18be060, 0xffff8202dacf68a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8ab8db16-f8ce-4d23-84d3-f114a50af9b2. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 23:12:53 on ‎14/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffab82e8d88060, 0xffffab8307d97050, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 35c11566-3d83-4ceb-91b0-78211f52d843. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 23:07:56 on ‎14/‎11/‎2021 was unexpected. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ASUSSystemAnalysis service. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {3EB3C877-1F16-487C-9050-104DBCD66683} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {E12CFF52-A866-4C77-9A90-F570A7AA2C6B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 192.168.1.166 with the system having network hardware address 44-AD-B1-C8-71-6B. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service 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: {9E175B6D-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 ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service 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 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.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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 UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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 camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.CapabilityAccess ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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: {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 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 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.Management.CapabilityUsage ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityUsage ------------------------------------------------------------------- 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_2f0e4 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f0e4 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f0e4 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f0e4 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_2f0e4 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_2f0e4 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service 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_2f0e4 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- 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 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 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 ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- Bootmgr failed to obtain the BitLocker volume master key from the TPM. ------------------------------------------------------------------- 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 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.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_30835 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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 UdkUserSvc_30835 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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 UdkUserSvc_30835 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_30835 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_30835 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- 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 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: {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 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 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.Management.CapabilityUsage ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service camsvc with arguments "Unavailable" in order to run the server: Windows.Internal.CapabilityAccess.Management.CapabilityUsage ------------------------------------------------------------------- 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_30835 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_30835 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_30835 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_30835 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 TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.WamProviderRegistration ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service UdkUserSvc_30835 with arguments "Unavailable" in order to run the server: WindowsUdk.UI.Shell.ViewCoordinator ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service WpnUserService_30835 with arguments "Unavailable" in order to run the server: {D18705BE-FC2F-44C8-AEFF-1CD49AEA8FC1} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service TokenBroker with arguments "Unavailable" in order to run the server: Windows.Internal.Security.Authentication.Web.TokenBrokerInternal ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service 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_30835 with arguments "Unavailable" in order to run the server: {1FFE4FFD-25B1-40B1-A1EA-EF633353BB4E} ------------------------------------------------------------------- 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 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 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 RmSvc with arguments "Unavailable" in order to run the server: {581333F6-28DB-41BE-BC7A-FF201F12F3F6} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service ShellHWDetection with arguments "Unavailable" in order to run the server: {DD522ACC-F821-461A-A407-50B198B896DC} ------------------------------------------------------------------- DCOM got error "1084" attempting to start the service DispBrokerDesktopSvc with arguments "Unavailable" in order to run the server: DispBrokerDesktop.GlobalBrokerInstance ------------------------------------------------------------------- Bootmgr failed to obtain the BitLocker volume master key from the TPM. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The cplspcon service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff8f0428619360, 0xffff8f04413b89a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 25f53259-37aa-4862-987d-adc26e0beeb8. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 07:42:15 on ‎05/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff800e391c4060, 0xffff800e512598a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 054c3bde-6078-43a4-bc61-42ec2110a18b. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 07:23:59 on ‎05/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffbd0e69443360, 0xffffbd0e816549a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 297553e2-7255-4cb1-9022-fc697484551b. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 07:05:45 on ‎05/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff860c10066360, 0xffff860c26acc8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 163fdbe4-06b1-4efb-8dcf-e91288a05723. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 06:47:30 on ‎05/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff9b8ff2dec360, 0xffff9b8ffd2098a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e7c7ed4f-cf34-4864-b63b-ebb3c1227d2b. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 06:29:16 on ‎05/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffdf0d160b3060, 0xffffdf0d2c3f76a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5e89a1e2-c154-47f9-b96c-59396265fc05. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 06:11:00 on ‎05/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff9683ea9ee360, 0xffff96840321f8a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: f4534b93-6b33-468f-9e88-da8a8c9a83d1. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The previous system shutdown at 05:45:44 on ‎05/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\system32\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did 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: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server Microsoft.LockApp_10.0.22000.1_neutral__cw5n1h2txyewy!WindowsDefaultLockScreen did not register with DCOM within the required timeout. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffca084c8ce060, 0xffffca08653c4570, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 29283f38-96cc-4f07-ba9a-52662a9950da. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 21:15:01 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd90e17244060, 0xffffd90e2ead3a30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 58057bbd-504d-4038-9129-ee59e2448e17. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:59:50 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff8286229d5360, 0xffff82863af39010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: bc8d343a-30ac-4470-92f9-811908fe25c2. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:41:38 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe48715833360, 0xffffe4872e2dd010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b407e919-b703-4d2a-805a-8cd7760d41d9. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:23:21 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb38852b94360, 0xffffb3886c49c010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: dec0037f-fbe6-4cbe-8a03-85237c38144f. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 14:05:08 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa78c7ede3360, 0xffffa78c99233520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: a8c33b30-3977-4e74-ac34-e88a39cc87ea. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 13:46:53 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa58e7c7c4360, 0xffffa58e954dd520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: fb2999f5-1e2f-4cb6-b461-7fa0560be0af. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 13:28:32 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffbf0e7cd98360, 0xffffbf0e964a9010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7ecabd7a-a704-4af1-bcef-41b79b985d63. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 13:10:17 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffad046f7d7060, 0xffffad04882688e0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 86984513-6371-48f6-b0a7-7ea79b9e829c. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 12:52:02 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa088be9f0360, 0xffffa088d74aa550, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b6146ee6-b107-4d24-a33e-71b877fe3f25. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 12:33:48 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffaa86023ef360, 0xffffaa8619feca70, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 8c413cdc-1a42-447d-a1f9-db216d695208. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 12:15:34 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffb106ad825360, 0xffffb106c6361520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 719a89ee-6afa-4fad-9a7d-d536471c41d7. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 11:57:17 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa58a993df360, 0xffffa58ab0f388a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 1176a067-1de8-4a50-8421-03ca1ea62f5c. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 11:43:34 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffdf89440a8060, 0xffffdf8940d7e010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: b7ad0fb9-1048-4508-bf83-2bef3abf56cc. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 10:10:19 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff8203d53d9060, 0xffff8203d5fb0010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 25343286-8c92-4ee0-9c99-20baf42bc0c0. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 10:01:59 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffd10545e3b060, 0xffffd1055f9e68a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: ec55531d-28bd-4e7e-9b6d-3e4066b02824. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 08:37:19 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system detected an address conflict for IP address 192.168.1.163 with the system having network hardware address 44-AD-B1-C8-71-6B. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff8b8ea0a7b360, 0xffff8b8eb9297010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 36393df3-ee0c-49a4-8dd3-964d65220d28. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 08:25:04 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffe00fb5654060, 0xffffe00fce0f1a30, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 85fa54bb-03b7-49b8-becd-fdeef8ad83f4. ------------------------------------------------------------------- The previous system shutdown at 08:12:46 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffa58731cd4360, 0xffffa5874b6c7520, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: d7c43420-f470-475c-b612-b23c7804b787. ------------------------------------------------------------------- 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 generation succeded. ------------------------------------------------------------------- The previous system shutdown at 08:00:30 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffc90ea6985360, 0xffffc90ebfc929a0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 21d7b537-1ddf-49f7-8263-41ccb2519ee3. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 07:52:45 on ‎02/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, 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 computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffff898cf0632060, 0xffff898d08ac3010, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: bc771f90-b1e0-475f-947d-3aa6d46eb4dd. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 22:11:59 on ‎01/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000005, 0xffffaa8b8afdb360, 0xffffaa8ba49f2aa0, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: aee0c001-ed75-4a1c-91aa-6a4f6844ec09. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- The previous system shutdown at 20:56:57 on ‎01/‎11/‎2021 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFHVQM-MICROSOFT.WINDOWSCOMMUNICATIONSAPPS. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The DbxSvc service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- 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: 9WZDNCRFHVQM-MICROSOFT.WINDOWSCOMMUNICATIONSAPPS. ------------------------------------------------------------------- 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: 9WZDNCRFHVQM-MICROSOFT.WINDOWSCOMMUNICATIONSAPPS. ------------------------------------------------------------------- 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: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- Intel(R) Wi-Fi 6 AX201 160MHz : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {d0bf9bb7-1710-44fb-bbc8-b2733a667ccf}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- WLAN Extensibility Module has stopped unexpectedly. Module Path: C:\WINDOWS\system32\IntelIHVRouter08.dll ------------------------------------------------------------------- WLAN Extensibility Module has stopped unexpectedly. Module Path: C:\WINDOWS\system32\IntelIHVRouter08.dll ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{ED1A994E-4647-4E00-84A3-56FD1FE9C58C} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did 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: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE. ------------------------------------------------------------------- The Printer Extensions and Notifications service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. ------------------------------------------------------------------- The cplspcon service terminated with the following error: Unspecified error ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 1/7/2022, 19:47:44 Machine name: LAPTOP-LPCNDEAI Machine Id: {FD4B6446-43CE-42E6-8FAB-DDF1F0C772FF} Operating System: Windows 11 Pro 64-bit (10.0, Build 22000) (22000.co_release.210604-1628) Language: English (Regional Setting: English) System Manufacturer: ASUSTeK COMPUTER INC. System Model: VivoBook_ASUSLaptop X513EA_S513EA BIOS: X513EA.308 (type: UEFI) Processor: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 CPUs), ~2.4GHz Memory: 16384MB RAM Available OS Memory: 16066MB RAM Page File: 8591MB used, 9906MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.2.2 DxDiag Version: 10.00.22000.0001 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: Intel(R) Iris(R) Xe Graphics Manufacturer: Intel Corporation Chip type: Intel(R) Iris(R) Xe Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_9A49&SUBSYS_14321043&REV_01 Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 8160 MB Dedicated Memory: 128 MB Shared Memory: 8032 MB Current Mode: 1920 x 1080 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Internal Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.639648,0.330078), Green(0.299805,0.599609), Blue(0.149414,0.059570), White Point(0.312500,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: unknown Monitor Id: KDC0830 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: Internal Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12umd64.dll Driver File Version: 30.00.0100.9929 (English) Driver Version: 30.0.100.9929 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 3.0 Hardware Scheduling: DriverSupportState:AlwaysOff Enabled:False Graphics Preemption: Primitive Compute Preemption: Thread group Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: DISABLE_HWSCH Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 30/09/2021 00:00:00, 1481672 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-D909-11CF-3A55-5634AEC2D335} Vendor ID: 0x8086 Device ID: 0x9A49 SubSys ID: 0x14321043 Revision ID: 0x0001 Driver Strong Name: oem0.inf:5f63e5348b96c4a0:iTGLD_w10_DS:30.0.100.9929:PCI\VEN_8086&DEV_9A49&SUBSYS_14321043 Rank Of Driver: 00CF0001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {9B31316B-F204-455D-8A8C-9345DCA77C01} {AFE4285C-AB63-4B2D-8278-E6BAACEA2CE9} {277DE9C5-ED83-48DD-AB8F-AC2D24B22943} {04C5BA10-4E9A-4B8E-8DBF-4F4B48AFA27C} {0ACEF8BC-285F-415D-AB22-7BF2527A3D2E} {24D19FCA-C5A2-4B8E-9F93-F8F6EF15C890} {353ACA91-D945-4C13-AE7E-469060FAC8D8} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {B8B28E0C-ECAB-4217-8C82-EAAA9755AAF0} {8732ECFD-9747-4897-B42A-E534F9FF2B7A} {E139B5CA-47B2-40E1-AF1C-AD71A67A1836} {056A6E36-F3A8-4D00-9663-7E9430358BF9} {5415A68C-231E-46F4-878B-5E9A22E967E9} {161BE912-44C2-49C0-B61E-D946852B32A1} {D6D6BC4F-D51A-4712-97E8-750917C860FD} {7FEF652D-3233-44DF-ACF7-ECFB584DAB35} {580DA148-E4BF-49B1-943B-4214AB05A6FF} {CEE393AB-1030-4F7B-8DBC-55629C72F17E} {87B2AE39-C9A5-4C53-86B8-A52D7EDBA488} {10E19AC8-BF39-4443-BEC3-1B0CBFE4C7AA} {2DEC00C7-21EE-4BF8-8F0E-773F11F126A2} {C35153A0-23C0-4A81-B3BB-6A1326F2B76B} {A33FD0EC-A9D3-4C21-9276-C241CC90F6C7} {310E59D2-7EA4-47BB-B319-500E78855336} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {E484DCB8-CAC9-4859-99F5-5C0D45069089} {41A5AF96-E415-4B0C-9D03-907858E23E78} {6A6A81BA-912A-485D-B57F-CCD2D37B8D94} {E4E3CF5B-97D2-4658-AACB-366E3EE2CEEE} {FD9D9559-0FD3-4917-A9A7-07E714EE9EF9} {0E4BC693-5D2C-4936-B125-AEFE32B16D8A} {2F08B5B1-DBC2-4D48-883A-4E7B8174CFF6} {5467807A-295D-445D-BD2E-CBA8C2457C3D} {AE0D4E15-2360-40A8-BF82-028E6A0DD827} {8FF8A3AA-C456-4132-B6EF-69D9DD72571D} {C23DD857-874B-423C-B6E0-82CEAA9B118A} {5B08E35D-0C66-4C51-A6F1-89D00CB2C197} {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {68A21C7B-D58F-4E74-9993-E4B8172B19A0} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {1D5C4D76-B55A-4430-904C-3383A7AE3B16} {A7F759DD-5F54-4D7F-8291-42E883C546FE} {F34FA92F-DC79-474C-B0DB-B7BD4522DF77} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {CA44AFC5-E1D0-42E6-9154-B127186D4D40} {F9A16190-3FB4-4DC5-9846-C8751F83D6D7} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466} Deinterlace Caps: {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {BF752EF6-8CC4-457A-BE1B-08BD1CAEEE9F}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_EdgeFiltering {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBVerticalStretch {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend D3D9 Overlay: Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 3 MPO Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) MPO Stretch: 21.000X - 0.334X MPO Media Hints: colorspace Conversion MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM PanelFitter Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) PanelFitter Stretch: 21.000X - 0.334X Extension Drivers: Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_02b731d0a430421c\iigd_ext.inf Driver Version: 30.0.100.9929 Driver Date: 09/30/2021 Driver Provider: Intel Corporation Catalog Attributes: Universal:False Declarative:True Component Drivers: Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A ------------- Sound Devices ------------- Description: Speakers (Realtek(R) Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0256&SUBSYS_10431032&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.9202.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 06/07/2021 00:00:00, 6523968 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: Microphone (Realtek(R) Audio) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: RTKVHD64.sys Driver Version: 6.0.9202.1 (English) Driver Attributes: Final Retail Date and Size: 06/07/2021 00:00:00, 6523968 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 1 --------------------- FriendlyName: USB2.0 HD UVC WebCam Category: Camera SymbolicLink: \\?\usb#vid_13d3&pid_56a8&mi_00#6&2361c5f6&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 SensorOrientation: 0 Manufacturer: Realtek HardwareID: USB\VID_13D3&PID_56A8&REV_1951&MI_00,USB\VID_13D3&PID_56A8&MI_00 DriverDesc: Realtek PC Camera Driver DriverProvider: Realtek DriverVersion: 10.0.19041.20152 DriverDateEnglish: 7/17/2020 00:00:00 DriverDateLocalized: 17/07/2020 00:00:00 Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: USB2.0 HD UVC WebCam Parent: USB\VID_13D3&PID_56A8\0x0001 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {78DCB7D0-33EA-458B-B98A-56E9A3A40B50} MFT0: n/a DMFT: {09824200-9A44-4B06-8C74-92D99E09B435} CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: {09824200-9A44-4B06-8C74-92D99E09B435} EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a MSXUCapability: n/a ProfileIDs: n/a ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04F3, 0x30F7 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + PC/AT Enhanced PS/2 Keyboard (101/102-Key) | Matching Device ID: *PNP030B | Service: i8042prt | Driver: i8042prt.sys, 6/5/2021 12:04:46, 155648 bytes | Driver: kbdclass.sys, 6/5/2021 12:04:46, 90424 bytes | + HID-compliant mouse | Vendor/Product ID: 0x04F3, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 6/5/2021 12:04:46, 65536 bytes | Driver: mouclass.sys, 6/5/2021 12:04:46, 90448 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 356.4 GB Total Space: 486.9 GB File System: NTFS Model: NVMe INTEL SSDPEKNW512G8 -------------- System Devices -------------- Name: Intel(R) SMBus - A0A3 Device ID: PCI\VEN_8086&DEV_A0A3&SUBSYS_14321043&REV_20\3&11583659&0&FC Driver: n/a Name: Intel(R) GNA Scoring Accelerator module Device ID: PCI\VEN_8086&DEV_9A11&SUBSYS_14321043&REV_01\3&11583659&0&40 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\gna.inf_amd64_689d3d5fefeef458\gna.sys, 10.64.0002.19041 (English), 11/6/2020 11:37:57, 84880 bytes Name: Intel RST VMD Managed Controller 09AB Device ID: PCI\VEN_8086&DEV_09AB&SUBSYS_14321043&REV_00\3&11583659&0&E8 Driver: n/a Name: Intel RST VMD Managed Controller 09AB Device ID: PCI\VEN_8086&DEV_09AB&SUBSYS_14321043&REV_00\3&11583659&0&B8 Driver: n/a Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_A0C8&SUBSYS_10321043&REV_20\3&11583659&0&FB Driver: C:\WINDOWS\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_7f5b544b68b44930\IntcAudioBus.sys, 10.30.0000.5152 (English), 2/18/2021 01:42:30, 297224 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.22000.0120 (English), 10/12/2021 19:18:39, 135168 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.22000.0120 (English), 10/12/2021 19:18:39, 462848 bytes Name: Intel(R) Platform Monitoring Technology Driver Device ID: PCI\VEN_8086&DEV_9A0D&SUBSYS_00000000&REV_01\3&11583659&0&50 Driver: C:\WINDOWS\system32\DRIVERS\IntelPMT.sys, 10.00.22000.0001 (English), 6/5/2021 12:04:46, 74224 bytes Name: PCI standard host CPU bridge Device ID: PCI\VEN_8086&DEV_9A14&SUBSYS_14321043&REV_01\3&11583659&0&00 Driver: n/a Name: Intel(R) Serial IO SPI Host Controller - A0AA Device ID: PCI\VEN_8086&DEV_A0AA&SUBSYS_14321043&REV_20\3&11583659&0&F2 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_spi_tgl.inf_amd64_b6ea3d48ee329530\iaLPSS2_SPI_TGL.sys, 30.100.2031.0002 (English), 8/12/2020 15:37:34, 155816 bytes Name: Intel(R) Serial IO I2C Host Controller - A0E8 Device ID: PCI\VEN_8086&DEV_A0E8&SUBSYS_14321043&REV_20\3&11583659&0&A8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_tgl.inf_amd64_ab87bf17a571e523\iaLPSS2_I2C_TGL.sys, 30.100.2031.0002 (English), 8/12/2020 15:37:34, 197272 bytes Name: Intel(R) Dynamic Tuning Processor Participant Device ID: PCI\VEN_8086&DEV_9A03&SUBSYS_14321043&REV_01\3&11583659&0&20 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\esif_lf.sys, 8.07.10401.16510 (English), 8/27/2020 01:14:04, 420008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\dptf_cpu.sys, 8.07.10401.16510 (English), 8/27/2020 01:14:02, 73384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\esif_uf.exe, 8.07.10401.16510 (English), 9/21/2020 08:52:18, 2254776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\esif_umdf2.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:06, 988328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\Dptf.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:54, 2406568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyRfim.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:00, 793768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyActive.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:56, 806568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyActive2.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:56, 988840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyAdaptiveUserPresence.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:56, 981160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyAdaptivePerformance.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:56, 1183912 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyCritical.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:56, 784040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyPassive.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:58, 1116328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyPassive2.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:58, 1041064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyPid.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:58, 963240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyPowerBoss.dll, 8.07.10401.16510 (English), 8/27/2020 01:13:58, 1399976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyVirtualSensor.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:02, 949416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyPowerShare.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:00, 944296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicyPowerShare2.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:00, 960168 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\DptfPolicySystemConfiguration.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:00, 750760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\upe_wwan.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:10, 132776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\upe_wifi.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:08, 66728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\upe_nvme.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:08, 114344 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\upe_battery.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:06, 71336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\upe_socwc.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:08, 224936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\upe_hwpf.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:08, 73896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\dptf_helper.exe, 8.07.10401.16510 (English), 9/21/2020 08:52:14, 531384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\esif_cmp.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:04, 138408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\esif_ws.dll, 8.07.10401.16510 (English), 8/27/2020 01:14:06, 230568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\dptf_cpu.inf_amd64_e3868713e3d137ef\dsp.dv, 8/27/2020 01:03:12, 877280 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_A0E0&SUBSYS_14321043&REV_20\3&11583659&0&B0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_e9ffe3f2557dd9e9\x64\TeeDriverW10x64.sys, 2040.100.0000.1029 (English), 10/26/2020 15:42:32, 300040 bytes Name: Intel RST VMD Controller 9A0B Device ID: PCI\VEN_8086&DEV_9A0B&SUBSYS_00008086&REV_00\3&11583659&0&70 Driver: C:\WINDOWS\system32\DRIVERS\iaStorVD.sys, 18.06.0001.1016 (English), 8/30/2021 12:38:58, 1544912 bytes Driver: C:\WINDOWS\system32\DRIVERS\iaStorAfs.sys, 18.06.0001.1016 (English), 8/30/2021 12:38:58, 74448 bytes Driver: C:\WINDOWS\system32\iaStorAfsService.exe, 18.06.0001.1016 (English), 8/30/2021 12:38:58, 3160784 bytes Driver: C:\WINDOWS\system32\iaStorAfsNative.exe, 18.06.0001.1016 (English), 8/30/2021 12:38:58, 220368 bytes Driver: C:\WINDOWS\system32\OptaneEventLogMsg.dll, 18.06.0001.1016 (English), 8/30/2021 12:38:58, 24256 bytes Driver: C:\WINDOWS\system32\Optane.dll, 18.06.0001.1016 (English), 8/30/2021 12:38:58, 134336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iastorvd.inf_amd64_a5ea1b1d8db1527e\RstMwService.exe, 18.06.0001.1016 (English), 8/30/2021 12:38:58, 1998024 bytes Driver: C:\WINDOWS\system32\RstMwEventLogMsg.dll, 18.06.0001.1016 (English), 8/30/2021 12:38:58, 28368 bytes Name: Intel(R) LPC Controller/eSPI Controller (U Premium) - A082 Device ID: PCI\VEN_8086&DEV_A082&SUBSYS_14321043&REV_20\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.22000.0001 (English), 6/5/2021 12:04:45, 53576 bytes Name: Intel(R) SPI (flash) Controller - A0A4 Device ID: PCI\VEN_8086&DEV_A0A4&SUBSYS_14321043&REV_20\3&11583659&0&FD Driver: n/a Name: PCI standard RAM Controller Device ID: PCI\VEN_8086&DEV_A0EF&SUBSYS_14321043&REV_20\3&11583659&0&A2 Driver: n/a Name: Intel(R) Serial IO I2C Host Controller - A0E9 Device ID: PCI\VEN_8086&DEV_A0E9&SUBSYS_14321043&REV_20\3&11583659&0&A9 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_tgl.inf_amd64_ab87bf17a571e523\iaLPSS2_I2C_TGL.sys, 30.100.2031.0002 (English), 8/12/2020 15:37:34, 197272 bytes Name: Intel(R) Wi-Fi 6 AX201 160MHz Device ID: PCI\VEN_8086&DEV_A0F0&SUBSYS_00748086&REV_20\3&11583659&0&A3 Driver: C:\WINDOWS\system32\DRIVERS\Netwtw10.sys, 22.90.0000.0005 (English), 10/12/2021 18:40:16, 5166672 bytes Driver: C:\WINDOWS\system32\DRIVERS\Netwfw10.dat, 10/12/2021 18:40:14, 27967916 bytes Driver: C:\WINDOWS\system32\IntelIHVRouter08.dll, 22.12080.0000.0003 (English), 10/12/2021 18:40:14, 1529400 bytes Name: Intel(R) Iris(R) Xe Graphics Device ID: PCI\VEN_8086&DEV_9A49&SUBSYS_14321043&REV_01\3&11583659&0&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdkmdn64.sys, 30.00.0100.9929 (English), 10/5/2021 15:50:22, 30956040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxsn64.vp, 10/5/2021 15:19:02, 6033 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd10iumd64.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:40, 27117224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd11dxva64.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:50, 78466000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12dxva64.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:56, 78232016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12umd64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:06, 10564448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12um64ldr.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:02, 151088 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12um64xel.dll, 10/5/2021 15:51:04, 9263152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdgmm64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:34, 4047656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igfxcmrt64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:52, 224568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igfx11cmrt64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:48, 227760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdumdim64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:46, 1481672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdail64.dll, 10/5/2021 15:50:18, 202568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd9dxva64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:18, 64974032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iga64.dll, 10/5/2021 15:50:28, 3018080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igc64.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:36, 53672104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\SPIRVDLL.dll, 10/5/2021 15:51:34, 3470688 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\DnnlPlugin.dll, 10/5/2021 15:50:26, 42241776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\UniversalAdapter64.dll, 10/5/2021 15:53:06, 353800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\opencl-clang64.dll, 2.00.0009.0000 (English), 10/5/2021 15:53:02, 83482496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdfcl64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:26, 1069584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdmd64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:40, 9320632 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdml64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:42, 4763872 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdde64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:20, 429656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdinfo64.dll, 10/5/2021 15:51:36, 165832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdext64.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:24, 292584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd10iumd32.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:38, 22632248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd11dxva32.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:44, 77073768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12dxva32.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:54, 76840896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12umd32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:04, 10165568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12um32ldr.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:58, 115184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd12um32xel.dll, 10/5/2021 15:51:00, 8827064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdgmm32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:28, 3187400 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdumdim32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:44, 1312896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdail32.dll, 10/5/2021 15:50:16, 166728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igd9dxva32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:12, 63608472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igfxcmrt32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:52, 180984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igfx11cmrt32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:46, 182544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iga32.dll, 10/5/2021 15:50:28, 2416392 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igc32.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:32, 45313032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\SPIRVDLL32.dll, 10/5/2021 15:51:36, 2689352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\UniversalAdapter32.dll, 10/5/2021 15:53:06, 293184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\opencl-clang32.dll, 2.00.0009.0000 (English), 10/5/2021 15:52:58, 61948464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdfcl32.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:20, 968528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdmd32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:38, 7865336 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdml32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:40, 3725376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdde32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:20, 349688 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdinfo32.dll, 10/5/2021 15:51:34, 139760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdext32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:22, 237096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libigd12umd64.so, 10/5/2021 15:19:04, 8190432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libigc.so, 10/5/2021 15:19:04, 38575424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libLLVM-9.so, 10/5/2021 15:19:04, 38562040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libigdgmm.so.11, 10/5/2021 15:19:04, 2161168 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libUniversalAdapter64.so, 10/5/2021 15:19:06, 505936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libigdfcl.so, 10/5/2021 15:19:04, 971064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libopencl-clang.so.9, 10/5/2021 15:19:06, 80933576 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libwsl_compute_helper.so, 10/5/2021 15:19:06, 501840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\UMED.dll, 10/5/2021 15:53:04, 152184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxo64.vp, 10/5/2021 15:19:02, 42513 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxc64.vp, 10/5/2021 15:19:02, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxg64.vp, 10/5/2021 15:19:02, 43760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxo64_dev.vp, 10/5/2021 15:19:02, 43143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxc64_dev.vp, 10/5/2021 15:19:02, 43214 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxg64_dev.vp, 10/5/2021 15:19:02, 43732 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxa64.vp, 10/5/2021 15:19:02, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\iglhxa64.cpa, 10/5/2021 15:19:02, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\IntelCpHDCPSvc.exe, 30.00.0100.9929 (English), 10/5/2021 15:50:58, 347656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\cp_resources.bin, 10/5/2021 15:18:28, 2572396 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igxelpicd64.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:56, 16497504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igxelpicd32.dll, 30.00.0100.9929 (English), 10/5/2021 15:50:54, 13561184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\OSSCOPYRIGHT.txt, 10/5/2021 15:19:10, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igvk64.dll, 30.00.0100.9929 (English), 10/5/2021 15:52:02, 20305584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igvk64.json, 10/5/2021 15:19:02, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\VulkanRT-EULA.txt, 10/5/2021 15:19:10, 4008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igvk32.dll, 30.00.0100.9929 (English), 10/5/2021 15:51:58, 18313296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igvk32.json, 10/5/2021 15:19:02, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\vulkan-1-64.dll, 1.02.0176.0001 (English), 10/5/2021 15:51:40, 1115648 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\vulkaninfo-64.exe, 1.02.0176.0001 (English), 10/5/2021 15:51:42, 1886904 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\vulkan-1-32.dll, 1.02.0176.0001 (English), 10/5/2021 15:51:38, 969232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\vulkaninfo-32.exe, 1.02.0176.0001 (English), 10/5/2021 15:51:42, 1462848 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.02.0176.0001 (English), 10/5/2021 15:51:38, 969232 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.02.0176.0001 (English), 10/5/2021 15:51:42, 1462848 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.02.0176.0001 (English), 10/5/2021 15:51:38, 969232 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.02.0176.0001 (English), 10/5/2021 15:51:42, 1462848 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.02.0176.0001 (English), 10/5/2021 15:51:40, 1115648 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.02.0176.0001 (English), 10/5/2021 15:51:42, 1886904 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.02.0176.0001 (English), 10/5/2021 15:51:40, 1115648 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.02.0176.0001 (English), 10/5/2021 15:51:42, 1886904 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 10/5/2021 15:51:08, 370544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdrcl32.dll, 23.20.0100.9929 (English), 10/5/2021 15:50:28, 5096776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 10/5/2021 15:51:08, 507752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\ze_loader.dll, 1.04.0001.0000 (English), 10/5/2021 15:51:46, 376136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\ze_validation_layer.dll, 1.04.0001.0000 (English), 10/5/2021 15:51:48, 148296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\ze_tracing_layer.dll, 1.04.0001.0000 (English), 10/5/2021 15:51:46, 459096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\ControlLib.dll, 1.00.0037.0000 (English), 10/5/2021 15:50:22, 436424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\igdrcl64.dll, 23.20.0100.9929 (English), 10/5/2021 15:50:28, 5800776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\ze_intel_gpu64.dll, 1.02.0000.0000 (English), 10/5/2021 15:51:44, 5203784 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 3.00.0001.0000 (English), 6/5/2021 12:08:55, 78336 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 3.00.0001.0000 (English), 6/5/2021 12:08:54, 118784 bytes Driver: C:\WINDOWS\system32\ze_loader.dll, 1.04.0001.0000 (English), 10/5/2021 15:51:46, 376136 bytes Driver: C:\WINDOWS\system32\ze_validation_layer.dll, 1.04.0001.0000 (English), 10/5/2021 15:51:48, 148296 bytes Driver: C:\WINDOWS\system32\ze_tracing_layer.dll, 1.04.0001.0000 (English), 10/5/2021 15:51:46, 459096 bytes Driver: C:\WINDOWS\system32\ControlLib.dll, 1.00.0037.0000 (English), 10/5/2021 15:50:22, 436424 bytes Driver: C:\WINDOWS\SysWow64\libmfxhw32.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:28, 717960 bytes Driver: C:\WINDOWS\SysWow64\mfxplugin32_hw.dll, 21.08.0031.0272 (English), 10/5/2021 15:51:12, 20639072 bytes Driver: C:\WINDOWS\system32\libmfxhw64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:30, 959256 bytes Driver: C:\WINDOWS\system32\mfxplugin64_hw.dll, 21.08.0031.0272 (English), 10/5/2021 15:51:14, 27896656 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:04, 48112 bytes Driver: C:\WINDOWS\system32\libvpl.dll, 10/5/2021 15:53:10, 494880 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:06, 45440 bytes Driver: C:\WINDOWS\SysWow64\libvpl.dll, 10/5/2021 15:53:08, 429672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfxplugin64_hw.dll, 21.08.0031.0272 (English), 10/5/2021 15:51:14, 27896656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfxplugin64_av1e_gacc.dll, 3.11.0005.0020 (English), 10/5/2021 15:52:26, 12606224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\intel_gfx_api-x64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:04, 48112 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfxplugin32_hw.dll, 21.08.0031.0272 (English), 10/5/2021 15:51:12, 20639072 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfxplugin32_av1e_gacc.dll, 3.11.0005.0020 (English), 10/5/2021 15:52:22, 8648640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\intel_gfx_api-x86.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:06, 45440 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_h264ve_32.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:42, 2498840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_mjpgvd_32.dll, 21.08.0031.0272 (English), 10/5/2021 15:51:18, 2353504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_h265ve_32.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:46, 2512048 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_vp9ve_32.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:52, 2506200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_encrypt_32.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:38, 2361216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_av1hve_32.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:34, 2508384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\c_32.cpa, 10/5/2021 15:18:28, 1361159 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\cpa_32.vp, 10/5/2021 15:18:28, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\dev_32.vp, 10/5/2021 15:18:28, 57143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\he_32.vp, 10/5/2021 15:18:28, 73861 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mj_32.vp, 10/5/2021 15:19:06, 69497 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\h265e_32.vp, 10/5/2021 15:18:28, 75497 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\vp9e_32.vp, 10/5/2021 15:19:10, 75060 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_av1hve_32.vp, 10/5/2021 15:19:06, 75125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_h264ve_64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:44, 3036528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_mjpgvd_64.dll, 21.08.0031.0272 (English), 10/5/2021 15:51:20, 2860880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_h265ve_64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:48, 3056016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_vp9ve_64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:54, 3049760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_encrypt_64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:40, 2868368 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_av1hve_64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:34, 3051920 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\c_64.cpa, 10/5/2021 15:18:28, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\cpa_64.vp, 10/5/2021 15:18:28, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\dev_64.vp, 10/5/2021 15:18:28, 56359 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\he_64.vp, 10/5/2021 15:18:28, 13055 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mj_64.vp, 10/5/2021 15:19:06, 12779 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\h265e_64.vp, 10/5/2021 15:18:28, 13675 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\vp9e_64.vp, 10/5/2021 15:19:10, 13502 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\mfx_mft_av1hve_64.vp, 10/5/2021 15:19:06, 13471 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libmfxhw64.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:18, 29158800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libmfxhw32.dll, 21.08.0031.0272 (English), 10/5/2021 15:52:16, 27559040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libmfx64-gen.dll, 21.08.0031.1608 (English), 10/5/2021 15:52:12, 24625992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2091181eebf21f65\libmfx32-gen.dll, 21.08.0031.1608 (English), 10/5/2021 15:52:10, 23326840 bytes Name: Intel(R) Serial IO UART Host Controller - A0A8 Device ID: PCI\VEN_8086&DEV_A0A8&SUBSYS_14321043&REV_20\3&11583659&0&F0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_uart2_tgl.inf_amd64_1a8e964d43720594\iaLPSS2_UART2_TGL.sys, 30.100.2031.0002 (English), 8/12/2020 15:37:34, 310440 bytes Name: Intel(R) USB 3.10 eXtensible Host Controller - 1.20 (Microsoft) Device ID: PCI\VEN_8086&DEV_A0ED&SUBSYS_201F1043&REV_20\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.22000.0348 (English), 12/9/2021 13:39:07, 655696 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.22000.0348 (English), 12/9/2021 13:39:07, 161512 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.22000.0120 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.22000.0120 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.22000.0120 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.22000.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.22000.0001 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.22000.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.22000.0120 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.22000.0001 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.22000.0001 DV Muxer,0x00400000,0,0,qdv.dll,10.00.22000.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.22000.0001 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.22000.0318 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.22000.0001 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.22000.0001 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.22000.0037 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.22000.0376 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.22000.0001 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.22000.0037 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.22000.0001 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.22000.0001 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.22000.0001 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.22000.0001 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.22000.0001 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.22000.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.22000.0037 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22000.0120 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.22000.0001 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.22000.0001 DV Splitter,0x00600000,1,2,qdv.dll,10.00.22000.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.22000.0001 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.22000.0120 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.22000.0001 Video Renderer,0x00800001,1,0,quartz.dll,10.00.22000.0001 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.22000.0037 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.22000.0001 Video Renderer,0x00400000,1,0,quartz.dll,10.00.22000.0001 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.22000.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.22000.0318 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,10.00.22000.0282 File writer,0x00200000,1,0,qcap.dll,10.00.22000.0001 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.22000.0001 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.22000.0001 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22000.0120 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.22000.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.22000.0001 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.22000.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.22000.0001 Null Renderer,0x00200000,1,0,qedit.dll,10.00.22000.0001 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.22000.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.22000.0120 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.22000.0037 Smart Tee,0x00200000,1,2,qcap.dll,10.00.22000.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.22000.0001 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.22000.0001 Wave Parser,0x00400000,1,1,quartz.dll,10.00.22000.0001 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.22000.0001 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.22000.0001 File stream renderer,0x00400000,1,1,quartz.dll,10.00.22000.0001 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.22000.0120 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.22000.0037 AVI Mux,0x00200000,1,0,qcap.dll,10.00.22000.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.22000.0001 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.22000.0001 File Source (URL),0x00400000,0,1,quartz.dll,10.00.22000.0001 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.22000.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.22000.0001 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.22000.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.22000.0001 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.22000.0120 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.22000.0001 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.22000.0282 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.22000.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.22000.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.22000.0001 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.22000.0001 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.22000.0001 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.22000.0001 PCM,0x00200000,1,1,quartz.dll,10.00.22000.0001 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.22000.0001 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.22000.0001 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.22000.0001 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.22000.0001 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.22000.0001 Audio Capture Sources: Microphone (Realtek(R) Audio),0x00200000,0,0,qcap.dll,10.00.22000.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.22000.0194 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.22000.0194 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.22000.0194 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.22000.0001 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.22000.0001 WDM Streaming Capture Devices: ,0x00000000,0,0,, Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,10.00.22000.0120 ,0x00000000,0,0,, Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.22000.0120 USB2.0 HD UVC WebCam,0x00200000,1,1,ksproxy.ax,10.00.22000.0120 WDM Streaming Rendering Devices: Realtek HD Audio output with SST,0x00200000,2,2,ksproxy.ax,10.00.22000.0120 Realtek HD Audio 2nd output with SST,0x00200000,2,2,ksproxy.ax,10.00.22000.0120 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.22000.0001 Video Capture Sources: USB2.0 HD UVC WebCam,0x00200000,1,1,ksproxy.ax,10.00.22000.0120 PowerToys VideoConference Mute,0x00200000,0,1,PowerToys.VideoConferenceProxyFilter_x64.dll, Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.22000.0001 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.22000.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.22000.0001 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.22000.0120 Audio Renderers: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.22000.0001 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.22000.0001 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.22000.0001 DirectSound: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.22000.0001 ---------------------------- 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.22000.0376 mfreadwrite.dll, 10.00.22000.0001 mfcaptureengine.dll, 10.00.22000.0348 mfsensorgroup.dll, 10.00.22000.0001 windows.media.dll, 10.00.22000.0282 frameserver.dll, 10.00.22000.0065 frameserverclient.dll, 10.00.22000.0001 --------------------------- 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, 21.08.0031.0272 Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 21.08.0031.0272 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.22000.0376 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.22000.0001 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.22000.0001 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.22000.0376 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.22000.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.22000.0120 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.22000.0318 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.22000.0001 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.22000.0001 VP9VideoExtensionDecoder WebpImageExtension HEIFImageExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 21.08.0031.0272 Intel� Hardware Accelerated AV1 Encoder MFT, {62C053CE-5357-4794-8C5A-FBEFFEFFB82D}, 0x4, 7, mfx_mft_av1hve_64.dll, 21.08.0031.0272 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 21.08.0031.0272 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 21.08.0031.0272 Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 21.08.0031.0272 Intel� Hardware Accelerated AV1 Encoder MFT, {62C053CE-5357-4794-8C5A-FBEFFEFFB82D}, 0x4, 7, mfx_mft_av1hve_64.dll, 21.08.0031.0272 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 21.08.0031.0272 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 21.08.0031.0272 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.22000.0348 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.22000.0001 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.22000.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.22000.0282 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.22000.0120 VP9VideoExtensionEncoder HEIFImageExtension Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.22000.0001 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.22000.0071 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.22000.0001 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.22000.0001 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.22000.0071 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.22000.0348 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.22000.0258 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.22000.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.22000.0120 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.22000.0184 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.22000.0376 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.22000.0376 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.22000.0120 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.22000.0001 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.22000.0001 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.22000.0184 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.22000.0120 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.22000.0376 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.22000.0376 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.22000.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.22000.0001 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.22000.0376 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.22000.0120 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.22000.0120 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.22000.0120 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.22000.0376 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.22000.0001 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.22000.0001 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.22000.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.22000.0120 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.22000.0001 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.22000.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.22000.0001 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.22000.0120 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.22000.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.22000.0001 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.22000.0348 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.22000.0376 -------------------------------------------- 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} {E06D8033-DB46-11CF-B4D1-00805F6CBBEA}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {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} {C2FE6F0A-4E3C-4DF1-9B60-50863091E4B9}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} 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: {651288E5-A7ED-4076-A96B-6CC62D848FE1} (Balanced) 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 , type 0 Event Name: crashpad_log Response: Not available Cab Id: 0 Problem signature: P1: msedgewebview2setup.exe P2: 96.0.1054.62 P3: ExcessiveVersionDirCount P4: 0x16 P5: P6: P7: P8: P9: P10: +++ WER1 +++: Fault bucket 1894628727267409332, type 5 Event Name: crashpad_log Response: Not available Cab Id: 0 Problem signature: P1: msedgewebview2setup.exe P2: 96.0.1054.62 P3: ExcessiveVersionDirCount P4: 0x16 P5: P6: P7: P8: P9: P10: +++ WER2 +++: Fault bucket , type 0 Event Name: crashpad_log Response: Not available Cab Id: 0 Problem signature: P1: msedgewebview2setup.exe P2: 96.0.1054.62 P3: ExcessiveVersionDirCount P4: 0x16 P5: P6: P7: P8: P9: P10: +++ WER3 +++: Fault bucket 1894628727267409332, type 5 Event Name: crashpad_log Response: Not available Cab Id: 0 Problem signature: P1: msedgewebview2setup.exe P2: 96.0.1054.62 P3: ExcessiveVersionDirCount P4: 0x16 P5: P6: P7: P8: P9: P10: +++ WER4 +++: Fault bucket 0x9F_5_IMAGE_IntcAudioBus.sys, type 0 Event Name: BlueScreen Response: Not available Cab Id: 37ae2e59-3e06-4914-855f-de07f3f73661 Problem signature: P1: 9f P2: 5 P3: ffff808a7e29d360 P4: ffff808a7ed2aaa0 P5: 0 P6: 10_0_22000 P7: 0_0 P8: 256_1 P9: P10: +++ WER5 +++: Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 9f P2: 5 P3: ffff808a7e29d360 P4: ffff808a7ed2aaa0 P5: 0 P6: 10_0_22000 P7: 0_0 P8: 256_1 P9: P10: +++ WER6 +++: Fault bucket , type 0 Event Name: crashpad_log Response: Not available Cab Id: 0 Problem signature: P1: msedgewebview2setup.exe P2: 96.0.1054.62 P3: ExcessiveVersionDirCount P4: 0x16 P5: P6: P7: P8: P9: P10: +++ WER7 +++: Fault bucket 1894628727267409332, type 5 Event Name: crashpad_log Response: Not available Cab Id: 0 Problem signature: P1: msedgewebview2setup.exe P2: 96.0.1054.62 P3: ExcessiveVersionDirCount P4: 0x16 P5: P6: P7: P8: P9: P10: +++ WER8 +++: Fault bucket , type 0 Event Name: crashpad_log Response: Not available Cab Id: 0 Problem signature: P1: msedgewebview2setup.exe P2: 96.0.1054.62 P3: ExcessiveVersionDirCount P4: 0x16 P5: P6: P7: P8: P9: P10: +++ WER9 +++: Fault bucket 1894628727267409332, type 5 Event Name: crashpad_log Response: Not available Cab Id: 0 Problem signature: P1: msedgewebview2setup.exe P2: 96.0.1054.62 P3: ExcessiveVersionDirCount P4: 0x16 P5: P6: P7: P8: P9: P10: ...#SSU#...