# SSU Scan Information Scan Info: Version:"3.0.0.2" Date:"11/11/2023" Time:"00:01:08.5976243" # Scanned Hardware Computer: BaseBoard Manufacturer:"LENOVO" BIOS Mode:"Legacy" BIOS Version/Date:"LENOVO LHCN16WW , 01/30/2023 12:00 AM" CD or DVD:"Not Available" Embedded Controller Version:"1.16" Platform Role:"Mobile" Processor:"13th Gen Intel(R) Core(TM) i7-1355U , GenuineIntel" Secure Boot State:"On" SMBIOS Version:"3.4" Sound Card:"Realtek High Definition Audio(SST)" System Manufacturer:"LENOVO" System Model:"82YN" System SKU:"LENOVO_MT_82YN_BU_idea_FM_Yoga 7 16IRL8" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"Not Available" - "Intel(R) Iris(R) Xe Graphics" Adapter Compatibility:"Intel Corporation" Adapter DAC Type:"Internal" Adapter RAM:"1.00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" - "Caption":"Intel(R) Iris(R) Xe Graphics" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Iris+Xe+Graphics" CoInstallers:"oem20.inf,iRPLPD_w10_DS,Internal,Intel(R) Iris(R) Xe Graphics Family" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"igdkmdn64.sys" Driver Date:"10/19/2023 07:00 PM" Driver Path:"C:\Windows\system32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdkmdn64.sys" Driver Provider:"Intel Corporation" Driver Version:"31.0.101.4900" INF:"oem20.inf" INF Section:"iRPLPD_w10_DS" Install Date:"Not Available" Installed Drivers:"<>,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\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_A7A1&SUBSYS_380517AA&REV_04\3&11583659&1&10" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"60 Hz" Refresh Rate - Maximum:"60 Hz" Refresh Rate - Minimum:"60 Hz" Resolution:"1920 X 1200" Scan Mode:"Noninterlaced" Service Name:"igfxn" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"Intel(R) Iris(R) Xe Graphics Family" - "Memory" Physical Memory (Available):"8.82 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.73 GB" - "BANK 0" Capacity:"2 GB" Channel:"Controller0-ChannelA" Configured Clock Speed:"5200 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"First position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKBKB@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 0" Capacity:"2 GB" Channel:"Controller1-ChannelA" Configured Clock Speed:"5200 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"First position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKBKB@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 1" Capacity:"2 GB" Channel:"Controller0-ChannelB" Configured Clock Speed:"5200 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Second position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKBKB@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 1" Capacity:"2 GB" Channel:"Controller1-ChannelB" Configured Clock Speed:"5200 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Second position" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKBKB@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 2" Capacity:"2 GB" Channel:"Controller0-ChannelC" Configured Clock Speed:"5200 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKBKB@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 2" Capacity:"2 GB" Channel:"Controller1-ChannelC" Configured Clock Speed:"5200 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKBKB@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 3" Capacity:"2 GB" Channel:"Controller0-ChannelD" Configured Clock Speed:"5200 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKBKB@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 3" Capacity:"2 GB" Channel:"Controller1-ChannelD" Configured Clock Speed:"5200 MHz" Configured Voltage:"500 millivolts" Data Width:"16 bits" Form Factor:"Unknown" Interleave Position:"Not Available" Manufacturer:"Samsung" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"K3LKBKB@BM-MGCP" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"LHCN16WW, LENOVO - 1" Caption:"Motherboard" Chipset:"Not Available" Date:"01/29/2023 06:00 PM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"LENOVO" Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"LNVNB161216" Serial Number:"YX0649QP" Status:"OK" Version:"SDK0T76463 WIN" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Intel(R) Wi-Fi 6E AX211 160MHz" Access Point: Authentication: Availability:"Running or Full Power" - "Caption":"Intel(R) Wi-Fi 6E AX211 160MHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Wi+Fi+6E+AX211+160MHz" Channel: Cipher: CoInstallers:"Not Available" Connection Mode: Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"Netwtw12.sys" Driver Date:"05/09/2023 12:00 AM" Driver Path:"C:\Windows\system32\DriverStore\FileRepository\netwtw6e.inf_amd64_eae931aa85cab080\Netwtw12.sys" Driver Provider:"Intel" Driver Version:"22.230.0.8" Index:"0002" INF:"oem73.inf" INF Section:"Install_GEN_SLR_GfP2_211_AX_6G_2x2_WinT" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"11/11/2023 06:16 PM" Location:"PCI bus 0, device 20, function 3" MAC Address:"56:7C:1E:9E:76:E7" Manufacturer:"Intel Corporation" Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{46297E18-7C40-41D8-8889-0F984CDE34BB}" Network Name:"Wi-Fi" Network Type: PNP Device ID:"PCI\VEN_8086&DEV_51F1&SUBSYS_00948086&REV_01\3&11583659&1&A3" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Wi-Fi 6E AX211 160MHz" Profile: Radio Type: Receive Rate: Service Name:"Netwtw12" Signal Strength: State:"disconnected" Status:"Enabled" Transmit Rate: Type:"Ethernet 802.3" - "Service Bindings" Bridge Driver: Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: QoS Packet Scheduler: - "Settings" *DeviceSleepOnDisconnect:Sleep on WoWLAN Disconnect:"Disabled (0)" *PacketCoalescing:Packet Coalescing:"Enabled (1)" *PMARPOffload:ARP offload for WoWLAN:"Enabled (1)" *PMNSOffload:NS offload for WoWLAN:"Enabled (1)" *PMWiFiRekeyOffload:GTK rekeying for WoWLAN:"Enabled (1)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" ChannelWidth24:Channel Width for 2.4GHz:"Auto (1)" ChannelWidth52:Channel Width for 5GHz:"Auto (1)" ChannelWidth6:Channel Width for 6GHz:"Auto (1)" CtsToItself:Mixed Mode Protection:"RTS/CTS Enabled (0)" FatChannelIntolerant:Fat Channel Intolerant:"Disabled (0)" IbssTxPower:Transmit Power:"5. Highest (100)" IEEE11nMode:802.11n/ac/ax Wireless Mode:"4. 802.11ax (3)" Is6GhzBandSupported:Ultra High Band (6GHz):"Enabled (1)" MIMOPowerSaveMode:MIMO Power Save Mode:"Auto SMPS (0)" RoamAggressiveness:Roaming Aggressiveness:"3. Medium (2)" RoamingPreferredBandType:Preferred Band:"1. No Preference (0)" ThroughputBoosterEnabled:Throughput Booster:"Disabled (0)" uAPSDSupport:U-APSD support:"Disabled (0)" WirelessMode:802.11a/b/g Wireless Mode:"6. Dual Band 802.11a/b/g (34)" - "Operating System" .Net Framework Version:"4.0,4.8" Boot Device:"\Device\HarddiskVolume1" Internet Browser:"Internet Explorer,11.1, Microsoft Edge,117.0" Locale:"United States" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 11 Home" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"12.00 GB" Physical Memory (Available):"8.81 GB" Physical Memory (Installed):"16 GB" Physical Memory (Total):"15.73 GB" System Directory:"C:\Windows\system32" Version:"10.0.22621 Build 22621" Virtual Memory (Available):"19.90 GB" Virtual Memory (Total):"27.73 GB" Windows Directory:"C:\Windows" - "Installed Updates" KB2151757:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [7/9/2023]" KB2151757:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [7/9/2023]" KB2467173:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [7/9/2023]" KB2467173:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [7/9/2023]" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB5012170:"Security Update [4/20/2023]" KB5026039:"Update [4/18/2023]" KB5028756:"Update [8/9/2023]" KB5028948:"Update [8/9/2023]" KB5029263:"Security Update [8/9/2023]" KB982573:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [7/9/2023]" KB982573:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [7/9/2023]" Microsoft ASP.NET Core 7.0.7 - Shared Framework (x64):".NET [10/24/2023]" SP1:"Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 [Not Available]" SP1:"Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 [Not Available]" - "Processor" - "13th Gen Intel(R) Core(TM) i7-1355U" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 186 Stepping 3" - "Chipset Name":"13th Gen Intel(R) Core(TM) i7-1355U" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=13th+Gen++Core+i7+1355U" CPU Speed:"1.70 GHz" Current Voltage:"1.8 volts" Driver:"Not Available" Driver Date:"04/21/2009 12:00 AM" Driver Path:"C:\Windows\system32\drivers\intelppm.sys" Driver Provider:"Microsoft" Driver Version:"10.0.22621.1485" Ext. Family:"Not Available" Family:"Intel Core™ i7-2760QM" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"10 x 96 KB" Level 2 Cache:"10 x 6656 KB" Level 3 Cache:"12 MB" Load:"0%" Manufacturer:"GenuineIntel" Model:"186" Name:"13th Gen Intel(R) Core(TM) i7-1355U" Number of Cores:"10" Number of Cores Enabled:"10" Number of Logical Processors:"12" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000B06A3" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"3" Version:"Not Available" - "Storage" - " SDHC SCSI Disk Device" Capablities:"Random Access, Supports Writing, Supports Removable Media" Caption:"SDHC SCSI Disk Device" Cylinder - Total:"1893" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.22621.1778" Error Code:"Device is working properly" Firmware Revision:"0001" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"SDHC SCSI Disk Device" Name:"\\.\PHYSICALDRIVE0" Partitions:"1" Physical Sector Size:"512" PNP Device ID:"SCSI\DISK&VEN_&PROD_SDHC_\5&3269F9B3&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"0" Sectors - Per Track:"63" Sectors - Total:"30411045" Serial Number:"" Size:"14.50 GB" Size – Available:"13.26 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"482715" - "E:" Availability:"Not Available" Caption:"E:" Compression Method:"Not Compressed" Description:"Removable Disk" File System:"FAT32" Name:"Not Available" Serial Number:"231882FD" Size:"14.50 GB" Size – Available:"13.26 GB" Status:"Not Available" Volume Dirty:"No" - "WD PC SN740 SDDPMQD-512G-1101" Capablities:"Random Access, Supports Writing" Caption:"WD PC SN740 SDDPMQD-512G-1101" Cylinder - Total:"62260" Description:"Disk drive" Driver:"Not Available" Driver Date:"06/21/2006 12:00 AM" Driver Version:"10.0.22621.1778" Error Code:"Device is working properly" Firmware Revision:"73110001" Heads - Total:"255" Index:"1" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"WD PC SN740 SDDPMQD-512G-1101" Name:"\\.\PHYSICALDRIVE1" Partitions:"3" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_WD_PC_SN740_SDDP\5&460C029&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"1" Sectors - Per Track:"63" Sectors - Total:"1000206900" Serial Number:"E823_8FA6_BF53_0001_001B_448B_4EB8_2161." Size:"476.94 GB" Size – Available:"86.40 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"15876300" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Windows-SSD" Serial Number:"66433366" Size:"474.72 GB" Size – Available:"86.41 GB" Status:"Not Available" Volume Dirty:"No" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- The Windows Update service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service dosvc with arguments "Unavailable" in order to run the server: {5B99FA76-721C-423C-ADAC-56D03C8A8007} ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service dosvc with arguments "Unavailable" in order to run the server: {5B99FA76-721C-423C-ADAC-56D03C8A8007} ------------------------------------------------------------------- The Intel(R) Arc Control 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 Update service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {815211C2-E515-4437-A8CC-E93857DF54F5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:15:44 PM on ‎11/‎10/‎2023 was unexpected. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} 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 following service has repeatedly stopped responding to service control requests: CDPUserSvc_42640 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 CDPUserSvc_42640 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CDPUserSvc_42640 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CDPUserSvc_42640 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CDPUserSvc_42640 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CDPUserSvc_42640 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CDPUserSvc_42640 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CDPUserSvc_42640 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CDPUserSvc_42640 service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the CDPUserSvc_42640 service. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} 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 Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The Energy Server Service queencreek service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} 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 Energy Server Service queencreek service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Windows Error Reporting Service service to connect. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} 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 device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Not Jose's S21 FE (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Not Jose's S21 FE (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Not Jose's S21 FE (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Not Jose's S21 FE (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 2:48:26 PM on ‎11/‎1/‎2023 was unexpected. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} 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 embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 9:41:14 AM on ‎10/‎31/‎2023 was unexpected. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} 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 embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The device Intel® Smart Sound Technology Detection Verification (location Detection Notification) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device HID Sensor Collection V2 (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- The device Not Jose's S21 FE (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device in the shared process 1 more times before moving the device in its own process. Please contact the device manufacturer for more information about this problem. ------------------------------------------------------------------- A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Modules Installer service did not shut down properly after receiving a preshutdown control. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} 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: {3E8C9ABE-9226-4609-BF5B-60288A391DEE} ------------------------------------------------------------------- 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 embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Media.Capture.Internal.AppCaptureShell did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Microsoft Store Install Service service terminated unexpectedly. It has done this 6 time(s). ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Windows.Media.Capture.Internal.AppCaptureShell did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UDCService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the UDCService service. ------------------------------------------------------------------- The Microsoft Store Install Service service terminated unexpectedly. It has done this 5 time(s). ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (00:0b:e4:8c:08:48) failed. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Microsoft Store Install Service service terminated unexpectedly. It has done this 4 time(s). ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Microsoft Store Install Service service terminated unexpectedly. It has done this 3 time(s). ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The Microsoft Store Install Service service terminated unexpectedly. It has done this 2 time(s). ------------------------------------------------------------------- The Microsoft Store Install Service service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service BcastDVRUserService_58e42 with arguments "Unavailable" in order to run the server: Windows.Media.Capture.Internal.AppCaptureShell ------------------------------------------------------------------- The BcastDVRUserService_58e42 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 BcastDVRUserService_58e42 service to connect. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} 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 embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has encountered an internal error and has failed. ------------------------------------------------------------------- Intel(R) Wi-Fi 6E AX211 160MHz : Has determined that the network adapter is not functioning properly. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Miniport SAMSUNG Mobile USB Remote NDIS Network Device, {5849dfe3-3ce5-4c50-b6b0-3f0804402d6a}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\Harddisk2\DR2. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A55803CC-4D53-404C-8557-FD63DBA95D24} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Safer Web DNS Resolver service terminated unexpectedly. It has done this 1 time(s). ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- Not Available ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The previous system shutdown at 6:37:16 AM on ‎9/‎21/‎2023 was unexpected. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service edgeupdate with arguments "/comsvc" in order to run the server: {CECDDD22-2E72-4832-9606-A9B0E5E344B2} ------------------------------------------------------------------- The Microsoft Edge Update Service (edgeupdate) 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 Microsoft Edge Update Service (edgeupdate) service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {354FF91B-5E49-4BDC-A8E6-1CB6C6877182} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service BcastDVRUserService_4bbe0 with arguments "Unavailable" in order to run the server: Windows.Media.Capture.Internal.AppCaptureShell ------------------------------------------------------------------- The BcastDVRUserService_4bbe0 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 BcastDVRUserService_4bbe0 service to connect. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- DCOM got error "1053" attempting to start the service BcastDVRUserService_46e37 with arguments "Unavailable" in order to run the server: Windows.Media.Capture.Internal.AppCaptureShell ------------------------------------------------------------------- The BcastDVRUserService_46e37 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 BcastDVRUserService_46e37 service to connect. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SecurityHealthService service. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- Miniport SAMSUNG Mobile USB Remote NDIS Network Device, {5849dfe3-3ce5-4c50-b6b0-3f0804402d6a}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} 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. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {08728914-3F57-4D52-9E31-49DAECA5A80A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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: {3E8C9ABE-9226-4609-BF5B-60288A391DEE} ------------------------------------------------------------------- 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 embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server Microsoft.LockApp_10.0.22621.1_neutral__cw5n1h2txyewy!WindowsDefaultLockScreen did not register with DCOM within the required timeout. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The IPv6 TCP/IP interface with index 39 failed to bind to its provider. ------------------------------------------------------------------- The IPv4 TCP/IP interface with index 39 failed to bind to its provider. ------------------------------------------------------------------- Miniport SAMSUNG Mobile USB Remote NDIS Network Device, {5849dfe3-3ce5-4c50-b6b0-3f0804402d6a}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Group Policy Client service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Group Policy Client service to connect. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Encrypted volume check: Volume information on D: cannot be read. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {995C996E-D918-4A8C-A302-45719A6F4EA7} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {D4872B74-3AFC-47CD-B8A2-9E4F998539BC} 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 {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- Miniport Microsoft Wi-Fi Direct Virtual Adapter #2, {f617d2f7-6b84-4dd7-92dd-586f34af0b5e}, had event Fatal error: The miniport has failed a power transition to operational power ------------------------------------------------------------------- The SysMain service terminated with the following error: The parameter is incorrect. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {021E4F06-9DCC-49AD-88CF-ECC2DA314C8A} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9WZDNCRFHVQM-MICROSOFT.WINDOWSCOMMUNICATIONSAPPS. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {BE19F061-C08B-426E-811F-2A1CEB1E80AD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {BE19F061-C08B-426E-811F-2A1CEB1E80AD} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x8024200B: Update for Microsoft Defender Antivirus antimalware platform - KB4052623 (Version 4.18.23070.1004). ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The ClickToRunSvc service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The PEFService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The LenovoVantageService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The LanmanServer service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The LanmanServer service was unable to log on as NT AUTHORITY\SYSTEM with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The ImControllerService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The igccservice service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The LVAWService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The WMIRegistrationService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The ss_conn_service2 service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The ss_conn_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. ------------------------------------------------------------------- The mfemms service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The Lenovo Smart Appearance Intelligent Sensing Aware 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. ------------------------------------------------------------------- The ModuleCoreService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The LITSSVC service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The ipfsvc service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The DolbyDAXAPI service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The ElevocService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The UDCService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The RtkAudioUniversalService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The SmartAppearanceAISVC service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The SmartNoteService service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. ------------------------------------------------------------------- The Dhcp service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Dhcp service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The wtd service depends on the BFE service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The IKEEXT service depends on the BFE service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The BFE service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WinDefend service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The rsDNSSvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The rsDNSClientSvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The DiagTrack service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WinDefend 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 Winmgmt 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 WpnService service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WpnService 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 StiSvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The StiSvc service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The rsDNSSvc 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 rsDNSClientSvc 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 StateRepository service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The StateRepository 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 DiagTrack 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 StateRepository service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The jhi_service service depends on the iphlpsvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The iphlpsvc service depends on the WinHttpAutoProxySvc service which failed to start because of the following error: The dependency service or group failed to start. ------------------------------------------------------------------- The WinHttpAutoProxySvc service depends on the Dhcp service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Dhcp service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Dhcp service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The TrkWks service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The TrkWks 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 BFE service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The dptftcs service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The StateRepository 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 dptftcs service was unable to log on as NT Authority\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The CryptSvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The CryptSvc service was unable to log on as NT Authority\NetworkService 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 LanmanWorkstation service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The LanmanWorkstation service was unable to log on as NT AUTHORITY\NetworkService 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 mpssvc service depends on the BFE service which failed to start because of the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The BFE service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The BFE service was unable to log on as NT AUTHORITY\LocalService with the currently configured password due to the following error: The request is not supported. To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC). ------------------------------------------------------------------- The WbioSrvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WbioSrvc 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 Spooler service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The Spooler 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 ShellHWDetection 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 WlanSvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The WlanSvc 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 hns service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The Windows Modules Installer service terminated with the following error: The process cannot access the file because it is being used by another process. ------------------------------------------------------------------- The server Microsoft.AAD.BrokerPlugin_1000.19580.1000.0_neutral_neutral_cw5n1h2txyewy!Windows.Security.Authentication.Web.Core.BackgroundGetTokenTask.ClassId.WebAccountProvider did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The Windows Camera Frame Server Monitor 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 Camera Frame Server Monitor service to connect. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {5F7F3F7B-1177-4D4B-B1DB-BC6F671B8F25} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {69B7FE84-6361-4423-B948-1D64820B1E96} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server MicrosoftWindows.Client.CBS_1000.22644.1000.0_x64__cw5n1h2txyewy!Global.IrisService.AppXwwah2tbqj7j749pkqvs0hna8en4npvp8.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- : The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 11/11/2023, 18:20:02 Machine name: YAHOO Machine Id: {03350906-FFDA-401A-AAFD-E8A698AB8E38} Operating System: Windows 11 Home 64-bit (10.0, Build 22621) (22621.ni_release.220506-1250) Language: English (Regional Setting: English) System Manufacturer: LENOVO System Model: 82YN BIOS: LHCN16WW (type: UEFI) Processor: 13th Gen Intel(R) Core(TM) i7-1355U (12 CPUs), ~1.7GHz Memory: 16384MB RAM Available OS Memory: 16108MB RAM Page File: 7813MB used, 20583MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 120 DPI (125 percent) System DPI Setting: 120 DPI (125 percent) DWM DPI Scaling: UnKnown Miracast: Available, with HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.4.7 DxDiag Version: 10.00.22621.0001 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Input Tab: No problems found. -------------------- DirectX Debug Levels -------------------- Direct3D: 0/4 (retail) DirectDraw: 0/4 (retail) DirectInput: 0/5 (retail) DirectMusic: 0/5 (retail) DirectPlay: 0/9 (retail) DirectSound: 0/5 (retail) DirectShow: 0/6 (retail) --------------- Display Devices --------------- Card name: Intel(R) Iris(R) Xe Graphics Manufacturer: Intel Corporation Chip type: Intel(R) Iris(R) Xe Graphics Family DAC type: Internal Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_8086&DEV_A7A1&SUBSYS_380517AA&REV_04 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: 8182 MB Dedicated Memory: 128 MB Shared Memory: 8054 MB Current Mode: 1920 x 1200 (32 bit) (60Hz) HDR Support: Not Supported Display Topology: Internal Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.639648,0.330078), Green(0.299805,0.599609), Blue(0.149414,0.059570), White Point(0.312500,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: Generic PnP Monitor Monitor Model: unknown Monitor Id: LEN8986 Native Mode: 1920 x 1200(p) (60.002Hz) Output Type: Internal Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: <>,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10iumd64.dll,C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd12umd64.dll Driver File Version: 31.00.0101.4900 (English) Driver Version: 31.0.101.4900 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 3.1 Hardware Scheduling: DriverSupportState:Experimental Enabled:False Displayable: Supported Graphics Preemption: Triangle Compute Preemption: Thread group Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Integrated Power P-states: Not Supported Virtualization: Paravirtualization Block List: DISABLE_HWSCH Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 10/19/2023 6:00:00 PM, 4284432 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B78E66-E4E1-11CF-3E67-6018ABC2D235} Vendor ID: 0x8086 Device ID: 0xA7A1 SubSys ID: 0x380517AA Revision ID: 0x0004 Driver Strong Name: oem20.inf:5f63e534e0145cc7:iRPLPD_w10_DS:31.0.101.4900:PCI\VEN_8086&DEV_A7A1 Rank Of Driver: 00CF2001 Video Accel: DXVA2 Modes: DXVA2_ModeMPEG2_VLD DXVA2_ModeMPEG2_IDCT DXVA2_ModeVC1_D2010 {E07EC519-E651-4CD6-AC84-1370CCEEC851} {BCC5DB6D-A2B6-4AF0-ACE4-ADB1F787BC89} DXVA2_ModeWMV9_IDCT DXVA2_ModeVC1_IDCT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_Multiview_NoFGT {C528916C-C0AF-4645-8CB2-372B6D4ADC2A} {91CD2D6E-897B-4FA1-B0D7-51DC88010E0A} {97688186-56A8-4094-B543-FC9DAAA49F4B} {1424D4DC-7CF5-4BB1-9CD7-B63717A72A6B} {C346E8A3-CBED-4D27-87CC-A70EB4DC8C27} {FFC79924-5EAF-4666-A736-06190F281443} {464BDB3C-91C4-4E9B-896F-225496AC4ED6} {9B31316B-F204-455D-8A8C-9345DCA77C01} {AFE4285C-AB63-4B2D-8278-E6BAACEA2CE9} {277DE9C5-ED83-48DD-AB8F-AC2D24B22943} {04C5BA10-4E9A-4B8E-8DBF-4F4B48AFA27C} {0ACEF8BC-285F-415D-AB22-7BF2527A3D2E} {24D19FCA-C5A2-4B8E-9F93-F8F6EF15C890} {353ACA91-D945-4C13-AE7E-469060FAC8D8} {28566328-F041-4466-8B14-8F5831E78F8B} {6B4A94DB-54FE-4AE1-9BE4-7A7DAD004600} {B8B28E0C-ECAB-4217-8C82-EAAA9755AAF0} {8732ECFD-9747-4897-B42A-E534F9FF2B7A} {E139B5CA-47B2-40E1-AF1C-AD71A67A1836} {056A6E36-F3A8-4D00-9663-7E9430358BF9} {5415A68C-231E-46F4-878B-5E9A22E967E9} {161BE912-44C2-49C0-B61E-D946852B32A1} {D6D6BC4F-D51A-4712-97E8-750917C860FD} {7FEF652D-3233-44DF-ACF7-ECFB584DAB35} {87B2AE39-C9A5-4C53-86B8-A52D7EDBA488} {10E19AC8-BF39-4443-BEC3-1B0CBFE4C7AA} {2DEC00C7-21EE-4BF8-8F0E-773F11F126A2} {C35153A0-23C0-4A81-B3BB-6A1326F2B76B} {A33FD0EC-A9D3-4C21-9276-C241CC90F6C7} {310E59D2-7EA4-47BB-B319-500E78855336} {036DFF40-94A6-45B3-A0B3-71F0CDF35129} {8C56EB1E-2B47-466F-8D33-7DBCD63F3DF2} DXVA2_ModeHEVC_VLD_Main {75FC75F7-C589-4A07-A25B-72E03B0383B3} DXVA2_ModeHEVC_VLD_Main10 {9CC55490-E37C-4932-8684-4920F9F6409C} {0BAC4FE5-1532-4429-A854-F84DE04953DB} {4008018F-F537-4B36-98CF-61AF8A2C1A33} {0DABEFFA-4458-4602-BC03-0795659D617C} {1A72925F-0C2C-4F15-96FB-B17D1473603F} {55BCAC81-F311-4093-A7D0-1CBC0B849BEE} {9798634D-FE9D-48E5-B4DA-DBEC45B3DF01} {E484DCB8-CAC9-4859-99F5-5C0D45069089} {41A5AF96-E415-4B0C-9D03-907858E23E78} {6A6A81BA-912A-485D-B57F-CCD2D37B8D94} {E4E3CF5B-97D2-4658-AACB-366E3EE2CEEE} {FD9D9559-0FD3-4917-A9A7-07E714EE9EF9} {0E4BC693-5D2C-4936-B125-AEFE32B16D8A} {2F08B5B1-DBC2-4D48-883A-4E7B8174CFF6} {5467807A-295D-445D-BD2E-CBA8C2457C3D} {AE0D4E15-2360-40A8-BF82-028E6A0DD827} {8FF8A3AA-C456-4132-B6EF-69D9DD72571D} {C23DD857-874B-423C-B6E0-82CEAA9B118A} {5B08E35D-0C66-4C51-A6F1-89D00CB2C197} {07CFAFFB-5A2E-4B99-B62A-E4CA53B6D5AA} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {76988A52-DF13-419A-8E64-FFCF4A336CF5} {68A21C7B-D58F-4E74-9993-E4B8172B19A0} {80A3A7BD-89D8-4497-A2B8-2126AF7E6EB8} {1D5C4D76-B55A-4430-904C-3383A7AE3B16} {A7F759DD-5F54-4D7F-8291-42E883C546FE} {F34FA92F-DC79-474C-B0DB-B7BD4522DF77} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {CA44AFC5-E1D0-42E6-9154-B127186D4D40} {F9A16190-3FB4-4DC5-9846-C8751F83D6D7} {50925B7B-E931-4978-A12A-586630F095F9} {B69C20E0-2508-8790-0305-875499E0A2D0} {49761BEC-4B63-4349-A5FF-87FFDF088466} Deinterlace Caps: {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC1,0x31434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC2,0x32434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC3,0x33434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(IMC4,0x34434d49) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(S340,0x30343353) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate {E064B480-A8BB-4D81-8181-59DC0BE51D02}: Format(In/Out)=(S342,0x32343353) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY VideoProcess_AlphaBlend DeinterlaceTech_BOBLineReplicate DeinterlaceTech_FieldAdaptive D3D9 Overlay: Not Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 3 MPO Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) MPO Stretch: 21.000X - 0.334X MPO Media Hints: colorspace Conversion MPO Formats: NV12,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM PanelFitter Caps: ROTATION,HORIZONTAL_FLIP,RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) PanelFitter Stretch: 21.000X - 0.334X Component Drivers: Driver Name: Unknown Driver Version: Unknown Driver Date: Unknown Driver Provider: Unknown Catalog Attributes: N/A ------------- Sound Devices ------------- Description: Speakers (Realtek(R) Audio) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: INTELAUDIO\FUNC_01&VEN_10EC&DEV_0287&SUBSYS_17AA389A&REV_1000 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.9486.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 2/28/2023 6:00:00 PM, 6449000 bytes Other Files: Driver Provider: Realtek Semiconductor Corp. HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- --------------------- Video Capture Devices Number of Devices: 3 --------------------- FriendlyName: Integrated Camera Category: Camera SymbolicLink: \\?\usb#vid_5986&pid_215d&mi_00#6&2b7db935&1&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global Location: Front Rotation: 0 SensorOrientation: 0 Manufacturer: SunplusIT HardwareID: USB\VID_5986&PID_215D&REV_5807&MI_00,USB\VID_5986&PID_215D&MI_00 DriverDesc: Integrated Camera DriverProvider: SunplusIT DriverVersion: 5.0.18.170 DriverDateEnglish: 11/21/2022 00:00:00 DriverDateLocalized: 11/21/2022 12:00:00 AM Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Integrated Camera Parent: USB\VID_5986&PID_215D\01.00.00 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {131FF57B-1F53-4963-860E-9F190063C2C8} MFT0: n/a DMFT: {55DF2DA5-6817-486f-933B-2324858CAE30} CustomCaptureSource: n/a DependentStillCapture: False EnablePlatformDMFT: True DMFTChain: {55DF2DA5-6817-486f-933B-2324858CAE30},{D8AF2BBF-356C-4079-AEA7-2D80D7904E8E} EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a MSXUCapability: 0x00000106 ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 FriendlyName: Integrated IR Camera Category: Sensor SymbolicLink: \\?\usb#vid_5986&pid_215d&mi_02#6&2b7db935&1&0002#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\global Location: Front Rotation: 0 SensorOrientation: 0 Manufacturer: SunplusIT HardwareID: USB\VID_5986&PID_215D&REV_5807&MI_02,USB\VID_5986&PID_215D&MI_02 DriverDesc: Integrated IR Camera DriverProvider: SunplusIT DriverVersion: 5.0.18.170 DriverDateEnglish: 11/21/2022 00:00:00 DriverDateLocalized: 11/21/2022 12:00:00 AM Service: usbvideo Class: Camera DevNodeStatus: 180200A[DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] ContainerId: {00000000-0000-0000-FFFF-FFFFFFFFFFFF} ProblemCode: No Problem BusReportedDeviceDesc: Integrated IR Camera Parent: USB\VID_5986&PID_215D\01.00.00 DriverProblemDesc: n/a UpperFilters: n/a LowerFilters: WdmCompanionFilter Stack: \Driver\ksthunk,\Driver\usbvideo,\Driver\ACPI,\Driver\usbccgp ContainerCategory: n/a SensorGroupID: {131FF57B-1F53-4963-860E-9F190063C2C8} MFT0: n/a DMFT: {81510F34-8A08-4FEB-85CB-1F2E82062ED4} CustomCaptureSource: n/a DependentStillCapture: n/a EnablePlatformDMFT: n/a DMFTChain: {81510F34-8A08-4FEB-85CB-1F2E82062ED4} EnableDshowRedirection: True FrameServerEnabled: n/a AnalogProviders: n/a MSXUCapability: 0x000001e6 ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 FriendlyName: AvStream Media Device Category: Sensor Group SymbolicLink: \\?\swd#sgdevapi#b40bf605655eff69b35338e038df6eb2f27b929a70faf537027865fcca7bd0c8#{669c7214-0a88-4311-a7f3-4e79820e33bd}\b40bf605655eff69b35338e038df6eb2f27b929a70faf537027865fcca7bd0c8 DeviceSymbolicLinks: \\?\USB#VID_5986&PID_215D&MI_00#6&2b7db935&1&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\GLOBAL,\\?\USB#VID_5986&PID_215D&MI_02#6&2b7db935&1&0002#{24e552d7-6523-47f7-a647-d3465bf1f5ca}\GLOBAL ProfileIDs: {B4894D81-62B7-4EEC-8740-80658C4A9D3E},0;{81361B22-700B-4546-A2D4-C52E907BFC27},0 ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04F3, 0x3293 FF Driver: n/a Device Name: HIDI2C Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x04F3, 0x3293 FF Driver: n/a Device Name: Wacom Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x056A, 0x5365 FF Driver: n/a Device Name: Wacom Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x056A, 0x5365 FF Driver: n/a Device Name: Wacom Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x056A, 0x5365 FF Driver: n/a Device Name: vJoy Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x1234, 0xBEAD FF Driver: C:\Windows\System32\pid.dll FF Driver Date: 5/6/2022 23:20:04 FF Driver Version: 10.00.22621.0001 FF Driver Size: 69632 bytes Device Name: Wacom Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x056A, 0x5365 FF Driver: n/a Device Name: Wacom Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x056A, 0x5365 FF Driver: n/a Device Name: Wacom Device Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x056A, 0x5365 FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x51ED | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 7/11/2023 14:36:51, 722264 bytes | +-+ USB Input Device | | Vendor/Product ID: 0x03F0, 0x134A | | Location: Port_#0003.Hub_#0002 | | Matching Device ID: USB\Class_03&SubClass_01 | | Service: HidUsb | | Driver: hidusb.sys, 3/6/2023 05:29:01, 77824 bytes | | Driver: hidclass.sys, 3/6/2023 05:29:01, 278528 bytes | | Driver: hidparse.sys, 3/6/2023 05:29:01, 90112 bytes | | | +-+ HID-compliant mouse | | | Vendor/Product ID: 0x03F0, 0x134A | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | Service: mouhid | | | Driver: mouhid.sys, 5/6/2022 23:19:25, 69632 bytes | | | Driver: mouclass.sys, 5/6/2022 23:19:25, 95592 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + Standard PS/2 Keyboard | Matching Device ID: *PNP0303 | Service: i8042prt | Driver: i8042prt.sys, 5/6/2022 23:19:25, 159744 bytes | Driver: kbdclass.sys, 5/6/2022 23:19:25, 95576 bytes | + HID-compliant mouse | Vendor/Product ID: 0x056A, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 5/6/2022 23:19:25, 69632 bytes | Driver: mouclass.sys, 5/6/2022 23:19:25, 95592 bytes | + HID-compliant mouse | Vendor/Product ID: 0x04F3, 0x0000 | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | Service: mouhid | Driver: mouhid.sys, 5/6/2022 23:19:25, 69632 bytes | Driver: mouclass.sys, 5/6/2022 23:19:25, 95592 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 88.5 GB Total Space: 486.1 GB File System: NTFS Model: WD PC SN740 SDDPMQD-512G-1101 Drive: G: Free Space: 5.1 GB Total Space: 15.4 GB File System: FAT32 Model: n/a -------------- System Devices -------------- Name: PCI Express Root Port Device ID: PCI\VEN_8086&DEV_A76E&SUBSYS_381317AA&REV_01\3&11583659&1&38 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.22621.1778 (English), 6/13/2023 20:58:20, 570704 bytes Name: Intel(R) SMBus - 51A3 Device ID: PCI\VEN_8086&DEV_51A3&SUBSYS_384517AA&REV_01\3&11583659&1&FC Driver: n/a Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_51E0&SUBSYS_383917AA&REV_01\3&11583659&1&B0 Driver: C:\Windows\System32\DriverStore\FileRepository\heci.inf_amd64_cf249bf95c3b8dcb\x64\TeeDriverW10x64.sys, 2306.04.0003.0000 (English), 2/27/2023 03:18:58, 320096 bytes Name: Intel(R) SPI (flash) Controller - 51A4 Device ID: PCI\VEN_8086&DEV_51A4&SUBSYS_383817AA&REV_01\3&11583659&1&FD Driver: n/a Name: Intel(R) LPC Controller - 519D Device ID: PCI\VEN_8086&DEV_519D&SUBSYS_381B17AA&REV_01\3&11583659&1&F8 Driver: C:\Windows\system32\DRIVERS\msisadrv.sys, 10.00.22621.0001 (English), 5/6/2022 23:19:04, 54608 bytes Name: Standard NVM Express Controller Device ID: PCI\VEN_15B7&DEV_5016&SUBSYS_501615B7&REV_01\4&2E4915AB&0&0032 Driver: C:\Windows\system32\DRIVERS\stornvme.sys, 10.00.22621.2070 (English), 8/8/2023 20:30:10, 251224 bytes Name: Intel(R) Integrated Sensor Solution Device ID: PCI\VEN_8086&DEV_51FC&SUBSYS_384717AA&REV_01\3&11583659&1&90 Driver: C:\Windows\System32\DriverStore\FileRepository\ish.inf_amd64_206ab8df50dd8cd2\ISH.sys, 3.01.0000.4589 (English), 8/14/2023 17:06:44, 175232 bytes Name: Intel(R) PCI Express Root Port #6 - 51BD Device ID: PCI\VEN_8086&DEV_51BD&SUBSYS_383E17AA&REV_01\3&11583659&1&E0 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.22621.1778 (English), 6/13/2023 20:58:20, 570704 bytes Name: Intel(R) Serial IO I2C Host Controller - 51E9 Device ID: PCI\VEN_8086&DEV_51E9&SUBSYS_382717AA&REV_01\3&11583659&1&A9 Driver: C:\Windows\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_e736c048ca307ed2\iaLPSS2_I2C_ADL.sys, 30.100.2237.0026 (English), 10/17/2022 12:20:10, 220224 bytes Name: Intel(R) USB 3.10 eXtensible Host Controller - 1.20 (Microsoft) Device ID: PCI\VEN_8086&DEV_51ED&SUBSYS_383A17AA&REV_01\3&11583659&1&A0 Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.22621.1928 (English), 7/11/2023 14:36:51, 677192 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.22621.1928 (English), 7/11/2023 14:36:51, 170824 bytes Name: PCI Express Root Port Device ID: PCI\VEN_8086&DEV_A73D&SUBSYS_383D17AA&REV_01\3&11583659&1&32 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.22621.1778 (English), 6/13/2023 20:58:20, 570704 bytes Name: Intel(R) Serial IO I2C Host Controller - 51E8 Device ID: PCI\VEN_8086&DEV_51E8&SUBSYS_383517AA&REV_01\3&11583659&1&A8 Driver: C:\Windows\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_e736c048ca307ed2\iaLPSS2_I2C_ADL.sys, 30.100.2237.0026 (English), 10/17/2022 12:20:10, 220224 bytes Name: Intel(R) GNA Scoring Accelerator module Device ID: PCI\VEN_8086&DEV_A74F&SUBSYS_380D17AA&REV_01\3&11583659&1&40 Driver: C:\Windows\System32\DriverStore\FileRepository\gna.inf_amd64_04d4eecc5838a558\gna.sys, 3.00.0000.1457 (English), 8/19/2022 04:02:16, 88784 bytes Name: PCI Express Root Port Device ID: PCI\VEN_8086&DEV_A74D&SUBSYS_380B17AA&REV_01\3&11583659&1&30 Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.22621.1778 (English), 6/13/2023 20:58:20, 570704 bytes Name: USB4(TM) Host Router (Microsoft) Device ID: PCI\VEN_8086&DEV_A76D&SUBSYS_381017AA&REV_01&USB4_MS_CM\3&11583659&1&6B Driver: C:\Windows\System32\DriverStore\FileRepository\usb4hostrouter.inf_amd64_1c6dfa4aa838b50b\Usb4HostRouter.sys, 10.00.22621.1928 (English), 7/11/2023 14:36:51, 611656 bytes Name: Intel(R) Iris(R) Xe Graphics Device ID: PCI\VEN_8086&DEV_A7A1&SUBSYS_380517AA&REV_04\3&11583659&1&10 Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdkmdn64.sys, 31.00.0101.4900 (English), 10/20/2023 10:13:42, 50729048 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxsn64.vp, 10/20/2023 13:03:14, 5313 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10iumd64.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:06, 4284432 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd11dxva64.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:58, 4095488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd12dxva64.dll, 31.00.0101.4900 (English), 10/20/2023 10:16:02, 3163672 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igddxvacommon64.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:34, 18789568 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\media_bin_64.dll, 31.00.0101.4900 (English), 10/20/2023 10:21:34, 30834856 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd12umd64.dll, 31.00.0101.4900 (English), 10/20/2023 10:16:44, 161864 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10um64xe.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:26, 26245040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10umt64xe.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:46, 21974608 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10mg64.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:12, 2279424 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd12um64xel.dll, 31.00.0101.4900 (English), 10/20/2023 10:16:36, 27258480 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdgmm64.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:58, 4482296 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igfxcmrt64.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:44, 222712 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igfx11cmrt64.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:40, 225816 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdumdim64.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:32, 2485000 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd9trinity32.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:06, 19710784 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd9trinity64.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:14, 21478360 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdail64.dll, 10/20/2023 10:13:32, 277072 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd9dxva64.dll, 31.00.0101.4900 (English), 10/20/2023 10:16:56, 20442176 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iga64.dll, 31.00.0101.4900 (English), 10/20/2023 10:14:20, 3315024 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igc64.dll, 31.00.0101.4900 (English), 10/20/2023 10:14:46, 67669880 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\DnnlPlugin.dll, 10/20/2023 10:13:54, 19304488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\XeFX.dll, 0.02.0267.0000 (English), 10/20/2023 10:23:16, 141200 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igxess.dll, 0.04.0267.0000 (English), 10/20/2023 10:19:34, 88133560 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\UniversalAdapter64.dll, 10/20/2023 10:23:08, 623080 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igmlsblob64xel.dll, 0.01.0050.0000 (English), 10/20/2023 10:18:54, 3066552 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igmlsblob64xeh.dll, 0.01.0050.0000 (English), 10/20/2023 10:18:48, 6325680 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\opencl-clang64.dll, 2.00.0009.0000 (English), 10/20/2023 10:22:50, 66983528 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdfcl64.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:50, 1158592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdmd64.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:12, 16656832 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdml64.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:20, 3368224 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdde64.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:22, 419112 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdinfo64.dll, 10/20/2023 10:18:02, 165376 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdext64.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:48, 161384 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10iumd32.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:02, 4186800 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd11dxva32.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:54, 3425488 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd12dxva32.dll, 31.00.0101.4900 (English), 10/20/2023 10:16:00, 2640408 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\media_bin_32.dll, 31.00.0101.4900 (English), 10/20/2023 10:21:18, 25409328 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igddxvacommon32.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:26, 17839576 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd12umd32.dll, 31.00.0101.4900 (English), 10/20/2023 10:16:44, 128152 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10um32xe.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:16, 24221864 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10umt32xe.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:38, 20303704 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd10mg32.dll, 31.00.0101.4900 (English), 10/20/2023 10:15:10, 2190024 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd12um32xel.dll, 31.00.0101.4900 (English), 10/20/2023 10:16:18, 26591664 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdgmm32.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:52, 3427568 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdumdim32.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:26, 2664176 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdail32.dll, 10/20/2023 10:13:30, 253016 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igd9dxva32.dll, 31.00.0101.4900 (English), 10/20/2023 10:16:48, 19278056 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igfxcmrt32.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:42, 180328 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igfx11cmrt32.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:36, 181352 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iga32.dll, 31.00.0101.4900 (English), 10/20/2023 10:14:18, 2658984 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igc32.dll, 31.00.0101.4900 (English), 10/20/2023 10:14:28, 60122184 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\UniversalAdapter32.dll, 10/20/2023 10:23:06, 536264 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\opencl-clang32.dll, 2.00.0009.0000 (English), 10/20/2023 10:22:34, 48930784 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdfcl32.dll, 31.00.0101.4900 (English), 10/20/2023 10:13:34, 1108560 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdmd32.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:06, 12287592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdml32.dll, 31.00.0101.4900 (English), 10/20/2023 10:18:18, 1044432 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdde32.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:22, 353872 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdinfo32.dll, 10/20/2023 10:18:00, 141680 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdext32.dll, 31.00.0101.4900 (English), 10/20/2023 10:17:40, 136416 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libigd12dxva64.so, 10/20/2023 13:01:32, 24028168 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libigd12umd64.so, 10/20/2023 13:01:28, 47296 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libigd12um64xel.so, 10/20/2023 13:01:32, 7402088 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libigc.so, 10/20/2023 13:01:30, 44951528 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libLLVM-14.so, 10/20/2023 13:01:30, 56201880 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libigdgmm_w.so.12, 10/20/2023 13:01:30, 2349712 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libUniversalAdapter64.so, 10/20/2023 13:01:30, 587840 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libigdfcl.so, 10/20/2023 13:01:30, 1042936 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libopencl-clang.so.14, 10/20/2023 13:01:30, 164356216 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libwsl_compute_helper.so, 10/20/2023 13:01:32, 559152 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxo64.vp, 10/20/2023 13:01:46, 42513 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxc64.vp, 10/20/2023 13:01:46, 44194 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxg64.vp, 10/20/2023 13:01:48, 43760 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxo64_dev.vp, 10/20/2023 13:01:48, 43143 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxc64_dev.vp, 10/20/2023 13:01:48, 43214 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxg64_dev.vp, 10/20/2023 13:01:48, 43732 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxa64.vp, 10/20/2023 13:01:48, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\iglhxa64.cpa, 10/20/2023 13:01:48, 1376256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\cp_resources.bin, 10/20/2023 13:01:48, 2572396 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igxelpicd64.dll, 31.00.0101.4900 (English), 10/20/2023 10:14:56, 18479184 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igxelpicd32.dll, 31.00.0101.4900 (English), 10/20/2023 10:14:52, 15147600 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\OSSCOPYRIGHT.txt, 10/20/2023 03:21:36, 1372 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igvk64.dll, 31.00.0101.4900 (English), 10/20/2023 10:19:10, 19662768 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igvk64.json, 10/20/2023 03:22:38, 135 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\VulkanRT-EULA.txt, 6/30/2023 11:14:22, 4008 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igvk32.dll, 31.00.0101.4900 (English), 10/20/2023 10:19:00, 18353400 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igvk32.json, 10/20/2023 03:22:38, 135 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igvkMedia64.dll, 31.00.0101.4900 (English), 10/20/2023 10:19:22, 1341496 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igvkMedia32.dll, 31.00.0101.4900 (English), 10/20/2023 10:19:20, 1042352 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\vulkan-1-64.dll, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 664144 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\vulkaninfo-64.exe, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 851648 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\vulkan-1-32.dll, 1.03.0250.0001 (English), 10/20/2023 10:16:06, 649816 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\vulkaninfo-32.exe, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 732352 bytes Driver: C:\Windows\SysWow64\vulkan-1.dll, 1.03.0250.0001 (English), 10/20/2023 10:16:06, 649816 bytes Driver: C:\Windows\SysWow64\vulkaninfo.exe, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 732352 bytes Driver: C:\Windows\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0250.0001 (English), 10/20/2023 10:16:06, 649816 bytes Driver: C:\Windows\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 732352 bytes Driver: C:\Windows\system32\vulkan-1.dll, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 664144 bytes Driver: C:\Windows\system32\vulkaninfo.exe, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 851648 bytes Driver: C:\Windows\system32\vulkan-1-999-0-0-0.dll, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 664144 bytes Driver: C:\Windows\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0250.0001 (English), 10/20/2023 10:16:08, 851648 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\Intel_OpenCL_ICD32.dll, 2.02.0008.0000 (English), 10/20/2023 10:15:20, 378960 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdrcl32.dll, 23.20.0101.4900 (English), 10/20/2023 10:14:04, 10735808 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\Intel_OpenCL_ICD64.dll, 2.02.0008.0000 (English), 10/20/2023 10:15:22, 516176 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\ze_loader.dll, 1.14.0000.0000 (English), 10/20/2023 10:16:20, 466624 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\ze_validation_layer.dll, 1.14.0000.0000 (English), 10/20/2023 10:16:24, 307392 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\ze_tracing_layer.dll, 1.14.0000.0000 (English), 10/20/2023 10:16:22, 518848 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\IntelControlLib.dll, 1.00.0164.0000 (English), 10/20/2023 10:20:06, 595656 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\IntelControlLib32.dll, 1.00.0164.0000 (English), 10/20/2023 10:20:10, 514512 bytes Driver: C:\Windows\SysWow64\IntelControlLib32.dll, 1.00.0164.0000 (English), 10/20/2023 10:20:10, 514512 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\igdrcl64.dll, 23.20.0101.4900 (English), 10/20/2023 10:14:08, 11968704 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\ze_intel_gpu64.dll, 1.03.27193.0000 (English), 10/20/2023 10:16:12, 16165568 bytes Driver: C:\Windows\SysWow64\OpenCL.dll, 3.00.0001.0000 (English), 5/12/2023 22:04:28, 76800 bytes Driver: C:\Windows\system32\OpenCL.dll, 3.00.0001.0000 (English), 5/12/2023 22:04:28, 118784 bytes Driver: C:\Windows\system32\ze_loader.dll, 1.14.0000.0000 (English), 10/20/2023 10:16:20, 466624 bytes Driver: C:\Windows\system32\ze_validation_layer.dll, 1.14.0000.0000 (English), 10/20/2023 10:16:24, 307392 bytes Driver: C:\Windows\system32\ze_tracing_layer.dll, 1.14.0000.0000 (English), 10/20/2023 10:16:22, 518848 bytes Driver: C:\Windows\system32\ControlLib.dll, 1.00.0164.0000 (English), 10/20/2023 10:13:50, 282128 bytes Driver: C:\Windows\SysWow64\ControlLib32.dll, 1.00.0164.0000 (English), 10/20/2023 10:13:52, 231016 bytes Driver: C:\Windows\SysWow64\libmfxhw32.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:00, 706224 bytes Driver: C:\Windows\SysWow64\mfxplugin32_hw.dll, 23.06.0021.0536 (English), 10/20/2023 10:15:24, 20688464 bytes Driver: C:\Windows\system32\libmfxhw64.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:00, 943320 bytes Driver: C:\Windows\system32\mfxplugin64_hw.dll, 23.06.0021.0536 (English), 10/20/2023 10:15:38, 27964496 bytes Driver: C:\Windows\system32\intel_gfx_api-x64.dll, 23.06.0021.0536 (English), 10/20/2023 10:20:12, 591992 bytes Driver: C:\Windows\system32\libvpl.dll, 2.09.0000.0000 (English), 10/20/2023 10:23:12, 577184 bytes Driver: C:\Windows\SysWow64\intel_gfx_api-x86.dll, 23.06.0021.0536 (English), 10/20/2023 10:20:14, 453632 bytes Driver: C:\Windows\SysWow64\libvpl.dll, 2.09.0000.0000 (English), 10/20/2023 10:23:10, 508952 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfxplugin64_hw.dll, 23.06.0021.0536 (English), 10/20/2023 10:15:38, 27964496 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfxplugin64_av1e_gacc.dll, 3.11.0005.0020 (English), 10/20/2023 10:21:54, 12444824 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\intel_gfx_api-x64.dll, 23.06.0021.0536 (English), 10/20/2023 10:20:12, 591992 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfxplugin32_hw.dll, 23.06.0021.0536 (English), 10/20/2023 10:15:24, 20688464 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfxplugin32_av1e_gacc.dll, 3.11.0005.0020 (English), 10/20/2023 10:21:50, 8538544 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\intel_gfx_api-x86.dll, 23.06.0021.0536 (English), 10/20/2023 10:20:14, 453632 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_h264ve_32.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:18, 2505624 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_mjpgvd_32.dll, 23.06.0021.0536 (English), 10/20/2023 10:15:56, 2410576 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_h265ve_32.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:22, 2518528 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_vp9ve_32.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:28, 2512864 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_encrypt_32.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:12, 2369744 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_av1hve_32.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:02, 2514512 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\c_32.cpa, 10/20/2023 13:01:52, 1361159 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\cpa_32.vp, 10/20/2023 13:01:52, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\dev_32.vp, 10/20/2023 13:01:52, 57143 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\he_32.vp, 10/20/2023 13:01:52, 75577 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mj_32.vp, 10/20/2023 13:01:54, 71117 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\h265e_32.vp, 10/20/2023 13:01:52, 77145 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\vp9e_32.vp, 10/20/2023 13:01:54, 76704 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_av1hve_32.vp, 10/20/2023 13:01:54, 76781 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_h264ve_64.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:20, 3049616 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_mjpgvd_64.dll, 23.06.0021.0536 (English), 10/20/2023 10:15:58, 2932304 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_h265ve_64.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:24, 3068120 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_vp9ve_64.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:30, 3062424 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_encrypt_64.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:14, 2883208 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_av1hve_64.dll, 23.06.0021.0536 (English), 10/20/2023 10:22:06, 3063992 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\c_64.cpa, 10/20/2023 13:01:54, 1376256 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\cpa_64.vp, 10/20/2023 13:01:54, 1125 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\dev_64.vp, 10/20/2023 13:01:54, 56359 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\he_64.vp, 10/20/2023 13:01:54, 13235 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mj_64.vp, 10/20/2023 13:01:56, 12959 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\h265e_64.vp, 10/20/2023 13:01:56, 13803 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\vp9e_64.vp, 10/20/2023 13:01:56, 13654 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\mfx_mft_av1hve_64.vp, 10/20/2023 13:01:56, 13623 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libmfx64-gen.dll, 23.10.0005.0001 (English), 10/20/2023 10:20:26, 23307888 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\libmfx32-gen.dll, 23.10.0005.0001 (English), 10/20/2023 10:20:16, 21669016 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\enctools32.dll, 10/20/2023 10:14:06, 7761592 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\enctools64.dll, 10/20/2023 10:14:12, 8890720 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\IntelCpHDCPSvc.exe, 31.00.0101.4900 (English), 10/20/2023 10:15:10, 347736 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\clangFEWrapper.dll, 10/20/2023 10:13:34, 33173896 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_2b7da3f145c0b5f4\clangFEWrapper32.dll, 10/20/2023 10:13:44, 26427808 bytes Name: PCI standard host CPU bridge Device ID: PCI\VEN_8086&DEV_A708&SUBSYS_380117AA&REV_01\3&11583659&1&00 Driver: n/a Name: Intel(R) USB 3.20 eXtensible Host Controller - 1.20 (Microsoft) Device ID: PCI\VEN_8086&DEV_A71E&SUBSYS_380F17AA&REV_01\3&11583659&1&68 Driver: C:\Windows\system32\DRIVERS\USBXHCI.SYS, 10.00.22621.1928 (English), 7/11/2023 14:36:51, 677192 bytes Driver: C:\Windows\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.22621.1928 (English), 7/11/2023 14:36:51, 170824 bytes Name: Intel(R) Innovation Platform Framework Processor Participant Device ID: PCI\VEN_8086&DEV_A71D&SUBSYS_380A17AA&REV_01\3&11583659&1&20 Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipf_lf.sys, 1.00.11200.30652 (English), 11/14/2022 02:23:36, 445080 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipf_cpu.sys, 1.00.11200.30652 (English), 11/14/2022 02:23:36, 80536 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipf_umdf2.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:38, 1129112 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipf_uf.exe, 1.00.11200.30652 (English), 11/14/2022 02:23:36, 2781336 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\dsp.dv, 11/14/2022 02:23:42, 418562 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ppm.dv, 11/14/2022 02:23:38, 255896 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\upe_capi.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:40, 61040 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\upe_wwan.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:42, 139376 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\upe_wifi.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:42, 72344 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\upe_nvme.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:40, 116888 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\upe_battery.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:40, 72856 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\upe_nvapi.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:40, 67224 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\upe_socwc.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:40, 235672 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\upe_hwpf.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:40, 75888 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipf_helper.exe, 1.00.11200.30652 (English), 11/14/2022 02:23:36, 612504 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipf_cmp.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:42, 141976 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipfcore.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:38, 693400 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipfipc.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:38, 579696 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_7218f3b363a821fe\ipfsrv.dll, 1.00.11200.30652 (English), 11/14/2022 02:23:38, 767128 bytes Name: Intel(R) Platform Monitoring Technology Driver Device ID: PCI\VEN_8086&DEV_A77D&SUBSYS_380E17AA&REV_01\3&11583659&1&50 Driver: C:\Windows\system32\DRIVERS\IntelPMT.sys, 10.00.22621.1485 (English), 4/20/2023 09:48:12, 91688 bytes Name: Intel� Smart Sound Technology BUS Device ID: PCI\VEN_8086&DEV_51CA&SUBSYS_383F17AA&REV_01\3&11583659&1&FB Driver: C:\Windows\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_b5ff032962a11ae8\IntcAudioBus.sys, 10.29.0000.8854 (English), 8/14/2023 17:06:48, 316016 bytes Driver: C:\Windows\system32\DRIVERS\drmk.sys, 10.00.22621.2070 (English), 8/8/2023 20:30:09, 143360 bytes Driver: C:\Windows\system32\DRIVERS\portcls.sys, 10.00.22621.2070 (English), 8/8/2023 20:30:09, 471040 bytes Name: Intel(R) Wi-Fi 6E AX211 160MHz Device ID: PCI\VEN_8086&DEV_51F1&SUBSYS_00948086&REV_01\3&11583659&1&A3 Driver: C:\Windows\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_eae931aa85cab080\Netwtw12.sys, 22.230.0000.0008 (English), 8/14/2023 17:15:06, 5231904 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_eae931aa85cab080\netwfw12.dat, 8/14/2023 17:15:06, 38549968 bytes Driver: C:\Windows\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_eae931aa85cab080\IntelIHVRouter12.dll, 22.12230.0000.0002 (English), 8/14/2023 17:15:06, 1474848 bytes Name: USB4(TM) Host Router (Microsoft) Device ID: PCI\VEN_8086&DEV_A73E&SUBSYS_380917AA&REV_01&USB4_MS_CM\3&11583659&1&6A Driver: C:\Windows\System32\DriverStore\FileRepository\usb4hostrouter.inf_amd64_1c6dfa4aa838b50b\Usb4HostRouter.sys, 10.00.22621.1928 (English), 7/11/2023 14:36:51, 611656 bytes Name: PCI Express Root Port Device ID: PCI\VEN_8086&DEV_A72F&SUBSYS_384017AA&REV_01\3&11583659&1&3A Driver: C:\Windows\system32\DRIVERS\pci.sys, 10.00.22621.1778 (English), 6/13/2023 20:58:20, 570704 bytes Name: Intel(R) Shared SRAM - 51EF Device ID: PCI\VEN_8086&DEV_51EF&SUBSYS_384117AA&REV_01\3&11583659&1&A2 Driver: n/a Name: BayHubTech Integrated MMC/SD controller Device ID: PCI\VEN_1217&DEV_8621&SUBSYS_389317AA&REV_01\4&1E07DD4D&0&00E0 Driver: C:\Windows\system32\DRIVERS\bhtsddr.sys, 2.01.0101.10630 (English), 9/6/2022 05:21:26, 186928 bytes Driver: C:\Windows\system32\bhtv5Icon.dll, 1.00.0000.0006 (English), 9/6/2022 05:21:28, 1908504 bytes Driver: C:\Windows\sysWoW64\bhtv5Icon.dll, 1.00.0000.0006 (English), 9/6/2022 05:21:28, 1908504 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.22621.2070 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.22621.2070 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.22621.2070 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.22621.0608 Mpeg4s Decoder DMO,0x00800001,1,1,mp4sdecd.dll,10.00.22621.0001 WMV Screen decoder DMO,0x00600800,1,1,wmvsdecd.dll,10.00.22621.0001 WMVideo Decoder DMO,0x00800001,1,1,wmvdecod.dll,10.00.22621.2070 Mpeg43 Decoder DMO,0x00800001,1,1,mp43decd.dll,10.00.22621.0001 Mpeg4 Decoder DMO,0x00800001,1,1,mpg4decd.dll,10.00.22621.0001 DV Muxer,0x00400000,0,0,qdv.dll,10.00.22621.0001 Color Space Converter,0x00400001,1,1,quartz.dll,10.00.22621.0755 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.22621.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.22621.0755 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.22621.0755 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.22621.2070 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.22621.2134 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.22621.0001 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.22621.2070 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.22621.0755 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.22621.0755 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.22621.0755 VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.22621.0001 MPEG-2 Splitter,0x005fffff,1,0,mpg2splt.ax,10.00.22621.0001 Closed Captions Analysis Filter,0x00200000,2,5,cca.dll,10.00.22621.0001 SBE2FileScan,0x00200000,0,0,sbe.dll,10.00.22621.2070 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22621.2070 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.22621.0755 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.22621.0755 DV Splitter,0x00600000,1,2,qdv.dll,10.00.22621.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.22621.0755 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.22621.2070 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.22621.0755 Video Renderer,0x00800001,1,0,quartz.dll,10.00.22621.0755 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.22621.2070 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.22621.0755 Video Renderer,0x00400000,1,0,quartz.dll,10.00.22621.0755 VPS Decoder,0x00200000,0,0,WSTPager.ax,10.00.22621.0001 WM ASF Writer,0x00400000,0,0,qasf.dll,12.00.22621.0001 VBI Surface Allocator,0x00600000,1,1,vbisurf.ax,10.00.22621.0001 File writer,0x00200000,1,0,qcap.dll,10.00.22621.0001 DVD Navigator,0x00200000,0,3,qdvd.dll,10.00.22621.0755 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.22621.0755 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22621.2070 WST Pager,0x00200000,1,1,WSTPager.ax,10.00.22621.0001 MPEG-2 Demultiplexer,0x00600000,1,1,mpg2splt.ax,10.00.22621.0001 DV Video Decoder,0x00800000,1,1,qdv.dll,10.00.22621.0001 SampleGrabber,0x00200000,1,1,qedit.dll,10.00.22621.0001 Null Renderer,0x00200000,1,0,qedit.dll,10.00.22621.0001 MPEG-2 Sections and Tables,0x005fffff,1,0,Mpeg2Data.ax,10.00.22621.0001 Microsoft AC3 Encoder,0x00200000,1,1,msac3enc.dll,10.00.22621.2070 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.22621.2070 Smart Tee,0x00200000,1,2,qcap.dll,10.00.22621.0001 Overlay Mixer,0x00200000,0,0,, AVI Decompressor,0x00600000,1,1,quartz.dll,10.00.22621.0755 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.22621.0755 Wave Parser,0x00400000,1,1,quartz.dll,10.00.22621.0755 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.22621.0755 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.22621.0755 File stream renderer,0x00400000,1,1,quartz.dll,10.00.22621.0755 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.22621.2070 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.22621.2070 AVI Mux,0x00200000,1,0,qcap.dll,10.00.22621.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.22621.0755 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.22621.0755 File Source (URL),0x00400000,0,1,quartz.dll,10.00.22621.0755 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.22621.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.22621.0755 BDA MPEG2 Transport Information Filter,0x00200000,2,0,psisrndr.ax,10.00.22621.0001 MPEG Video Decoder,0x40000001,1,1,quartz.dll,10.00.22621.0755 WDM Streaming Tee/Splitter Devices: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 Video Compressors: WMVideo8 Encoder DMO,0x00600800,1,1,wmvxencd.dll,10.00.22621.0001 WMVideo9 Encoder DMO,0x00600800,1,1,wmvencod.dll,10.00.22621.0001 MSScreen 9 encoder DMO,0x00600800,1,1,wmvsencd.dll,10.00.22621.0001 DV Video Encoder,0x00200000,0,0,qdv.dll,10.00.22621.0001 MJPEG Compressor,0x00200000,0,0,quartz.dll,10.00.22621.0755 Audio Compressors: WM Speech Encoder DMO,0x00600800,1,1,WMSPDMOE.DLL,10.00.22621.0001 WMAudio Encoder DMO,0x00600800,1,1,WMADMOE.DLL,10.00.22621.0001 IMA ADPCM,0x00200000,1,1,quartz.dll,10.00.22621.0755 PCM,0x00200000,1,1,quartz.dll,10.00.22621.0755 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.22621.0755 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.22621.0755 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.22621.0755 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.22621.0755 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.22621.0755 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.22621.2070 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.22621.2070 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.22621.2070 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.22621.0755 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.22621.0755 WDM Streaming Capture Devices: ,0x00000000,0,0,, Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 ,0x00000000,0,0,, Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 Integrated Camera,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 WDM Streaming Rendering Devices: Realtek HD Audio output with SST,0x00200000,2,2,ksproxy.ax,10.00.22621.0001 Realtek HD Audio 2nd output with SST,0x00200000,2,2,ksproxy.ax,10.00.22621.0001 BDA Network Providers: Microsoft ATSC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22621.0001 Microsoft DVBC Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22621.0001 Microsoft DVBS Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22621.0001 Microsoft DVBT Network Provider,0x00200000,0,1,MSDvbNP.ax,10.00.22621.0001 Microsoft Network Provider,0x00200000,0,1,MSNP.ax,10.00.22621.0001 Video Capture Sources: Integrated Camera,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 Intel Virtual Camera,0x00200000,0,1,VirtualCamDevice.dll,1.00.0000.0001 Multi-Instance Capable VBI Codecs: VBI Codec,0x00600000,1,4,VBICodec.ax,10.00.22621.0001 BDA Transport Information Renderers: BDA MPEG2 Transport Information Filter,0x00600000,2,0,psisrndr.ax,10.00.22621.0001 MPEG-2 Sections and Tables,0x00600000,1,0,Mpeg2Data.ax,10.00.22621.0001 WDM Streaming Communication Transforms: Tee/Sink-to-Sink Converter,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 Audio Renderers: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.22621.0755 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.22621.0755 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.22621.0755 DirectSound: Speakers (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.22621.0755 ---------------------------- 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.22621.2134 mfreadwrite.dll, 10.00.22621.1778 mfcaptureengine.dll, 10.00.22621.0001 mfsensorgroup.dll, 10.00.22621.1635 windows.media.dll, 10.00.22621.1928 frameserver.dll, 10.00.22621.1778 frameserverclient.dll, 10.00.22621.1635 --------------------------- Media Foundation Transforms --------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms] : , , , [, ], Video Decoders: Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 23.06.0021.0536 Intel� Hardware M-JPEG Decoder MFT, {00C69F81-0524-48C0-A353-4DD9D54F9A6E}, 0x6, 7, mfx_mft_mjpgvd_64.dll, 23.06.0021.0536 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.22621.2134 DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432}, 0x1, mfdvdec.dll, 10.00.22621.0001 Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT, 0x1, mp4sdecd.dll, 10.00.22621.0001 Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT, 0x1, msmpeg2vdec.dll, 10.00.22621.2134 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.22621.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.22621.2070 MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905}, 0x1, mfmjpegdec.dll, 10.00.22621.0001 Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject, 0x1, mp43decd.dll, 10.00.22621.0001 Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject, 0x1, mpg4decd.dll, 10.00.22621.0001 WebpImageExtension HEIFImageExtension VP9VideoExtensionDecoder MPEG2VideoExtension HEVCVideoExtension AV1VideoExtension Video Encoders: Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 23.06.0021.0536 Intel� Hardware Accelerated AV1 Encoder MFT, {62C053CE-5357-4794-8C5A-FBEFFEFFB82D}, 0x4, 7, mfx_mft_av1hve_64.dll, 23.06.0021.0536 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 23.06.0021.0536 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 23.06.0021.0536 Intel� Quick Sync Video H.264 Encoder MFT, {4BE8D3C0-0515-4A37-AD55-E4BAE19AF471}, 0x4, 7, mfx_mft_h264ve_64.dll, 23.06.0021.0536 Intel� Hardware Accelerated AV1 Encoder MFT, {62C053CE-5357-4794-8C5A-FBEFFEFFB82D}, 0x4, 7, mfx_mft_av1hve_64.dll, 23.06.0021.0536 Intel� Hardware H265 Encoder MFT, {BC10864D-2B34-408F-912A-102B1B867B6C}, 0x4, 7, mfx_mft_h265ve_64.dll, 23.06.0021.0536 Intel� Hardware VP9 Encoder MFT, {D186A626-77CA-4D80-942F-61E0A5111AFE}, 0x4, 7, mfx_mft_vp9ve_64.dll, 23.06.0021.0536 H264 Encoder MFT, {6CA50344-051A-4DED-9779-A43305165E35}, 0x1, mfh264enc.dll, 10.00.22621.0001 WMVideo8 Encoder MFT, CLSID_CWMVXEncMediaObject, 0x1, wmvxencd.dll, 10.00.22621.0001 H263 Encoder MFT, {BC47FCFE-98A0-4F27-BB07-698AF24F2B38}, 0x1, mfh263enc.dll, 10.00.22621.0001 WMVideo9 Encoder MFT, CLSID_CWMV9EncMediaObject, 0x1, wmvencod.dll, 10.00.22621.0001 Microsoft MPEG-2 Video Encoder MFT, {E6335F02-80B7-4DC4-ADFA-DFE7210D20D5}, 0x2, msmpeg2enc.dll, 10.00.22621.2070 HEIFImageExtension VP9VideoExtensionEncoder HEVCVideoExtensionEncoder Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.22621.0001 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.22621.1265 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.22621.0608 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.22621.0001 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.22621.1265 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.22621.1928 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.22621.2070 MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E}, 0x1, MSAMRNBDecoder.dll, 10.00.22621.0001 WMAudio Decoder MFT, CLSID_CWMADecMediaObject, 0x1, WMADMOD.DLL, 10.00.22621.2070 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.22621.2070 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.22621.2134 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.22621.2134 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.22621.2070 Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A}, 0x1, MSOpusDecoder.dll, 10.00.22621.0001 Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9}, 0x1, MSFlacDecoder.dll, 10.00.22621.0001 Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B}, 0x1, MSAudDecMFT.dll, 10.00.22621.2070 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.22621.2070 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.22621.2134 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.22621.2134 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.22621.0608 Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879}, 0x1, MSAlacDecoder.dll, 10.00.22621.0001 ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD}, 0x1, mfcore.dll, 10.00.22621.2134 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.22621.2070 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.22621.2070 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.22621.2070 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.22621.2134 Microsoft FLAC Audio Encoder MFT, {128509E9-C44E-45DC-95E9-C255B8F466A6}, 0x1, MSFlacEncoder.dll, 10.00.22621.0001 WM Speech Encoder DMO, CLSID_CWMSPEncMediaObject2, 0x1, WMSPDMOE.DLL, 10.00.22621.0001 MS AMRNB Encoder MFT, {2FAE8AFE-04A3-423A-A814-85DB454712B0}, 0x1, MSAMRNBEncoder.dll, 10.00.22621.0001 Microsoft MPEG-2 Audio Encoder MFT, {46A4DD5C-73F8-4304-94DF-308F760974F4}, 0x1, msmpeg2enc.dll, 10.00.22621.2070 WMAudio Encoder MFT, CLSID_CWMAEncMediaObject, 0x1, WMADMOE.DLL, 10.00.22621.0001 Microsoft AAC Audio Encoder MFT, {93AF0C51-2275-45D2-A35B-F2BA21CAED00}, 0x1, mfAACEnc.dll, 10.00.22621.0001 Microsoft ALAC Audio Encoder MFT, {9AB6A28C-748E-4B6A-BFFF-CC443B8E8FB4}, 0x1, MSAlacEncoder.dll, 10.00.22621.0001 Microsoft Dolby Digital Encoder MFT, {AC3315C9-F481-45D7-826C-0B406C1F64B8}, 0x1, msac3enc.dll, 10.00.22621.2070 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.22621.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.22621.0608 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.22621.2134 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.22621.2134 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableEncoders = 1 EnableDecoders = 1 ------------------------------------- Media Foundation Byte Stream Handlers ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\ByteStreamHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] .3g2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .ac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .adt, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred .am?, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler .amr, {EFE6208A-0A2C-49FA-8A01-3768B559B6DA}, MF AMRNB Media Source ByteStreamHandler, Preferred .asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred .dvr-ms, {A8721937-E2FB-4D7A-A9EE-4EB08C890B6E}, MF SBE Source ByteStreamHandler .dvr-ms, {65964407-A5D8-4060-85B0-1CCD63F768E2}, dvr-ms Byte Stream Handler, Preferred .ec3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred .flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred .m2t, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m2ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mk3d, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mka, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mks, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mkv, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred .mod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mov, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp2v, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mp4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred .mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mpg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .mts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .nsc, {B084785C-DDE0-4D30-8CA8-05A373E185BE}, NSC Byte Stream Handler, Preferred .sami, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .smi, {7A56C4CB-D678-4188-85A8-BA2EF68FA10D}, SAMI Byte Stream Handler, Preferred .tod, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .ts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .uvu, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred .vob, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred .wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred .weba, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred .wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred .wtv, {65964407-A5D8-4060-85B0-1CCD63F768E2}, WTV Byte Stream Handler, Preferred audio/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/aacp, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/eac3, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/L16, {3FFB3B8C-EB99-472B-8902-E1C1B05F07CF}, LPCM Byte Stream Handler, Preferred audio/mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/MP4A-LATM, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/mpa, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/mpeg3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/vnd.dlna.adts, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/vnd.dolby.dd-raw, {46031BA1-083F-47D9-8369-23C92BDAB2FF}, AC-3 Byte Stream Handler, Preferred audio/wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred audio/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred audio/x-aac, {926F41F7-003E-4382-9E84-9E953BE10562}, ADTS Byte Stream Handler, Preferred audio/x-flac, {0E41CFB8-0506-40F4-A516-77CC23642D91}, MF FLAC Media Source ByteStreamHandler, Preferred audio/x-m4a, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred audio/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred audio/x-mp3, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-mpeg, {A82E50BA-8E92-41EB-9DF2-433F50EC2993}, MP3 Byte Stream Handler, Preferred audio/x-ms-wma, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred audio/x-wav, {42C9B9F5-16FC-47EF-AF22-DA05F7C842E3}, WAV Byte Stream Handler, Preferred video/3gpp, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/3gpp2, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/avi, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/mpeg, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred video/vnd.dece.mp4, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/vnd.dlna.mpeg-tts, {40871C59-AB40-471F-8DC3-1F259D862479}, MPEG2 Byte Stream Handler, Preferred video/webm, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, WEBM Byte Stream Handler, Preferred video/x-m4v, {271C3902-6095-4C45-A22F-20091816EE9E}, MPEG4 Byte Stream Handler, Preferred video/x-matroska, {1F9A2C18-D89E-463E-B4F4-BB90152ACC64}, MKV Byte Stream Handler, Preferred video/x-ms-asf, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wm, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-ms-wmv, {41457294-644C-4298-A28A-BD69F2C0CF3B}, ASF Byte Stream Handler, Preferred video/x-msvideo, {7AFA253E-F823-42F6-A5D9-714BDE467412}, AVI Byte Stream Handler, Preferred -------------------------------- Media Foundation Scheme Handlers -------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\SchemeHandlers] [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\Preferred] , , [, Preferred] file:, {477EC299-1421-4BDD-971F-7CCB933F21AD}, File Scheme Handler, Preferred http:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler http:, {9EC4B4F9-3029-45AD-947B-344DE2A249E2}, Urlmon Scheme Handler http:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpd:, {44CB442B-9DA9-49DF-B3FD-023777B16E50}, Http Scheme Handler, Preferred https:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpsd:, {37A61C8B-7F8E-4D08-B12B-248D73E9AB4F}, Secure Http Scheme Handler, Preferred httpt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred httpu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcast:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred mcrecv:, {FA6D33D4-9405-4BA5-9983-12604AC8E77A}, Miracast Sink Scheme Handler, Preferred mms:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ms-appdata:, {CFC81939-3886-4ACF-9692-DA58037AE716}, MsAppData Scheme Handler, Preferred ms-appx-web:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppxWeb Scheme Handler, Preferred ms-appx:, {8DB0224B-3D65-4F6F-8E12-BEB4B78B8974}, MsAppx Scheme Handler, Preferred ms-winsoundevent:, {F79A6BF9-7415-4CF3-AE10-4559509ABC3C}, Sound Event Scheme Handler, Preferred rtsp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtsps:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspt:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred rtspu:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred sdp:, {E9F4EBAB-D97B-463E-A2B1-C54EE3F9414D}, Net Scheme Handler, Preferred ------------------------------------- Preferred Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\Preferred] , [, ] {EB27CEC4-163E-4CA3-8B74-8E25F91B517E}, Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B} {E06D8033-DB46-11CF-B4D1-00805F6CBBEA}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {E06D802C-DB46-11CF-B4D1-00805F6CBBEA}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFVideoFormat_MPEG2, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} {C2FE6F0A-4E3C-4DF1-9B60-50863091E4B9}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} MEDIASUBTYPE_DOLBY_DDPLUS, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} {A61AC364-AD0E-4744-89FF-213CE0DF8804}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {A2E58EB7-0FA9-48BB-A40C-FA0E156D0645}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {7634706D-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {73616D72-767A-494D-B478-F29D25DC9037}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} MEDIASUBTYPE_mp4s, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_DVSL, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVSD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} MFVideoFormat_DVHD, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {63616C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} MFVideoFormat_MP4V, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_MP4S, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT {53314356-0000-0010-8000-00AA00389B71}, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVR, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_WMVP, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MJPG, MJPEG Decoder MFT, {CB17E772-E1CC-4633-8450-5617AF577905} MEDIASUBTYPE_WMVA, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {3F40F4F0-5622-4FF8-B6D8-A17A584BEE5E}, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MEDIASUBTYPE_mpg4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MPG4, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_H264, Microsoft H264 Video Decoder MFT, CLSID_CMSH264DecoderMFT MFVideoFormat_WMV3, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject {33363248-0000-0010-8000-00AA00389B71}, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_mp43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MFVideoFormat_MP43, Mpeg43 Decoder MFT, CLSID_CMpeg43DecMediaObject MEDIASUBTYPE_m4s2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MFVideoFormat_WMV2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS2, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_M4S2, Mpeg4s Decoder MFT, CLSID_CMpeg4sDecMFT MEDIASUBTYPE_WVP2, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MEDIASUBTYPE_mp42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MEDIASUBTYPE_MP42, Mpeg4 Decoder MFT, CLSID_CMpeg4DecMediaObject MFVideoFormat_WMV1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_MSS1, WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject MFVideoFormat_MPG1, Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9} MFVideoFormat_WVC1, WMVideo Decoder MFT, CLSID_CWMVDecMediaObject MFVideoFormat_DVC, DV Decoder MFT, {404A6DE5-D4D6-4260-9BC7-5A6CBD882432} {0000F1AC-0000-0010-8000-00AA00389B71}, Microsoft FLAC Audio Decoder MFT, {6B0B3E6B-A2C5-4514-8055-AFE8A95242D9} {00007361-0000-0010-8000-00AA00389B71}, MS AMRNB Decoder MFT, {265011AE-5481-4F77-A295-ABB6FFE8D63E} {0000704F-0000-0010-8000-00AA00389B71}, Microsoft Opus Audio Decoder MFT, {63E17C10-2D43-4C42-8FE3-8D8B63E46A6A} {00006C61-0000-0010-8000-00AA00389B71}, Microsoft ALAC Audio Decoder MFT, {C0CD7D12-31FC-4BBC-B363-7322EE3E1879} {00002001-0000-0010-8000-00AA00389B71}, DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F} {00002000-0000-0010-8000-00AA00389B71}, Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4} MFAudioFormat_AAC, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_ADTS, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_WMAudio_Lossless, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV9, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MFAudioFormat_WMAudioV8, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_MSAUDIO1, WMAudio Decoder MFT, CLSID_CWMADecMediaObject MEDIASUBTYPE_RAW_AAC1, Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT MFAudioFormat_MP3, MP3 Decoder MFT, CLSID_CMP3DecMediaObject MFAudioFormat_MPEG, Microsoft MPEG Audio Decoder MFT, {70707B39-B2CA-4015-ABEA-F8447D22D88B} {00000031-0000-0010-8000-00AA00389B71}, GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC} {00000011-0000-0010-8000-00AA00389B71}, IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE} KSDATAFORMAT_SUBTYPE_MULAW, G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514} {00000006-0000-0010-8000-00AA00389B71}, A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786} KSDATAFORMAT_SUBTYPE_ADPCM, ADPCM ACM Wrapper MFT, {CA34FE0A-5722-43AD-AF23-05F7650257DD} WMMEDIASUBTYPE_WMSP2, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject MFAudioFormat_MSP1, WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject ------------------------------------- Disabled Media Foundation Transforms ------------------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms\DoNotUse] ------------------------ Disabled Media Sources ------------------------ [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\MediaSources\DoNotUse] --------------- EVR Power Information --------------- Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) Quality Flags: 2576 Enabled: Force throttling Allow half deinterlace Allow scaling Decode Power Usage: 100 Balanced Flags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 50 PowerFlags: 1424 Enabled: Force throttling Allow batching Force half deinterlace Force scaling Decode Power Usage: 0 --------------- Diagnostics --------------- Windows Error Reporting: +++ WER0 +++: Fault bucket , type 0 Event Name: StoreAgentScanForUpdatesFailure0 Response: Not available Cab Id: 0 Problem signature: P1: Update; P2: 8024402c P3: 22621 P4: 2134 P5: Windows.Desktop P6: P7: P8: P9: P10: +++ WER1 +++: Fault bucket , type 0 Event Name: StoreAgentScanForUpdatesFailure0 Response: Not available Cab Id: 0 Problem signature: P1: Update; P2: 8024001e P3: 22621 P4: 2134 P5: Windows.Desktop P6: P7: P8: P9: P10: +++ WER2 +++: Fault bucket , type 0 Event Name: StoreAgentScanForUpdatesFailure0 Response: Not available Cab Id: 0 Problem signature: P1: Update; P2: 8024402c P3: 22621 P4: 2134 P5: Windows.Desktop P6: P7: P8: P9: P10: +++ WER3 +++: Fault bucket , type 0 Event Name: MoAppHang Response: Not available Cab Id: 0 Problem signature: P1: AppUp.IntelGraphicsExperience_1.100.5185.0_x64__8j3eq9eme6ctt P2: praid:App P3: 1.100.5185.0 P4: 64d20123 P5: 1ec2 P6: 2097152 P7: P8: P9: P10: +++ WER4 +++: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: ArcControlService.exe P2: 1.73.5335.2 P3: 6504dca5 P4: ArcControlService.exe P5: 1.73.5335.2 P6: 6504dca5 P7: c0000005 P8: 0000000000035ad6 P9: P10: +++ WER5 +++: Fault bucket , type 0 Event Name: StoreAgentDownloadFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Update; P2: 80240438 P3: 22621 P4: 2134 P5: Windows.Desktop P6: G P7: P8: P9: P10: +++ WER6 +++: Fault bucket , type 0 Event Name: StoreAgentScanForUpdatesFailure0 Response: Not available Cab Id: 0 Problem signature: P1: Update; P2: 8024402c P3: 22621 P4: 2134 P5: Windows.Desktop P6: P7: P8: P9: P10: +++ WER7 +++: Fault bucket , type 0 Event Name: StoreAgentScanForUpdatesFailure0 Response: Not available Cab Id: 0 Problem signature: P1: Update; P2: 8024001e P3: 22621 P4: 2134 P5: Windows.Desktop P6: P7: P8: P9: P10: +++ WER8 +++: Fault bucket , type 0 Event Name: StoreAgentScanForUpdatesFailure0 Response: Not available Cab Id: 0 Problem signature: P1: Update; P2: 8024402c P3: 22621 P4: 2134 P5: Windows.Desktop P6: P7: P8: P9: P10: +++ WER9 +++: Fault bucket , type 0 Event Name: MoAppHang Response: Not available Cab Id: 0 Problem signature: P1: AppUp.IntelGraphicsExperience_1.100.5185.0_x64__8j3eq9eme6ctt P2: praid:App P3: 1.100.5185.0 P4: 64d20123 P5: 1ec2 P6: 2097152 P7: P8: P9: P10: ...#SSU#...