# SSU Scan Information Scan Info: Version:"2.5.0.15" Date:"01/06/2023" Time:"00:01:00.9744897" # Scanned Hardware Computer: BaseBoard Manufacturer:"AZW" BIOS Mode:"Legacy" BIOS Version/Date:"INSYDE Corp. CB1D_FV106 , 02/11/2021 12:00 AM" CD or DVD:"Not Available" Embedded Controller Version:"1.7" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz , GenuineIntel" Secure Boot State:"Off" SMBIOS Version:"3.0" Sound Card:"Intel(R) Display Audio" Sound Card:"Intel® Smart Sound Technology (Intel® SST)" Sound Card:"Digital Video Recorder" System Manufacturer:"AZW" System Model:"SEi" System SKU:"Type1Sku0" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"Not Available" - "Intel(R) Iris(R) Plus Graphics 655" 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) Plus Graphics 655" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Iris+Plus+Graphics+655" CoInstallers:"oem49.inf,iCFL_w10_DS,Internal,Intel(R) Iris(R) Plus Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"11/15/2022 04:00 PM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"31.0.101.2115" INF:"oem49.inf" INF Section:"iCFL_w10_DS" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\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_3EA5&SUBSYS_800C1E50&REV_01\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"59 Hz" Refresh Rate - Maximum:"60 Hz" Refresh Rate - Minimum:"23 Hz" Resolution:"1920 X 1080" Scan Mode:"Noninterlaced" Service Name:"igfx" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) Iris(R) Plus Graphics Family" - "Memory" Physical Memory (Available):"10.15 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.85 GB" - "BANK 2" Capacity:"16 GB" Channel:"ChannelB-DIMM0" Configured Clock Speed:"2400 MHz" Configured Voltage:"1200 millivolts" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Second position" Manufacturer:"859B" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"CT16G4SFS832A.C8FE" Serial Number:"E5FBCEDE" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"CB1D_FV106, INSYDE - 2" Caption:"Motherboard" - "Chipset":"I/O LPC Controller - 9D84 for Intel(R) 300 Series" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=I%2fO+LPC+Controller+++9D84+for++300+Series" Date:"11/01/2021 05:00 PM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"AZW" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"SEi" Serial Number:"CB1D34211C14S0334" Status:"OK" Version:"Type2 - Board Version" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Bluetooth Device (Personal Area Network)" Availability:"Running or Full Power" Caption:"Bluetooth Device (Personal Area Network)" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"bthpan.sys" Driver Date:"06/21/2006 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\bthpan.sys" Driver Provider:"Microsoft" Driver Version:"10.0.22000.653" Index:"0005" INF:"bthpan.inf" INF Section:"BthPan.Install" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/06/2023 06:49 PM" Location:"Not Available" MAC Address:"38:87:D5:B9:85:CE" Manufacturer:"Microsoft" Media Type: Net Connection ID:"Bluetooth Network Connection" NetCfgInstanceId:"{A48A602E-902F-4807-A2C0-6F198B2A1A0E}" Number of VLANs:"0" PNP Device ID:"BTH\MS_BTHPAN\6&B8E020F&0&2" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Bluetooth Device (Personal Area Network)" Service Name:"BthPan" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): Npcap Packet Driver (NPF): - "Intel(R) Dual Band Wireless-AC 7265 #2" Access Point:"e0:db:d1:c7:d2:44" Authentication:"WPA2-Personal" Availability:"Running or Full Power" - "Caption":"Intel(R) Dual Band Wireless-AC 7265 #2" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Dual+Band+Wireless+AC+7265+%232" Channel:"44" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Auto Connect" Default IP Gateway:"10.0.0.1" DHCP Enabled:"Yes" DHCP Lease Expires:"01/08/2023 06:49 PM" DHCP Lease Obtained:"01/06/2023 06:49 PM" DHCP Server:"10.0.0.1" Driver:"Netwtw04.sys" Driver Date:"08/02/2022 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\Netwtw04.sys" Driver Provider:"Intel" Driver Version:"19.51.42.2" Index:"0006" INF:"oem88.inf" INF Section:"Install_MPCIEX_GENM2_D_REV_59_7265_AC_2x2_HMC_WINT_64_AC" Install Date:"Not Available" Installed:"Yes" IP Address:"10.0.0.230" IP Subnet:"255.255.255.0" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/06/2023 06:49 PM" Location:"PCI bus 3, device 0, function 0" MAC Address:"38:87:D5:B9:85:CA" Manufacturer:"Intel Corporation" Media Type: Net Connection ID:"Wi-Fi 2" NetCfgInstanceId:"{9A35E583-F360-45F9-B223-360B0E7A9E06}" Network Name:"Pentire 5G" Network Type:"Infrastructure" Number of VLANs:"0" PNP Device ID:"PCI\VEN_8086&DEV_095A&SUBSYS_50108086&REV_59\3887D5FFFFB9E19600" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Dual Band Wireless-AC 7265" Profile:"Pentire 5G" Radio Type:"802.11ac" Receive Rate:"866.7 Mbps" Service Name:"Netwtw04" Signal Strength:"99%" 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): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: NordVPN LightWeight Firewall: Npcap Packet Driver (NPCAP): Npcap Packet Driver (NPF): QoS Packet Scheduler: - "Settings" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac Wireless Mode:"802.11ac (2)" 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)" - "NordLynx Tunnel" Availability:"Running or Full Power" Caption:"NordLynx Tunnel" CoInstallers:"Not Available" Default IP Gateway:"0.0.0.0" DHCP Enabled:"No" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"Not Available" Driver Date:"10/13/2021 12:00 AM" Driver Path:"Not Available" Driver Provider:"WireGuard LLC" Driver Version:"0.14.0.0" Index:"0017" INF:"oem44.inf" INF Section:"Wintun.Install" Install Date:"Not Available" Installed:"Yes" IP Address:"10.5.0.2;fe80::413b:ba6a:5eb:1c00" IP Subnet:"255.255.0.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/06/2023 06:49 PM" Location:"Not Available" MAC Address:"Not Available" Manufacturer:"WireGuard LLC" Media Type: Net Connection ID:"NordLynx" NetCfgInstanceId:"{9272E2BF-6BD5-1513-A95C-605FD4C46776}" Number of VLANs:"0" PNP Device ID:"SWD\WINTUN\{9272E2BF-6BD5-1513-A95C-605FD4C46776}" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Wintun Userspace Tunnel" Service Name:"wintun" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Not Available" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: Npcap Packet Driver (NPCAP): Npcap Packet Driver (NPF): - "Realtek PCIe GbE Family Controller" Availability:"Running or Full Power" Caption:"Realtek PCIe GbE Family Controller" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"rt68cx21x64.sys" Driver Date:"07/21/2022 12:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\rt68cx21x64.inf_amd64_12e5292d75bc9d96\rt68cx21x64.sys" Driver Provider:"Realtek" Driver Version:"1168.10.720.2022" Index:"0001" INF:"oem61.inf" INF Section:"RTL8168H.ndi.NT" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/06/2023 06:49 PM" Location:"PCI bus 1, device 0, function 0" MAC Address:"84:47:09:0C:57:F4" Manufacturer:"Realtek" Media Type: Net Connection ID:"Ethernet" NetCfgInstanceId:"{729A54F6-11B9-4F86-ABE9-5F9A1E678BFB}" Number of VLANs:"0" PNP Device ID:"PCI\VEN_10EC&DEV_8168&SUBSYS_012310EC&REV_15\01000000684CE00000" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: Yes" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Realtek PCIe GbE Family Controller" Service Name:"rt68cx21" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: NordVPN LightWeight Firewall: Npcap Packet Driver (NPCAP): Npcap Packet Driver (NPF): QoS Packet Scheduler: - "Settings" *EEE:Energy-Efficient Ethernet:"Enabled (1)" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Frame:"Disabled (1514)" *LsoV2IPv4:Large Send Offload v2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload v2 (IPv6):"Enabled (1)" *PMARPOffload:ARP Offload:"Enabled (1)" *PMNSOffload:NS Offload:"Enabled (1)" *PriorityVlanTag:Priority & VLAN:"Priority & VLAN Enabled (3)" *ReceiveBuffers:Receive Buffers:"512 (512)" *RscIPv4:Recv Segment Coalescing (IPv4):"Enabled (1)" *RscIPv6:Recv Segment Coalescing (IPv6):"Enabled (1)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"128 (128)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on pattern match:"Enabled (1)" AdvancedEEE:Advanced EEE:"Disabled (0)" EnableGreenEthernet:Green Ethernet:"Enabled (1)" GigaLite:Gigabit Lite:"Enabled (1)" PowerSavingMode:Power Saving Mode:"Enabled (1)" RegVlanid:VLAN ID:"0 (0)" S5WakeOnLan:Shutdown Wake-On-Lan:"Enabled (1)" WolShutdownLinkSpeed:WOL & Shutdown Link Speed:"10 Mbps First (0)" - "TAP-NordVPN Windows Adapter V9" Availability:"Running or Full Power" Caption:"TAP-NordVPN Windows Adapter V9" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"tapnordvpn.sys" Driver Date:"05/30/2018 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\tapnordvpn.sys" Driver Provider:"TAP-NordVPN Windows Provider V9" Driver Version:"9.0.0.23" Index:"0004" INF:"oem20.inf" INF Section:"tapnordvpn.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/06/2023 06:49 PM" Location:"Not Available" MAC Address:"00:FF:0E:E8:8D:17" Manufacturer:"TAP-NordVPN Windows Provider V9" Media Type: Net Connection ID:"Ethernet 3" NetCfgInstanceId:"{0EE88D17-9ACB-488B-815C-1F6EBA728EC9}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0002" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"TAP-NordVPN Windows Adapter V9" Service Name:"tapnordvpn" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: NordVPN LightWeight Firewall: Npcap Packet Driver (NPCAP): Npcap Packet Driver (NPF): QoS Packet Scheduler: - "Settings" AllowNonAdmin:Non-Admin Access:"Allowed (1)" MediaStatus:Media Status:"Application Controlled (0)" MTU:MTU:"1500 (1500)" - "TAP-Windows Adapter V9" Availability:"Running or Full Power" Caption:"TAP-Windows Adapter V9" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"tap0901.sys" Driver Date:"09/27/2019 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\tap0901.sys" Driver Provider:"TAP-Windows Provider V9" Driver Version:"9.24.2.601" Index:"0003" INF:"oem21.inf" INF Section:"tap0901.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"01/06/2023 06:49 PM" Location:"Not Available" MAC Address:"00:FF:D7:B1:D9:50" Manufacturer:"TAP-Windows Provider V9" Media Type: Net Connection ID:"Local Area Connection" NetCfgInstanceId:"{D7B1D950-822E-47EE-BEA9-90C7CE00AC69}" Number of VLANs:"0" PNP Device ID:"ROOT\NET\0001" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"TAP-Windows Adapter V9" Service Name:"tap0901" Status:"Enabled" Team Name:"Not in a team" Temperature: Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: NordVPN LightWeight Firewall: Npcap Packet Driver (NPCAP): Npcap Packet Driver (NPF): QoS Packet Scheduler: - "Settings" AllowNonAdmin:Non-Admin Access:"Allowed (1)" MediaStatus:Media Status:"Application Controlled (0)" MTU:MTU:"1500 (1500)" - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Locale:"United States" 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):"10.15 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.85 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.22000 Build 22000" Virtual Memory (Available):"11.93 GB" Virtual Memory (Total):"18.22 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [31/05/2022]" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [22/05/2022]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [22/05/2022]" KB2467173:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [31/05/2022]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871:"Microsoft .NET Framework 4 Client Profile [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 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB5012170:"Security Update [8/9/2022]" KB5019385:"Update [11/18/2022]" KB5020875:"Update [12/15/2022]" KB5021234:"Security Update [12/15/2022]" KB982573:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [31/05/2022]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [22/05/2022]" SP1:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [Not Available]" SP1:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [Not Available]" - "Processor" - "Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 142 Stepping 10" - "Chipset Name":"Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i3+8109U+CPU+" CPU Speed:"3 GHz" Current Voltage:"9. volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.22000.1219" 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:"2 x 128 KB" Level 2 Cache:"2 x 512 KB" Level 3 Cache:"4 MB" Load:"16%" Manufacturer:"GenuineIntel" Model:"142" Name:"Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz" Number of Cores:"2" Number of Cores Enabled:"2" Number of Logical Processors:"4" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000806EA" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"10" Version:"Not Available" - "Storage" - "KINGSTON SNVS500G" Capablities:"Random Access, Supports Writing" Caption:"KINGSTON SNVS500G" Cylinder - Total:"60801" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.22000.832" Error Code:"Device is working properly" Firmware Revision:"S8H40104" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"KINGSTON SNVS500G" Name:"\\.\PHYSICALDRIVE0" Partitions:"4" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_KINGSTON_SNVS500\5&CE5FAA1&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"976768065" Serial Number:"0000_0000_0000_0000_0026_B738_13CE_D985." Size:"465.76 GB" Size – Available:"263.21 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"15504255" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Drive C" Serial Number:"DE9A36C8" Size:"247.39 GB" Size – Available:"97.22 GB" Status:"Not Available" Volume Dirty:"No" - "D:" Availability:"Not Available" Caption:"D:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Drive D" Serial Number:"10F7134C" Size:"216.42 GB" Size – Available:"165.99 GB" Status:"Not Available" Volume Dirty:"No" - "Samsung Portable SSD T5 SCSI Disk Device" Capablities:"Random Access, Supports Writing" Caption:"Samsung Portable SSD T5 SCSI Disk Device" Cylinder - Total:"121601" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.22000.832" Error Code:"Device is working properly" Firmware Revision:"0" Heads - Total:"255" Index:"1" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"Samsung Portable SSD T5 SCSI Disk Device" Name:"\\.\PHYSICALDRIVE1" Partitions:"1" Physical Sector Size:"512" PNP Device ID:"SCSI\DISK&VEN_SAMSUNG&PROD_PORTABLE_SSD_T5\6&B685553&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"2" Sectors - Per Track:"63" Sectors - Total:"1953520065" Serial Number:"0FA298654321" Size:"931.51 GB" Size – Available:"82.03 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"31008255" - "G:" Availability:"Not Available" Caption:"G:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"exFAT" Name:"Samsung_T5" Serial Number:"3C112986" Size:"931.48 GB" Size – Available:"82.03 GB" Status:"Not Available" Volume Dirty:"No" - "WD Ext HDD 1021 USB Device" Capablities:"Random Access, Supports Writing" Caption:"WD Ext HDD 1021 USB Device" Cylinder - Total:"243201" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.22000.832" Error Code:"Device is working properly" Firmware Revision:"2002" Heads - Total:"255" Index:"2" INF:"disk.inf" Install Date:"Not Available" Interface Type:"USB" Manufacturer:"(Standard disk drives)" Model:"WD Ext HDD 1021 USB Device" Name:"\\.\PHYSICALDRIVE2" Partitions:"1" Physical Sector Size:"512" PNP Device ID:"USBSTOR\DISK&VEN_WD&PROD_EXT_HDD_1021&REV_2002\574D415A4130343933313835&0" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" Sectors - Per Track:"63" Sectors - Total:"3907024065" Serial Number:"WMAZA0493185" Size:"1.82 TB" Size – Available:"416.33 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"62016255" - "F:" Availability:"Not Available" Caption:"F:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Elements" Serial Number:"66410644" Size:"1863.01 GB" Size – Available:"416.33 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:58:47 PM on ‎2022-‎12-‎29 was unexpected. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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 IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:22:30 PM on ‎2022-‎12-‎22 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:05:16 PM on ‎2022-‎12-‎16 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The IvacyService service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The Audiosrv service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Audiosrv service was unable to log on as NT AUTHORITY\LocalService 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 system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:31:50 PM on ‎2022-‎12-‎13 was unexpected. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (70:b3:d5:f0:d1:94) failed. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 6:44:42 PM on ‎2022-‎12-‎05 was unexpected. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9272E2BF-6BD5-1513-A95C-605FD4C46776} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9272E2BF-6BD5-1513-A95C-605FD4C46776} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:53:14 PM on ‎2022-‎11-‎27 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8A11A6C8-9017-4E7E-8C12-499F5A22F1B4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8A11A6C8-9017-4E7E-8C12-499F5A22F1B4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8A11A6C8-9017-4E7E-8C12-499F5A22F1B4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8A11A6C8-9017-4E7E-8C12-499F5A22F1B4} 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_{8A11A6C8-9017-4E7E-8C12-499F5A22F1B4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8A11A6C8-9017-4E7E-8C12-499F5A22F1B4} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DEF324FA-1DAC-4469-8A64-305860429554} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DEF324FA-1DAC-4469-8A64-305860429554} 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_{DEF324FA-1DAC-4469-8A64-305860429554} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DEF324FA-1DAC-4469-8A64-305860429554} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DEF324FA-1DAC-4469-8A64-305860429554} 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_{DEF324FA-1DAC-4469-8A64-305860429554} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACEE6261-C3B4-4A22-A610-3CC90514E958} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACEE6261-C3B4-4A22-A610-3CC90514E958} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACEE6261-C3B4-4A22-A610-3CC90514E958} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACEE6261-C3B4-4A22-A610-3CC90514E958} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACEE6261-C3B4-4A22-A610-3CC90514E958} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7C5FE3A5-F25B-44A3-B506-85CD6E89CDDE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7C5FE3A5-F25B-44A3-B506-85CD6E89CDDE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7C5FE3A5-F25B-44A3-B506-85CD6E89CDDE} 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_{7C5FE3A5-F25B-44A3-B506-85CD6E89CDDE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7C5FE3A5-F25B-44A3-B506-85CD6E89CDDE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{967BFC9D-9D4B-489A-883E-2A19922D9155} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{967BFC9D-9D4B-489A-883E-2A19922D9155} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{967BFC9D-9D4B-489A-883E-2A19922D9155} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{967BFC9D-9D4B-489A-883E-2A19922D9155} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{967BFC9D-9D4B-489A-883E-2A19922D9155} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5AA42258-6BA9-4924-B98E-225FE5084FE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5AA42258-6BA9-4924-B98E-225FE5084FE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5AA42258-6BA9-4924-B98E-225FE5084FE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5AA42258-6BA9-4924-B98E-225FE5084FE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5AA42258-6BA9-4924-B98E-225FE5084FE4} 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_{5AA42258-6BA9-4924-B98E-225FE5084FE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B8C3DA7-EFCB-4B6A-97C8-2CB1662F858A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B8C3DA7-EFCB-4B6A-97C8-2CB1662F858A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B8C3DA7-EFCB-4B6A-97C8-2CB1662F858A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B8C3DA7-EFCB-4B6A-97C8-2CB1662F858A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B8C3DA7-EFCB-4B6A-97C8-2CB1662F858A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B8C3DA7-EFCB-4B6A-97C8-2CB1662F858A} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{4939AFF6-9C3D-484F-99EB-FE82FD995B0D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{4939AFF6-9C3D-484F-99EB-FE82FD995B0D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{4939AFF6-9C3D-484F-99EB-FE82FD995B0D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{4939AFF6-9C3D-484F-99EB-FE82FD995B0D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{4939AFF6-9C3D-484F-99EB-FE82FD995B0D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6B0D0E01-B886-485D-9FEF-76F0B74F864A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6B0D0E01-B886-485D-9FEF-76F0B74F864A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6B0D0E01-B886-485D-9FEF-76F0B74F864A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6B0D0E01-B886-485D-9FEF-76F0B74F864A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6B0D0E01-B886-485D-9FEF-76F0B74F864A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6B0D0E01-B886-485D-9FEF-76F0B74F864A} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{C9C97244-FB2E-4D7E-AC09-D6D30BB15225} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{C9C97244-FB2E-4D7E-AC09-D6D30BB15225} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{C9C97244-FB2E-4D7E-AC09-D6D30BB15225} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{C9C97244-FB2E-4D7E-AC09-D6D30BB15225} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{C9C97244-FB2E-4D7E-AC09-D6D30BB15225} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{C9C97244-FB2E-4D7E-AC09-D6D30BB15225} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{961663C6-E0B4-4E24-9D6E-8F6C6F9FC214} 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_{961663C6-E0B4-4E24-9D6E-8F6C6F9FC214} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{961663C6-E0B4-4E24-9D6E-8F6C6F9FC214} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{961663C6-E0B4-4E24-9D6E-8F6C6F9FC214} 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_{961663C6-E0B4-4E24-9D6E-8F6C6F9FC214} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{961663C6-E0B4-4E24-9D6E-8F6C6F9FC214} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A15368DF-36D5-442E-B291-994AAA6C53D9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A15368DF-36D5-442E-B291-994AAA6C53D9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A15368DF-36D5-442E-B291-994AAA6C53D9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A15368DF-36D5-442E-B291-994AAA6C53D9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A15368DF-36D5-442E-B291-994AAA6C53D9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{975B4D30-3862-4A89-A352-7C42FDB4156B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{975B4D30-3862-4A89-A352-7C42FDB4156B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{975B4D30-3862-4A89-A352-7C42FDB4156B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{975B4D30-3862-4A89-A352-7C42FDB4156B} 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_{975B4D30-3862-4A89-A352-7C42FDB4156B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69DCEAE6-9820-455A-9BFA-4419EC8659C8} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69DCEAE6-9820-455A-9BFA-4419EC8659C8} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69DCEAE6-9820-455A-9BFA-4419EC8659C8} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69DCEAE6-9820-455A-9BFA-4419EC8659C8} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69DCEAE6-9820-455A-9BFA-4419EC8659C8} 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_{69DCEAE6-9820-455A-9BFA-4419EC8659C8} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{35753446-B9A7-48AB-A3CC-0B7821EF57BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{35753446-B9A7-48AB-A3CC-0B7821EF57BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{35753446-B9A7-48AB-A3CC-0B7821EF57BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{35753446-B9A7-48AB-A3CC-0B7821EF57BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{35753446-B9A7-48AB-A3CC-0B7821EF57BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{35753446-B9A7-48AB-A3CC-0B7821EF57BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{539739DE-D79D-430C-A856-BD8A06A84C92} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{539739DE-D79D-430C-A856-BD8A06A84C92} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{539739DE-D79D-430C-A856-BD8A06A84C92} 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_{539739DE-D79D-430C-A856-BD8A06A84C92} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{539739DE-D79D-430C-A856-BD8A06A84C92} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{86B2B558-37E8-4706-83D1-5FEE956CEABA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{86B2B558-37E8-4706-83D1-5FEE956CEABA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{86B2B558-37E8-4706-83D1-5FEE956CEABA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{86B2B558-37E8-4706-83D1-5FEE956CEABA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{86B2B558-37E8-4706-83D1-5FEE956CEABA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F32058E4-DF88-4DD9-A5C3-F4EAC58B569B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F32058E4-DF88-4DD9-A5C3-F4EAC58B569B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F32058E4-DF88-4DD9-A5C3-F4EAC58B569B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F32058E4-DF88-4DD9-A5C3-F4EAC58B569B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F32058E4-DF88-4DD9-A5C3-F4EAC58B569B} 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_{F32058E4-DF88-4DD9-A5C3-F4EAC58B569B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D0FD9037-5ABA-4A52-B847-B3248307D51F} 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_{D0FD9037-5ABA-4A52-B847-B3248307D51F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D0FD9037-5ABA-4A52-B847-B3248307D51F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D0FD9037-5ABA-4A52-B847-B3248307D51F} 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_{D0FD9037-5ABA-4A52-B847-B3248307D51F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B7F124F2-963D-4E8C-B2AC-DF300754027E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B7F124F2-963D-4E8C-B2AC-DF300754027E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B7F124F2-963D-4E8C-B2AC-DF300754027E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B7F124F2-963D-4E8C-B2AC-DF300754027E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B7F124F2-963D-4E8C-B2AC-DF300754027E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B7F124F2-963D-4E8C-B2AC-DF300754027E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{4A916887-8D6F-43EA-A54D-236B2086439E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{4A916887-8D6F-43EA-A54D-236B2086439E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{4A916887-8D6F-43EA-A54D-236B2086439E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{4A916887-8D6F-43EA-A54D-236B2086439E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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 {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:56:05 PM on ‎2022-‎11-‎22 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F1F3362B-882D-4C3D-8414-F2F1E6513DE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F1F3362B-882D-4C3D-8414-F2F1E6513DE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F1F3362B-882D-4C3D-8414-F2F1E6513DE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F1F3362B-882D-4C3D-8414-F2F1E6513DE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F1F3362B-882D-4C3D-8414-F2F1E6513DE4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2DBA0A4D-6A09-4B11-A9FF-2FD2028BB55A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2DBA0A4D-6A09-4B11-A9FF-2FD2028BB55A} 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_{2DBA0A4D-6A09-4B11-A9FF-2FD2028BB55A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2DBA0A4D-6A09-4B11-A9FF-2FD2028BB55A} 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_{2DBA0A4D-6A09-4B11-A9FF-2FD2028BB55A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2DBA0A4D-6A09-4B11-A9FF-2FD2028BB55A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{75850223-1560-4266-A94E-24E2E9689061} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{75850223-1560-4266-A94E-24E2E9689061} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{75850223-1560-4266-A94E-24E2E9689061} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{75850223-1560-4266-A94E-24E2E9689061} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{75850223-1560-4266-A94E-24E2E9689061} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{75850223-1560-4266-A94E-24E2E9689061} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Search service terminated with the following error: The system cannot find the drive specified. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9EB29283-03F8-495B-B2EB-A8236DE8D7BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9EB29283-03F8-495B-B2EB-A8236DE8D7BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9EB29283-03F8-495B-B2EB-A8236DE8D7BA} 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_{9EB29283-03F8-495B-B2EB-A8236DE8D7BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9EB29283-03F8-495B-B2EB-A8236DE8D7BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9EB29283-03F8-495B-B2EB-A8236DE8D7BA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E451316-3CEC-4D5B-95EE-2D255FA5C482} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E451316-3CEC-4D5B-95EE-2D255FA5C482} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E451316-3CEC-4D5B-95EE-2D255FA5C482} 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_{6E451316-3CEC-4D5B-95EE-2D255FA5C482} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E451316-3CEC-4D5B-95EE-2D255FA5C482} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{766CB3DD-6D4C-41EE-9293-E2DBB95C5505} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{766CB3DD-6D4C-41EE-9293-E2DBB95C5505} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{766CB3DD-6D4C-41EE-9293-E2DBB95C5505} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{766CB3DD-6D4C-41EE-9293-E2DBB95C5505} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{766CB3DD-6D4C-41EE-9293-E2DBB95C5505} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{196256B0-F588-458D-AA44-FCB6DB24741A} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{196256B0-F588-458D-AA44-FCB6DB24741A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{196256B0-F588-458D-AA44-FCB6DB24741A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{196256B0-F588-458D-AA44-FCB6DB24741A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{196256B0-F588-458D-AA44-FCB6DB24741A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{196256B0-F588-458D-AA44-FCB6DB24741A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{196256B0-F588-458D-AA44-FCB6DB24741A} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{61CC0166-42E1-4B73-BAC2-E8B0F80CC1A6} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{61CC0166-42E1-4B73-BAC2-E8B0F80CC1A6} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{61CC0166-42E1-4B73-BAC2-E8B0F80CC1A6} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{61CC0166-42E1-4B73-BAC2-E8B0F80CC1A6} 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_{61CC0166-42E1-4B73-BAC2-E8B0F80CC1A6} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{339C6CD3-2938-463C-986C-1B7F49BEF00F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{339C6CD3-2938-463C-986C-1B7F49BEF00F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{339C6CD3-2938-463C-986C-1B7F49BEF00F} 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_{339C6CD3-2938-463C-986C-1B7F49BEF00F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{339C6CD3-2938-463C-986C-1B7F49BEF00F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{339C6CD3-2938-463C-986C-1B7F49BEF00F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EE383022-DFDE-4807-8BC5-7FED7B7768FF} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EE383022-DFDE-4807-8BC5-7FED7B7768FF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EE383022-DFDE-4807-8BC5-7FED7B7768FF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EE383022-DFDE-4807-8BC5-7FED7B7768FF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EE383022-DFDE-4807-8BC5-7FED7B7768FF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:59:29 PM on ‎2022-‎11-‎19 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7DFE8330-1D89-4D07-8379-C0F3398302C4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7DFE8330-1D89-4D07-8379-C0F3398302C4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7DFE8330-1D89-4D07-8379-C0F3398302C4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7DFE8330-1D89-4D07-8379-C0F3398302C4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7DFE8330-1D89-4D07-8379-C0F3398302C4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7DFE8330-1D89-4D07-8379-C0F3398302C4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5C88CB40-7CC6-4FA0-83EE-41AE159C5A26} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5C88CB40-7CC6-4FA0-83EE-41AE159C5A26} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{5C88CB40-7CC6-4FA0-83EE-41AE159C5A26} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5C88CB40-7CC6-4FA0-83EE-41AE159C5A26} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5C88CB40-7CC6-4FA0-83EE-41AE159C5A26} 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_{5C88CB40-7CC6-4FA0-83EE-41AE159C5A26} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{0ACE4C57-6E1A-4CFD-8A4D-6510968256ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{0ACE4C57-6E1A-4CFD-8A4D-6510968256ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{0ACE4C57-6E1A-4CFD-8A4D-6510968256ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{0ACE4C57-6E1A-4CFD-8A4D-6510968256ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{0ACE4C57-6E1A-4CFD-8A4D-6510968256ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{0ACE4C57-6E1A-4CFD-8A4D-6510968256ED} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{042FE4A9-C0EF-4FF5-B24D-50370C55C564} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{042FE4A9-C0EF-4FF5-B24D-50370C55C564} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{042FE4A9-C0EF-4FF5-B24D-50370C55C564} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{042FE4A9-C0EF-4FF5-B24D-50370C55C564} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{042FE4A9-C0EF-4FF5-B24D-50370C55C564} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{BA56A4A4-4633-4BB1-ACDF-B0057BD9741D} 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_{BA56A4A4-4633-4BB1-ACDF-B0057BD9741D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{BA56A4A4-4633-4BB1-ACDF-B0057BD9741D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{BA56A4A4-4633-4BB1-ACDF-B0057BD9741D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{BA56A4A4-4633-4BB1-ACDF-B0057BD9741D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:28:32 PM on ‎2022-‎11-‎18 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3BED7683-6DD8-448A-8B82-600AEBC78235} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3BED7683-6DD8-448A-8B82-600AEBC78235} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{3BED7683-6DD8-448A-8B82-600AEBC78235} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3BED7683-6DD8-448A-8B82-600AEBC78235} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3BED7683-6DD8-448A-8B82-600AEBC78235} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{6FF41B6E-75A7-41F5-A8EB-D4E87B1F9519} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6FF41B6E-75A7-41F5-A8EB-D4E87B1F9519} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6FF41B6E-75A7-41F5-A8EB-D4E87B1F9519} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6FF41B6E-75A7-41F5-A8EB-D4E87B1F9519} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6FF41B6E-75A7-41F5-A8EB-D4E87B1F9519} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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 IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{664376A5-76B7-43E6-AE48-977CA2EA5060} 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_{664376A5-76B7-43E6-AE48-977CA2EA5060} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{664376A5-76B7-43E6-AE48-977CA2EA5060} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{664376A5-76B7-43E6-AE48-977CA2EA5060} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{664376A5-76B7-43E6-AE48-977CA2EA5060} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69577CDB-E789-47F6-A57F-45A1818521FE} 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_{69577CDB-E789-47F6-A57F-45A1818521FE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69577CDB-E789-47F6-A57F-45A1818521FE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69577CDB-E789-47F6-A57F-45A1818521FE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69577CDB-E789-47F6-A57F-45A1818521FE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69577CDB-E789-47F6-A57F-45A1818521FE} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D460D073-3B82-4FFA-99D5-7DA334EBB6BC} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D460D073-3B82-4FFA-99D5-7DA334EBB6BC} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D460D073-3B82-4FFA-99D5-7DA334EBB6BC} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D460D073-3B82-4FFA-99D5-7DA334EBB6BC} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D460D073-3B82-4FFA-99D5-7DA334EBB6BC} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D460D073-3B82-4FFA-99D5-7DA334EBB6BC} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9576F4F2-E539-4619-BC91-19E6EBBFC874} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9576F4F2-E539-4619-BC91-19E6EBBFC874} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9576F4F2-E539-4619-BC91-19E6EBBFC874} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9576F4F2-E539-4619-BC91-19E6EBBFC874} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9576F4F2-E539-4619-BC91-19E6EBBFC874} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9576F4F2-E539-4619-BC91-19E6EBBFC874} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{80A96DDB-E40A-4964-B5A2-8B26AE6996A1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{80A96DDB-E40A-4964-B5A2-8B26AE6996A1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{80A96DDB-E40A-4964-B5A2-8B26AE6996A1} 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_{80A96DDB-E40A-4964-B5A2-8B26AE6996A1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{80A96DDB-E40A-4964-B5A2-8B26AE6996A1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{80A96DDB-E40A-4964-B5A2-8B26AE6996A1} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{B22B81E9-D3DF-4CE2-AD1B-9505B236980C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B22B81E9-D3DF-4CE2-AD1B-9505B236980C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B22B81E9-D3DF-4CE2-AD1B-9505B236980C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B22B81E9-D3DF-4CE2-AD1B-9505B236980C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B22B81E9-D3DF-4CE2-AD1B-9505B236980C} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{15B88AF1-E077-43A2-8CA8-D08176E9C20D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{15B88AF1-E077-43A2-8CA8-D08176E9C20D} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{15B88AF1-E077-43A2-8CA8-D08176E9C20D} 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_{15B88AF1-E077-43A2-8CA8-D08176E9C20D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{15B88AF1-E077-43A2-8CA8-D08176E9C20D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{15B88AF1-E077-43A2-8CA8-D08176E9C20D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9F493680-3ECD-4425-AB45-FA6A8645BA9D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9F493680-3ECD-4425-AB45-FA6A8645BA9D} 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_{9F493680-3ECD-4425-AB45-FA6A8645BA9D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9F493680-3ECD-4425-AB45-FA6A8645BA9D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9F493680-3ECD-4425-AB45-FA6A8645BA9D} 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_{9F493680-3ECD-4425-AB45-FA6A8645BA9D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D06D5B5C-7CA0-4B68-8A63-87E7323A908E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D06D5B5C-7CA0-4B68-8A63-87E7323A908E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D06D5B5C-7CA0-4B68-8A63-87E7323A908E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D06D5B5C-7CA0-4B68-8A63-87E7323A908E} 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_{D06D5B5C-7CA0-4B68-8A63-87E7323A908E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D06D5B5C-7CA0-4B68-8A63-87E7323A908E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{59C2AD64-6D4A-4E6A-BD7C-D4BBBB9765FE} 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_{59C2AD64-6D4A-4E6A-BD7C-D4BBBB9765FE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{59C2AD64-6D4A-4E6A-BD7C-D4BBBB9765FE} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{59C2AD64-6D4A-4E6A-BD7C-D4BBBB9765FE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{59C2AD64-6D4A-4E6A-BD7C-D4BBBB9765FE} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{58294BE3-D3ED-4E15-8666-F5B09099365A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{58294BE3-D3ED-4E15-8666-F5B09099365A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{58294BE3-D3ED-4E15-8666-F5B09099365A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{58294BE3-D3ED-4E15-8666-F5B09099365A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{58294BE3-D3ED-4E15-8666-F5B09099365A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{58294BE3-D3ED-4E15-8666-F5B09099365A} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DBEB616E-0277-4E0D-97E5-E2D4729C9E7D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DBEB616E-0277-4E0D-97E5-E2D4729C9E7D} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DBEB616E-0277-4E0D-97E5-E2D4729C9E7D} 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_{DBEB616E-0277-4E0D-97E5-E2D4729C9E7D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{22D89107-B442-4504-9D3E-50E8EDDE3813} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{22D89107-B442-4504-9D3E-50E8EDDE3813} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{22D89107-B442-4504-9D3E-50E8EDDE3813} 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_{22D89107-B442-4504-9D3E-50E8EDDE3813} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{22D89107-B442-4504-9D3E-50E8EDDE3813} 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_{22D89107-B442-4504-9D3E-50E8EDDE3813} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{39378BDE-63B1-411C-88C7-7FD65B02FC71} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{39378BDE-63B1-411C-88C7-7FD65B02FC71} 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_{39378BDE-63B1-411C-88C7-7FD65B02FC71} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{39378BDE-63B1-411C-88C7-7FD65B02FC71} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{39378BDE-63B1-411C-88C7-7FD65B02FC71} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{A1934FF7-99E9-402A-8100-CEFBBBC8C52F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A1934FF7-99E9-402A-8100-CEFBBBC8C52F} 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_{A1934FF7-99E9-402A-8100-CEFBBBC8C52F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A1934FF7-99E9-402A-8100-CEFBBBC8C52F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A1934FF7-99E9-402A-8100-CEFBBBC8C52F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A1934FF7-99E9-402A-8100-CEFBBBC8C52F} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{326F0C18-902A-429A-94E7-C412E6CA5F7A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{326F0C18-902A-429A-94E7-C412E6CA5F7A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{326F0C18-902A-429A-94E7-C412E6CA5F7A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{326F0C18-902A-429A-94E7-C412E6CA5F7A} 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_{326F0C18-902A-429A-94E7-C412E6CA5F7A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{326F0C18-902A-429A-94E7-C412E6CA5F7A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{92FC8563-D49E-4AD6-AA9B-71C48F1D8C69} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{92FC8563-D49E-4AD6-AA9B-71C48F1D8C69} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{92FC8563-D49E-4AD6-AA9B-71C48F1D8C69} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{92FC8563-D49E-4AD6-AA9B-71C48F1D8C69} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{92FC8563-D49E-4AD6-AA9B-71C48F1D8C69} 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_{92FC8563-D49E-4AD6-AA9B-71C48F1D8C69} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5750B1BA-0BF8-442D-9C31-DD06594F4ED3} 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_{5750B1BA-0BF8-442D-9C31-DD06594F4ED3} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5750B1BA-0BF8-442D-9C31-DD06594F4ED3} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5750B1BA-0BF8-442D-9C31-DD06594F4ED3} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5750B1BA-0BF8-442D-9C31-DD06594F4ED3} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 7:13:21 PM on ‎2022-‎11-‎11 was unexpected. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{FE795ADC-8EE8-4D26-8C65-83D4D7FDE4D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{FE795ADC-8EE8-4D26-8C65-83D4D7FDE4D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{FE795ADC-8EE8-4D26-8C65-83D4D7FDE4D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{FE795ADC-8EE8-4D26-8C65-83D4D7FDE4D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{FE795ADC-8EE8-4D26-8C65-83D4D7FDE4D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{21B9B8F6-5192-4824-903D-FCC713118196} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{21B9B8F6-5192-4824-903D-FCC713118196} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{21B9B8F6-5192-4824-903D-FCC713118196} 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_{21B9B8F6-5192-4824-903D-FCC713118196} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{21B9B8F6-5192-4824-903D-FCC713118196} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E5463A5-42BB-426D-A74A-361141252CEF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E5463A5-42BB-426D-A74A-361141252CEF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E5463A5-42BB-426D-A74A-361141252CEF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E5463A5-42BB-426D-A74A-361141252CEF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E5463A5-42BB-426D-A74A-361141252CEF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{6E5463A5-42BB-426D-A74A-361141252CEF} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{48E1BFBA-D0C1-4083-8B6E-968C22B41D0B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{48E1BFBA-D0C1-4083-8B6E-968C22B41D0B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{48E1BFBA-D0C1-4083-8B6E-968C22B41D0B} 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_{48E1BFBA-D0C1-4083-8B6E-968C22B41D0B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{48E1BFBA-D0C1-4083-8B6E-968C22B41D0B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{48E1BFBA-D0C1-4083-8B6E-968C22B41D0B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F13F2B1A-BEA5-4924-A146-3F105CD0FF40} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F13F2B1A-BEA5-4924-A146-3F105CD0FF40} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F13F2B1A-BEA5-4924-A146-3F105CD0FF40} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F13F2B1A-BEA5-4924-A146-3F105CD0FF40} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F13F2B1A-BEA5-4924-A146-3F105CD0FF40} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A2620D31-D94A-4CE8-BDF2-BE998CF82345} 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_{A2620D31-D94A-4CE8-BDF2-BE998CF82345} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A2620D31-D94A-4CE8-BDF2-BE998CF82345} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A2620D31-D94A-4CE8-BDF2-BE998CF82345} 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_{A2620D31-D94A-4CE8-BDF2-BE998CF82345} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AD0F5EEB-12E5-4CC2-A6E5-E7968F973489} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AD0F5EEB-12E5-4CC2-A6E5-E7968F973489} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AD0F5EEB-12E5-4CC2-A6E5-E7968F973489} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AD0F5EEB-12E5-4CC2-A6E5-E7968F973489} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AD0F5EEB-12E5-4CC2-A6E5-E7968F973489} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69B59B67-84B8-4064-92CF-2B9596911FF4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69B59B67-84B8-4064-92CF-2B9596911FF4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69B59B67-84B8-4064-92CF-2B9596911FF4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69B59B67-84B8-4064-92CF-2B9596911FF4} 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_{69B59B67-84B8-4064-92CF-2B9596911FF4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{69B59B67-84B8-4064-92CF-2B9596911FF4} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EA2E006F-C55D-4F95-B3CB-3368A9B2BF2B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EA2E006F-C55D-4F95-B3CB-3368A9B2BF2B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EA2E006F-C55D-4F95-B3CB-3368A9B2BF2B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{EA2E006F-C55D-4F95-B3CB-3368A9B2BF2B} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{33D2FA97-792E-40D3-94DE-E196BCC9AEEA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{33D2FA97-792E-40D3-94DE-E196BCC9AEEA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{33D2FA97-792E-40D3-94DE-E196BCC9AEEA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{33D2FA97-792E-40D3-94DE-E196BCC9AEEA} 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_{33D2FA97-792E-40D3-94DE-E196BCC9AEEA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7CFC08C6-B341-4455-ADBB-4BDB1A086DC2} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7CFC08C6-B341-4455-ADBB-4BDB1A086DC2} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7CFC08C6-B341-4455-ADBB-4BDB1A086DC2} 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_{7CFC08C6-B341-4455-ADBB-4BDB1A086DC2} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7CFC08C6-B341-4455-ADBB-4BDB1A086DC2} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D961922D-3C04-44FE-ACE3-2231EBCDF72B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D961922D-3C04-44FE-ACE3-2231EBCDF72B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D961922D-3C04-44FE-ACE3-2231EBCDF72B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D961922D-3C04-44FE-ACE3-2231EBCDF72B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E1E352AB-5DBC-491B-A87F-1829AAB8318C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E1E352AB-5DBC-491B-A87F-1829AAB8318C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E1E352AB-5DBC-491B-A87F-1829AAB8318C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E1E352AB-5DBC-491B-A87F-1829AAB8318C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E1E352AB-5DBC-491B-A87F-1829AAB8318C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACB2FA63-5ED1-4206-B369-FA86A5039F36} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACB2FA63-5ED1-4206-B369-FA86A5039F36} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACB2FA63-5ED1-4206-B369-FA86A5039F36} 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_{ACB2FA63-5ED1-4206-B369-FA86A5039F36} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACB2FA63-5ED1-4206-B369-FA86A5039F36} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{ACB2FA63-5ED1-4206-B369-FA86A5039F36} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{FCD00455-03E3-4A6C-B188-74F51A7319ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{FCD00455-03E3-4A6C-B188-74F51A7319ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{FCD00455-03E3-4A6C-B188-74F51A7319ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{FCD00455-03E3-4A6C-B188-74F51A7319ED} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9E2751F9-CFC9-437A-A5F9-2F90F60C252B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9E2751F9-CFC9-437A-A5F9-2F90F60C252B} 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_{9E2751F9-CFC9-437A-A5F9-2F90F60C252B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9E2751F9-CFC9-437A-A5F9-2F90F60C252B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9E2751F9-CFC9-437A-A5F9-2F90F60C252B} 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_{9E2751F9-CFC9-437A-A5F9-2F90F60C252B} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{CEDE2F53-E091-4B3F-BFAF-655C0994DE20} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{CEDE2F53-E091-4B3F-BFAF-655C0994DE20} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{CEDE2F53-E091-4B3F-BFAF-655C0994DE20} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{CEDE2F53-E091-4B3F-BFAF-655C0994DE20} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{CEDE2F53-E091-4B3F-BFAF-655C0994DE20} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{CEDE2F53-E091-4B3F-BFAF-655C0994DE20} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{227261CA-CD9C-49DF-8A52-348C88728666} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{227261CA-CD9C-49DF-8A52-348C88728666} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{227261CA-CD9C-49DF-8A52-348C88728666} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{227261CA-CD9C-49DF-8A52-348C88728666} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{227261CA-CD9C-49DF-8A52-348C88728666} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{227261CA-CD9C-49DF-8A52-348C88728666} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F316ACF-5965-46C7-83EB-8ED1EAA7F6BF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F316ACF-5965-46C7-83EB-8ED1EAA7F6BF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F316ACF-5965-46C7-83EB-8ED1EAA7F6BF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F316ACF-5965-46C7-83EB-8ED1EAA7F6BF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F316ACF-5965-46C7-83EB-8ED1EAA7F6BF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F316ACF-5965-46C7-83EB-8ED1EAA7F6BF} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:02:41 PM on ‎2022-‎11-‎02 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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 {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 24 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 23 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 22 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 21 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 20 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 19 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 18 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 17 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 16 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 15 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 14 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 13 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 12 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 11 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 10 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 9 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 8 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 7 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 6 time(s). ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 4 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 3 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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 WSearch service. ------------------------------------------------------------------- Encrypted volume check: Volume information on G: cannot be read. ------------------------------------------------------------------- Encrypted volume check: Volume information on G: cannot be read. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:42:58 PM on ‎2022-‎10-‎12 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{7A43DD40-97CB-42B3-B1FC-B6197CAC271A} 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_{7A43DD40-97CB-42B3-B1FC-B6197CAC271A} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Search service terminated with the following error: The system cannot find the drive specified. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:04:51 PM on ‎2022-‎10-‎05 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:12:15 PM on ‎2022-‎10-‎04 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:51:41 PM on ‎2022-‎10-‎02 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:13:54 PM on ‎2022-‎09-‎27 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The previous system shutdown at 9:45:20 PM on ‎2022-‎09-‎26 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C00B000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C00A000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:12:22 PM on ‎2022-‎09-‎23 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The previous system shutdown at 12:35:02 PM on ‎2022-‎09-‎17 was unexpected. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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 IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Audiosrv service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Audiosrv service was unable to log on as NT AUTHORITY\LocalService 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 SysMain service terminated with the following error: The authentication service is unknown. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The previous system shutdown at 10:03:47 PM on ‎2022-‎09-‎07 was unexpected. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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 {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- Encrypted volume check: Volume information on G: cannot be read. ------------------------------------------------------------------- Encrypted volume check: Volume information on G: cannot be read. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024001E: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.373.1447.0). ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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 IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Search service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Search service terminated with the following error: The system cannot find the drive specified. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The previous system shutdown at 10:42:28 PM on ‎2022-‎08-‎23 was unexpected. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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 IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:32:45 PM on ‎2022-‎08-‎19 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 11:05:38 PM on ‎2022-‎08-‎18 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C00F000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C00E000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C00D000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C00C000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C00B000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C00A000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 6:42:40 PM on ‎2022-‎08-‎15 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- 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 IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR4. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5391836A-68BA-49E6-B5FF-CFE01A5997FA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5391836A-68BA-49E6-B5FF-CFE01A5997FA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5391836A-68BA-49E6-B5FF-CFE01A5997FA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5391836A-68BA-49E6-B5FF-CFE01A5997FA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5391836A-68BA-49E6-B5FF-CFE01A5997FA} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{5391836A-68BA-49E6-B5FF-CFE01A5997FA} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B8DD22ED-27A9-4CDC-B59A-D54E18484E1D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B8DD22ED-27A9-4CDC-B59A-D54E18484E1D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B8DD22ED-27A9-4CDC-B59A-D54E18484E1D} 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_{B8DD22ED-27A9-4CDC-B59A-D54E18484E1D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{B8DD22ED-27A9-4CDC-B59A-D54E18484E1D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The previous system shutdown at 10:24:30 PM on ‎2022-‎08-‎02 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:56:21 PM on ‎2022-‎07-‎31 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:33:59 PM on ‎2022-‎07-‎25 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:27:25 PM on ‎2022-‎07-‎21 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{57710185-3ACB-49B1-A582-AAD285AA97D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{57710185-3ACB-49B1-A582-AAD285AA97D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{57710185-3ACB-49B1-A582-AAD285AA97D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{57710185-3ACB-49B1-A582-AAD285AA97D1} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{57710185-3ACB-49B1-A582-AAD285AA97D1} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A23826C4-EE21-45DF-BEE9-93FB9B63A9A9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A23826C4-EE21-45DF-BEE9-93FB9B63A9A9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A23826C4-EE21-45DF-BEE9-93FB9B63A9A9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A23826C4-EE21-45DF-BEE9-93FB9B63A9A9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A23826C4-EE21-45DF-BEE9-93FB9B63A9A9} 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_{A23826C4-EE21-45DF-BEE9-93FB9B63A9A9} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F4770894-FBA4-4A92-9777-89515D18C4C6} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F4770894-FBA4-4A92-9777-89515D18C4C6} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F4770894-FBA4-4A92-9777-89515D18C4C6} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F4770894-FBA4-4A92-9777-89515D18C4C6} 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_{F4770894-FBA4-4A92-9777-89515D18C4C6} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{F4770894-FBA4-4A92-9777-89515D18C4C6} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E460518B-B9FB-4448-BC9C-2DCC1437C1B0} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E460518B-B9FB-4448-BC9C-2DCC1437C1B0} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E460518B-B9FB-4448-BC9C-2DCC1437C1B0} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{E460518B-B9FB-4448-BC9C-2DCC1437C1B0} 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_{E460518B-B9FB-4448-BC9C-2DCC1437C1B0} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{AB8E9FE9-9762-4494-885E-4981A839885D} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DF699AD5-F89F-47A4-98BD-FE475699CBD4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DF699AD5-F89F-47A4-98BD-FE475699CBD4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DF699AD5-F89F-47A4-98BD-FE475699CBD4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DF699AD5-F89F-47A4-98BD-FE475699CBD4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{DF699AD5-F89F-47A4-98BD-FE475699CBD4} 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_{DF699AD5-F89F-47A4-98BD-FE475699CBD4} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A5ABF27E-E1BA-47FA-9886-3E5C973CED16} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A5ABF27E-E1BA-47FA-9886-3E5C973CED16} 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_{A5ABF27E-E1BA-47FA-9886-3E5C973CED16} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A5ABF27E-E1BA-47FA-9886-3E5C973CED16} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{A5ABF27E-E1BA-47FA-9886-3E5C973CED16} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F02AC15-B863-4ECC-90BE-735D67EB3190} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F02AC15-B863-4ECC-90BE-735D67EB3190} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F02AC15-B863-4ECC-90BE-735D67EB3190} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F02AC15-B863-4ECC-90BE-735D67EB3190} 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_{2F02AC15-B863-4ECC-90BE-735D67EB3190} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{2F02AC15-B863-4ECC-90BE-735D67EB3190} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B9BFB3F-F047-43CF-89FB-93D36270968A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B9BFB3F-F047-43CF-89FB-93D36270968A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B9BFB3F-F047-43CF-89FB-93D36270968A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{3B9BFB3F-F047-43CF-89FB-93D36270968A} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D038C6BF-9FB3-4B62-8232-1CDB2B697C99} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D038C6BF-9FB3-4B62-8232-1CDB2B697C99} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D038C6BF-9FB3-4B62-8232-1CDB2B697C99} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D038C6BF-9FB3-4B62-8232-1CDB2B697C99} 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_{D038C6BF-9FB3-4B62-8232-1CDB2B697C99} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{372D24D7-6D5E-4A64-A5C3-EDAF6198FC1C} 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_{372D24D7-6D5E-4A64-A5C3-EDAF6198FC1C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{372D24D7-6D5E-4A64-A5C3-EDAF6198FC1C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{372D24D7-6D5E-4A64-A5C3-EDAF6198FC1C} 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_{372D24D7-6D5E-4A64-A5C3-EDAF6198FC1C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{372D24D7-6D5E-4A64-A5C3-EDAF6198FC1C} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D633DFC9-9513-4235-A631-C4E10CE586A8} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D633DFC9-9513-4235-A631-C4E10CE586A8} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D633DFC9-9513-4235-A631-C4E10CE586A8} 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_{D633DFC9-9513-4235-A631-C4E10CE586A8} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 9 failed to bind to its provider. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D8A3E9CD-85C3-4D99-882F-12CCA193CC43} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D8A3E9CD-85C3-4D99-882F-12CCA193CC43} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D8A3E9CD-85C3-4D99-882F-12CCA193CC43} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{D8A3E9CD-85C3-4D99-882F-12CCA193CC43} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Delivery Optimization service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The SysMain service terminated with the following error: The parameter is incorrect. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- 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. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C00B000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C00A000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Update service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The IvacyService service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{7791755A-5F6E-4C81-A97B-C0B4F48206EF} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C009000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C008000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C007000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C006000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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 system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 10:04:27 PM on ‎2022-‎06-‎17 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9N0DX20HK701-Microsoft.WindowsTerminal. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NZKPSTSNW4P-Microsoft.XboxGamingOverlay. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Security Service 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 0x8024200B: Update for Windows Security platform - KB5007651 (Version 1.0.2109.27002). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server windows.immersivecontrolpanel_10.0.6.1000_neutral_neutral_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- 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. ------------------------------------------------------------------- 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 system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:40:20 PM on ‎2022-‎05-‎22 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The server {9BA05972-F6A8-11CF-A442-00A0C90A8F39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBMP-MICROSOFT.WINDOWSSTORE. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFJBH4-Microsoft.Windows.Photos. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 12:47:53 PM on ‎2022-‎05-‎21 was unexpected. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C005000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C004000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C003000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C002000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C011010000250200C001000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- Initialization failed because the driver device could not be created. Use the string "000000000100320000000000D71000C013010000250200C000000000000000000000000000000000" to identify the interface for which initialization failed. It represents the MAC address of the failed interface or the Globally Unique Interface Identifier (GUID) if NetBT was unable to map from GUID to MAC address. If neither the MAC address nor the GUID were available, the string represents a cluster device name. ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{8D69708D-DDEC-A599-BB02-0475A5D2150E} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} 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_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: 2022-04 Update for Windows 11 for x64-based Systems (KB4023057). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Intel Corporation - Display - 27.20.100.8935. ------------------------------------------------------------------- The Windows Update service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240016: Surface - System - 1.0.104.0. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240016: Surface - System - 1.0.104.0. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240017: 2021-11 Update for Windows 11 for x64-based Systems (KB5008295). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x800F0988: 2022-05 Cumulative Update for Windows 11 for x64-based Systems (KB5013943). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240016: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.367.233.0). ------------------------------------------------------------------- The server could not bind to the transport \Device\NetBT_Tcpip_{9A35E583-F360-45F9-B223-360B0E7A9E06} because another computer on the network has the same name. The server could not start. ------------------------------------------------------------------- The Intel(R) Content Protection HECI Service service terminated with the following error: The data area passed to a system call is too small. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Unable to start a DCOM Server: {5250E46F-BB09-D602-5891-F476DC89B700} as Unavailable/Unavailable. The error: "2147958016" Happened while starting this command: "C:\WINDOWS\SysWOW64\DllHost.exe" /Processid:{5250E46F-BB09-D602-5891-F476DC89B700} ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 1/6/2023, 19:13:13 Machine name: DESKTOP-6ICBO6K Machine Id: {6FD8143A-FDD4-4C26-929D-5F8C5E276219} Operating System: Windows 11 Pro 64-bit (10.0, Build 22000) (22000.co_release.210604-1628) Language: English (Regional Setting: English) System Manufacturer: AZW System Model: SEi BIOS: CB1D_FV106 (type: UEFI) Processor: Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz (4 CPUs), ~3.0GHz Memory: 16384MB RAM Available OS Memory: 16226MB RAM Page File: 6565MB used, 12093MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 144 DPI (150 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.0653 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) Plus Graphics 655 Manufacturer: Intel Corporation Chip type: Intel(R) Iris(R) Plus Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_3EA5&SUBSYS_800C1E50&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: 8241 MB Dedicated Memory: 128 MB Shared Memory: 8113 MB Current Mode: 1920 x 1080 (32 bit) (59Hz) 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: LG TV Monitor Id: GSM0001 Native Mode: 1920 x 1080(p) (60.000Hz) Output Type: HDMI Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12umd64.dll Driver File Version: 31.00.0101.2115 (English) Driver Version: 31.0.101.2115 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: Triangle Compute Preemption: Thread Miracast: Supported 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: 15/11/2022 04:00:00 PM, 1721640 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-7DE5-11CF-A375-69A0AEC2D235} Vendor ID: 0x8086 Device ID: 0x3EA5 SubSys ID: 0x800C1E50 Revision ID: 0x0001 Driver Strong Name: oem49.inf:5f63e5341264f0f6:iCFL_w10_DS:31.0.101.2115:PCI\VEN_8086&DEV_3EA5 Rank Of Driver: 00CF2001 Video Accel: ModeMPEG2_A ModeMPEG2_C ModeWMV9_C ModeVC1_C DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} DXVA2_ModeVP8_VLD {442B942A-B4D9-4940-BC45-A882E5F919F3} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {2364D06A-F67F-4186-AED0-62B99E1784F1} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {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: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) MPO Stretch: 5.000X - 0.334X MPO Media Hints: colorspace Conversion MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM PanelFitter Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) PanelFitter Stretch: 5.000X - 0.334X 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: LG TV (Intel(R) Display Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_8086&DEV_280B&SUBSYS_80860101&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: IntcDAud.sys Driver Version: 10.27.0.12 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 20/11/2021 04:00:00 PM, 348728 bytes Other Files: Driver Provider: Intel(R) Corporation HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: Line in (Digital Video Recorder) Default Sound Capture: No Default Voice Capture: No Driver Name: jaksta_va.sys Driver Version: 1.3.1.188 (English) Driver Attributes: Final Retail Date and Size: 26/11/2014 04:00:00 PM, 102352 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF Description: Microphone (Digital Video Recorder) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: jaksta_va.sys Driver Version: 1.3.1.188 (English) Driver Attributes: Final Retail Date and Size: 26/11/2014 04:00:00 PM, 102352 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 0 --------------------- ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Micr Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x07B2 FF Driver: n/a Device Name: Micr Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x07B2 FF Driver: n/a Device Name: Micr Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x07B2 FF Driver: n/a Device Name: Micr Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x07B2 FF Driver: n/a Device Name: Microsoft Hardware USB Mouse Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x045E, 0x07B2 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x9DED | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 9/13/2021 07:31:17, 696656 bytes | +-+ Microsoft Mouse and Keyboard Detection Driver (USB) | | Vendor/Product ID: 0x045E, 0x07B2 | | Location: Port_#0007.Hub_#0001 | | Matching Device ID: USB\VID_045E&PID_07B2 | | Upper Filters: dc3d | | Service: usbccgp | | Driver: dc3d.sys, 5/21/2022 19:09:35, 95024 bytes | | Driver: usbccgp.sys, 9/7/2022 19:37:10, 222552 bytes | | Driver: WdfCoInstaller01011.dll, 5/21/2022 18:58:30, 1804696 bytes | | | +-+ Microsoft Hardware USB Keyboard | | | Vendor/Product ID: 0x045E, 0x07B2 | | | Location: 0000.0014.0000.007.000.000.000.000.000 | | | Matching Device ID: usb\vid_045e&pid_07b2&mi_00 | | | Service: HidUsb | | | Driver: hidusb.sys, 11/8/2022 17:08:11, 73728 bytes | | | Driver: hidclass.sys, 11/8/2022 17:08:11, 274432 bytes | | | Driver: hidparse.sys, 11/8/2022 17:08:11, 77824 bytes | | | Driver: coin99itp.dll, 5/21/2022 19:08:56, 466728 bytes | | | | | +-+ Wireless Keyboard Filter Device | | | | Vendor/Product ID: 0x045E, 0x07B2 | | | | Matching Device ID: HID\VID_045E&PID_07B2&MI_00 | | | | Upper Filters: WirelessKeyboardFilter | | | | Service: kbdhid | | | | Driver: WirelessKeyboardFilter.sys, 3/11/2018 21:43:42, 49336 bytes | | | | Driver: kbdhid.sys, 5/20/2022 17:33:39, 69632 bytes | | | | Driver: kbdclass.sys, 5/20/2022 17:33:39, 91488 bytes | | | | +-+ Microsoft Hardware USB Mouse | | | Vendor/Product ID: 0x045E, 0x07B2 | | | Location: 0000.0014.0000.007.000.000.000.000.000 | | | Matching Device ID: usb\vid_045e&pid_07b2&mi_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 11/8/2022 17:08:11, 73728 bytes | | | Driver: hidclass.sys, 11/8/2022 17:08:11, 274432 bytes | | | Driver: hidparse.sys, 11/8/2022 17:08:11, 77824 bytes | | | Driver: coin99ip.dll, 5/21/2022 18:56:15, 466728 bytes | | | | | +-+ Microsoft USB Dual Receiver Wireless Mouse (Mouse and Keyboard Center) | | | | Vendor/Product ID: 0x045E, 0x07B2 | | | | Matching Device ID: HID\VID_045E&PID_07B2&MI_01&Col01 | | | | Upper Filters: Point64 | | | | Service: mouhid | | | | Driver: point64.sys, 5/21/2022 18:58:30, 68904 bytes | | | | Driver: mouhid.sys, 5/20/2022 17:33:39, 65536 bytes | | | | Driver: mouclass.sys, 5/20/2022 17:33:39, 91488 bytes | | | | Driver: WdfCoInstaller01011.dll, 5/21/2022 18:58:30, 1804696 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 99.6 GB Total Space: 253.3 GB File System: NTFS Model: KINGSTON SNVS500G Drive: D: Free Space: 170.0 GB Total Space: 221.6 GB File System: NTFS Model: KINGSTON SNVS500G Drive: F: Free Space: 426.3 GB Total Space: 1907.7 GB File System: NTFS Model: WD Ext HDD 1021 USB Device Drive: G: Free Space: 84.0 GB Total Space: 953.8 GB File System: exFAT Model: Samsung Portable SSD T5 SCSI Disk Device -------------- System Devices -------------- Name: Intel(R) Serial IO I2C Host Controller - 9DEA Device ID: PCI\VEN_8086&DEV_9DEA&SUBSYS_72708086&REV_30\3&11583659&0&AA Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_cnl.inf_amd64_a464164235fd7582\iaLPSS2_I2C_CNL.sys, 30.100.2132.0002 (English), 5/21/2022 19:01:50, 196256 bytes Name: CannonLake SCS1: eMMC - 9DC4 Device ID: PCI\VEN_8086&DEV_9DC4&SUBSYS_72708086&REV_30\3&11583659&0&D0 Driver: C:\WINDOWS\system32\DRIVERS\sdbus.sys, 10.00.22000.0918 (English), 9/7/2022 19:37:10, 337240 bytes Driver: C:\WINDOWS\system32\DRIVERS\dumpsd.sys, 10.00.22000.0918 (English), 9/7/2022 19:37:10, 230728 bytes Name: Intel(R) Serial IO SPI Host Controller - 9DAB Device ID: PCI\VEN_8086&DEV_9DAB&SUBSYS_72708086&REV_30\3&11583659&0&F3 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_spi_cnl.inf_amd64_375f6296fd620d89\iaLPSS2_SPI_CNL.sys, 30.100.2132.0002 (English), 5/21/2022 19:01:00, 156832 bytes Name: Intel(R) Serial IO I2C Host Controller - 9DE9 Device ID: PCI\VEN_8086&DEV_9DE9&SUBSYS_72708086&REV_30\3&11583659&0&A9 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_cnl.inf_amd64_a464164235fd7582\iaLPSS2_I2C_CNL.sys, 30.100.2132.0002 (English), 5/21/2022 19:01:50, 196256 bytes Name: Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) Device ID: PCI\VEN_8086&DEV_9DED&SUBSYS_72708086&REV_30\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.22000.1165 (English), 11/3/2022 20:59:20, 656720 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.22000.1165 (English), 11/3/2022 20:59:20, 162560 bytes Name: Realtek PCIe GbE Family Controller Device ID: PCI\VEN_10EC&DEV_8168&SUBSYS_012310EC&REV_15\01000000684CE00000 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\rt68cx21x64.inf_amd64_12e5292d75bc9d96\rt68cx21x64.sys, 1168.10.0720.2022 (English), 12/8/2022 16:07:31, 713136 bytes Name: Intel(R) PCI Express Root Port #7 - 9DBE Device ID: PCI\VEN_8086&DEV_9DBE&SUBSYS_72708086&REV_F0\3&11583659&0&E0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22000.1281 (English), 11/17/2022 17:40:28, 542048 bytes Name: CannonLake SCS3: SD Card - 9DF5 Device ID: PCI\VEN_8086&DEV_9DF5&SUBSYS_72708086&REV_30\3&11583659&0&A5 Driver: C:\WINDOWS\system32\DRIVERS\sdbus.sys, 10.00.22000.0918 (English), 9/7/2022 19:37:10, 337240 bytes Driver: C:\WINDOWS\system32\DRIVERS\dumpsd.sys, 10.00.22000.0918 (English), 9/7/2022 19:37:10, 230728 bytes Name: Intel(R) PCI Express Root Port #14 - 9DB5 Device ID: PCI\VEN_8086&DEV_9DB5&SUBSYS_72708086&REV_F0\3&11583659&0&ED Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22000.1281 (English), 11/17/2022 17:40:28, 542048 bytes Name: Intel(R) 300 Series Chipset Family SATA AHCI Controller Device ID: PCI\VEN_8086&DEV_9DD3&SUBSYS_72708086&REV_30\3&11583659&0&B8 Driver: C:\WINDOWS\system32\DRIVERS\iaStorAC.sys, 17.11.0000.1000 (English), 5/21/2022 18:59:04, 1347776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iaahcic.inf_amd64_3de4831720bb2934\RstMwService.exe, 17.11.0000.1000 (English), 5/21/2022 18:59:04, 2244800 bytes Driver: C:\WINDOWS\system32\RstMwEventLogMsg.dll, 17.11.0000.1000 (English), 5/21/2022 18:59:04, 27328 bytes Name: Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller Device ID: PCI\VEN_8086&DEV_9DC8&SUBSYS_119E10EC&REV_30\3&11583659&0&FB Driver: C:\WINDOWS\system32\DRIVERS\IntcAudioBus.sys, 10.23.0000.4880 (English), 5/12/2021 15:04:20, 273264 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.22000.0653 (English), 5/20/2022 17:33:35, 135168 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.22000.0653 (English), 5/20/2022 17:33:35, 462848 bytes Name: Intel(R) Serial IO UART Host Controller - 9DA8 Device ID: PCI\VEN_8086&DEV_9DA8&SUBSYS_72708086&REV_30\3&11583659&0&F0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_uart2_cnl.inf_amd64_5d70ae894dd84fc1\iaLPSS2_UART2_CNL.sys, 30.100.2132.0002 (English), 5/21/2022 19:02:39, 305808 bytes Name: Intel(R) PCI Express Root Port #9 - 9DB0 Device ID: PCI\VEN_8086&DEV_9DB0&SUBSYS_72708086&REV_F0\3&11583659&0&E8 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22000.1281 (English), 11/17/2022 17:40:28, 542048 bytes Name: Intel(R) Serial IO I2C Host Controller - 9DC5 Device ID: PCI\VEN_8086&DEV_9DC5&SUBSYS_72708086&REV_30\3&11583659&0&C8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_cnl.inf_amd64_a464164235fd7582\iaLPSS2_I2C_CNL.sys, 30.100.2132.0002 (English), 5/21/2022 19:01:50, 196256 bytes Name: ELAN SMBus Driver Device ID: PCI\VEN_8086&DEV_9DA3&SUBSYS_72708086&REV_30\3&11583659&0&FC Driver: C:\WINDOWS\system32\DRIVERS\ETDSMBus.sys, 15.07.0021.0018 (Chinese (Traditional)), 5/21/2022 19:04:56, 53632 bytes Name: PCI standard RAM Controller Device ID: PCI\VEN_8086&DEV_9DEF&SUBSYS_9DEF8086&REV_30\3&11583659&0&A2 Driver: n/a Name: Standard NVM Express Controller Device ID: PCI\VEN_2646&DEV_500F&SUBSYS_500F2646&REV_03\4&24F73C2F&0&00E8 Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.22000.1042 (English), 9/22/2022 17:48:44, 238936 bytes Name: I/O LPC Controller - 9D84 for Intel(R) 300 Series Chipset Family On-Package Platform Controller Hub Device ID: PCI\VEN_8086&DEV_9D84&SUBSYS_72708086&REV_30\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.22000.0001 (English), 6/5/2021 04:04:45, 53576 bytes Name: Intel(R) Host Bridge/DRAM Registers - 3ECC Device ID: PCI\VEN_8086&DEV_3ECC&SUBSYS_72708086&REV_08\3&11583659&0&00 Driver: n/a Name: Intel(R) Thermal Subsystem - 9DF9 Device ID: PCI\VEN_8086&DEV_9DF9&SUBSYS_72708086&REV_30\3&11583659&0&90 Driver: n/a Name: Intel(R) Dual Band Wireless-AC 7265 #2 Device ID: PCI\VEN_8086&DEV_095A&SUBSYS_50108086&REV_59\3887D5FFFFB9E19600 Driver: C:\WINDOWS\system32\DRIVERS\Netwtw04.sys, 19.51.0042.0002 (English), 11/6/2022 20:10:46, 8772696 bytes Driver: C:\WINDOWS\system32\DRIVERS\Netwfw04.dat, 11/6/2022 20:10:45, 2073972 bytes Driver: C:\WINDOWS\system32\IntelIHVRouter04.dll, 22.12160.0000.0003 (English), 11/6/2022 20:10:45, 1677376 bytes Name: Intel(R) Serial IO SPI Host Controller - 9DAA Device ID: PCI\VEN_8086&DEV_9DAA&SUBSYS_72708086&REV_30\3&11583659&0&F2 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_spi_cnl.inf_amd64_375f6296fd620d89\iaLPSS2_SPI_CNL.sys, 30.100.2132.0002 (English), 5/21/2022 19:01:00, 156832 bytes Name: Intel(R) Serial IO I2C Host Controller - 9DE8 Device ID: PCI\VEN_8086&DEV_9DE8&SUBSYS_72708086&REV_30\3&11583659&0&A8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_cnl.inf_amd64_a464164235fd7582\iaLPSS2_I2C_CNL.sys, 30.100.2132.0002 (English), 5/21/2022 19:01:50, 196256 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_9DE0&SUBSYS_72708086&REV_30\3&11583659&0&B0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_6467379f0b0f181f\x64\TeeDriverW10x64.sys, 2229.03.0002.0000 (English), 10/14/2022 17:06:42, 319064 bytes Name: Intel(R) Gaussian Mixture Model - 1911 Device ID: PCI\VEN_8086&DEV_1911&SUBSYS_72708086&REV_00\3&11583659&0&40 Driver: n/a Name: Intel(R) SPI (flash) Controller - 9DA4 Device ID: PCI\VEN_8086&DEV_9DA4&SUBSYS_72708086&REV_30\3&11583659&0&FD Driver: n/a Name: Intel(R) Iris(R) Plus Graphics 655 Device ID: PCI\VEN_8086&DEV_3EA5&SUBSYS_800C1E50&REV_01\3&11583659&0&10 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdkmd64.sys, 31.00.0101.2115 (English), 12/20/2022 18:24:02, 44234800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxs64.vp, 12/20/2022 18:03:48, 5984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd10iumd64.dll, 31.00.0101.2115 (English), 12/20/2022 18:33:42, 671016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd10um64gen11.dll, 31.00.0101.2115 (English), 12/20/2022 18:33:50, 7467592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd11dxva64.dll, 31.00.0101.2115 (English), 12/20/2022 18:35:08, 51694536 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12dxva64.dll, 31.00.0101.2115 (English), 12/20/2022 18:35:54, 51699168 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12umd64.dll, 31.00.0101.2115 (English), 12/20/2022 18:36:28, 134384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12um64kbl.dll, 12/20/2022 18:36:26, 10799104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12um64icl.dll, 12/20/2022 18:36:18, 10860032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdgmm64.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:42, 4258640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igfxcmrt64.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:14, 207208 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igfx11cmrt64.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:10, 210296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdumdim64.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:06, 1721640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdail64.dll, 12/20/2022 18:23:48, 196008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd9dxva64.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:28, 51422368 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iga64.dll, 31.00.0101.2115 (English), 12/20/2022 18:32:36, 2874376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igc64.dll, 31.00.0101.2115 (English), 12/20/2022 18:33:38, 58527872 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\DnnlPlugin.dll, 12/20/2022 18:32:30, 16725000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\UniversalAdapter64.dll, 12/20/2022 18:41:46, 332736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\opencl-clang64.dll, 2.00.0009.0000 (English), 12/20/2022 18:41:42, 82134544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdfcl64.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:38, 1059960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdmd64.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:58, 5489968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdml64.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:00, 1221592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdde64.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:32, 408680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdinfo64.dll, 12/20/2022 18:37:46, 148880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdext64.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:36, 289880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd10iumd32.dll, 31.00.0101.2115 (English), 12/20/2022 18:33:40, 645152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd10um32gen11.dll, 31.00.0101.2115 (English), 12/20/2022 18:33:46, 7231056 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd11dxva32.dll, 31.00.0101.2115 (English), 12/20/2022 18:34:30, 50614976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12dxva32.dll, 31.00.0101.2115 (English), 12/20/2022 18:35:30, 50592776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12umd32.dll, 31.00.0101.2115 (English), 12/20/2022 18:36:28, 97656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12um32kbl.dll, 12/20/2022 18:36:12, 10249432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd12um32icl.dll, 12/20/2022 18:36:04, 10318192 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdgmm32.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:40, 3306152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdumdim32.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:04, 1540728 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdail32.dll, 12/20/2022 18:23:46, 159664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igd9dxva32.dll, 31.00.0101.2115 (English), 12/20/2022 18:36:50, 50345384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igfxcmrt32.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:12, 163784 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igfx11cmrt32.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:06, 165832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iga32.dll, 31.00.0101.2115 (English), 12/20/2022 18:32:32, 2302552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igc32.dll, 31.00.0101.2115 (English), 12/20/2022 18:33:04, 49616584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\UniversalAdapter32.dll, 12/20/2022 18:41:44, 276832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\opencl-clang32.dll, 2.00.0009.0000 (English), 12/20/2022 18:41:00, 60946616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdfcl32.dll, 31.00.0101.2115 (English), 12/20/2022 18:23:50, 983504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdmd32.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:54, 4338136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdml32.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:00, 907528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdde32.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:30, 333240 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdinfo32.dll, 12/20/2022 18:37:44, 123456 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdext32.dll, 31.00.0101.2115 (English), 12/20/2022 18:37:34, 230384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libigd12dxva64.so, 12/20/2022 18:03:50, 34118592 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libigd12umd64.so, 12/20/2022 18:03:50, 43208 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libigd12um64kbl.so, 12/20/2022 18:03:50, 4775480 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libigd12um64icl.so, 12/20/2022 18:03:50, 4909608 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libigc.so, 12/20/2022 18:03:48, 41968416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libLLVM-9.so, 12/20/2022 18:03:50, 38566232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libigdgmm.so.12, 12/20/2022 18:03:50, 2288248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libUniversalAdapter64.so, 12/20/2022 18:03:52, 505936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libigdfcl.so, 12/20/2022 18:03:50, 986832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libopencl-clang.so.9, 12/20/2022 18:03:52, 81366600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libwsl_compute_helper.so, 12/20/2022 18:03:52, 567376 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxo64.vp, 12/20/2022 18:03:48, 42513 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxc64.vp, 12/20/2022 18:03:48, 44194 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxg64.vp, 12/20/2022 18:03:48, 43760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxo64_dev.vp, 12/20/2022 18:03:48, 43143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxc64_dev.vp, 12/20/2022 18:03:48, 43214 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxg64_dev.vp, 12/20/2022 18:03:48, 43732 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxa64.vp, 12/20/2022 18:03:48, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\iglhxa64.cpa, 12/20/2022 18:03:48, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\IntelCpHDCPSvc.exe, 31.00.0101.2115 (English), 12/20/2022 18:25:02, 343128 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\cp_resources.bin, 12/20/2022 18:03:46, 2572396 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\ig9icd64.dll, 31.00.0101.2115 (English), 12/20/2022 18:23:40, 17350064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\ig9icd32.dll, 31.00.0101.2115 (English), 12/20/2022 18:23:32, 13838800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\OSSCOPYRIGHT.txt, 12/20/2022 18:03:54, 1372 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igvk64.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:44, 23379032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igvk64.json, 12/20/2022 18:03:48, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\VulkanRT-EULA.txt, 12/20/2022 18:03:54, 4008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igvk32.dll, 31.00.0101.2115 (English), 12/20/2022 18:38:34, 21441568 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igvk32.json, 12/20/2022 18:03:48, 135 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\vulkan-1-64.dll, 1.03.0204.0001 (English), 12/20/2022 18:26:08, 1432320 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\vulkaninfo-64.exe, 1.03.0204.0001 (English), 12/20/2022 18:26:12, 1969720 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\vulkan-1-32.dll, 1.03.0204.0001 (English), 12/20/2022 18:26:06, 1145600 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\vulkaninfo-32.exe, 1.03.0204.0001 (English), 12/20/2022 18:26:10, 1526328 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.03.0204.0001 (English), 12/20/2022 18:26:06, 1145600 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.03.0204.0001 (English), 12/20/2022 18:26:10, 1526328 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0204.0001 (English), 12/20/2022 18:26:06, 1145600 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0204.0001 (English), 12/20/2022 18:26:10, 1526328 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.03.0204.0001 (English), 12/20/2022 18:26:08, 1432320 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.03.0204.0001 (English), 12/20/2022 18:26:12, 1969720 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.03.0204.0001 (English), 12/20/2022 18:26:08, 1432320 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0204.0001 (English), 12/20/2022 18:26:12, 1969720 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 12/20/2022 18:25:08, 362960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdrcl32.dll, 23.20.0101.2115 (English), 12/20/2022 18:24:26, 3753392 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 12/20/2022 18:25:12, 500176 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\ze_loader.dll, 1.08.0001.0000 (English), 12/20/2022 18:26:18, 382896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\ze_validation_layer.dll, 1.08.0001.0000 (English), 12/20/2022 18:26:24, 143776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\ze_tracing_layer.dll, 1.08.0001.0000 (English), 12/20/2022 18:26:20, 477104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\igdrcl64.dll, 23.20.0101.2115 (English), 12/20/2022 18:24:28, 4305840 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\ze_intel_gpu64.dll, 1.03.0000.0000 (English), 12/20/2022 18:26:16, 4375464 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 3.00.0001.0000 (English), 5/20/2022 17:41:04, 78336 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 3.00.0001.0000 (English), 5/20/2022 17:41:03, 114688 bytes Driver: C:\WINDOWS\system32\ze_loader.dll, 1.08.0001.0000 (English), 12/20/2022 18:26:18, 382896 bytes Driver: C:\WINDOWS\system32\ze_validation_layer.dll, 1.08.0001.0000 (English), 12/20/2022 18:26:24, 143776 bytes Driver: C:\WINDOWS\system32\ze_tracing_layer.dll, 1.08.0001.0000 (English), 12/20/2022 18:26:20, 477104 bytes Driver: C:\WINDOWS\SysWow64\libmfxhw32.dll, 22.05.0019.0430 (English), 12/20/2022 18:39:50, 690104 bytes Driver: C:\WINDOWS\SysWow64\mfxplugin32_hw.dll, 22.05.0019.0430 (English), 12/20/2022 18:25:30, 20672464 bytes Driver: C:\WINDOWS\system32\libmfxhw64.dll, 22.05.0019.0430 (English), 12/20/2022 18:39:52, 927200 bytes Driver: C:\WINDOWS\system32\mfxplugin64_hw.dll, 22.05.0019.0430 (English), 12/20/2022 18:25:46, 27948496 bytes Driver: C:\WINDOWS\system32\intel_gfx_api-x64.dll, 22.05.0019.0430 (English), 12/20/2022 18:38:50, 575960 bytes Driver: C:\WINDOWS\system32\libvpl.dll, 2.06.0000.0000 (English), 12/20/2022 18:41:50, 497024 bytes Driver: C:\WINDOWS\SysWow64\intel_gfx_api-x86.dll, 22.05.0019.0430 (English), 12/20/2022 18:38:54, 437488 bytes Driver: C:\WINDOWS\SysWow64\libvpl.dll, 2.06.0000.0000 (English), 12/20/2022 18:41:48, 438152 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfxplugin64_hw.dll, 22.05.0019.0430 (English), 12/20/2022 18:25:46, 27948496 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfxplugin64_av1e_gacc.dll, 3.11.0005.0020 (English), 12/20/2022 18:39:48, 12428672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\intel_gfx_api-x64.dll, 22.05.0019.0430 (English), 12/20/2022 18:38:50, 575960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfxplugin32_hw.dll, 22.05.0019.0430 (English), 12/20/2022 18:25:30, 20672464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfxplugin32_av1e_gacc.dll, 3.11.0005.0020 (English), 12/20/2022 18:39:42, 8521936 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\intel_gfx_api-x86.dll, 22.05.0019.0430 (English), 12/20/2022 18:38:54, 437488 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_h264ve_32.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:10, 2486536 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_mjpgvd_32.dll, 22.05.0019.0430 (English), 12/20/2022 18:25:50, 2391472 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_h265ve_32.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:16, 2499432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_vp9ve_32.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:24, 2494280 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_encrypt_32.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:02, 2350616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_av1hve_32.dll, 22.05.0019.0430 (English), 12/20/2022 18:39:56, 2495808 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\c_32.cpa, 12/20/2022 18:03:46, 1361159 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\cpa_32.vp, 12/20/2022 18:03:46, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\dev_32.vp, 12/20/2022 18:03:46, 57143 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\he_32.vp, 12/20/2022 18:03:46, 75457 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mj_32.vp, 12/20/2022 18:03:54, 71013 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\h265e_32.vp, 12/20/2022 18:03:46, 77061 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\vp9e_32.vp, 12/20/2022 18:03:54, 76672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_av1hve_32.vp, 12/20/2022 18:03:52, 76697 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_h264ve_64.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:12, 3029896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_mjpgvd_64.dll, 22.05.0019.0430 (English), 12/20/2022 18:25:54, 2913704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_h265ve_64.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:20, 3048520 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_vp9ve_64.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:26, 3043360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_encrypt_64.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:06, 2864064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_av1hve_64.dll, 22.05.0019.0430 (English), 12/20/2022 18:40:00, 3044864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\c_64.cpa, 12/20/2022 18:03:46, 1376256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\cpa_64.vp, 12/20/2022 18:03:46, 1125 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\dev_64.vp, 12/20/2022 18:03:46, 56359 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\he_64.vp, 12/20/2022 18:03:46, 13227 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mj_64.vp, 12/20/2022 18:03:54, 12955 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\h265e_64.vp, 12/20/2022 18:03:46, 13815 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\vp9e_64.vp, 12/20/2022 18:03:54, 13646 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\mfx_mft_av1hve_64.vp, 12/20/2022 18:03:52, 13635 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libmfxhw64.dll, 22.05.0019.0430 (English), 12/20/2022 18:39:36, 28714440 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\libmfxhw32.dll, 22.05.0019.0430 (English), 12/20/2022 18:39:18, 27127696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\IntelCpHeciSvc.exe, 9.02.0001.0920 (English), 12/20/2022 18:25:02, 518744 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\clangFEWrapper.dll, 12/20/2022 18:32:06, 32971952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_b53c057d22ce6f37\clangFEWrapper32.dll, 12/20/2022 18:32:14, 26067824 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.0653 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.0653 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.22000.1281 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.22000.0653 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.22000.0653 DV Muxer,0x00400000,0,0,qdv.dll,10.00.22000.0653 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.22000.0001 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.22000.0653 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.0653 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.22000.1335 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.22000.0653 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.22000.0653 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.0653 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.22000.0653 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.22000.0653 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.22000.0653 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22000.1042 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.0653 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.1042 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.0653 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.0653 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.22000.0653 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,10.00.22000.0653 File writer,0x00200000,1,0,qcap.dll,10.00.22000.0653 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.22000.0653 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.1042 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.22000.0653 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.22000.0653 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.22000.0653 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.22000.0653 Null Renderer,0x00200000,1,0,qedit.dll,10.00.22000.0653 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.22000.0653 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.22000.1042 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.22000.0653 Smart Tee,0x00200000,1,2,qcap.dll,10.00.22000.0653 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.1042 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.22000.0653 AVI Mux,0x00200000,1,0,qcap.dll,10.00.22000.0653 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.0653 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.22000.1042 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.22000.0653 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.0708 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.22000.0653 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.22000.0653 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.22000.0653 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.22000.0653 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.0653 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 (Digital Video Recorder),0x00200000,0,0,qcap.dll,10.00.22000.0653 Line in (Digital Video Recorder),0x00200000,0,0,qcap.dll,10.00.22000.0653 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.22000.0653 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.22000.0653 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.22000.0653 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,, Digital Video Recorder,0x00200000,2,2,ksproxy.ax,10.00.22000.0708 WDM Streaming Rendering Devices: ,0x00000000,0,0,, ,0x00200000,1,1,, Intel(R) Display Audio Output 1,0x00200000,1,1,ksproxy.ax,10.00.22000.0708 Digital Video Recorder,0x00200000,2,2,ksproxy.ax,10.00.22000.0708 Intel� Smart Sound Technology (Intel� SST) Output,0x00200000,2,2,ksproxy.ax,10.00.22000.0708 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0653 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0653 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0653 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22000.0653 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.22000.0653 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.22000.0653 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.22000.0653 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.22000.0653 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.22000.0708 Audio Renderers: LG TV (Intel(R) Display 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: LG TV (Intel(R) Display 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.1335 mfreadwrite.dll, 10.00.22000.0001 mfcaptureengine.dll, 10.00.22000.0653 mfsensorgroup.dll, 10.00.22000.0708 windows.media.dll, 10.00.22000.1335 frameserver.dll, 10.00.22000.0708 frameserverclient.dll, 10.00.22000.0708 --------------------------- 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, 22.05.0019.0430 Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 22.05.0019.0430 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.22000.1335 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.22000.0653 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.1335 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.22000.0653 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.22000.1281 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.22000.0653 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.22000.0653 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.22000.0653 HEVCVideoExtension VP9VideoExtensionDecoder HEIFImageExtension WebpImageExtension AV1VideoExtension MPEG2VideoExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 22.05.0019.0430 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 22.05.0019.0430 Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 22.05.0019.0430 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 22.05.0019.0430 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.22000.0778 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.22000.0653 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.22000.0653 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.22000.0653 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.22000.1042 HEVCVideoExtensionEncoder VP9VideoExtensionEncoder HEIFImageExtension Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.22000.0653 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.22000.0653 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.22000.0653 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.22000.0653 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.0832 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.22000.1281 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.22000.0708 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.1281 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.22000.1335 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.22000.1335 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.0653 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.22000.0653 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.22000.1281 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.22000.0653 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.22000.1335 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.22000.1335 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.0653 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.22000.1335 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.22000.0653 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.22000.0653 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.22000.0653 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.22000.1335 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.22000.0653 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.22000.0653 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.22000.0653 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.22000.1042 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.0653 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.22000.0653 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.22000.1042 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.22000.0653 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.1281 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.22000.1335 -------------------------------------------- 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: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER1 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER2 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER3 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER4 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER5 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER6 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER7 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER8 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: +++ WER9 +++: Fault bucket 1341849032420379965, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Everything.exe P2: 1.4.1.1022 P3: 63436523 P4: Everything.exe P5: 1.4.1.1022 P6: 63436523 P7: c0000005 P8: 000000000003b92c P9: P10: ...#SSU#...