# SSU Scan Information Scan Info: Version:"4.0.0.0" Date:"02/02/2025" Time:"00:03:01.9979046" # Scanned Hardware Computer: BaseBoard Manufacturer:"LENOVO" BIOS Mode:"UEFI" BIOS Version/Date:"LENOVO E0CN45WW , 01/13/2016 12:00 AM" CD or DVD:"HL-DT-ST DVDRAM GUE0N" Embedded Controller Version:"1.45" Platform Role:"Mobile" Processor:"Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"2.7" Sound Card:"Conexant SmartAudio HD" System Manufacturer:"LENOVO" System Model:"80QQ" System SKU:"LENOVO_MT_80QQ_BU_idea_FM_Lenovo ideapad 100-15IBD" System Type:"x64-based PC" - "Graphics" Intel ® Graphics Driver Version:"20.19.15.5171" - "Intel(R) HD Graphics 5500" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Not Available" Adapter RAM:"Not Available" Availability:"Offline" Bits Per Pixel:"Not Available" - "Caption":"Intel(R) HD Graphics 5500" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=HD+Graphics+5500" CoInstallers:"igfxCoIn_v5171.dll, CoDeviceInstall" Color Table Entries:"Not Available" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"11/04/2020 12:00 AM" Driver Path:"C:\Windows\system32\DRIVERS\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"20.19.15.5171" INF:"oem8.inf" INF Section:"iBDWM_w10" Install Date:"Not Available" Installed Drivers:"igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"Not Available" Manufacturer:"Intel Corporation" Microsoft DirectX* Version:"11.X" Monochrome:"No" Number of Colors:"Not Available" Number of Video Pages:"Not Available" PNP Device ID:"ROOT\DISPLAY\0000" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"Not Available" Refresh Rate - Maximum:"Not Available" Refresh Rate - Minimum:"Not Available" Resolution:"Not Available" Scan Mode:"Not Available" Service Name:"igfx" Status:"Error" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Not Available" - "Intel(R) HD Graphics 5500" 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) HD Graphics 5500" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=HD+Graphics+5500" CoInstallers:"igfxCoIn_v5171.dll, CoDeviceInstall" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmd64.sys" Driver Date:"03/28/2017 01:00 AM" Driver Path:"C:\Windows\system32\DRIVERS\igdkmd64.sys" Driver Provider:"Intel Corporation" Driver Version:"20.19.15.4642" INF:"oem29.inf" INF Section:"iBDWM_w10" Install Date:"Not Available" Installed Drivers:"igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,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:"11.X" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_1616&SUBSYS_382A17AA&REV_09\3&11583659&0&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"59 Hz" Refresh Rate - Maximum:"59 Hz" Refresh Rate - Minimum:"59 Hz" Resolution:"1366 X 768" Scan Mode:"Noninterlaced" Service Name:"igfx" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) HD Graphics Family" - "Memory" Physical Memory (Available):"0.77 GB" Physical Memory (Installed):"4 GB" Physical Memory (Total):"3.91 GB" - "BANK 2" Capacity:"4 GB" Channel:"ChannelB-DIMM0" Configured Clock Speed:"1600 MHz" Configured Voltage:"Not Available" Data Width:"64 bits" Form Factor:"SODIMM" Interleave Position:"Second position" Manufacturer:"Hynix/Hyundai" Maximum Voltage:"Not Available" Memory Type:"DDR3" Minimum Voltage:"Not Available" Part Number:"HMT451S6BFR8A-PB" Serial Number:"23682310" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"E0CN45WW, LENOVO - 1" Caption:"Motherboard" - "Chipset":"Intel(R) 9 Series" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=9+Series" Date:"01/13/2016 12:00 AM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"LENOVO" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"Nano 5B6" Serial Number:"PF0FF4YW" Status:"OK" Version:"NO DPK" - "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.19041.3636" Index:"0001" 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:"02/02/2025 07:25 AM" Location:"Not Available" MAC Address:"A8:A7:95:8A:81:2E" Manufacturer:"Microsoft" Net Connection ID:"Bluetooth Network Connection" NetCfgInstanceId:"{FD035363-E61F-4EF4-A0E3-D93D4AAA570B}" PNP Device ID:"BTH\MS_BTHPAN\6&B63AC85&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" 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: - "Famatech Radmin VPN Ethernet Adapter" Availability:"Running or Full Power" Caption:"Famatech Radmin VPN Ethernet Adapter" CoInstallers:"Not Available" Default IP Gateway:"26.0.0.1" DHCP Enabled:"No" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"RvNetMP60.sys" Driver Date:"11/08/2022 12:00 AM" Driver Path:"C:\Windows\system32\drivers\RvNetMP60.sys" Driver Provider:"Famatech" Driver Version:"15.39.54.8" Index:"0014" INF:"oem33.inf" INF Section:"RVpnNetMP.ndi" Install Date:"Not Available" Installed:"Yes" IP Address:"26.199.164.153;fe80::34eb:247:7c96:41a3;fdfd::1ac7:a499" IP Subnet:"255.0.0.0;64;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02/02/2025 07:25 AM" Location:"Not Available" MAC Address:"02:50:2D:16:FB:A8" Manufacturer:"Famatech" Net Connection ID:"Radmin VPN" NetCfgInstanceId:"{1B64B9EC-975A-42CB-A579-D053E2F48C9C}" PNP Device ID:"ROOT\NET\0000" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Famatech Radmin VPN Ethernet Adapter" Service Name:"RvNetMP60" Status:"Enabled" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Realtek PCIe FE Family Controller" Availability:"Running or Full Power" Caption:"Realtek PCIe FE Family Controller" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"rt640x64.sys" Driver Date:"11/05/2021 12:00 AM" Driver Path:"C:\Windows\system32\drivers\rt640x64.sys" Driver Provider:"Realtek" Driver Version:"10.50.511.2021" Index:"0003" INF:"oem22.inf" INF Section:"RTL8106EUS.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:"02/02/2025 07:25 AM" Location:"PCI bus 2, device 0, function 0" MAC Address:"50:7B:9D:BE:91:F9" Manufacturer:"Realtek" Net Connection ID:"Ethernet" NetCfgInstanceId:"{3BF58743-D4F2-438F-BCE6-93B940CFCACC}" PNP Device ID:"PCI\VEN_10EC&DEV_8136&SUBSYS_383C17AA&REV_08\01000000364CE00000" 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:"Realtek PCIe FE Family Controller" Service Name:"rt640x64" Status:"Enabled" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *EEE:Energy-Efficient Ethernet:"Disabled (0)" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *LsoV2IPv4:Large Send Offload v2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload v2 (IPv6):"Enabled (1)" *ModernStandbyWoLMagicPacket:Wake on magic packet when system is in the S0ix power state:"Disabled (0)" *NumRssQueues:Maximum Number of RSS Queues:"4 Queues (4)" *PMARPOffload:ARP Offload:"Enabled (1)" *PMNSOffload:NS Offload:"Enabled (1)" *PriorityVLANTag:Priority & VLAN:"Priority & VLAN Enabled (3)" *ReceiveBuffers:Receive Buffers:"512 (512)" *RSS:Receive Side Scaling:"Enabled (1)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *TransmitBuffers:Transmit Buffers:"128 (128)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on pattern match:"Enabled (1)" AdvancedEEE:Advanced EEE:"Disabled (0)" 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)" - "Realtek RTL8723BE Wireless LAN 802.11n PCI-E NIC" Access Point:"ee:01:db:d7:96:17" Authentication:"WPA2-Personal" Availability:"Running or Full Power" Caption:"Realtek RTL8723BE Wireless LAN 802.11n PCI-E NIC" Channel:"11" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Auto Connect" Default IP Gateway:"192.168.93.204;fe80::ec01:dbff:fed7:9617" DHCP Enabled:"Yes" DHCP Lease Expires:"02/02/2025 08:31 AM" DHCP Lease Obtained:"02/02/2025 07:31 AM" DHCP Server:"192.168.93.204" Driver:"rtwlane02.sys" Driver Date:"05/26/2019 12:00 AM" Driver Path:"C:\Windows\system32\drivers\rtwlane02.sys" Driver Provider:"Realtek Semiconductor Corp." Driver Version:"2024.0.4.208" Index:"0002" INF:"oem19.inf" INF Section:"LC8723be.ndi.NT" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.93.28;fe80::72b0:81fe:9322:1c14;2401:4900:3f27:496d:89bc:c70:6f81:b548;2401:4900:3f27:496d:612c:154f:4bfa:1b39" IP Subnet:"255.255.255.0;64;128;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02/02/2025 07:25 AM" Location:"PCI bus 3, device 0, function 0" MAC Address:"A8:A7:95:8A:81:2D" Manufacturer:"Realtek Semiconductor Corp." Net Connection ID:"WiFi" NetCfgInstanceId:"{C58D64A8-13D8-40E0-B14A-8C13B94535F3}" Network Name:"Redmi 10" Network Type:"Infrastructure" PNP Device ID:"PCI\VEN_10EC&DEV_B723&SUBSYS_B72817AA&REV_00\0023B7FEFF4CE00000" 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:"Realtek RTL8723BE Wireless LAN 802.11n PCI-E NIC" Profile:"Redmi 10" Radio Type:"802.11n" Receive Rate:"72.2 Mbps" Service Name:"RTWlanE02" Signal Strength:"100%" State:"connected" Status:"Enabled" Transmit Rate:"72.2 Mbps" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" AH_BcnIntv:Beacon Interval:"100 (100)" BWSetting:Bandwidth:"20_40MHz (1)" Dot11dEnable:802.11d:"Disabled (0)" MultiChannelFcsMode:Multi-Channel Concurrent:"Enabled (12)" PreambleMode:Preamble Mode:"Short & long (2)" RegROAMSensitiveLevel:Roaming Sensitivity Level:"Low (80)" WirelessMode:Wireless Mode:"Auto (8)" - "Operating System" .Net Framework Version:"2.0,3.0,3.5,4.0,4.8" Boot Device:"\Device\HarddiskVolume2" Internet Browser:"Internet Explorer,11.3636, Microsoft Edge,130.0" Locale:"United Kingdom" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 10 Pro" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"6.00 GB" Physical Memory (Available):"0.35 GB" Physical Memory (Installed):"4 GB" Physical Memory (Total):"3.91 GB" System Directory:"C:\Windows\system32" Version:"10.0.19045 Build 19045" Virtual Memory (Available):"5.40 GB" Virtual Memory (Total):"9.91 GB" Windows Directory:"C:\Windows" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [10/31/2024]" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [1/3/2025]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [1/3/2025]" KB2467173:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [10/31/2024]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB5011048:"Update [11/3/2024]" KB5014032:"Security Update [12/4/2023]" KB5015684:"Update [12/4/2023]" KB5031988:"Update [12/4/2023]" KB5032907:"Update [12/4/2023]" KB5043130:"Update [11/7/2024]" KB5046823:"Update [12/7/2024]" KB5048652:"Security Update [12/11/2024]" KB5050411:"Security Update [1/19/2025]" KB5050576:"Update [1/31/2025]" KB982573:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [10/31/2024]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [1/3/2025]" SP1:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [Not Available]" SP1:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [Not Available]" - "Processor" - "Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 61 Stepping 4" - "Chipset Name":"Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Core+i3+5005U+CPU+" CPU Speed:"2 GHz" Current Voltage:"8. volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00 AM" Driver Path:"C:\Windows\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.19041.4355" 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 32 KB" Level 2 Cache:"2 x 256 KB" Level 3 Cache:"3 MB" Load:"3%" Manufacturer:"GenuineIntel" Model:"61" Name:"Intel(R) Core(TM) i3-5005U CPU @ 2.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:"BFEBFBFF000306D4" Revision:"15620" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"4" Version:"Not Available" - "Storage" - "ST1000LM024 HN-M101MBB" Capablities:"Random Access, Supports Writing, SMART Notification" Caption:"ST1000LM024 HN-M101MBB" Cylinder - Total:"121601" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.19041.4597" Error Code:"Device is working properly" Firmware Revision:"2BA30001" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"IDE" Manufacturer:"(Standard disk drives)" Model:"ST1000LM024 HN-M101MBB" Name:"\\.\PHYSICALDRIVE0" Partitions:"5" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_ST1000LM&PROD_024_HN-M101MBB\4&DC4B387&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" Sectors - Per Track:"63" Sectors - Total:"1953520065" Serial Number:"S30YJ9CGC12363" Size:"931.51 GB" Size – Available:"423.40 GB" SMART Attributes:"Self-Test: 202 minutes, OK, Short Self-Test: 2 minutes, OK" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"31008255" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Not Available" Serial Number:"1AFD7240" Size:"442.09 GB" Size – Available:"231.99 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:"New Volume" Serial Number:"440A994E" Size:"488.28 GB" Size – Available:"191.41 GB" Status:"Not Available" Volume Dirty:"No" - "SMART" 0x01 Raw Read Error Rate:119:"51" 0x02 Throughput Performance:0:"0" 0x03 Spin Up Time:2483:"25" 0x04 Start/Stop Count:10145:"0" 0x05 Reallocated Sector Count:0:"10" 0x07 Seek Error Rate:0:"51" 0x08 Seek Timer Performance:0:"15" 0x09 Power-On Hours:8197:"0" 0x0A Spin Retry Count:0:"51" 0x0B Calibration Retry Count:238:"0" 0x0C Power Cycle Count:4385:"0" 0xBF G-sense Rate/Servo Tracking:7336:"0" 0xC0 Unsafe Shutdown Count:430:"0" 0xC2 Internal Device Temperature:34° C:"0" 0xC3 Hardware ECC Recovered:0:"0" 0xC4 Reallocation Count:0:"0" 0xC5 Current Pending Errors Count:0:"0" 0xC6 Uncorrectable Sector Count:0:"0" 0xC7 CRC Error Count:0:"0" 0xC8 Write Error Rate:34082:"0" 0xDF Load/Unload Retry Count:238:"0" 0xE1 Host Writes:215375:"0" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The WinDefend 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 17:09:48 on ‎01/‎02/‎2025 was unexpected. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The WinDefend service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The WinDefend 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 16:44:20 on ‎31/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The SSDP Discovery service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. ------------------------------------------------------------------- The Function Discovery Resource Publication service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Location Awareness service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. ------------------------------------------------------------------- The Workstation service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The DNS Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service. ------------------------------------------------------------------- The Cryptographic Services service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The WinDefend service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Microsoft Defender Antivirus Service service failed to start due to the following error: The system cannot find the file specified. ------------------------------------------------------------------- The Microsoft Defender Antivirus Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Camera Frame Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The SSDP Discovery service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. ------------------------------------------------------------------- The Function Discovery Resource Publication service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:04:18 on ‎30/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The SSDP Discovery service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. ------------------------------------------------------------------- The Function Discovery Resource Publication service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 11:58:27 on ‎30/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.System.Internal.UserManager did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8A1A8BB1-242F-431A-9F5B-254BA754631C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {0134A8B2-3407-4B45-AD25-E9F7C92A80BC} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.System.Internal.UserManager did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The following service has repeatedly stopped responding to service control requests: Windows Update Contact the service vendor or the system administrator about whether to disable this service until the problem is identified. You may have to restart the computer in safe mode before you can disable the service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Winmgmt service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Winmgmt service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Winmgmt service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Winmgmt service. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service BITS with arguments "Unavailable" in order to run the server: {4991D34B-80A1-4291-83B6-3328366B9097} ------------------------------------------------------------------- The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Winmgmt service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Winmgmt service. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service BITS with arguments "Unavailable" in order to run the server: {4991D34B-80A1-4291-83B6-3328366B9097} ------------------------------------------------------------------- The Background Intelligent Transfer Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Winmgmt service. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 17:07:58 on ‎29/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- 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:39:55 on ‎29/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- 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:23:12 on ‎29/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The Delivery Optimization 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 0x80070050: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.1591.0) - Current Channel (Broad). ------------------------------------------------------------------- The Energy Server Service queencreek service hung on starting. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- 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:27:21 on ‎27/‎01/‎2025 was unexpected. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 06:16:43 on ‎27/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- 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 04:47:04 on ‎27/‎01/‎2025 was unexpected. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80246007: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.1553.0) - Current Channel (Broad). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 03:57:48 on ‎27/‎01/‎2025 was unexpected. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 03:40:29 on ‎27/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 01:53:09 on ‎27/‎01/‎2025 was unexpected. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- 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 08:50:21 on ‎26/‎01/‎2025 was unexpected. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 06:19:41 on ‎26/‎01/‎2025 was unexpected. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 15:51:46 on ‎22/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization 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 0x80240016: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.1489.0) - Current Channel (Broad). ------------------------------------------------------------------- The Connected User Experiences and Telemetry service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 30000 milliseconds: Restart the service. ------------------------------------------------------------------- The BattlEye Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the BattlEye Service service to connect. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 13:06:07 on ‎22/‎01/‎2025 was unexpected. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the wlidsvc service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UsoSvc service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TokenBroker service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Themes service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the IKEEXT service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Appinfo service. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 12:55:31 on ‎22/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The Security Center service terminated unexpectedly. It has done this 3 time(s). ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Microsoft Passport service terminated with the following error: There are no more endpoints available from the endpoint mapper. ------------------------------------------------------------------- The Security Center service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Security Center service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {E60687F7-01A1-40AA-86AC-DB1CBF673334} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {4991D34B-80A1-4291-83B6-3328366B9097} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Internal.Security.Authentication.Web.TokenBrokerInternal did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8BC3F05E-D86B-11D0-A075-00C04FB68820} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The following service has repeatedly stopped responding to service control requests: Windows Update Contact the service vendor or the system administrator about whether to disable this service until the problem is identified. You may have to restart the computer in safe mode before you can disable the service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WpnService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the wlidsvc service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the OneSyncSvc_62b6e service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UsoSvc service. ------------------------------------------------------------------- The Energy Server Service queencreek service hung on starting. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TokenBroker service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Themes service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the iphlpsvc service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the IKEEXT service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Appinfo service. ------------------------------------------------------------------- The Sync Host_62b6e service terminated with the following error: There are no more endpoints available from the endpoint mapper. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 12:25:07 on ‎22/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Push Notifications System Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 2000 milliseconds: Restart the service. ------------------------------------------------------------------- The Microsoft Account Sign-in Assistant service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- The User Manager service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The User Profile Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service. ------------------------------------------------------------------- The Xbox Live Auth Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Update service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Push Notifications System Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service. ------------------------------------------------------------------- The Microsoft Account Sign-in Assistant service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Management Instrumentation service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Update Orchestrator Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The User Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Web Account Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Themes service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The System Event Notification Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Task Scheduler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service in a separate process. ------------------------------------------------------------------- The User Profile Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The IP Helper service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The IKE and AuthIP IPsec Keying Modules service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Group Policy Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Application Information service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 12:14:16 on ‎22/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The Xbox Live Auth Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Update service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Push Notifications System Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service. ------------------------------------------------------------------- The Microsoft Account Sign-in Assistant service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Management Instrumentation service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Update Orchestrator Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The User Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Web Account Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Themes service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The System Event Notification Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Task Scheduler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service in a separate process. ------------------------------------------------------------------- The User Profile Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The IP Helper service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The IKE and AuthIP IPsec Keying Modules service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Group Policy Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Application Information service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the IKEEXT service. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- 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:05:15 on ‎22/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 11:50:00 on ‎22/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:21:20 on ‎21/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024001E: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.1465.0) - Current Channel (Broad). ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Crash dump initialization failed! ------------------------------------------------------------------- The previous system shutdown at 12:14:26 on ‎21/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:27:51 on ‎20/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- 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:57:33 on ‎20/‎01/‎2025 was unexpected. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 12:05:20 on ‎20/‎01/‎2025 was unexpected. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240017: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.1449.0) - Current Channel (Broad). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Microsoft Defender Antivirus Service service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.1449.0) - Current Channel (Broad). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 16:47:28 on ‎19/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 16:19:41 on ‎19/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Update Orchestrator Service service terminated with the following error: The media is write protected. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 11:43:30 on ‎19/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The Downloaded Maps Manager service hung on starting. ------------------------------------------------------------------- The Energy Server Service queencreek service hung on starting. ------------------------------------------------------------------- Potentially revoked boot manager was detected in EFI partition. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the FontCache3.0.0.0 service. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Connected User Experiences and Telemetry service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The AppX Deployment Service (AppXSVC) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Gaming Services service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Windows Malicious Software Removal Tool x64 - v5.131 (KB890830). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: 2025-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5050411). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 05:54:42 on ‎19/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 10:21:20 on ‎12/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 14:58:30 on ‎10/‎01/‎2025 was unexpected. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek 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 {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 07:33:08 on ‎22/‎12/‎2024 was unexpected. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Diagnostic System Host service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Distributed Link Tracking Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Storage Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Program Compatibility Assistant Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Connections service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Connection Broker service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- The Human Interface Device Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Display Enhancement Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Device Association Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Audio Endpoint Builder service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 15:46:51 on ‎21/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240009: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.859.0) - Current Channel (Broad). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12f1:9eb5:1d47:e94f:eccf:1eb2 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Client License Service (ClipSVC) service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The AppX Deployment Service (AppXSVC) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.837.0) - Current Channel (Broad). ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- 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 Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1290" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The Windows Update service failed to start due to the following error: The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service. ------------------------------------------------------------------- DCOM got error "1290" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- The Windows Update service failed to start due to the following error: The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service. ------------------------------------------------------------------- The Device Setup Manager service failed to start due to the following error: The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service. ------------------------------------------------------------------- The Device Setup Manager service failed to start due to the following error: The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240016: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.804.0) - Current Channel (Broad). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the FontCache3.0.0.0 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SystemUsageReportSvc_QUEENCREEK service. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12ca:95cd:75da:f73e:32eb:6877 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f47:48ad:1d57:3602:4201:54f with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The AppX Deployment Service (AppXSVC) service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the AppX Deployment Service (AppXSVC) service to connect. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 07:42:00 on ‎12/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- Volume C: (\Device\HarddiskVolume4) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME " locally or remotely via PowerShell. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 04:02:37 on ‎12/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x800F0835: 2024-12 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5048652). ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Conexant - MEDIA - 7/26/2016 12:00:00 AM - 8.66.29.53. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 10:42:25 on ‎11/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {F9717507-6651-4EDB-BFF7-AE615179BCCF} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 15:51:45 on ‎10/‎12/‎2024 was unexpected. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Intel(R) System Usage Report Service SystemUsageReportSvc_QUEENCREEK service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Camera Frame Server service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 11:45:55 on ‎10/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Intel(R) SUR QC Software Asset Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12f7:3326:1349:4db9:8325:8d4f with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 13:26:35 on ‎09/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Windows Update service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3a77:6abb:d875:828a:23b5:dc80 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Diagnostic System Host service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Distributed Link Tracking Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Storage Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Program Compatibility Assistant Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Connections service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Connection Broker service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- The Human Interface Device Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Display Enhancement Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Device Association Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Audio Endpoint Builder service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f17:49b2:2b94:5275:9eb:7bab with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f27:4959:fcc9:a1b0:7847:3419 with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Microsoft.Windows.StartMenuExperienceHost_10.0.19041.5072_neutral_neutral_cw5n1h2txyewy!App did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 12:46:30 on ‎08/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12cc:7914:843d:e535:88ff:35f1 with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {2F87250D-063D-4871-9399-3A603DFA0E04} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {506E0B02-79C0-444C-B657-DDB69CD339FF} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {D529741A-1BF1-4D1E-9976-35089622E758} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {3E8C9ABE-9226-4609-BF5B-60288A391DEE} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {D529741A-1BF1-4D1E-9976-35089622E758} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {3E8C9ABE-9226-4609-BF5B-60288A391DEE} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {D529741A-1BF1-4D1E-9976-35089622E758} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {3E8C9ABE-9226-4609-BF5B-60288A391DEE} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {506E0B02-79C0-444C-B657-DDB69CD339FF} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {D529741A-1BF1-4D1E-9976-35089622E758} ------------------------------------------------------------------- DCOM got error "87" attempting to start the service GamingServices with arguments "Unavailable" in order to run the server: {3E8C9ABE-9226-4609-BF5B-60288A391DEE} ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- A corruption was discovered in the file system structure on volume C:. A corruption was found in a file system index structure. The file reference number is 0x2000000052ef0. The name of the file is "\Users\0000000000000\AppData\Local\Overwolf\Extensions\ojgnfnbjckbpfaciphphehonokbggjhpnnoafack\263.0.1\vendors". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION". ------------------------------------------------------------------- A corruption was discovered in the file system structure on volume C:. A corruption was found in a file system index structure. The file reference number is 0x2000000052e1b. The name of the file is "\Users\0000000000000\AppData\Local\Overwolf\Extensions\ojgnfnbjckbpfaciphphehonokbggjhpnnoafack\263.0.1\templates". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION". ------------------------------------------------------------------- A corruption was discovered in the file system structure on volume C:. A corruption was found in a file system index structure. The file reference number is 0x2000000052d3b. The name of the file is "\Users\0000000000000\AppData\Local\Overwolf\Extensions\ojgnfnbjckbpfaciphphehonokbggjhpnnoafack\263.0.1\styles". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION". ------------------------------------------------------------------- A corruption was discovered in the file system structure on volume C:. A corruption was found in a file system index structure. The file reference number is 0x2000000052ad5. The name of the file is "\Users\0000000000000\AppData\Local\Overwolf\Extensions\ojgnfnbjckbpfaciphphehonokbggjhpnnoafack\263.0.1\scripts". The corrupted index attribute is ":$I30:$INDEX_ALLOCATION". ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f17:48de:6cee:e7d5:217f:3f26 with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f17:496e:eee8:951:c203:d73a with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Intel(R) SUR QC Software Asset Manager service to connect. ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Windows Presentation Foundation Font Cache 3.0.0.0 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the Windows Presentation Foundation Font Cache 3.0.0.0 service to connect. ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Intel(R) SUR QC Software Asset Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 13:44:25 on ‎07/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The DSAUpdateService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the DSAUpdateService service to connect. ------------------------------------------------------------------- The SystemUsageReportSvc_QUEENCREEK service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (45000 milliseconds) while waiting for the SystemUsageReportSvc_QUEENCREEK service to connect. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Energy Server Service queencreek service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Gaming Services service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Gaming Services service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 08:59:55 on ‎07/‎12/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- The system watchdog timer was triggered. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2409:4066:eb4:cd4e:5eb5:c0f7:65bb:435f with the system having network hardware address 02-50-F3-00-08-04. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2409:4066:eb4:cd4e:5eb5:c0f7:65bb:435f with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2409:4066:eb4:cd4e:7d2b:1033:f1f6:af15 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240016: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.647.0) - Current Channel (Broad). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 08:13:52 on ‎30/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:7527:b873:cdc3:77e7:f4b7:4548 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240017: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.534.0) - Current Channel (Broad). ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system detected an address conflict for IP address 2409:4066:282:95eb:e7ec:63f3:4619:89e3 with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 12:15:28 on ‎29/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected an internal driver error on \Device\VBoxNetLwf. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:7531:a236:23ec:97b5:a06:6556 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 06:43:36 on ‎29/‎11/‎2024 was unexpected. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the BITS service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Appinfo service. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The system detected an address conflict for IP address 2409:4066:282:95eb:e7ec:63f3:4619:89e3 with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 13:35:40 on ‎14/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Diagnostic System Host service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Distributed Link Tracking Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Storage Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Program Compatibility Assistant Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Connections service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Connection Broker service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- The Human Interface Device Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Display Enhancement Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Device Association Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Audio Endpoint Builder service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 08:34:27 on ‎14/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Network Location Awareness service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 100 milliseconds: Restart the service. ------------------------------------------------------------------- The Workstation service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The DNS Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service. ------------------------------------------------------------------- The Cryptographic Services service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 16:18:25 on ‎13/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 15:52:37 on ‎13/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12dd:910d:f8fc:9f9d:61ea:12 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 07:04:50 on ‎13/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12d5:ae71:2ffa:51ec:e0e2:3ab1 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12c4:afd8:227a:d50a:b502:c260 with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12c2:a403:7aba:99fe:ba74:fc2 with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f27:489b:5c5e:c739:ea05:2b54 with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f37:58ca:c30e:e838:37dd:d847 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f47:48e4:9baa:815c:6361:4af5 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:3f37:49ee:95e6:91bf:693a:f802 with the system having network hardware address 02-50-F3-00-06-02. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 06:23:51 on ‎10/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 08:10:12 on ‎09/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 16:06:28 on ‎08/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The Gaming Services service terminated with the following error: This operation returned because the timeout period expired. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 15:59:58 on ‎08/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system detected an address conflict for IP address 2401:4900:12e0:7fc2:e4a2:33da:ec3e:5ff with the system having network hardware address 02-50-F3-00-07-03. Network operations on this system may be disrupted as a result. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this machine.. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931 ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 07:16:16 on ‎08/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 05:51:51 on ‎08/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The Windows Push Notifications System Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Management Instrumentation service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Update Orchestrator Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The User Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Web Account Manager service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Themes service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Shell Hardware Detection service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The System Event Notification Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Task Scheduler service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 0 milliseconds: Restart the service in a separate process. ------------------------------------------------------------------- The User Profile Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Geolocation Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 10000 milliseconds: Restart the service. ------------------------------------------------------------------- The Server service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The IP Helper service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Background Intelligent Transfer Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Application Information service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Storage Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 300000 milliseconds: Restart the service. ------------------------------------------------------------------- The Program Compatibility Assistant Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Connection Broker service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- The Display Enhancement Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Device Association Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Audio Endpoint Builder service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Diagnostic System Host service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Distributed Link Tracking Client service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Storage Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Program Compatibility Assistant Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Network Connection Broker service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- The Human Interface Device Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Display Enhancement Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Device Association Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Windows Audio Endpoint Builder 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 0x800706BE: 2024-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5044273). ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 04:35:50 on ‎08/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 13:21:50 on ‎07/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 12:52:42 on ‎07/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 12:34:45 on ‎07/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 11:23:54 on ‎07/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed successfully. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset. ------------------------------------------------------------------- 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 system watchdog timer was triggered. ------------------------------------------------------------------- The previous system shutdown at 11:11:04 on ‎07/‎11/‎2024 was unexpected. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.549981C3F5F10_4.2308.1005.0_x64__8wekyb3d8bbwe!App did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The SysMain service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Background Intelligent Transfer Service service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The Background Intelligent Transfer Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.Search_1.14.10.19041_neutral_neutral_cw5n1h2txyewy!ShellFeedsUI.AppXfbff151h5bmghg166fvn34ccayg70vts.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service BcastDVRUserService_4cc6e with arguments "Unavailable" in order to run the server: Windows.Media.Capture.Internal.AppCaptureShell ------------------------------------------------------------------- The GameDVR and Broadcast User Service_4cc6e service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the GameDVR and Broadcast User Service_4cc6e service to connect. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service BcastDVRUserService_4cc6e with arguments "Unavailable" in order to run the server: Windows.Media.Capture.Internal.AppCaptureShell ------------------------------------------------------------------- The GameDVR and Broadcast User Service_4cc6e service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the GameDVR and Broadcast User Service_4cc6e service to connect. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Intel(R) Content Protection HECI Service service terminated with the following error: No more data is available. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19041.3636.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Security Service service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service wuauserv with arguments "Unavailable" in order to run the server: {E60687F7-01A1-40AA-86AC-DB1CBF673334} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service TrustedInstaller with arguments "Unavailable" in order to run the server: {752073A1-23F2-4396-85F0-8FDB879ED0ED} ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80240017: Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.421.23.0) - Current Channel (Broad). ------------------------------------------------------------------- The Function Discovery Resource Publication service terminated with the following error: The requested address is not valid in its context. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Google Update Service (gupdate) service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Google Update Service (gupdatem) service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Steam Client Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. ------------------------------------------------------------------- The Intel(R) Content Protection HECI Service service terminated with the following error: No more data is available. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The Delivery Optimization service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. ------------------------------------------------------------------- The device Microsoft Remote Display Adapter (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The Windows Search service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The WerSvc service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The Network List Service service terminated with the following error: The device is not ready. ------------------------------------------------------------------- The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Connected Devices Platform Service service depends on the Network Connection Broker service which failed to start because of the following error: After starting, the service hung in a start-pending state. ------------------------------------------------------------------- The Network Connection Broker service hung on starting. ------------------------------------------------------------------- The Printer Extensions and Notifications service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. ------------------------------------------------------------------- The server {7D096C5F-AC08-4F1F-BEB7-5C22C517CE39} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Network List Service service terminated with the following error: The device is not ready. ------------------------------------------------------------------- The server {A47979D2-C419-11D9-A5B4-001185AD2B89} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The netprofm service terminated with the following error: The device is not ready. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 2/2/2025, 07:59:17 Machine name: DESKTOP-SFG6VCL Machine Id: {C515750A-A807-44E5-AECC-9FF90609438A} Operating System: Windows 10 Pro 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406) Language: English (Regional Setting: English) System Manufacturer: LENOVO System Model: 80QQ BIOS: E0CN45WW (type: UEFI) Processor: Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz (4 CPUs), ~2.0GHz Memory: 4096MB RAM Available OS Memory: 4008MB RAM Page File: 4247MB used, 5904MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.0.8 DxDiag Version: 10.00.19041.5198 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Display Tab 2: There is a problem with Intel(R) HD Graphics 5500 device. For more information, search for 'graphics device driver error code 31' 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) HD Graphics 5500 Manufacturer: Intel Corporation Chip type: Intel(R) HD Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_1616&SUBSYS_382A17AA&REV_09 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: 2516 MB Dedicated Memory: 512 MB Shared Memory: 2004 MB Current Mode: 1280 x 720 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Internal Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.584961,0.346680), Green(0.333984,0.569336), Blue(0.164062,0.117188), White Point(0.311523,0.338867) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: unknown Monitor Id: BOE061D Native Mode: 1366 x 768(p) (59.973Hz) Output Type: Internal Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll Driver File Version: 20.19.0015.4642 (English) Driver Version: 20.19.15.4642 DDI Version: 12 Feature Levels: 11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 2.0 Hardware Scheduling: Supported:False Enabled:False Graphics Preemption: Triangle Compute Preemption: Thread group Miracast: Supported Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Not Supported Block List: DISABLE_HWSCH Catalog Attributes: N/A Driver Attributes: Final Retail Driver Date/Size: 3/28/2017 12:00:00 AM, 39860744 bytes WHQL Logo'd: n/a WHQL Date Stamp: n/a Device Identifier: {D7B78E66-5556-11CF-3866-2518B5C2D935} Vendor ID: 0x8086 Device ID: 0x1616 SubSys ID: 0x382A17AA Revision ID: 0x0009 Driver Strong Name: oem29.inf:5f63e53468b7076c:iBDWM_w10:20.19.15.4642:pci\ven_8086&dev_1616&subsys_382a17aa Rank Of Driver: 00D10001 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 {9B8175D4-D670-4CF2-A9F0-FA56DF71A1AE} {8EFA5926-BD9E-4B04-8B72-8F977DC44C36} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} {442B942A-B4D9-4940-BC45-A882E5F919F3} {97688186-56A8-4094-B543-FC9DAAA49F4B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {F416F7BD-098A-4CF1-A11B-CE54959CA03D} {BF44DACD-217F-4370-A383-D573BC56707E} {D41289C2-ECF3-4EDE-9A04-3BBF9068A629} {2364D06A-F67F-4186-AED0-62B99E1784F1} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {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: 1 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported Card name: Intel(R) HD Graphics 5500 Manufacturer: Intel Corporation Chip type: Unknown DAC type: Unknown Device Type: n/a Device Key: Enum\ROOT\DISPLAY Device Status: 01802401 [DN_ROOT_ENUMERATED|DN_HAS_PROBLEM|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] Device Problem Code: 0000001F [CM_PROB_FAILED_ADD] Driver Problem Code: Unknown Display Memory: Unknown Dedicated Memory: n/a Shared Memory: n/a Current Mode: Unknown HDR Support: Unknown Display Topology: Unknown Display Color Space: Unknown Color Primaries: Unknown Display Luminance: Unknown Driver Name: igdumdim64.dll,igd10iumd64.dll,igd10iumd64.dll,igd12umd64.dll Driver File Version: 20.19.0015.4642 (English) Driver Version: 20.19.15.5171 DDI Version: unknown Feature Levels: Unknown Driver Model: Unknown Hardware Scheduling: Graphics Preemption: Unknown Compute Preemption: Unknown Miracast: Unknown Detachable GPU: No Hybrid Graphics GPU: Unknown Power P-states: Unknown Virtualization: Not Supported Block List: Unknown Catalog Attributes: Universal:False Declarative:False Driver Attributes: Final Retail Driver Date/Size: 11/4/2020 12:00:00 AM, 39860744 bytes WHQL Logo'd: n/a WHQL Date Stamp: n/a Device Identifier: Unknown Vendor ID: Unknown Device ID: Unknown SubSys ID: Unknown Revision ID: Unknown Driver Strong Name: oem8.inf:5f63e53468b7076c:iBDWM_w10:20.19.15.5171:pci\ven_8086&dev_1616 Rank Of Driver: 00D10000 Video Accel: Unknown DXVA2 Modes: Unknown Deinterlace Caps: n/a D3D9 Overlay: Unknown DXVA-HD: Unknown DDraw Status: Enabled D3D Status: Not Available AGP Status: Enabled MPO MaxPlanes: Unknown MPO Caps: Unknown MPO Stretch: Unknown MPO Media Hints: Unknown MPO Formats: Unknown PanelFitter Caps: Unknown PanelFitter Stretch: Unknown ------------- Sound Devices ------------- Description: Speakers (Conexant SmartAudio HD) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: HDAUDIO\FUNC_01&VEN_14F1&DEV_510F&SUBSYS_17AA3826&REV_1001 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: CHDRT64.sys Driver Version: 8.66.29.53 (English) Driver Attributes: Final Retail WHQL Logo'd: n/a Date and Size: 7/26/2016 12:00:00 AM, 1560608 bytes Other Files: Driver Provider: Conexant HW Accel Level: Emulation Only Cap Flags: 0x0 Min/Max Sample Rate: 0, 0 Static/Strm HW Mix Bufs: 0, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: Microphone (Conexant SmartAudio HD) Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: CHDRT64.sys Driver Version: 8.66.29.53 (English) Driver Attributes: Final Retail Date and Size: 7/26/2016 12:00:00 AM, 1560608 bytes Cap Flags: 0x0 Format Flags: 0x0 --------------------- Video Capture Devices Number of Devices: 1 --------------------- FriendlyName: Lenovo EasyCamera Category: Camera SymbolicLink: \\?\usb#vid_13d3&pid_5744&mi_00#6&2755c6f&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 Manufacturer: AzureWave HardwareID: USB\VID_13D3&PID_5744&REV_0731&MI_00,USB\VID_13D3&PID_5744&MI_00 DriverDesc: Lenovo EasyCamera DriverProvider: GenesysLogic DriverVersion: 8.0.1.2379 DriverDateEnglish: 3/24/2016 00:00:00 DriverDateLocalized: 3/24/2016 12:00:00 AM Service: glavcam Class: Image DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Lenovo EasyCamera Parent: USB\VID_13D3&PID_5744\5&25ecce01&0&6 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: n/a Stack: \Driver\ksthunk,\Driver\glavcam,\Driver\ACPI,\Driver\usbccgp ContainerCategory: Imaging.Webcam SensorGroupID: n/a MFT0: n/a DMFT: n/a CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: n/a EnableDshowRedirection: n/a FrameServerEnabled: n/a AnalogProviders: n/a ProfileIDs: n/a ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: usb keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0xC0F4, 0x05C0 FF Driver: n/a Device Name: usb keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0xC0F4, 0x05C0 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x9CB1 | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 11/8/2024 04:56:21, 649696 bytes | +-+ USB Composite Device | | Vendor/Product ID: 0xC0F4, 0x05C0 | | Location: Port_#0001.Hub_#0002 | | Matching Device ID: USB\COMPOSITE | | Service: usbccgp | | Driver: usbccgp.sys, 11/8/2024 04:56:21, 191968 bytes | | | +-+ USB Input Device | | | Vendor/Product ID: 0xC0F4, 0x05C0 | | | Location: 0000.0014.0000.001.000.000.000.000.000 | | | Matching Device ID: USB\Class_03&SubClass_01 | | | Service: HidUsb | | | Driver: hidusb.sys, 12/4/2023 02:43:54, 44032 bytes | | | Driver: hidclass.sys, 12/4/2023 02:43:54, 233472 bytes | | | Driver: hidparse.sys, 12/4/2023 02:43:54, 46080 bytes | | | | | +-+ HID Keyboard Device | | | | Vendor/Product ID: 0xC0F4, 0x05C0 | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | Service: kbdhid | | | | Driver: kbdhid.sys, 12/7/2019 09:07:56, 46592 bytes | | | | Driver: kbdclass.sys, 12/7/2019 09:07:56, 71480 bytes | | +-+ USB Input Device | | Vendor/Product ID: 0x093A, 0x2510 | | Location: Port_#0002.Hub_#0002 | | Matching Device ID: USB\Class_03&SubClass_01 | | Service: HidUsb | | Driver: hidusb.sys, 12/4/2023 02:43:54, 44032 bytes | | Driver: hidclass.sys, 12/4/2023 02:43:54, 233472 bytes | | Driver: hidparse.sys, 12/4/2023 02:43:54, 46080 bytes | | | +-+ USB HID-compliant mouse | | | Vendor/Product ID: 0x093A, 0x2510 | | | Matching Device ID: hid\vid_093a&pid_2510 | | | Service: Amusbprt | | | Driver: Amusbx64.sys, 11/4/2024 10:26:40, 17920 bytes | | | Driver: Amfltx64.sys, 11/4/2024 10:26:40, 12288 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 12/7/2019 09:07:56, 118272 bytes | Driver: kbdclass.sys, 12/7/2019 09:07:56, 71480 bytes | + ELAN pointing device | Matching Device ID: acpi\etd064d | Upper Filters: ETD | Service: i8042prt | Driver: ETD.sys, 8/14/2016 20:11:24, 594008 bytes | Driver: ETDCtrl.exe, 8/14/2016 20:11:56, 3805928 bytes | Driver: ETDUninst.dll, 8/14/2016 20:12:18, 2238184 bytes | Driver: ETDUn_inst.exe, 8/14/2016 20:12:16, 2741984 bytes | Driver: ETDApi.dll, 8/14/2016 20:11:34, 2664168 bytes | Driver: ETDDeviceInformation.exe, 8/14/2016 20:12:02, 2707688 bytes | Driver: ETDApi32.dll, 8/14/2016 20:11:36, 2093288 bytes | Driver: ETD_DLL.dll, 8/14/2016 20:11:28, 2243304 bytes | Driver: ETDService.exe, 8/14/2016 20:12:12, 134888 bytes | Driver: ETDCtrlHelper.exe, 8/14/2016 20:11:58, 2654432 bytes | Driver: ETDApix.dll, 8/14/2016 20:11:38, 2725608 bytes | Driver: ETDCmds.dll, 8/14/2016 20:11:48, 2863840 bytes | Driver: ETDMcpl.dll, 8/14/2016 20:12:10, 7192296 bytes | Driver: ETDFavorite.dll, 8/14/2016 20:12:04, 2287336 bytes | Driver: ETDTouch.exe, 8/14/2016 20:12:14, 130272 bytes | Driver: ETDAniConf.exe, 8/14/2016 20:11:32, 8861416 bytes | Driver: ETDIntelligent.exe, 8/14/2016 20:12:06, 2267368 bytes | Driver: Lenovo.exe, 8/14/2016 20:12:24, 2016488 bytes | Driver: Lenovo_Win8.exe, 8/14/2016 20:12:26, 2017000 bytes | Driver: LenovoAPI.dll, 8/14/2016 20:12:28, 2592488 bytes | Driver: Button_ClickPad.avi, 8/14/2016 19:45:42, 118272 bytes | Driver: Button_SmartPad.avi, 8/14/2016 19:45:42, 113152 bytes | Driver: DnD01.avi, 8/14/2016 19:45:44, 74752 bytes | Driver: DnD02.avi, 8/14/2016 19:45:44, 98304 bytes | Driver: DnD03.avi, 8/14/2016 19:45:44, 83456 bytes | Driver: Edge_Auto.avi, 8/14/2016 19:45:46, 4378624 bytes | Driver: Edge_Inertial.avi, 8/14/2016 19:45:46, 794112 bytes | Driver: Edge_Scroll.avi, 8/14/2016 19:45:46, 1215488 bytes | Driver: Rotation_Twist.avi, 8/14/2016 19:45:56, 212480 bytes | Driver: Rotation_Clockwise.avi, 8/14/2016 19:45:56, 110592 bytes | Driver: Scroll_Auto.avi, 8/14/2016 19:45:56, 2421760 bytes | Driver: Scroll_Inertial.avi, 8/14/2016 19:45:56, 1012224 bytes | Driver: Scroll_No_FreeScroll.avi, 8/14/2016 19:45:56, 686592 bytes | Driver: Swipe_3F_LR_PageupDown.avi, 8/14/2016 19:45:58, 300032 bytes | Driver: Tapping_1F.avi, 8/14/2016 19:45:58, 68608 bytes | Driver: Zooming.avi, 8/14/2016 19:45:58, 293888 bytes | Driver: Press_3F.avi, 8/14/2016 19:45:56, 90112 bytes | Driver: Continuous_EdgeScroll_H.avi, 8/14/2016 19:45:42, 1902080 bytes | Driver: Continuous_EdgeScroll_V.avi, 8/14/2016 19:45:44, 1576448 bytes | Driver: Continuous_Scroll_V_2F.avi, 8/14/2016 19:45:44, 2278400 bytes | Driver: Continuous_Scroll_H_2F.avi, 8/14/2016 19:45:44, 1594880 bytes | Driver: Scroll_Reverse_V.avi, 8/14/2016 19:45:56, 628224 bytes | Driver: Scroll_Reverse_H.avi, 8/14/2016 19:45:56, 409088 bytes | Driver: Edge_Reverse_V.avi, 8/14/2016 19:45:46, 579584 bytes | Driver: Edge_Reverse_H.avi, 8/14/2016 19:45:46, 407552 bytes | Driver: Win8EdgeSwipe_Left.avi, 8/14/2016 19:45:58, 720434 bytes | Driver: Win8EdgeSwipe_Right.avi, 8/14/2016 19:45:58, 147766 bytes | Driver: Win8EdgeSwipe_Top.avi, 8/14/2016 19:45:58, 267604 bytes | Driver: Continuous_EdgeScroll_Reverse-H.avi, 8/14/2016 19:45:44, 1902080 bytes | Driver: Continuous_EdgeScroll_Reverse-V.avi, 8/14/2016 19:45:44, 1569280 bytes | Driver: Continuous_Scroll_Reverse-H_2F.avi, 8/14/2016 19:45:44, 1637888 bytes | Driver: Continuous_Scroll_Reverse-V_2F.avi, 8/14/2016 19:45:44, 2237952 bytes | Driver: Edge_Auto_Reverse.avi, 8/14/2016 19:45:46, 2697216 bytes | Driver: Edge_Inertial_Reverse.avi, 8/14/2016 19:45:46, 792576 bytes | Driver: Scroll_Auto_Reverse.avi, 8/14/2016 19:45:56, 2393088 bytes | Driver: Scroll_Inertial_Reverse.avi, 8/14/2016 19:45:56, 1041920 bytes | Driver: PTP_Swipe_3F_Up_Down_Left_Right.avi, 8/14/2016 19:45:56, 889344 bytes | Driver: PTP_Tapping_3F_Cortana.avi, 8/14/2016 19:45:56, 84992 bytes | Driver: PTP_Tapping_4F_Notification_Center.avi, 8/14/2016 19:45:56, 674304 bytes | Driver: ETDSetup.ini, 8/14/2016 19:45:52, 2223401 bytes | Driver: mouclass.sys, 12/7/2019 09:07:56, 67600 bytes | Driver: i8042prt.sys, 12/7/2019 09:07:56, 118272 bytes | Driver: ETDCoInstaller15012.dll, 8/14/2016 20:11:50, 198888 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 237.5 GB Total Space: 452.7 GB File System: NTFS Model: ST1000LM024 HN-M101MBB Drive: D: Free Space: 196.0 GB Total Space: 500.0 GB File System: NTFS Model: ST1000LM024 HN-M101MBB Drive: F: Model: HL-DT-ST DVDRAM GUE0N Driver: C:\WINDOWS\SYSTEM32\DRIVERS\CDROM.SYS, 10.00.19041.4355 (English), 11/8/2024 04:56:18, 175616 bytes -------------- System Devices -------------- Name: Mobile 5th Generation Intel(R) Core(TM) PCI Express Root Port #3 - 9C94 Device ID: PCI\VEN_8086&DEV_9C94&SUBSYS_382A17AA&REV_E3\3&11583659&0&E2 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.4842 (English), 11/8/2024 04:56:19, 479736 bytes Name: Mobile 5th Generation Intel(R) Core(TM) USB EHCI Controller - 9CA6 Device ID: PCI\VEN_8086&DEV_9CA6&SUBSYS_382A17AA&REV_03\3&11583659&0&E8 Driver: C:\Windows\system32\drivers\usbehci.sys, 10.00.19041.4474 (English), 11/8/2024 04:56:21, 87408 bytes Driver: C:\Windows\system32\drivers\usbport.sys, 10.00.19041.4474 (English), 11/8/2024 04:56:21, 474592 bytes Driver: C:\Windows\system32\drivers\usbhub.sys, 10.00.19041.4474 (English), 11/8/2024 04:56:21, 527344 bytes Name: Mobile 5th Generation Intel(R) Core(TM) Host Bridge - OPI - 1604 Device ID: PCI\VEN_8086&DEV_1604&SUBSYS_382A17AA&REV_09\3&11583659&0&00 Driver: n/a Name: Realtek PCIe FE Family Controller Device ID: PCI\VEN_10EC&DEV_8136&SUBSYS_383C17AA&REV_08\01000000364CE00000 Driver: C:\Windows\system32\DRIVERS\rt640x64.sys, 10.50.0511.2021 (English), 11/4/2024 10:25:20, 1151992 bytes Name: Mobile 5th Generation Intel(R) Core(TM) PCI Express Root Port #1 - 9C90 Device ID: PCI\VEN_8086&DEV_9C90&SUBSYS_382A17AA&REV_E3\3&11583659&0&E0 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.4842 (English), 11/8/2024 04:56:19, 479736 bytes Name: Mobile 5th Generation Intel(R) Core(TM) SMBus Controller - 9CA2 Device ID: PCI\VEN_8086&DEV_9CA2&SUBSYS_382A17AA&REV_03\3&11583659&0&FB Driver: n/a Name: Intel(R) 9 Series Chipset Family SATA AHCI Controller Device ID: PCI\VEN_8086&DEV_9C83&SUBSYS_382A17AA&REV_03\3&11583659&0&FA Driver: C:\Windows\system32\DRIVERS\iaStorA.sys, 14.08.0016.1063 (English), 11/4/2024 10:18:59, 1469952 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_9CBA&SUBSYS_382A17AA&REV_03\3&11583659&0&B0 Driver: C:\Windows\System32\DriverStore\FileRepository\heci.inf_amd64_0f5b7bb40dc5cf1b\x64\TeeDriverW10x64.sys, 2433.06.0003.0000 (English), 11/4/2024 10:23:26, 325488 bytes Name: Intel(R) HD Graphics 5500 Device ID: PCI\VEN_8086&DEV_1616&SUBSYS_382A17AA&REV_09\3&11583659&0&10 Driver: C:\Windows\system32\DRIVERS\igdkmd64.sys, 20.19.0015.4642 (English), 5/26/2017 05:10:38, 7970232 bytes Driver: C:\Windows\system32\igd10iumd64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:04, 16456200 bytes Driver: C:\Windows\system32\igd10idpp64.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:52, 312248 bytes Driver: C:\Windows\system32\igd11dxva64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:12, 33470408 bytes Driver: C:\Windows\system32\igd12umd64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:18, 4268480 bytes Driver: C:\Windows\system32\igdumdim64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:42, 39860744 bytes Driver: C:\Windows\system32\igdail64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:26, 192968 bytes Driver: C:\Windows\system32\igfxcmrt64.dll, 5.00.0000.1148 (English), 5/26/2017 05:11:08, 183928 bytes Driver: C:\Windows\system32\igfx11cmrt64.dll, 5.00.0000.1148 (English), 5/26/2017 05:11:00, 182904 bytes Driver: C:\Windows\system32\igfxcmjit64.dll, 5.00.0000.1148 (English), 5/26/2017 05:10:54, 1590728 bytes Driver: C:\Windows\system32\igdde64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:28, 222680 bytes Driver: C:\Windows\system32\IntelCpHDCPSvc.exe, 1.00.0000.0001 (English), 5/26/2017 05:12:06, 448952 bytes Driver: C:\Windows\system32\igdusc64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:50, 6693088 bytes Driver: C:\Windows\system32\igc64.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:44, 15477928 bytes Driver: C:\Windows\system32\igdmd64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:34, 2393112 bytes Driver: C:\Windows\SysWow64\igd10iumd32.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:58, 13071112 bytes Driver: C:\Windows\SysWow64\igd10idpp32.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:46, 297112 bytes Driver: C:\Windows\SysWow64\igd11dxva32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:06, 34823400 bytes Driver: C:\Windows\SysWow64\igd12umd32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:14, 4240160 bytes Driver: C:\Windows\SysWow64\igdumdim32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:38, 38903336 bytes Driver: C:\Windows\SysWow64\igdail32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:24, 173520 bytes Driver: C:\Windows\SysWow64\igdde32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:22, 181784 bytes Driver: C:\Windows\SysWow64\igfxcmrt32.dll, 5.00.0000.1148 (English), 5/26/2017 05:11:04, 160216 bytes Driver: C:\Windows\SysWow64\igfx11cmrt32.dll, 5.00.0000.1148 (English), 5/26/2017 05:10:54, 160216 bytes Driver: C:\Windows\SysWow64\igfxcmjit32.dll, 5.00.0000.1148 (English), 5/26/2017 05:10:50, 1178576 bytes Driver: C:\Windows\SysWow64\igdusc32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:46, 5137760 bytes Driver: C:\Windows\SysWow64\igc32.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:38, 13483144 bytes Driver: C:\Windows\SysWow64\igdmd32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:30, 1858584 bytes Driver: C:\Windows\SysWow64\iglhcp32.dll, 3.00.0001.0026 (English), 5/26/2017 05:11:18, 205304 bytes Driver: C:\Windows\SysWow64\iglhsip32.dll, 9.00.0030.9000 (English), 5/26/2017 05:11:26, 1814008 bytes Driver: C:\Windows\SysWow64\IntelCpHeciSvc.exe, 9.00.0031.9015 (English), 5/26/2017 05:12:10, 301488 bytes Driver: C:\Windows\system32\iglhxs64.vp, 5/26/2017 02:03:40, 4862 bytes Driver: C:\Windows\system32\iglhxo64.vp, 5/26/2017 02:03:40, 40343 bytes Driver: C:\Windows\system32\iglhxc64.vp, 5/26/2017 02:03:40, 40316 bytes Driver: C:\Windows\system32\iglhxg64.vp, 5/26/2017 02:03:40, 39658 bytes Driver: C:\Windows\system32\iglhxo64_dev.vp, 5/26/2017 02:03:40, 40931 bytes Driver: C:\Windows\system32\iglhxc64_dev.vp, 5/26/2017 02:03:40, 41296 bytes Driver: C:\Windows\system32\iglhxg64_dev.vp, 5/26/2017 02:03:40, 39798 bytes Driver: C:\Windows\system32\iglhxa64.vp, 5/26/2017 02:03:40, 1125 bytes Driver: C:\Windows\system32\iglhxa64.cpa, 5/26/2017 02:03:40, 2813952 bytes Driver: C:\Windows\system32\iglhcp64.dll, 3.00.0001.0026 (English), 5/26/2017 05:11:22, 242104 bytes Driver: C:\Windows\system32\iglhsip64.dll, 9.00.0030.9000 (English), 5/26/2017 05:11:28, 1816664 bytes Driver: C:\Windows\system32\cp_resources.bin, 8/31/2020 11:05:54, 511260 bytes Driver: C:\Windows\system32\difx64.exe, 1.04.0003.0000 (English), 5/26/2017 05:09:46, 175032 bytes Driver: C:\Windows\system32\igfxDH.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:06, 755152 bytes Driver: C:\Windows\system32\igfxDHLib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:08, 84944 bytes Driver: C:\Windows\system32\igfxDHLibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:10, 95184 bytes Driver: C:\Windows\system32\igfxDI.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:12, 398280 bytes Driver: C:\Windows\system32\igfxDILib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:16, 29136 bytes Driver: C:\Windows\system32\igfxDILibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:18, 29136 bytes Driver: C:\Windows\system32\igfxLHM.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:40, 2141648 bytes Driver: C:\Windows\system32\igfxLHMLib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:42, 22480 bytes Driver: C:\Windows\system32\igfxLHMLibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:44, 22480 bytes Driver: C:\Windows\system32\igfxSDK.exe, 5/26/2017 05:11:50, 1023920 bytes Driver: C:\Windows\system32\igfxSDKLib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:52, 100816 bytes Driver: C:\Windows\system32\igfxSDKLibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:54, 111568 bytes Driver: C:\Windows\system32\igfxEM.exe, 6.15.0010.4642 (English), 5/26/2017 05:11:24, 354232 bytes Driver: C:\Windows\system32\igfxEMLib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:26, 27592 bytes Driver: C:\Windows\system32\igfxEMLibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:28, 27600 bytes Driver: C:\Windows\system32\GfxUIEx.exe, 6.15.0010.4642 (English), 5/26/2017 05:09:58, 466872 bytes Driver: C:\Windows\system32\Gfxv4_0.exe, 8.15.0010.4642 (English), 5/26/2017 05:10:04, 968112 bytes Driver: C:\Windows\system32\Gfxv4_0.exe.config, 8/31/2020 11:05:54, 935 bytes Driver: C:\Windows\system32\Gfxv2_0.exe, 8.15.0010.4642 (English), 5/26/2017 05:10:02, 964536 bytes Driver: C:\Windows\system32\Gfxv2_0.exe.config, 8/31/2020 11:05:54, 895 bytes Driver: C:\Windows\system32\GfxResources.dll, 8.15.0010.4642 (English), 5/26/2017 05:09:54, 5262800 bytes Driver: C:\Windows\system32\MetroIntelGenericUIFramework.dll, 1.00.0000.0000 (English), 5/26/2017 05:12:56, 704976 bytes Driver: C:\Windows\system32\igfxCUIServicePS.dll, 5/26/2017 05:11:02, 103376 bytes Driver: C:\Windows\system32\igfxCUIService.exe, 6.15.0010.4642 (English), 5/26/2017 05:10:58, 373680 bytes Driver: C:\Windows\system32\igfxCPL.cpl, 5/26/2017 05:10:56, 273360 bytes Driver: C:\Windows\system32\igfxTray.exe, 5/26/2017 05:11:56, 401840 bytes Driver: C:\Windows\system32\igfxDTCM.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:22, 254928 bytes Driver: C:\Windows\system32\igfxHK.exe, 6.15.0010.4642 (English), 5/26/2017 05:11:36, 268208 bytes Driver: C:\Windows\system32\igfxOSP.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:46, 389584 bytes Driver: C:\Windows\system32\DPTopologyApp.exe, 8.15.0010.4642 (English), 5/26/2017 05:09:50, 232368 bytes Driver: C:\Windows\system32\DPTopologyApp.exe.config, 8/31/2020 11:05:54, 935 bytes Driver: C:\Windows\system32\DPTopologyAppv2_0.exe, 8.15.0010.4642 (English), 5/26/2017 05:09:52, 231864 bytes Driver: C:\Windows\system32\DPTopologyAppv2_0.exe.config, 8/31/2020 11:05:54, 895 bytes Driver: C:\Windows\system32\igfxext.exe, 6.15.0010.4642 (English), 5/26/2017 05:11:34, 236472 bytes Driver: C:\Windows\system32\igfxexps.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:14, 55192 bytes Driver: C:\Windows\system32\ColorImageEnhancement.wmv, 8/31/2020 11:05:54, 375173 bytes Driver: C:\Windows\system32\ImageStabilization.wmv, 8/31/2020 11:05:58, 403671 bytes Driver: C:\Windows\system32\FilmModeDetection.wmv, 8/31/2020 11:05:54, 641530 bytes Driver: C:\Windows\SysWow64\igfxexps32.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:32, 52688 bytes Driver: C:\Windows\system32\ig8icd64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:16, 13650384 bytes Driver: C:\Windows\SysWow64\ig8icd32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:12, 10329032 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\llvm_release_license.txt, 11/3/2024 05:16:23, 1981 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\readme.txt, 11/3/2024 05:16:26, 9788 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\version.ini, 11/3/2024 05:16:26, 34 bytes Driver: C:\Windows\SysWow64\Intel_OpenCL_ICD32.dll, 2.00.0002.0000 (English), 5/26/2017 05:12:52, 103888 bytes Driver: C:\Windows\SysWow64\IntelOpenCL32.dll, 20.19.0015.4642 (English), 5/26/2017 05:12:10, 318416 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\task_executor32.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:16, 373192 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\OclCpuBackend32.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:16, 7126480 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\intelocl32.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:08, 1408464 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\cpu_device32.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:02, 522704 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8.rtl, 11/3/2024 05:16:22, 1223604 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.o, 11/3/2024 05:16:22, 296664 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.rtl, 11/3/2024 05:16:22, 389300 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9.rtl, 11/3/2024 05:16:22, 1157132 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.o, 11/3/2024 05:16:22, 287436 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.rtl, 11/3/2024 05:16:22, 389180 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9.rtl, 11/3/2024 05:16:22, 785172 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.o, 11/3/2024 05:16:22, 249992 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.rtl, 11/3/2024 05:16:22, 350952 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clang_compiler32.dll, 5.02.0000.10094 (English), 5/26/2017 05:13:56, 242640 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_n8.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:22, 5022664 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_g9.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:20, 5360080 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_s9.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:24, 5238224 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbbmalloc.dll, 4.02.2014.0601 (English), 5/26/2017 05:14:18, 208488 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbb.dll, 4.02.2014.0601 (English), 5/26/2017 05:14:18, 360040 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbb_preview.dll, 4.02.2013.1002 (), 5/26/2017 05:14:20, 355944 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\common\clbltfnshared.rtl, 11/3/2024 05:16:22, 1026520 bytes Driver: C:\Windows\system32\Intel_OpenCL_ICD64.dll, 2.00.0002.0000 (English), 5/26/2017 05:12:54, 99792 bytes Driver: C:\Windows\system32\IntelOpenCL64.dll, 20.19.0015.4642 (English), 5/26/2017 05:12:14, 416208 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\task_executor64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:18, 428496 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\OclCpuBackend64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:16, 9629128 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\intelocl64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:12, 1628112 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\cpu_device64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:06, 669136 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8.rtl, 11/3/2024 05:16:22, 1226660 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.o, 11/3/2024 05:16:22, 358288 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.rtl, 11/3/2024 05:16:22, 402580 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9.rtl, 11/3/2024 05:16:22, 1159784 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.o, 11/3/2024 05:16:22, 347104 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.rtl, 11/3/2024 05:16:22, 402468 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9.rtl, 11/3/2024 05:16:22, 788292 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.o, 11/3/2024 05:16:22, 294032 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.rtl, 11/3/2024 05:16:22, 364424 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clang_compiler64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:00, 267728 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_h8.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:22, 5234120 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_e9.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:20, 5744592 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_l9.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:22, 5627336 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbbmalloc.dll, 4.02.2014.0601 (English), 5/26/2017 05:14:18, 248424 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbb.dll, 4.02.2014.0601 (English), 5/26/2017 05:14:18, 438376 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbb_preview.dll, 4.02.2013.1002 (), 5/26/2017 05:14:20, 433768 bytes Driver: C:\Windows\SysWow64\IntelOpenCL32.dll, 20.19.0015.4642 (English), 5/26/2017 05:12:10, 318416 bytes Driver: C:\Windows\SysWow64\igdbcl32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:28, 388560 bytes Driver: C:\Windows\SysWow64\igdrcl32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:46, 4368840 bytes Driver: C:\Windows\SysWow64\common_clang32.dll, 4.00.0000.0000 (English), 5/26/2017 05:09:36, 19861456 bytes Driver: C:\Windows\SysWow64\igdmcl32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:42, 3972048 bytes Driver: C:\Windows\SysWow64\igdfcl32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:32, 225232 bytes Driver: C:\Windows\system32\IntelOpenCL64.dll, 20.19.0015.4642 (English), 5/26/2017 05:12:14, 416208 bytes Driver: C:\Windows\system32\igdbcl64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:30, 438736 bytes Driver: C:\Windows\system32\igdrcl64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:50, 4931024 bytes Driver: C:\Windows\system32\common_clang64.dll, 4.00.0000.0000 (English), 5/26/2017 05:09:40, 29101512 bytes Driver: C:\Windows\system32\igdmcl64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:44, 5683664 bytes Driver: C:\Windows\system32\igdfcl64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:34, 266192 bytes Driver: C:\Windows\system32\igdclbif.bin, 8/31/2020 11:05:56, 5799386 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw32.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:32, 8872536 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin32_hw.dll, 1.16.0010.0020 (English), 5/26/2017 05:13:00, 4741280 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:38, 1457080 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:16, 1350304 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp8vd_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:40, 1358496 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9vd_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:46, 1358496 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:44, 1471384 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_32.vp, 8/31/2020 11:05:54, 63761 bytes Driver: C:\Program Files\Intel\Media SDK\he_32.vp, 8/31/2020 11:05:54, 62217 bytes Driver: C:\Program Files\Intel\Media SDK\c_32.cpa, 8/31/2020 11:05:54, 846855 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_32.vp, 8/31/2020 11:05:54, 993 bytes Driver: C:\Program Files\Intel\Media SDK\dev_32.vp, 8/31/2020 11:05:54, 21523 bytes Driver: C:\Program Files\Intel\Media SDK\mj_32.vp, 8/31/2020 11:06:00, 57541 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw64.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:34, 9318328 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin64_hw.dll, 1.16.0010.0020 (English), 5/26/2017 05:13:02, 4919456 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:42, 1810840 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:20, 1677472 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp8vd_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:42, 1686168 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9vd_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:48, 1687200 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:48, 1836696 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_64.vp, 8/31/2020 11:05:54, 13485 bytes Driver: C:\Program Files\Intel\Media SDK\he_64.vp, 8/31/2020 11:05:54, 12873 bytes Driver: C:\Program Files\Intel\Media SDK\c_64.cpa, 8/31/2020 11:05:54, 1519616 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_64.vp, 8/31/2020 11:05:54, 993 bytes Driver: C:\Program Files\Intel\Media SDK\dev_64.vp, 8/31/2020 11:05:54, 21523 bytes Driver: C:\Program Files\Intel\Media SDK\mj_64.vp, 8/31/2020 11:06:00, 12365 bytes Driver: C:\Windows\system32\igfxCoIn_v4642.dll, 1.03.0024.0000 (English), 5/26/2017 05:12:00, 220104 bytes Driver: C:\Windows\system32\DisplayAudiox64.cab, 5/26/2017 02:03:38, 831685 bytes Name: Realtek RTL8723BE Wireless LAN 802.11n PCI-E NIC Device ID: PCI\VEN_10EC&DEV_B723&SUBSYS_B72817AA&REV_00\0023B7FEFF4CE00000 Driver: C:\Windows\system32\DRIVERS\rtwlane02.sys, 2024.00.0004.0208 (English), 11/4/2024 10:24:40, 9625384 bytes Driver: C:\Windows\system32\DRIVERS\rtldata02.txt, 11/4/2024 10:24:39, 94129 bytes Name: Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft) Device ID: PCI\VEN_8086&DEV_9CB1&SUBSYS_382A17AA&REV_03\3&11583659&0&A0 Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.19041.4355 (English), 11/8/2024 04:56:22, 620512 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.19041.4355 (English), 11/8/2024 04:56:22, 143792 bytes Name: Mobile 5th Generation Intel(R) Core(TM) PCI Express Root Port #4 - 9C96 Device ID: PCI\VEN_8086&DEV_9C96&SUBSYS_382A17AA&REV_E3\3&11583659&0&E3 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.19041.4842 (English), 11/8/2024 04:56:19, 479736 bytes Name: High Definition Audio Controller Device ID: PCI\VEN_8086&DEV_9CA0&SUBSYS_382A17AA&REV_03\3&11583659&0&D8 Driver: C:\Windows\system32\DRIVERS\hdaudbus.sys, 10.00.19041.4957 (English), 11/8/2024 04:56:12, 138752 bytes Driver: C:\Windows\system32\DRIVERS\drmk.sys, 10.00.19041.5072 (English), 12/7/2024 13:26:44, 97792 bytes Driver: C:\Windows\system32\DRIVERS\portcls.sys, 10.00.19041.5072 (English), 12/7/2024 13:26:44, 388608 bytes Name: Mobile 5th Generation Intel(R) Core(TM) Base SKU LPC Controller - 9CC5 Device ID: PCI\VEN_8086&DEV_9CC5&SUBSYS_382A17AA&REV_03\3&11583659&0&F8 Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 10.00.19041.3636 (English), 12/4/2023 02:43:52, 21480 bytes Name: Intel(R) HD Graphics 5500 Device ID: ROOT\DISPLAY\0000 Driver: C:\Windows\system32\DRIVERS\igdkmd64.sys, 20.19.0015.4642 (English), 5/26/2017 05:10:38, 7970232 bytes Driver: C:\Windows\system32\igd10iumd64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:04, 16456200 bytes Driver: C:\Windows\system32\igd10idpp64.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:52, 312248 bytes Driver: C:\Windows\system32\igd11dxva64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:12, 33470408 bytes Driver: C:\Windows\system32\igd12umd64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:18, 4268480 bytes Driver: C:\Windows\system32\igdumdim64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:42, 39860744 bytes Driver: C:\Windows\system32\igdail64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:26, 192968 bytes Driver: C:\Windows\system32\igfxcmrt64.dll, 5.00.0000.1148 (English), 5/26/2017 05:11:08, 183928 bytes Driver: C:\Windows\system32\igfx11cmrt64.dll, 5.00.0000.1148 (English), 5/26/2017 05:11:00, 182904 bytes Driver: C:\Windows\system32\igfxcmjit64.dll, 5.00.0000.1148 (English), 5/26/2017 05:10:54, 1590728 bytes Driver: C:\Windows\system32\igdde64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:28, 222680 bytes Driver: C:\Windows\system32\IntelCpHDCPSvc.exe, 1.00.0000.0001 (English), 5/26/2017 05:12:06, 448952 bytes Driver: C:\Windows\system32\igdusc64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:50, 6693088 bytes Driver: C:\Windows\system32\igc64.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:44, 15477928 bytes Driver: C:\Windows\system32\igdmd64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:34, 2393112 bytes Driver: C:\Windows\SysWow64\igd10iumd32.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:58, 13071112 bytes Driver: C:\Windows\SysWow64\igd10idpp32.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:46, 297112 bytes Driver: C:\Windows\SysWow64\igd11dxva32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:06, 34823400 bytes Driver: C:\Windows\SysWow64\igd12umd32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:14, 4240160 bytes Driver: C:\Windows\SysWow64\igdumdim32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:38, 38903336 bytes Driver: C:\Windows\SysWow64\igdail32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:24, 173520 bytes Driver: C:\Windows\SysWow64\igdde32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:22, 181784 bytes Driver: C:\Windows\SysWow64\igfxcmrt32.dll, 5.00.0000.1148 (English), 5/26/2017 05:11:04, 160216 bytes Driver: C:\Windows\SysWow64\igfx11cmrt32.dll, 5.00.0000.1148 (English), 5/26/2017 05:10:54, 160216 bytes Driver: C:\Windows\SysWow64\igfxcmjit32.dll, 5.00.0000.1148 (English), 5/26/2017 05:10:50, 1178576 bytes Driver: C:\Windows\SysWow64\igdusc32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:46, 5137760 bytes Driver: C:\Windows\SysWow64\igc32.dll, 20.19.0015.4642 (English), 5/26/2017 05:09:38, 13483144 bytes Driver: C:\Windows\SysWow64\igdmd32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:30, 1858584 bytes Driver: C:\Windows\SysWow64\iglhcp32.dll, 3.00.0001.0026 (English), 5/26/2017 05:11:18, 205304 bytes Driver: C:\Windows\SysWow64\iglhsip32.dll, 9.00.0030.9000 (English), 5/26/2017 05:11:26, 1814008 bytes Driver: C:\Windows\SysWow64\IntelCpHeciSvc.exe, 9.00.0031.9015 (English), 5/26/2017 05:12:10, 301488 bytes Driver: C:\Windows\system32\iglhxs64.vp, 5/26/2017 02:03:40, 4862 bytes Driver: C:\Windows\system32\iglhxo64.vp, 5/26/2017 02:03:40, 40343 bytes Driver: C:\Windows\system32\iglhxc64.vp, 5/26/2017 02:03:40, 40316 bytes Driver: C:\Windows\system32\iglhxg64.vp, 5/26/2017 02:03:40, 39658 bytes Driver: C:\Windows\system32\iglhxo64_dev.vp, 5/26/2017 02:03:40, 40931 bytes Driver: C:\Windows\system32\iglhxc64_dev.vp, 5/26/2017 02:03:40, 41296 bytes Driver: C:\Windows\system32\iglhxg64_dev.vp, 5/26/2017 02:03:40, 39798 bytes Driver: C:\Windows\system32\iglhxa64.vp, 5/26/2017 02:03:40, 1125 bytes Driver: C:\Windows\system32\iglhxa64.cpa, 5/26/2017 02:03:40, 2813952 bytes Driver: C:\Windows\system32\iglhcp64.dll, 3.00.0001.0026 (English), 5/26/2017 05:11:22, 242104 bytes Driver: C:\Windows\system32\iglhsip64.dll, 9.00.0030.9000 (English), 5/26/2017 05:11:28, 1816664 bytes Driver: C:\Windows\system32\cp_resources.bin, 8/31/2020 11:05:54, 511260 bytes Driver: C:\Windows\system32\difx64.exe, 1.04.0003.0000 (English), 5/26/2017 05:09:46, 175032 bytes Driver: C:\Windows\system32\igfxDH.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:06, 755152 bytes Driver: C:\Windows\system32\igfxDHLib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:08, 84944 bytes Driver: C:\Windows\system32\igfxDHLibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:10, 95184 bytes Driver: C:\Windows\system32\igfxDI.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:12, 398280 bytes Driver: C:\Windows\system32\igfxDILib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:16, 29136 bytes Driver: C:\Windows\system32\igfxDILibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:18, 29136 bytes Driver: C:\Windows\system32\igfxLHM.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:40, 2141648 bytes Driver: C:\Windows\system32\igfxLHMLib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:42, 22480 bytes Driver: C:\Windows\system32\igfxLHMLibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:44, 22480 bytes Driver: C:\Windows\system32\igfxSDK.exe, 5/26/2017 05:11:50, 1023920 bytes Driver: C:\Windows\system32\igfxSDKLib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:52, 100816 bytes Driver: C:\Windows\system32\igfxSDKLibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:54, 111568 bytes Driver: C:\Windows\system32\igfxEM.exe, 6.15.0010.4642 (English), 5/26/2017 05:11:24, 354232 bytes Driver: C:\Windows\system32\igfxEMLib.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:26, 27592 bytes Driver: C:\Windows\system32\igfxEMLibv2_0.dll, 1.00.0000.0000 (Invariant Language), 5/26/2017 05:11:28, 27600 bytes Driver: C:\Windows\system32\GfxUIEx.exe, 6.15.0010.4642 (English), 5/26/2017 05:09:58, 466872 bytes Driver: C:\Windows\system32\Gfxv4_0.exe, 8.15.0010.4642 (English), 5/26/2017 05:10:04, 968112 bytes Driver: C:\Windows\system32\Gfxv4_0.exe.config, 8/31/2020 11:05:54, 935 bytes Driver: C:\Windows\system32\Gfxv2_0.exe, 8.15.0010.4642 (English), 5/26/2017 05:10:02, 964536 bytes Driver: C:\Windows\system32\Gfxv2_0.exe.config, 8/31/2020 11:05:54, 895 bytes Driver: C:\Windows\system32\GfxResources.dll, 8.15.0010.4642 (English), 5/26/2017 05:09:54, 5262800 bytes Driver: C:\Windows\system32\MetroIntelGenericUIFramework.dll, 1.00.0000.0000 (English), 5/26/2017 05:12:56, 704976 bytes Driver: C:\Windows\system32\igfxCUIServicePS.dll, 5/26/2017 05:11:02, 103376 bytes Driver: C:\Windows\system32\igfxCUIService.exe, 6.15.0010.4642 (English), 5/26/2017 05:10:58, 373680 bytes Driver: C:\Windows\system32\igfxCPL.cpl, 5/26/2017 05:10:56, 273360 bytes Driver: C:\Windows\system32\igfxTray.exe, 5/26/2017 05:11:56, 401840 bytes Driver: C:\Windows\system32\igfxDTCM.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:22, 254928 bytes Driver: C:\Windows\system32\igfxHK.exe, 6.15.0010.4642 (English), 5/26/2017 05:11:36, 268208 bytes Driver: C:\Windows\system32\igfxOSP.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:46, 389584 bytes Driver: C:\Windows\system32\DPTopologyApp.exe, 8.15.0010.4642 (English), 5/26/2017 05:09:50, 232368 bytes Driver: C:\Windows\system32\DPTopologyApp.exe.config, 8/31/2020 11:05:54, 935 bytes Driver: C:\Windows\system32\DPTopologyAppv2_0.exe, 8.15.0010.4642 (English), 5/26/2017 05:09:52, 231864 bytes Driver: C:\Windows\system32\DPTopologyAppv2_0.exe.config, 8/31/2020 11:05:54, 895 bytes Driver: C:\Windows\system32\igfxext.exe, 6.15.0010.4642 (English), 5/26/2017 05:11:34, 236472 bytes Driver: C:\Windows\system32\igfxexps.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:14, 55192 bytes Driver: C:\Windows\system32\ColorImageEnhancement.wmv, 8/31/2020 11:05:54, 375173 bytes Driver: C:\Windows\system32\ImageStabilization.wmv, 8/31/2020 11:05:58, 403671 bytes Driver: C:\Windows\system32\FilmModeDetection.wmv, 8/31/2020 11:05:54, 641530 bytes Driver: C:\Windows\SysWow64\igfxexps32.dll, 6.15.0010.4642 (English), 5/26/2017 05:11:32, 52688 bytes Driver: C:\Windows\system32\ig8icd64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:16, 13650384 bytes Driver: C:\Windows\SysWow64\ig8icd32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:12, 10329032 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\llvm_release_license.txt, 11/3/2024 05:16:23, 1981 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\readme.txt, 11/3/2024 05:16:26, 9788 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\version.ini, 11/3/2024 05:16:26, 34 bytes Driver: C:\Windows\SysWow64\Intel_OpenCL_ICD32.dll, 2.00.0002.0000 (English), 5/26/2017 05:12:52, 103888 bytes Driver: C:\Windows\SysWow64\IntelOpenCL32.dll, 20.19.0015.4642 (English), 5/26/2017 05:12:10, 318416 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\task_executor32.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:16, 373192 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\OclCpuBackend32.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:16, 7126480 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\intelocl32.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:08, 1408464 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\cpu_device32.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:02, 522704 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8.rtl, 11/3/2024 05:16:22, 1223604 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.o, 11/3/2024 05:16:22, 296664 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.rtl, 11/3/2024 05:16:22, 389300 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9.rtl, 11/3/2024 05:16:22, 1157132 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.o, 11/3/2024 05:16:22, 287436 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.rtl, 11/3/2024 05:16:22, 389180 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9.rtl, 11/3/2024 05:16:22, 785172 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.o, 11/3/2024 05:16:22, 249992 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.rtl, 11/3/2024 05:16:22, 350952 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clang_compiler32.dll, 5.02.0000.10094 (English), 5/26/2017 05:13:56, 242640 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_n8.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:22, 5022664 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_g9.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:20, 5360080 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_s9.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:24, 5238224 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbbmalloc.dll, 4.02.2014.0601 (English), 5/26/2017 05:14:18, 208488 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbb.dll, 4.02.2014.0601 (English), 5/26/2017 05:14:18, 360040 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbb_preview.dll, 4.02.2013.1002 (), 5/26/2017 05:14:20, 355944 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\common\clbltfnshared.rtl, 11/3/2024 05:16:22, 1026520 bytes Driver: C:\Windows\system32\Intel_OpenCL_ICD64.dll, 2.00.0002.0000 (English), 5/26/2017 05:12:54, 99792 bytes Driver: C:\Windows\system32\IntelOpenCL64.dll, 20.19.0015.4642 (English), 5/26/2017 05:12:14, 416208 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\task_executor64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:18, 428496 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\OclCpuBackend64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:16, 9629128 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\intelocl64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:12, 1628112 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\cpu_device64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:06, 669136 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8.rtl, 11/3/2024 05:16:22, 1226660 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.o, 11/3/2024 05:16:22, 358288 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.rtl, 11/3/2024 05:16:22, 402580 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9.rtl, 11/3/2024 05:16:22, 1159784 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.o, 11/3/2024 05:16:22, 347104 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.rtl, 11/3/2024 05:16:22, 402468 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9.rtl, 11/3/2024 05:16:22, 788292 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.o, 11/3/2024 05:16:22, 294032 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.rtl, 11/3/2024 05:16:22, 364424 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clang_compiler64.dll, 5.02.0000.10094 (English), 5/26/2017 05:14:00, 267728 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_h8.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:22, 5234120 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_e9.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:20, 5744592 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_l9.dll, 3.04.0000.0000 (English), 5/26/2017 05:14:22, 5627336 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbbmalloc.dll, 4.02.2014.0601 (English), 5/26/2017 05:14:18, 248424 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbb.dll, 4.02.2014.0601 (English), 5/26/2017 05:14:18, 438376 bytes Driver: C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbb_preview.dll, 4.02.2013.1002 (), 5/26/2017 05:14:20, 433768 bytes Driver: C:\Windows\SysWow64\IntelOpenCL32.dll, 20.19.0015.4642 (English), 5/26/2017 05:12:10, 318416 bytes Driver: C:\Windows\SysWow64\igdbcl32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:28, 388560 bytes Driver: C:\Windows\SysWow64\igdrcl32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:46, 4368840 bytes Driver: C:\Windows\SysWow64\common_clang32.dll, 4.00.0000.0000 (English), 5/26/2017 05:09:36, 19861456 bytes Driver: C:\Windows\SysWow64\igdmcl32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:42, 3972048 bytes Driver: C:\Windows\SysWow64\igdfcl32.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:32, 225232 bytes Driver: C:\Windows\system32\IntelOpenCL64.dll, 20.19.0015.4642 (English), 5/26/2017 05:12:14, 416208 bytes Driver: C:\Windows\system32\igdbcl64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:30, 438736 bytes Driver: C:\Windows\system32\igdrcl64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:50, 4931024 bytes Driver: C:\Windows\system32\common_clang64.dll, 4.00.0000.0000 (English), 5/26/2017 05:09:40, 29101512 bytes Driver: C:\Windows\system32\igdmcl64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:44, 5683664 bytes Driver: C:\Windows\system32\igdfcl64.dll, 20.19.0015.4642 (English), 5/26/2017 05:10:34, 266192 bytes Driver: C:\Windows\system32\igdclbif.bin, 8/31/2020 11:05:56, 5799386 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw32.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:32, 8872536 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin32_hw.dll, 1.16.0010.0020 (English), 5/26/2017 05:13:00, 4741280 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:38, 1457080 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:16, 1350304 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp8vd_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:40, 1358496 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9vd_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:46, 1358496 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_32.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:44, 1471384 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_32.vp, 8/31/2020 11:05:54, 63761 bytes Driver: C:\Program Files\Intel\Media SDK\he_32.vp, 8/31/2020 11:05:54, 62217 bytes Driver: C:\Program Files\Intel\Media SDK\c_32.cpa, 8/31/2020 11:05:54, 846855 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_32.vp, 8/31/2020 11:05:54, 993 bytes Driver: C:\Program Files\Intel\Media SDK\dev_32.vp, 8/31/2020 11:05:54, 21523 bytes Driver: C:\Program Files\Intel\Media SDK\mj_32.vp, 8/31/2020 11:06:00, 57541 bytes Driver: C:\Program Files\Intel\Media SDK\libmfxhw64.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:34, 9318328 bytes Driver: C:\Program Files\Intel\Media SDK\mfxplugin64_hw.dll, 1.16.0010.0020 (English), 5/26/2017 05:13:02, 4919456 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h264ve_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:42, 1810840 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_mjpgvd_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:20, 1677472 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp8vd_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:42, 1686168 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_vp9vd_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:13:48, 1687200 bytes Driver: C:\Program Files\Intel\Media SDK\mfx_mft_h265ve_64.dll, 7.16.0010.0020 (English), 5/26/2017 05:11:48, 1836696 bytes Driver: C:\Program Files\Intel\Media SDK\h265e_64.vp, 8/31/2020 11:05:54, 13485 bytes Driver: C:\Program Files\Intel\Media SDK\he_64.vp, 8/31/2020 11:05:54, 12873 bytes Driver: C:\Program Files\Intel\Media SDK\c_64.cpa, 8/31/2020 11:05:54, 1519616 bytes Driver: C:\Program Files\Intel\Media SDK\cpa_64.vp, 8/31/2020 11:05:54, 993 bytes Driver: C:\Program Files\Intel\Media SDK\dev_64.vp, 8/31/2020 11:05:54, 21523 bytes Driver: C:\Program Files\Intel\Media SDK\mj_64.vp, 8/31/2020 11:06:00, 12365 bytes Driver: C:\Windows\system32\igfxCoIn_v5171.dll, 1.03.0025.0000 (English), 11/3/2024 05:16:13, 226200 bytes Driver: C:\Windows\system32\DisplayAudiox64.cab, 5/26/2017 02:03:38, 831685 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.19041.3636 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.19041.3636 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.19041.0001 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.19041.0001 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.19041.3636 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.19041.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.19041.3996 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.19041.3636 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.19041.3636 DV Muxer,0x00400000,0,0,qdv.dll,10.00.19041.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.19041.3636 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.19041.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.19041.3636 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.19041.3636 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.19041.5198 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.19041.3636 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.19041.0001 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.3636 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.19041.3636 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.3636 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.19041.3636 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.19041.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.19041.0001 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.4355 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.19041.3636 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.19041.3636 DV Splitter,0x00600000,1,2,qdv.dll,10.00.19041.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.19041.3636 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.19041.4355 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.19041.3636 Video Renderer,0x00800001,1,0,quartz.dll,10.00.19041.3636 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.19041.0001 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.19041.3636 Video Renderer,0x00400000,1,0,quartz.dll,10.00.19041.3636 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.19041.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.19041.0001 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax, File writer,0x00200000,1,0,qcap.dll,10.00.19041.0001 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.19041.3636 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.19041.3636 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.19041.4355 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.19041.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.19041.3636 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.19041.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.19041.4355 Null Renderer,0x00200000,1,0,qedit.dll,10.00.19041.4355 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.19041.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.19041.0001 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.19041.0001 Smart Tee,0x00200000,1,2,qcap.dll,10.00.19041.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.19041.3636 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.19041.3636 Wave Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.19041.3636 File stream renderer,0x00400000,1,1,quartz.dll,10.00.19041.3636 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.19041.4355 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.19041.0001 AVI Mux,0x00200000,1,0,qcap.dll,10.00.19041.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.19041.3636 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.19041.3636 File Source (URL),0x00400000,0,1,quartz.dll,10.00.19041.3636 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.19041.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.19041.4355 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.19041.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.19041.3636 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.4355 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.19041.3636 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.19041.0001 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.19041.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.19041.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.19041.3636 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.19041.3636 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.19041.3636 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 PCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.19041.3636 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.19041.3636 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.19041.3636 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.19041.3636 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.19041.3636 Audio Capture Sources: Microphone (Conexant SmartAudio HD),0x00200000,0,0,qcap.dll,10.00.19041.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.19041.5072 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.5072 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.19041.5072 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.19041.3636 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.19041.3636 WDM Streaming Capture Devices: ,0x00000000,0,0,, Conexant HD Audio capture,0x00200000,1,1,ksproxy.ax,10.00.19041.4355 Lenovo EasyCamera,0x00200000,1,1,ksproxy.ax,10.00.19041.4355 WDM Streaming Rendering Devices: ,0x00000000,0,0,, Conexant HD Audio output,0x00200000,1,1,ksproxy.ax,10.00.19041.4355 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.19041.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.19041.0001 Video Capture Sources: Lenovo EasyCamera,0x00200000,1,1,ksproxy.ax,10.00.19041.4355 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.19041.3636 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.19041.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.19041.0001 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.19041.4355 Audio Renderers: Speakers (Conexant SmartAudio HD),0x00200000,1,0,quartz.dll,10.00.19041.3636 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.19041.3636 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.19041.3636 DirectSound: Speakers (Conexant SmartAudio HD),0x00200000,1,0,quartz.dll,10.00.19041.3636 ---------------------------- Preferred DirectShow Filters ---------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\DirectShow\Preferred] , [, ] MEDIASUBTYPE_DVD_LPCM_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_AUDIO, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG2_VIDEO, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS {78766964-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_mp4s, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {64697678-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {58564944-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject {5634504D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_MP4S, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject {44495658-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMVA, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mpg4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_h264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_H264, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_WMV3, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_MP43, Mpeg43 Decoder DMO, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WMV2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS2, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_M4S2, Mpeg4s Decoder DMO, CLSID_CMpeg4sDecMediaObject MEDIASUBTYPE_WVP2, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder DMO, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_WMV1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_MSS1, WMV Screen decoder DMO, CLSID_CMSSCDecMediaObject MEDIASUBTYPE_WVC1, WMVideo Decoder DMO, CLSID_CWMVDecMediaObject MEDIASUBTYPE_AVC1, Microsoft DTV-DVD Video Decoder, CLSID_CMPEG2VidDecoderDS MEDIASUBTYPE_MPEG_LOAS, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_MPEG_ADTS_AAC, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS MEDIASUBTYPE_WMAUDIO_LOSSLESS, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_WMAUDIO3, WMAudio Decoder DMO, CLSID_CWMADecMediaObject WMMEDIASUBTYPE_WMAudioV8, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder DMO, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft DTV-DVD Audio Decoder, CLSID_CMPEG2AudDecoderDS WMMEDIASUBTYPE_MP3, MP3 Decoder DMO, CLSID_CMP3DecMediaObject MEDIASUBTYPE_MPEG1Payload, MPEG Video Decoder, CLSID_CMpegVideoCodec MEDIASUBTYPE_MPEG1Packet, MPEG Video Decoder, CLSID_CMpegVideoCodec {6C737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64737664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec {64687664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MJPG, MJPEG Decompressor, CLSID_MjpegDec {20637664-0000-0010-8000-00AA00389B71}, DV Video Decoder, CLSID_DVVideoCodec MEDIASUBTYPE_MPEG1AudioPayload, MPEG Audio Decoder, CLSID_CMpegAudioCodec WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject WMMEDIASUBTYPE_WMSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject --------------------------- Media Foundation File Versions --------------------------- mfcore.dll, 10.00.19041.5247 mfreadwrite.dll, 10.00.19041.4957 mfcaptureengine.dll, 10.00.19041.4355 mfsensorgroup.dll, 10.00.19041.4355 windows.media.dll, 10.00.19041.4355 frameserver.dll, 10.00.19041.4355 frameserverclient.dll, 10.00.19041.5198 --------------------------- 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, 7.16.0010.0020 Intel� Hardware VP8 Decoder MFT, {6D856398-834E-4A89-8EE5-071BB3F58BE4}, 0x6, mfx_mft_vp8vd_64.dll, 7.16.0010.0020 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.19041.5198 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.19041.0001 Intel� Hardware VP8 Sync Decoder MFT, {451E3CB7-2622-4BA5-8E1D-44B3C41D0924}, 0x1, mfx_mft_vp8vd_64.dll, 7.16.0010.0020 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.19041.3636 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.19041.5198 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.19041.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.19041.3996 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.19041.3636 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.19041.3636 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.19041.3636 VP9VideoExtensionDecoder WebpImageExtension HEIFImageExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 7.16.0010.0020 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.19041.3636 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.19041.3636 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.19041.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.19041.0001 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.19041.4355 VP9VideoExtensionEncoder HEIFImageExtension Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.19041.3636 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.19041.3636 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.19041.3636 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.19041.3636 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.19041.3636 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.19041.4355 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.19041.5198 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.19041.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.19041.3636 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.19041.4355 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.19041.5247 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.19041.5247 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.19041.3636 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.19041.3636 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.19041.4355 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.19041.4355 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.19041.0001 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.19041.5247 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.19041.5247 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.19041.0001 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.19041.3636 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.19041.5247 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.19041.3636 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.19041.5247 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.19041.4355 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.19041.3636 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.19041.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.19041.4355 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.19041.3636 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.19041.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.19041.3636 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.19041.0001 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.19041.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.19041.0001 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.19041.5247 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.19041.5198 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableEncoders = 1 EnableDecoders = 1 ------------------------------------- Media Foundation Byte Stream Handlers ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] .3g2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .ac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .adt, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .am?, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler .amr, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler, Preferred .asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred .dvr-ms, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler .dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred .ec3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred .m2t, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m2ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mk3d, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mka, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mks, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mkv, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mov, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp2v, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mpg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .nsc, {B084785C-DDE0-4D30-8CA8-05A373E185BE}, NSC Byte Stream Handler, Preferred .sami, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .smi, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .tod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .uvu, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .vob, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred .weba, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wtv, {65964407-A5D8-4060-85B0-1CCD63F768E2}, WTV Byte Stream Handler, Preferred audio/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/aacp, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/eac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/L16, {3FFB3B8C-EB99-472B-8902-E1C1B05F07CF}, LPCM Byte Stream Handler, Preferred audio/mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/MP4A-LATM, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/vnd.dlna.adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/vnd.dolby.dd-raw, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred audio/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred audio/x-aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/x-flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/x-m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred audio/x-mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-ms-wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred audio/x-wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred video/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/vnd.dece.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/vnd.dlna.mpeg-tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred video/x-m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred video/x-ms-asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred -------------------------------- Media Foundation Scheme Handlers -------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] file:, {477EC299-1421-4BDD-971F-7CCB933F21AD}, File Scheme Handler, Preferred http:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler http:, {9EC4B4F9-3029-45AD-947B-344DE2A249E2}, Urlmon Scheme Handler http:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpd:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler, Preferred https:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpsd:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcast:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcrecv:, {FA6D33D4-9405-4BA5-9983-12604AC8E77A}, Miracast Sink Scheme Handler, Preferred mms:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ms-appdata:, {CFC81939-3886-4ACF-9692-DA58037AE716}, MsAppData Scheme Handler, Preferred ms-appx-web:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppxWeb Scheme Handler, Preferred ms-appx:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppx Scheme Handler, Preferred ms-winsoundevent:, {F79A6BF9-7415-4CF3-AE10-4559509ABC3C}, Sound Event Scheme Handler, Preferred rtsp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtsps:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred sdp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ------------------------------------- Preferred Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred] , [, ] {EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B} {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905} MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9} {00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} {0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A} {00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} {00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B} {00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC} {00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE} KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514} {00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786} KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject ------------------------------------- Disabled Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse] ------------------------ Disabled Media Sources ------------------------ [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse] --------------- EVR Power Information --------------- Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket 1761065904726065415, type 5 Event Name: AppHangB1 Response: Not available Cab Id: 0 Problem signature: P1: left4dead2.exe P2: 0.0.0.0 P3: 6712ef31 P4: a206 P5: 134217728 P6: P7: P8: P9: P10: +++ WER1 +++: Fault bucket , type 0 Event Name: AppHangTransient Response: Not available Cab Id: 0 Problem signature: P1: left4dead2.exe P2: 0.0.0.0 P3: 6712ef31 P4: unknown P5: unknown P6: unknown P7: unknown P8: P9: P10: +++ WER2 +++: Fault bucket , type 0 Event Name: AppHangTransient Response: Not available Cab Id: 0 Problem signature: P1: left4dead2.exe P2: 0.0.0.0 P3: 6712ef31 P4: unknown P5: unknown P6: unknown P7: unknown P8: P9: P10: +++ WER3 +++: Fault bucket 1704174253423383305, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: GlyphCrashHandler64.exe P2: 0.0.0.0 P3: 644aa25d P4: GlyphCrashHandler64.exe P5: 0.0.0.0 P6: 644aa25d P7: c0000005 P8: 00000000001939e0 P9: P10: +++ WER4 +++: Fault bucket 107418060083, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DevilMayCry4SpecialEdition.exe P2: 1.0.0.0 P3: 556d7520 P4: DevilMayCry4SpecialEdition.exe P5: 1.0.0.0 P6: 556d7520 P7: c0000005 P8: 00052832 P9: P10: +++ WER5 +++: Fault bucket 107418060083, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DevilMayCry4SpecialEdition.exe P2: 1.0.0.0 P3: 556d7520 P4: DevilMayCry4SpecialEdition.exe P5: 1.0.0.0 P6: 556d7520 P7: c0000005 P8: 00052832 P9: P10: +++ WER6 +++: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DevilMayCry4SpecialEdition.exe P2: 1.0.0.0 P3: 556d7520 P4: DevilMayCry4SpecialEdition.exe P5: 1.0.0.0 P6: 556d7520 P7: c0000005 P8: 00052832 P9: P10: +++ WER7 +++: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DevilMayCry4SpecialEdition.exe P2: 1.0.0.0 P3: 556d7520 P4: DevilMayCry4SpecialEdition.exe P5: 1.0.0.0 P6: 556d7520 P7: c0000005 P8: 00052832 P9: P10: +++ WER8 +++: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DevilMayCry4SpecialEdition.exe P2: 1.0.0.0 P3: 556d7520 P4: DevilMayCry4SpecialEdition.exe P5: 1.0.0.0 P6: 556d7520 P7: c0000005 P8: 00052832 P9: P10: +++ WER9 +++: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: DevilMayCry4SpecialEdition.exe P2: 1.0.0.0 P3: 556d7520 P4: DevilMayCry4SpecialEdition.exe P5: 1.0.0.0 P6: 556d7520 P7: c0000005 P8: 00052832 P9: P10: ...#SSU#...