# SSU Scan Information Scan Info: Version:"3.0.0.2" Date:"02-27-2024" Time:"00:00:39.8096139" # Scanned Hardware Computer: BaseBoard Manufacturer:"ASUSTeK COMPUTER INC." BIOS Mode:"UEFI" BIOS Version/Date:"American Megatrends Inc. 1630 , 02-04-2024 12:00 AM" CD or DVD:"Not Available" Embedded Controller Version:"255.255" Platform Role:"Desktop" Processor:"13th Gen Intel(R) Core(TM) i5-13600KF , GenuineIntel" Secure Boot State:"Off" SMBIOS Version:"3.5" Sound Card:"NVIDIA Virtual Audio Device (Wave Extensible) (WDM)" Sound Card:"HyperX Cloud Stinger Core Wireless + 7.1" Sound Card:"NVIDIA High Definition Audio" Sound Card:"Realtek High Definition Audio" Sound Card:"ASUS Utility" System Manufacturer:"ASUS" System Model:"System Product Name" System SKU:"SKU" System Type:"x64-based PC" - "Display" Intel ® Graphics Driver Version:"Not Available" - "NVIDIA GeForce RTX 3070 Ti" Adapter Compatibility:"NVIDIA" Adapter DAC Type:"Integrated RAMDAC" Adapter RAM:"4.00 GB" Availability:"Running or Full Power" Bits Per Pixel:"32" Caption:"NVIDIA GeForce RTX 3070 Ti" CoInstallers:"oem25.inf,Section071,Integrated RAMDAC,NVIDIA GeForce RTX 3070 Ti" Color Table Entries:"4294967296" Dedicated Video Memory:"Not Available" Driver:"nvlddmkm.sys" Driver Date:"02-14-2024 07:00 PM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvlddmkm.sys" Driver Provider:"NVIDIA" Driver Version:"31.0.15.5161" INF:"oem25.inf" INF Section:"Section071" Install Date:"Not Available" Installed Drivers:"C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"Not Available" Location:"PCI bus 1, device 0, function 0" Manufacturer:"NVIDIA" Microsoft DirectX* Version:"DirectX 12" Monochrome:"No" Number of Colors:"4294967296" Number of Video Pages:"Not Available" PNP Device ID:"PCI\VEN_10DE&DEV_2482&SUBSYS_408F1458&REV_A1\4&256A0AA8&0&0008" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Refresh Rate - Current:"59 Hz" Refresh Rate - Maximum:"143 Hz" Refresh Rate - Minimum:"50 Hz" Resolution:"2560 X 1440" Scan Mode:"Noninterlaced" Service Name:"nvlddmkm" Status:"OK" Video Architecture:"VGA" Video Memory:"Unknown" Video Processor:"NVIDIA GeForce RTX 3070 Ti" - "Memory" Physical Memory (Available):"24.49 GB" Physical Memory (Installed):"32 GB" Physical Memory (Total):"31.82 GB" - "BANK 0" Capacity:"16 GB" Channel:"Controller0-DIMM1" Configured Clock Speed:"6000 MHz" Configured Voltage:"1100 millivolts" Data Width:"64 bits" Form Factor:"DIMM" Interleave Position:"First position" Manufacturer:"Corsair" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"CMK32GX5M2E6000C36" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "BANK 0" Capacity:"16 GB" Channel:"Controller1-DIMM1" Configured Clock Speed:"6000 MHz" Configured Voltage:"1100 millivolts" Data Width:"64 bits" Form Factor:"DIMM" Interleave Position:"Second position" Manufacturer:"Corsair" Maximum Voltage:"Not Available" Memory Type:"Unknown" Minimum Voltage:"Not Available" Part Number:"CMK32GX5M2E6000C36" Serial Number:"00000000" Status:"Not Available" Type:"Synchronous" - "Motherboard" Availability:"Running or Full Power" BIOS:"1630, ALASKA - 1072009" Caption:"Motherboard" Chipset:"Not Available" Date:"02-03-2024 07:00 PM" Install Date:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Manufacturer:"ASUSTeK COMPUTER INC." Model:"Not Available" Part Number:"Not Available" PNP Device ID:"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"Not Available" Product:"TUF GAMING Z790-PLUS WIFI" Serial Number:"230317743501557" Status:"OK" Version:"Rev 1.xx" - "Networking" Intel ® Network Connections Install Options:"Not Available" Intel ® Network Connections Version:"Not Available" Intel ® PROSet/Wireless Software Version:"Not Available" - "Bluetooth Device (Personal Area Network)" Availability:"Running or Full Power" Caption:"Bluetooth Device (Personal Area Network)" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"Not Available" DHCP Lease Obtained:"Not Available" DHCP Server:"Not Available" Driver:"bthpan.sys" Driver Date:"06-21-2006 12:00 AM" Driver Path:"C:\WINDOWS\system32\drivers\bthpan.sys" Driver Provider:"Microsoft" Driver Version:"10.0.22621.2506" Index:"0004" INF:"bthpan.inf" INF Section:"BthPan.Install" Install Date:"Not Available" Installed:"Yes" IP Address:"Not Available" IP Subnet:"Not Available" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02-22-2024 08:25 PM" Location:"Not Available" MAC Address:"58:1C:F8:29:24:7A" Manufacturer:"Microsoft" Net Connection ID:"Bluetooth Network Connection" NetCfgInstanceId:"{95386554-D590-4823-B474-D8F051FAF1F2}" PNP Device ID:"BTH\MS_BTHPAN\6&29D56E15&0&2" Port:"Not Available" Power Management (Low Power):"Not Available" Power Management (Wake On LAN):"Not Available" Power Management (Wake on Magic Packet):"Not Available" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Bluetooth Device (Personal Area Network)" Service Name:"BthPan" Status:"Enabled" Type:"Ethernet 802.3" - "Service Bindings" Client for Microsoft Networks: File and Printer Sharing for Microsoft Networks: Internet Protocol Version 4 (TCP/IPv4): Internet Protocol Version 6 (TCP/IPv6): Link-Layer Topology Discovery Mapper I/O Driver: Link-Layer Topology Discovery Responder: Microsoft LLDP Protocol Driver: - "Intel(R) Ethernet Controller I226-V" Availability:"Running or Full Power" - "Caption":"Intel(R) Ethernet Controller I226-V" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Ethernet+Controller+I226+V" CoInstallers:"Not Available" Default IP Gateway:"Not Available" DHCP Enabled:"Yes" DHCP Lease Expires:"02-22-2024 08:25 PM" DHCP Lease Obtained:"02-22-2024 08:25 PM" DHCP Server:"255.255.255.255" Driver:"e2fn.sys" Driver Date:"06-29-2023 12:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\e2fn.inf_amd64_fcb868ac03f43b71\e2fn.sys" Driver Provider:"Intel" Driver Version:"2.1.3.15" ETrackID:"Not Available" Index:"0001" INF:"oem83.inf" INF Section:"I226.10.0.1..21390" Install Date:"Not Available" Installed:"Yes" IP Address:"169.254.93.196;fe80::5adc:f6eb:3480:a70c" IP Subnet:"255.255.0.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02-22-2024 08:25 PM" Location:"PCI bus 6, device 0, function 0" MAC Address:"08:BF:B8:3D:F2:54" Manufacturer:"Intel" Net Connection ID:"Ethernet" NetCfgInstanceId:"{A2577A90-C985-4827-BD77-322309A2E202}" NVM Version:"Not Available" Part Number:"Not Available" PNP Device ID:"PCI\VEN_8086&DEV_125C&SUBSYS_88671043&REV_06\08BFB8FFFF3DF25400" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: Yes" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Ethernet Controller I226-V" Service Name:"e2fnexpress" Status:"Enabled" 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" *EEE:Energy Efficient Ethernet:"Off (0)" *FlowControl:Flow Control:"Rx & Tx Enabled (3)" *IdleRestriction:Idle power down restriction:"Disabled (0)" *InterruptModeration:Interrupt Moderation:"Enabled (1)" *IPChecksumOffloadIPv4:IPv4 Checksum Offload:"Rx & Tx Enabled (3)" *JumboPacket:Jumbo Packet:"Disabled (1514)" *LsoV2IPv4:Large Send Offload V2 (IPv4):"Enabled (1)" *LsoV2IPv6:Large Send Offload V2 (IPv6):"Enabled (1)" *PMARPOffload:ARP Offload:"Enabled (1)" *PMNSOffload:NS Offload:"Enabled (1)" *PriorityVLANTag:Packet Priority & VLAN:"Packet Priority & VLAN Enabled (3)" *SpeedDuplex:Speed & Duplex:"Auto Negotiation (0)" *TCPChecksumOffloadIPv4:TCP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *TCPChecksumOffloadIPv6:TCP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv4:UDP Checksum Offload (IPv4):"Rx & Tx Enabled (3)" *UDPChecksumOffloadIPv6:UDP Checksum Offload (IPv6):"Rx & Tx Enabled (3)" *WakeOnMagicPacket:Wake on Magic Packet:"Enabled (1)" *WakeOnPattern:Wake on Pattern Match:"Enabled (1)" ITR:Interrupt Moderation Rate:"Low (64)" WakeOnMagicPacketFromS5:Wake On Magic Packet From S5:"Enabled (1)" - "Intel(R) Wi-Fi 6E AX211 160MHz" Access Point:"68:ff:7b:47:ae:c3" Authentication:"WPA2-Personal" Availability:"Running or Full Power" - "Caption":"Intel(R) Wi-Fi 6E AX211 160MHz" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=Wi+Fi+6E+AX211+160MHz" Channel:"36" Cipher:"CCMP" CoInstallers:"Not Available" Connection Mode:"Auto Connect" Default IP Gateway:"192.168.2.1" DHCP Enabled:"Yes" DHCP Lease Expires:"03-01-2024 08:12 PM" DHCP Lease Obtained:"02-27-2024 08:12 PM" DHCP Server:"192.168.2.1" Driver:"Netwtw14.sys" Driver Date:"10-31-2023 12:00 AM" Driver Path:"C:\WINDOWS\system32\DriverStore\FileRepository\netwtw6e.inf_amd64_3600c12b90247a8b\Netwtw14.sys" Driver Provider:"Intel" Driver Version:"23.10.0.8" Index:"0002" INF:"oem96.inf" INF Section:"Install_GEN_SLR_GfP2_211_AX_6G_2x2_WinT" Install Date:"Not Available" Installed:"Yes" IP Address:"192.168.2.83;fe80::5b5e:8c02:7bb8:e13d" IP Subnet:"255.255.255.0;64" Last Error Code:"Not Available" Last Error Code Description:"Not Available" Last Reset:"02-22-2024 08:25 PM" Location:"PCI bus 0, device 20, function 3" MAC Address:"58:1C:F8:29:24:76" Manufacturer:"Intel Corporation" Net Connection ID:"Wi-Fi" NetCfgInstanceId:"{4A9FB731-92AA-4FDC-BC20-E261FE781C37}" Network Name:"BELL842" Network Type:"Infrastructure" PNP Device ID:"PCI\VEN_8086&DEV_7A70&SUBSYS_00948086&REV_11\3&11583659&0&A3" Port:"Not Available" Power Management (Low Power):"Active: Yes, Enable: Yes" Power Management (Wake On LAN):"Active: Yes, Enable: No" Power Management (Wake on Magic Packet):"Active: Yes, EnableWakeOnMagicPacketOnly: No" Power Management Capabilities:"Not Available" Power Management Supported:"No" Product Type:"Intel(R) Wi-Fi 6E AX211 160MHz" Profile:"BELL842" Radio Type:"802.11ac" Receive Rate:"650 Mbps" Service Name:"Netwtw14" Signal Strength:"89%" State:"connected" Status:"Enabled" Transmit Rate:"433.3 Mbps" 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\HarddiskVolume3" Internet Browser:"Internet Explorer,11.1, Microsoft Edge,122.0" Locale:"United States" OS Manufacturer:"Microsoft Corporation" OS Name:"Microsoft Windows 11 Pro" Other OS Description:"Not Available" Page File:"C:\pagefile.sys" Page File Space:"10.00 GB" Physical Memory (Available):"24.50 GB" Physical Memory (Installed):"32 GB" Physical Memory (Total):"31.82 GB" System Directory:"C:\WINDOWS\system32" Version:"10.0.22631 Build 22631" Virtual Memory (Available):"32.34 GB" Virtual Memory (Total):"41.82 GB" Windows Directory:"C:\WINDOWS" - "Installed Updates" KB2468871:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871:"Microsoft .NET Framework 4 Extended [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2468871v2:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Extended [Not Available]" KB2478063:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2533523:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2533523:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Extended [Not Available]" KB2544514:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600211:"Microsoft .NET Framework 4 Extended [Not Available]" KB2600211:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Client Profile [Not Available]" KB2600217:"Microsoft .NET Framework 4 Extended [Not Available]" KB5027397:"Update [11/8/2023]" KB5034225:"Update [1/25/2024]" KB5034467:"Update [2/14/2024]" KB5034765:"Security Update [2/14/2024]" - "Processor" - "13th Gen Intel(R) Core(TM) i5-13600KF" Architecture:"x64" ATPO:"Not Available" Availability:"Running or Full Power" Caption:"Intel64 Family 6 Model 183 Stepping 1" - "Chipset Name":"13th Gen Intel(R) Core(TM) i5-13600KF" Link:"http://www.intel.com/content/www/us/en/search.html?keyword=13th+Gen++Core+i5+13600KF" CPU Speed:"3.50 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.2506" Ext. Family:"Not Available" Family:"Not Available" FPO:"Not Available" INF:"cpu.inf" INF Section:"IntelPPM_Inst.NT" Install Date:"Not Available" Last Error Code:"Not Available" Level 1 Cache:"14 x 288 KB" Level 2 Cache:"14 x 20480 KB" Level 3 Cache:"24 MB" Load:"13%" Manufacturer:"GenuineIntel" Model:"183" Name:"13th Gen Intel(R) Core(TM) i5-13600KF" Number of Cores:"14" Number of Cores Enabled:"14" Number of Logical Processors:"20" Part Number:"To Be Filled By O.E.M." Power Management Capabilities:"Not Available" Power Management Supported:"No" Processor ID:"BFEBFBFF000B0671" Revision:"Not Available" Serial Number:"To Be Filled By O.E.M." Service Name:"intelppm" Status:"OK" Stepping:"1" Version:"Not Available" - "Storage" - "WD_BLACK SN850X HS 1000GB" Capablities:"Random Access, Supports Writing" Caption:"WD_BLACK SN850X HS 1000GB" Cylinder - Total:"121601" Description:"Disk drive" Driver:"Not Available" Driver Date:"06-21-2006 12:00 AM" Driver Version:"10.0.22621.2506" Error Code:"Device is working properly" Firmware Revision:"620311WD" Heads - Total:"255" Index:"1" INF:"disk.inf" Install Date:"Not Available" Interface Type:"SCSI" Manufacturer:"(Standard disk drives)" Model:"WD_BLACK SN850X HS 1000GB" Name:"\\.\PHYSICALDRIVE1" Partitions:"3" Physical Sector Size:"4096" PNP Device ID:"SCSI\DISK&VEN_NVME&PROD_WD_BLACK_SN850X\5&26BA485A&0&000000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" SCSI Bus:"0" SCSI LUN:"0" SCSI Port:"2" Sectors - Per Track:"63" Sectors - Total:"1953520065" Serial Number:"E823_8FA6_BF53_0001_001B_448B_4E28_FCF7." Size:"931.51 GB" Size – Available:"424.18 GB" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"31008255" - "C:" Availability:"Not Available" Caption:"C:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Not Available" Serial Number:"60A22405" Size:"930.74 GB" Size – Available:"424.18 GB" Status:"Not Available" Volume Dirty:"No" - "WDC WDBNCE0010PNC" Capablities:"Random Access, Supports Writing, SMART Notification" Caption:"WDC WDBNCE0010PNC" Cylinder - Total:"121601" Description:"Disk drive" Driver:"Not Available" Driver Date:"06-21-2006 12:00 AM" Driver Version:"10.0.22621.2506" Error Code:"Device is working properly" Firmware Revision:"415000RL" Heads - Total:"255" Index:"0" INF:"disk.inf" Install Date:"Not Available" Interface Type:"IDE" Manufacturer:"(Standard disk drives)" Model:"WDC WDBNCE0010PNC" Name:"\\.\PHYSICALDRIVE0" Partitions:"1" Physical Sector Size:"512" PNP Device ID:"SCSI\DISK&VEN_WDC&PROD_WDBNCE0010PNC\4&11742CA2&0&050000" Policies:"Read Retention Priority=EqualPriority, Write Retention Priority=EqualPriority, Scalar Prefetch=Not Available, Block Prefetch=Not Available" Sectors - Per Track:"63" Sectors - Total:"1953520065" Serial Number:"20245Z453605" Size:"931.51 GB" Size – Available:"931.34 GB" SMART Attributes:"Self-Test: 10 minutes, OK, Short Self-Test: 2 minutes, OK" Status:"OK" Tracks - Per Cylinder:"255" Tracks - Total:"31008255" - "D:" Availability:"Not Available" Caption:"D:" Compression Method:"Not Compressed" Description:"Local Fixed Disk" File System:"NTFS" Name:"Not Available" Serial Number:"76142788" Size:"931.50 GB" Size – Available:"931.34 GB" Status:"Not Available" Volume Dirty:"No" - "SMART" 0x05 Reallocated Sector Count:0:"0" 0x09 Power-On Hours:3101:"0" 0x0C Power Cycle Count:1967:"0" 0xAA Available Reserved Space:0:"0" 0xAB Program Fail Count:0:"0" 0xAC Erase Fail Count:0:"0" 0xAD Wear Leveling Count:5:"0" 0xAE Power-off Retract Count:47:"0" 0xB8 End-to-End Error Detection Count:0:"0" 0xBB Uncorrectable Error Count:0:"0" 0xBC Reported Command Timeouts:0:"0" 0xC2 Internal Device Temperature:27° C:"0" 0xC7 CRC Error Count:0:"0" 0xE6 Drive Life Protection Status:335010725966:"0" 0xE8 Available Reserved Space:100:"4" 0xE9 Media Wearout Indicator:5492:"0" 0xEA Maximum Erase Count:5846:"0" 0xF1 Total LBAs Written:5671:"0" 0xF2 Total LBAs Read:10030:"0" ...#SSU#... #Logs#System Messages#Included ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MV0B5HZVK9Z-Microsoft.GamingApp. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:11:56 PM on ‎2/‎21/‎2024 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The shadow copies of volume C: were aborted because the shadow copy storage could not grow due to a user imposed limit. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:20:24 PM on ‎2/‎18/‎2024 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did 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: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The AppX Deployment Service (AppXSVC) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Windows Recovery Environment servicing failed. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A timeout was reached (30000 milliseconds) while waiting for the Sync Host_2ca65af service to connect. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.22621.2506_neutral_neutral_cw5n1h2txyewy!App.AppX2dz2dz7bvszf1srfbwq1tqyrpq3nvxf6.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.22621.2506_neutral_neutral_cw5n1h2txyewy!App.AppX2dz2dz7bvszf1srfbwq1tqyrpq3nvxf6.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.22621.2506_neutral_neutral_cw5n1h2txyewy!App.AppX2dz2dz7bvszf1srfbwq1tqyrpq3nvxf6.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:49:44 PM on ‎2/‎9/‎2024 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} 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 NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:04:42 PM on ‎2/‎8/‎2024 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Windows Recovery Environment servicing failed. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server MicrosoftWindows.Client.CBS_1000.22681.1000.0_x64__cw5n1h2txyewy!Global.RulesEngine.AppXg6p1s9373bk1gyjynwzsms4dqcb1sqz1.mca 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.22681.1000.0_x64__cw5n1h2txyewy!Global.DesktopSpotlight.AppXmakp9w4re9tj70pp8mcdrt273xajen0x.mca did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The AppX Deployment Service (AppXSVC) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. ------------------------------------------------------------------- The 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Windows Recovery Environment servicing failed. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {FD06603A-2BDF-4BB1-B7DF-5DC68F353601} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {08949FF9-54D2-47CB-9B3F-82E9ACC93DF1} 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 {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 12:56:29 PM on ‎12/‎28/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- 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 {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {283EDD52-69B2-473D-BEB6-2C0B4C01FD73} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {628ACE20-B77A-456F-A88D-547DB6CEEDD5} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 10:35:46 PM on ‎12/‎27/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 2:39:31 PM on ‎12/‎26/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:46:29 AM on ‎12/‎26/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:38:42 PM on ‎12/‎20/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4QGHW-Microsoft.MicrosoftStickyNotes. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:09:24 PM on ‎12/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 1:52:36 PM on ‎12/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x000000000000000a, 0x0000000000000000, 0xffffe58037521180, 0x0000000000000011). A dump was saved in: C:\WINDOWS\Minidump\121723-7500-01.dmp. Report Id: c7a76818-6e75-44ca-8e7c-7938d9187630. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 1:19:19 PM on ‎12/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 12:54:21 PM on ‎12/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x000000000000000a, 0x0000000000000000, 0xffffd300f00a2180, 0x000000000000000c). A dump was saved in: C:\WINDOWS\Minidump\121723-7171-01.dmp. Report Id: afd4bd95-c941-4dbb-9e19-94a14c5cb652. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 12:35:53 PM on ‎12/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x000000000000000a, 0x0000000000000000, 0xffffd280e0a8f180, 0x000000000000000d). A dump was saved in: C:\WINDOWS\Minidump\121723-7484-01.dmp. Report Id: c2b6c994-021b-41ea-b032-98d62c00b181. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file generation succeded. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 12:18:41 PM on ‎12/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:29:38 AM on ‎12/‎17/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 11:07:48 PM on ‎12/‎16/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event. ------------------------------------------------------------------- The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x000000000000000a, 0x0000000000000000, 0xffff9700f6374180, 0x0000000000000004). A dump was saved in: C:\WINDOWS\Minidump\121623-7703-01.dmp. Report Id: 7bf26942-0c78-4216-aa17-d7e53bb8b28a. ------------------------------------------------------------------- The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- Dump file creation failed due to error during dump creation. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:08:48 PM on ‎12/‎16/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:44:44 PM on ‎12/‎16/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- A fatal hardware error has occurred. A record describing the condition is contained in the data section of this event. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:25:58 PM on ‎12/‎16/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- 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 system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:11:37 PM on ‎12/‎16/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:10:16 PM on ‎12/‎16/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:06:03 PM on ‎12/‎16/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {338B40F9-9D68-4B53-A793-6B9AA0C5F63B} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 5:59:29 PM on ‎12/‎16/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server 33C30B79.HyperXNGenuity_5.24.0.0_x64__0a78dr3hq0pvt!App 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 system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 11:03:41 PM on ‎12/‎15/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ArmouryCrateService service. ------------------------------------------------------------------- A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ArmouryCrateService service. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 10:41:51 PM on ‎12/‎15/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Windows Recovery Environment servicing failed. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:08:41 PM on ‎12/‎11/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MV0B5HZVK9Z-Microsoft.GamingApp. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9P1TBXR6QDCX-33C30B79.HyperXNGenuity. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {7966B4D8-4FDC-4126-A10B-39A3209AD251} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Windows Recovery Environment servicing failed. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MV0B5HZVK9Z-Microsoft.GamingApp. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9P1TBXR6QDCX-33C30B79.HyperXNGenuity. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:50:35 PM on ‎11/‎19/‎2023 was unexpected. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The VMSP service failed to start due to the following error: Insufficient system resources exist to complete the requested service. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:05:25 PM on ‎11/‎16/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Windows Recovery Environment servicing failed. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The ARMOURY CRATE Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4QGHW-Microsoft.MicrosoftStickyNotes. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4QGHW-Microsoft.MicrosoftStickyNotes. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Windows Recovery Environment servicing failed. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- DCOM got error "1115" attempting to start the service UsoSvc with arguments "Unavailable" in order to run the server: {9C695035-48D2-4229-8B73-4C70E756E519} ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Windows Recovery Environment servicing failed. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9P1TBXR6QDCX-33C30B79.HyperXNGenuity. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The Uncheater for BattleGrounds_GL service is marked as an interactive service. However, the system is configured to not allow interactive services. This service may not function properly. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9P1TBXR6QDCX-33C30B79.HyperXNGenuity. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4NNS1-Microsoft.DesktopAppInstaller. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- 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 AORUS LCD Panel 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 XTU3SERVICE 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 LightingService 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 RstMwService 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 AsusFanControlService 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 AsusROGLSLService 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 ROG Live 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 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 ArmouryCrateService 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 DtsApo4Service 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 jhi_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 AsusUpdateCheck 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 WpnService service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The TrkWks 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 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 WinDefend service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The StiSvc service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The iphlpsvc 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 DPS 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 DiagTrack service failed to start due to the following error: The service did not start due to a logon failure. ------------------------------------------------------------------- The iphlpsvc 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 wtd service depends on the BFE service which failed to start because of the following error: A system shutdown is in progress. ------------------------------------------------------------------- The DPS 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 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 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 mpssvc service depends on the BFE service which failed to start because of the following error: A system shutdown is in progress. ------------------------------------------------------------------- The BFE service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The LanmanWorkstation service terminated with the following error: A system shutdown is in progress. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:02:39 PM on ‎9/‎13/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9P1TBXR6QDCX-33C30B79.HyperXNGenuity. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NMPJ99VJBWV-Microsoft.YourPhone. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:07:24 PM on ‎9/‎4/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9P1TBXR6QDCX-33C30B79.HyperXNGenuity. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 10:10:03 PM on ‎9/‎3/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The ARMOURY CRATE Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9PM9DFQRDH3F-B9ECED6F.ArmouryCrate. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server Microsoft.Windows.ContentDeliveryManager_10.0.22621.1_neutral_neutral_cw5n1h2txyewy!App.AppXwdz8g2fxr36xz0tdtagygnvemf85s7gg.mca 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:55:01 PM on ‎8/‎27/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9NBLGGH4QGHW-Microsoft.MicrosoftStickyNotes. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- Installation Failure: Windows failed to install the following update with error 0x80073D02: 9MSSGKG348SP-MicrosoftWindows.Client.WebExperience. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 8:51:43 PM on ‎8/‎16/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {A28430CA-1EBF-48DD-AA17-9221B6F86A6C} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The server B9ECED6F.ArmouryCrate_5.6.8.0_x64__qmba6cd70vzyy!App.AppXk45kp2wyg1kqwk8c16pkwezk5783ddn6.mca 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} 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 driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The previous system shutdown at 9:46:23 PM on ‎8/‎15/‎2023 was unexpected. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- Windows failed fast startup with error status 0xC00000D4. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The virtualization-based security enablement policy check at phase 0 failed with status: Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. ------------------------------------------------------------------- Hypervisor launch failed; Either VMX not present or not enabled in BIOS. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6000 milliseconds: Restart the service. ------------------------------------------------------------------- The NVIDIA LocalSystem Container service terminated with the following error: A generic command executable returned a result that indicates failure. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The server {8CFC164F-4BE5-4FDD-94E9-E2AF73ED4A19} did not register with DCOM within the required timeout. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ------------------------------------------------------------------- The driver detected a controller error on \Device\RaidPort2. ...#SSU#... #Logs#Direct-X Diagnostics#Included ------------------ System Information ------------------ Time of this report: 2/27/2024, 20:17:57 Machine name: DESKTOP-9AB2FT0 Machine Id: {38E0EE13-8494-4AF5-9066-9C51EF19FA42} Operating System: Windows 11 Pro 64-bit (10.0, Build 22631) (22621.ni_release.220506-1250) Language: English (Regional Setting: English) System Manufacturer: ASUS System Model: System Product Name BIOS: 1630 (type: UEFI) Processor: 13th Gen Intel(R) Core(TM) i5-13600KF (20 CPUs), ~3.5GHz Memory: 32768MB RAM Available OS Memory: 32582MB RAM Page File: 9825MB used, 32996MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI (100 percent) System DPI Setting: 96 DPI (100 percent) DWM DPI Scaling: Disabled Miracast: Available, no HDCP Microsoft Graphics Hybrid: Not Supported DirectX Database Version: 1.4.9 DxDiag Version: 10.00.22621.0001 64bit Unicode ------------ DxDiag Notes ------------ Display Tab 1: No problems found. Sound Tab 1: No problems found. Sound Tab 2: No problems found. Sound Tab 3: No problems found. Sound Tab 4: 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: NVIDIA GeForce RTX 3070 Ti Manufacturer: NVIDIA Chip type: NVIDIA GeForce RTX 3070 Ti DAC type: Integrated RAMDAC Device Type: Full Device (POST) Device Key: Enum\PCI\VEN_10DE&DEV_2482&SUBSYS_408F1458&REV_A1 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: 24308 MB Dedicated Memory: 8018 MB Shared Memory: 16290 MB Current Mode: 2560 x 1440 (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.645508,0.330078), Green(0.309570,0.617188), Blue(0.152344,0.073242), White Point(0.313477,0.329102) Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000 Monitor Name: ViewSonic VX3258 Series Monitor Model: VX3258 series Monitor Id: VSCDE35 Native Mode: 2560 x 1440(p) (59.998Hz) Output Type: Displayport External Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll Driver File Version: 31.00.0015.5161 (English) Driver Version: 31.0.15.5161 DDI Version: 12 Feature Levels: 12_2,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:Stable Enabled:True Displayable: Supported Graphics Preemption: Pixel Compute Preemption: Dispatch Miracast: Not Supported by Graphics driver Detachable GPU: No Hybrid Graphics GPU: Discrete Power P-states: Not Supported Virtualization: Paravirtualization Block List: No Blocks Catalog Attributes: Universal:False Declarative:True Driver Attributes: Final Retail Driver Date/Size: 2024-02-14 7:00:00 PM, 785168 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B71E3E-67C2-11CF-C163-80600EC2D235} Vendor ID: 0x10DE Device ID: 0x2482 SubSys ID: 0x408F1458 Revision ID: 0x00A1 Driver Strong Name: oem25.inf:0f066de31a145f91:Section071:31.0.15.5161:pci\ven_10de&dev_2482 Rank Of Driver: 00CF2001 Video Accel: DXVA2 Modes: {86695F12-340E-4F04-9FD3-9253DD327460} DXVA2_ModeMPEG2_VLD {6F3EC719-3735-42CC-8063-65CC3CB36616} DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD {32FCFE3F-DE46-4A49-861B-AC71110649D5} DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeHEVC_VLD_Main DXVA2_ModeHEVC_VLD_Main10 {20BB8B0A-97AA-4571-8E99-64E60606C1A6} {15DF9B21-06C4-47F1-841E-A67C97D7F312} DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC {9947EC6F-689B-11DC-A320-0019DBBC4184} {33FCFE41-DE46-4A49-861B-AC71110649D5} DXVA2_ModeVP9_VLD_Profile0 DXVA2_ModeVP9_VLD_10bit_Profile2 {DDA19DC7-93B5-49F5-A9B3-2BDA28A2CE6E} {B8BE4CCB-CF53-46BA-8D59-D6B8A6DA5D2A} {6AFFD11E-1D96-42B1-A215-93A31F09A53D} {914C84A3-4078-4FA9-984C-E2F262CB5C9C} {8A1A1031-29BC-46D0-A007-E9B092CA6767} Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps= D3D9 Overlay: Not Supported DXVA-HD: Supported DDraw Status: Enabled D3D Status: Enabled AGP Status: Enabled MPO MaxPlanes: 4 MPO Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) MPO Stretch: 10.000X - 0.500X MPO Media Hints: resizing, colorspace Conversion MPO Formats: NV12,P010,YUY2,R16G16B16A16_FLOAT,R10G10B10A2_UNORM,R8G8B8A8_UNORM,B8G8R8A8_UNORM PanelFitter Caps: RGB,YUV,BILINEAR,HIGH_FILTER,STRETCH_YUV,STRETCH_RGB,IMMEDIATE,HDR (MPO3) PanelFitter Stretch: 10.000X - 0.500X ------------- Sound Devices ------------- Description: AI Noise-Canceling Speaker (ASUS Utility) Default Sound Playback: No Default Voice Playback: No Hardware ID: *IGOVAC Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: igovsd.sys Driver Version: 1.0.2.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 2021-09-22 7:00:00 PM, 43392 bytes Other Files: Driver Provider: ASUSTek Computer Inc. HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: Realtek Digital Output (Realtek(R) Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIO\FUNC_01&VEN_10EC&DEV_1168&SUBSYS_1043887C&REV_1001 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: RTKVHD64.sys Driver Version: 6.0.9527.1 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 2023-06-05 7:00:00 PM, 6489960 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 Description: Speakers (HyperX Cloud Stinger Core Wireless + 7.1) Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: USB\VID_0951&PID_170B&REV_4102&MI_00 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: USBAUDIO.sys Driver Version: 3.5.14.0 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 2019-12-09 7:00:00 PM, 282624 bytes Other Files: Driver Provider: Kingston Technology Corporation HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No Description: VX3258 series (NVIDIA High Definition Audio) Default Sound Playback: No Default Voice Playback: No Hardware ID: HDAUDIO\FUNC_01&VEN_10DE&DEV_009E&SUBSYS_1458408F&REV_1001 Manufacturer ID: N/A Product ID: N/A Type: N/A Driver Name: nvhda64v.sys Driver Version: 1.3.40.14 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 2023-01-18 7:00:00 PM, 121880 bytes Other Files: Driver Provider: NVIDIA Corporation HW Accel Level: Emulation Only Cap Flags: 0xF1F Min/Max Sample Rate: 100, 200000 Static/Strm HW Mix Bufs: 1, 0 Static/Strm HW 3D Bufs: 0, 0 HW Memory: 0 Voice Management: No EAX(tm) 2.0 Listen/Src: No, No I3DL2(tm) Listen/Src: No, No Sensaura(tm) ZoomFX(tm): No --------------------- Sound Capture Devices --------------------- Description: AI Noise-Canceling Microphone (ASUS Utility) Default Sound Capture: Yes Default Voice Capture: No Driver Name: igovsd.sys Driver Version: 1.0.2.1 (English) Driver Attributes: Final Retail Date and Size: 2021-09-22 7:00:00 PM, 43392 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF Description: Microphone (HyperX Cloud Stinger Core Wireless + 7.1) Default Sound Capture: No Default Voice Capture: Yes Driver Name: USBAUDIO.sys Driver Version: 3.5.14.0 (English) Driver Attributes: Final Retail Date and Size: 2019-12-09 7:00:00 PM, 282624 bytes Cap Flags: 0x1 Format Flags: 0xFFFFF --------------------- Video Capture Devices Number of Devices: 0 --------------------- ------------------- DirectInput Devices ------------------- Device Name: Mouse Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/a Vendor/Product ID: n/a FF Driver: n/a Device Name: AURA LED Controller Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x0B05, 0x19AF FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC539 FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC539 FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC539 FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC539 FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC539 FF Driver: n/a Device Name: USB Receiver Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC539 FF Driver: n/a Device Name: Hid Interface Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x0951, 0x170B FF Driver: n/a Device Name: Hid Interface Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x0951, 0x170B FF Driver: n/a Device Name: G413 Carbon Mechanical Gaming Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC33A FF Driver: n/a Device Name: G413 Carbon Mechanical Gaming Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC33A FF Driver: n/a Device Name: G413 Carbon Mechanical Gaming Keyboard Attached: 1 Controller ID: 0x0 Vendor/Product ID: 0x046D, 0xC33A FF Driver: n/a Poll w/ Interrupt: No ----------- USB Devices ----------- + USB Root Hub (USB 3.0) | Vendor/Product ID: 0x8086, 0x7A60 | Matching Device ID: USB\ROOT_HUB30 | Service: USBHUB3 | Driver: USBHUB3.SYS, 2/13/2024 20:52:14, 726496 bytes | +-+ Generic USB Hub | | Vendor/Product ID: 0x174C, 0x2074 | | Location: Port_#0006.Hub_#0001 | | Matching Device ID: USB\USB20_HUB | | Service: USBHUB3 | | Driver: USBHUB3.SYS, 2/13/2024 20:52:14, 726496 bytes | | | +-+ G413 | | | Vendor/Product ID: 0x046D, 0xC33A | | | Location: Port_#0003.Hub_#0003 | | | Matching Device ID: USB\VID_046D&PID_C33A | | | Lower Filters: vhf, logi_lamparray | | | Service: usbccgp | | | Driver: logi_lamparray.sys, 2/9/2024 20:44:06, 89072 bytes | | | Driver: logi_lamparray_service.exe, 2/9/2024 20:44:06, 9887216 bytes | | | Driver: usbccgp.sys, 2/13/2024 20:52:14, 230784 bytes | | | | | +-+ USB Input Device | | | | Vendor/Product ID: 0x046D, 0xC33A | | | | Location: 0000.0014.0000.006.003.000.000.000.000 | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | Service: HidUsb | | | | Driver: hidusb.sys, 10/26/2023 18:57:26, 77824 bytes | | | | Driver: hidclass.sys, 10/26/2023 18:57:26, 278528 bytes | | | | Driver: hidparse.sys, 10/26/2023 18:57:26, 90112 bytes | | | | | | | +-+ HID Keyboard Device | | | | | Vendor/Product ID: 0x046D, 0xC33A | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | Service: kbdhid | | | | | Driver: kbdhid.sys, 5/7/2022 00:19:25, 73728 bytes | | | | | Driver: kbdclass.sys, 5/7/2022 00:19:25, 95576 bytes | | | | | | +-+ USB Input Device | | | | Vendor/Product ID: 0x046D, 0xC33A | | | | Location: 0000.0014.0000.006.003.000.000.000.000 | | | | Matching Device ID: USB\Class_03 | | | | Service: HidUsb | | | | Driver: hidusb.sys, 10/26/2023 18:57:26, 77824 bytes | | | | Driver: hidclass.sys, 10/26/2023 18:57:26, 278528 bytes | | | | Driver: hidparse.sys, 10/26/2023 18:57:26, 90112 bytes | | | | | | | +-+ HID Keyboard Device | | | | | Vendor/Product ID: 0x046D, 0xC33A | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | Service: kbdhid | | | | | Driver: kbdhid.sys, 5/7/2022 00:19:25, 73728 bytes | | | | | Driver: kbdclass.sys, 5/7/2022 00:19:25, 95576 bytes | | | | +-+ LIGHTSPEED Receiver | | | Vendor/Product ID: 0x046D, 0xC539 | | | Location: Port_#0004.Hub_#0003 | | | Matching Device ID: USB\VID_046D&PID_C539 | | | Lower Filters: vhf, logi_lamparray | | | Service: usbccgp | | | Driver: logi_lamparray.sys, 2/9/2024 20:44:06, 89072 bytes | | | Driver: logi_lamparray_service.exe, 2/9/2024 20:44:06, 9887216 bytes | | | Driver: usbccgp.sys, 2/13/2024 20:52:14, 230784 bytes | | | | | +-+ USB Input Device | | | | Vendor/Product ID: 0x046D, 0xC539 | | | | Location: 0000.0014.0000.006.004.000.000.000.000 | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | Service: HidUsb | | | | Driver: hidusb.sys, 10/26/2023 18:57:26, 77824 bytes | | | | Driver: hidclass.sys, 10/26/2023 18:57:26, 278528 bytes | | | | Driver: hidparse.sys, 10/26/2023 18:57:26, 90112 bytes | | | | | | | +-+ HID Keyboard Device | | | | | Vendor/Product ID: 0x046D, 0xC539 | | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | | | | | Service: kbdhid | | | | | Driver: kbdhid.sys, 5/7/2022 00:19:25, 73728 bytes | | | | | Driver: kbdclass.sys, 5/7/2022 00:19:25, 95576 bytes | | | | | | +-+ USB Input Device | | | | Vendor/Product ID: 0x046D, 0xC539 | | | | Location: 0000.0014.0000.006.004.000.000.000.000 | | | | Matching Device ID: USB\Class_03&SubClass_01 | | | | Service: HidUsb | | | | Driver: hidusb.sys, 10/26/2023 18:57:26, 77824 bytes | | | | Driver: hidclass.sys, 10/26/2023 18:57:26, 278528 bytes | | | | Driver: hidparse.sys, 10/26/2023 18:57:26, 90112 bytes | | | | | | | +-+ HID-compliant mouse | | | | | Vendor/Product ID: 0x046D, 0xC539 | | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE | | | | | Service: mouhid | | | | | Driver: mouhid.sys, 5/7/2022 00:19:25, 69632 bytes | | | | | Driver: mouclass.sys, 5/7/2022 00:19:25, 95592 bytes ---------------- Gameport Devices ---------------- ------------ PS/2 Devices ------------ + HID Keyboard Device | Vendor/Product ID: 0x046D, 0xC232 | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD | Service: kbdhid | Driver: kbdhid.sys, 5/7/2022 00:19:25, 73728 bytes | Driver: kbdclass.sys, 5/7/2022 00:19:25, 95576 bytes ------------------------ Disk & DVD/CD-ROM Drives ------------------------ Drive: C: Free Space: 434.3 GB Total Space: 953.1 GB File System: NTFS Model: WD_BLACK SN850X HS 1000GB Drive: D: Free Space: 953.7 GB Total Space: 953.9 GB File System: NTFS Model: WDC WDBNCE0010PNC -------------- System Devices -------------- Name: Intel(R) Wi-Fi 6E AX211 160MHz Device ID: PCI\VEN_8086&DEV_7A70&SUBSYS_00948086&REV_11\3&11583659&0&A3 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_3600c12b90247a8b\Netwtw14.sys, 23.10.0000.0008 (English), 2/9/2024 20:44:54, 5377192 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_3600c12b90247a8b\netwfw14.dat, 2/9/2024 20:44:54, 30926788 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\netwtw6e.inf_amd64_3600c12b90247a8b\IntelIHVRouter14.dll, 23.12010.0000.0003 (English), 2/9/2024 20:44:53, 1472168 bytes Name: Standard SATA AHCI Controller Device ID: PCI\VEN_8086&DEV_7A62&SUBSYS_88821043&REV_11\3&11583659&0&B8 Driver: C:\WINDOWS\system32\DRIVERS\storahci.sys, 10.00.22621.2506 (English), 10/26/2023 18:57:12, 214400 bytes Name: Intel(R) SMBus - 7A23 Device ID: PCI\VEN_8086&DEV_7A23&SUBSYS_88821043&REV_11\3&11583659&0&FC Driver: n/a Name: Intel(R) PCI Express Root Port #25 - 7A48 Device ID: PCI\VEN_8086&DEV_7A48&SUBSYS_88821043&REV_11\3&11583659&0&D0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.2861 (English), 12/14/2023 20:12:24, 579056 bytes Name: High Definition Audio Controller Device ID: PCI\VEN_8086&DEV_7A50&SUBSYS_887C1043&REV_11\3&11583659&0&FB Driver: C:\WINDOWS\system32\DRIVERS\hdaudbus.sys, 10.00.22621.2792 (English), 12/4/2023 20:14:01, 192512 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.22621.2506 (English), 10/26/2023 18:57:10, 143360 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.22621.2506 (English), 10/26/2023 18:57:10, 471040 bytes Name: NVIDIA GeForce RTX 3070 Ti Device ID: PCI\VEN_10DE&DEV_2482&SUBSYS_408F1458&REV_A1\4&256A0AA8&0&0008 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NVWMI\nvPerfProvider.man, 2/15/2024 11:42:00, 14175 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NVWMI\nvWmi.mof, 2/15/2024 11:42:00, 148921 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NVWMI\nvWmi64.exe, 2.36.0000.0000 (English), 2/17/2024 06:39:34, 4518432 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\NVDisplay.Container.exe, 1.39.3323.1171 (English), 2/17/2024 06:38:50, 1274992 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\NvContainerRecovery.bat, 2/15/2024 11:42:00, 1951 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\NvMessageBus.dll, 3.12.3354.5005 (English), 2/17/2024 06:38:50, 3493512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\dlsargs.xml, 2/15/2024 11:42:00, 544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\dlsnetparams.csv, 2/15/2024 11:42:00, 201870 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\messagebus_client.conf, 2/15/2024 11:42:00, 313 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\nvgwls.exe, 2/17/2024 06:38:50, 3940976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\nvtopps.db3, 2/15/2024 11:42:00, 126976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\LocalSystem\NvXDCore.dll, 31.00.0015.5161 (English), 2/17/2024 06:38:52, 1893488 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\LocalSystem\NvcDispCorePlugin.dll, 31.00.0015.5161 (English), 2/17/2024 06:38:52, 521248 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\LocalSystem\NvcDispWatchdog.dll, 1.39.3323.1171 (English), 2/17/2024 06:38:52, 760352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\LocalSystem\_DisplayDriverRAS.dll, 1.10.0000.0000 (English), 2/17/2024 06:38:58, 2711672 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\LocalSystem\_NvMsgBusBroadcast.dll, 3.12.3354.5005 (English), 2/17/2024 06:38:58, 3491360 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\LocalSystem\_nvtopps.dll, 31.00.0015.5161 (English), 2/17/2024 06:39:00, 11492896 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\LocalSystem\messagebus.conf, 2/15/2024 11:42:00, 313 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\LocalSystem\wksServicePluginZ.dll, 31.00.0015.5161 (English), 2/17/2024 06:38:58, 279664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\Session\_NvGSTPlugin.dll, 31.00.0015.5161 (English), 2/17/2024 06:39:02, 2653200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\Session\nvprofileupdaterplugin.dll, 31.00.0015.5161 (English), 2/17/2024 06:39:00, 2228848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\Session\nvxdsyncplugin.dll, 8.17.0015.5161 (English), 2/17/2024 06:39:02, 1839120 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\Display.NvContainer\plugins\Session\wksServicePlugin.dll, 31.00.0015.5161 (English), 2/17/2024 06:39:02, 314400 bytes Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\Drs\dbInstaller.exe, 31.00.0015.5161 (English), 2/17/2024 06:32:14, 735240 bytes Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\Drs\nvdrsdb.bin, 2/15/2024 11:42:00, 1936004 bytes Driver: C:\WINDOWS\system32\nvcpl.dll, 8.17.0015.5161 (English), 2/17/2024 06:32:54, 5912712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nv3dappshext.dll, 6.14.0015.5161 (English), 2/17/2024 06:32:30, 1004560 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nv3dappshextr.dll, 6.14.0015.5161 (English), 2/17/2024 06:32:36, 97800 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvcoproc.bin, 2/15/2024 11:42:00, 10551347 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvcpl.dll, 8.17.0015.5161 (English), 2/17/2024 06:32:54, 5912712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdevtools.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:38, 4592160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdevtoolsr.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:40, 245792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdisps.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:42, 11656736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdispsr.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:42, 11575304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvgames.dll, 31.00.0015.5161 (English), 2/17/2024 06:34:14, 12491808 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvgamesr.dll, 31.00.0015.5161 (English), 2/17/2024 06:34:16, 13321224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvlicensings.dll, 6.14.0015.5161 (English), 2/17/2024 06:35:00, 4578952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvlicensingsr.dll, 6.14.0015.5161 (English), 2/17/2024 06:35:02, 363016 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvshext.dll, 1.02.0000.0001 (English), 2/17/2024 06:36:48, 133232 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvsmartmax.dll, 6.14.0010.10003 (English), 2/17/2024 06:36:48, 199280 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvsmartmax64.dll, 6.14.0010.10003 (English), 2/17/2024 06:36:48, 236680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvsmartmaxapp.exe, 6.14.0010.10003 (English), 2/17/2024 06:36:50, 274032 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvsmartmaxapp64.exe, 6.14.0010.10003 (English), 2/17/2024 06:36:50, 285216 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvsvc64.dll, 31.00.0015.5161 (English), 2/17/2024 06:36:52, 2673184 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvsvcr.dll, 31.00.0015.5161 (English), 2/17/2024 06:36:58, 1801760 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvsvs.dll, 31.00.0015.5161 (English), 2/17/2024 06:37:02, 5101064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvsvsr.dll, 31.00.0015.5161 (English), 2/17/2024 06:37:02, 2013704 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvui.dll, 8.17.0015.5161 (English), 2/17/2024 06:37:08, 6653984 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvuir.dll, 8.17.0015.5161 (English), 2/17/2024 06:37:14, 2649096 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvvitvs.dll, 31.00.0015.5161 (English), 2/17/2024 06:37:26, 7461512 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvvitvsr.dll, 31.00.0015.5161 (English), 2/17/2024 06:37:26, 4263544 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvwss.dll, 31.00.0015.5161 (English), 2/17/2024 06:38:04, 12268552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvwssr.dll, 31.00.0015.5161 (English), 2/17/2024 06:38:06, 9529352 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvxdapix.dll, 8.17.0015.5161 (English), 2/17/2024 06:38:08, 9412640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvxdbat.dll, 8.17.0015.5161 (English), 2/17/2024 06:38:12, 1653768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvxdplcy.dll, 8.17.0015.5161 (English), 2/17/2024 06:38:18, 1895456 bytes Driver: C:\WINDOWS\system32\lxss\lib\libcuda.so, 2/15/2024 11:42:00, 162552 bytes Driver: C:\WINDOWS\system32\lxss\lib\libcuda.so.1, 2/15/2024 11:42:00, 162552 bytes Driver: C:\WINDOWS\system32\lxss\lib\libcuda.so.1.1, 2/15/2024 11:42:00, 162552 bytes Driver: C:\WINDOWS\system32\lxss\lib\libcudadebugger.so.1, 1/18/2024 06:32:32, 10524136 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvcuvid.so, 2/15/2024 11:42:00, 11742584 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvcuvid.so.1, 2/15/2024 11:42:00, 11742584 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvdxdlkernels.so, 1/18/2024 06:32:32, 115888416 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-encode.so, 2/15/2024 11:42:00, 572008 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-encode.so.1, 2/15/2024 11:42:00, 572008 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-ml.so.1, 2/15/2024 11:42:00, 244344 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-opticalflow.so, 2/15/2024 11:42:00, 362960 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvidia-opticalflow.so.1, 2/15/2024 11:42:00, 362960 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvoptix.so.1, 2/15/2024 11:42:00, 72656 bytes Driver: C:\WINDOWS\system32\lxss\lib\libnvwgf2umx.so, 2/15/2024 11:42:00, 67608808 bytes Driver: C:\WINDOWS\system32\lxss\lib\nvidia-smi, 2/15/2024 11:42:00, 715296 bytes Driver: C:\WINDOWS\system32\DRIVERS\NVIDIA Corporation\license.txt, 10/4/2023 18:56:52, 35335 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\_nvngx.dll, 31.00.0015.5161 (English), 2/17/2024 06:38:36, 1553008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\cudnn_infer64_7.dll, 2/17/2024 06:32:02, 22774312 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvngx.dll, 30.00.0014.9516 (English), 2/17/2024 06:35:04, 488776 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvngx_update.exe, 31.00.0015.5161 (English), 2/17/2024 06:35:06, 1139824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\FreqTransfer32.exe, 2/17/2024 06:39:08, 3764768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\FreqTransfer64.exe, 2/17/2024 06:39:12, 4057632 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\GreenScreenBG01.jpg, 2/15/2024 11:42:00, 281528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\GreenScreenBG02.jpg, 2/15/2024 11:42:00, 499736 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\HighresBlender32.exe, 2/17/2024 06:39:16, 3860488 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\HighresBlender64.exe, 2/17/2024 06:39:16, 4163080 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\NvCamera32.dll, 7.01.0000.0000 (English), 2/17/2024 06:39:18, 8183968 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\NvCamera64.dll, 7.01.0000.0000 (English), 2/17/2024 06:39:18, 8684584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\NvCameraAllowlisting32.dll, 7.01.0000.0000 (English), 2/17/2024 06:39:24, 520256 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\NvCameraAllowlisting64.dll, 7.01.0000.0000 (English), 2/17/2024 06:39:26, 666504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\NvCameraEnable.exe, 2/17/2024 06:39:26, 374792 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\NvImageConvert32.exe, 2/17/2024 06:39:26, 3763720 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\NvImageConvert64.exe, 2/17/2024 06:39:28, 4037640 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\ReShadeFXC32.exe, 2.00.0000.0000 (English), 2/17/2024 06:39:28, 776712 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\ReShadeFXC64.exe, 2.00.0000.0000 (English), 2/17/2024 06:39:30, 891400 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\ShotWithGeforce518x32.rgba, 2/15/2024 11:42:00, 66304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\SphericalEquirect32.exe, 2/17/2024 06:39:30, 3716616 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\SphericalEquirect64.exe, 2/17/2024 06:39:34, 3941400 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\Sticker01.png, 2/15/2024 11:42:00, 49695 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\Sticker02.png, 2/15/2024 11:42:00, 474002 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\Sticker03.png, 2/15/2024 11:42:00, 380006 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\Sticker04.png, 2/15/2024 11:42:00, 86881 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\Sticker05.png, 2/15/2024 11:42:00, 59304 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\Sticker06.png, 2/15/2024 11:42:00, 13547 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\Sticker07.png, 2/15/2024 11:42:00, 6342 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\Sticker08.png, 2/15/2024 11:42:00, 96493 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\d3dcompiler_47_32.dll, 6.03.9600.16384 (English), 2/17/2024 06:39:04, 3470864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\d3dcompiler_47_64.dll, 6.03.9600.16384 (English), 2/17/2024 06:39:06, 4177928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\scratches.jpg, 2/15/2024 11:42:00, 346354 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\tools_licenses.txt, 2/15/2024 11:42:00, 15970 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvCamera\ui.tga, 2/15/2024 11:42:00, 120236 bytes Driver: C:\WINDOWS\system32\MCU.exe, 1.01.5204.20580 (English), 2/17/2024 06:32:28, 853000 bytes Driver: C:\WINDOWS\system32\nvdebugdump.exe, 6.14.0015.5161 (English), 2/17/2024 06:33:34, 459272 bytes Driver: C:\WINDOWS\system32\nvidia-smi.exe, 8.17.0015.5161 (English), 2/17/2024 06:34:24, 842272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvopencl32.dll, 31.00.0015.5161 (English), 2/17/2024 06:35:32, 18415624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvopencl64.dll, 31.00.0015.5161 (English), 2/17/2024 06:35:38, 11132552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvlddmkm.sys, 31.00.0015.5161 (English), 2/17/2024 06:34:46, 59965448 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvvm32.dll, 31.00.0015.5161 (English), 2/17/2024 06:37:30, 60441224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvvm64.dll, 31.00.0015.5161 (English), 2/17/2024 06:37:46, 68302368 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\gsp_ga10x.bin, 2/15/2024 11:42:00, 37090848 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\gsp_tu10x.bin, 2/15/2024 11:42:00, 24479384 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libcuda.so.1.1, 2/15/2024 11:42:00, 8980168 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libcuda_loader.so, 2/15/2024 11:42:00, 162552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libcudadebugger.so.1, 2/15/2024 11:42:00, 10524136 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvcuvid.so.1, 2/15/2024 11:42:00, 11742584 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvdxdlkernels.so, 2/15/2024 11:42:00, 115888416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvidia-encode.so.1, 2/15/2024 11:42:00, 572008 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvidia-ml.so.1, 2/15/2024 11:42:00, 1722024 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvidia-ml_loader.so, 2/15/2024 11:42:00, 244344 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvidia-nvvm.so.4, 2/15/2024 11:42:00, 27968664 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvidia-opticalflow.so.1, 2/15/2024 11:42:00, 362960 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvidia-ptxjitcompiler.so.1, 2/15/2024 11:42:00, 28543272 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvoptix_loader.so.1, 2/15/2024 11:42:00, 72656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\libnvwgf2umx.so, 2/15/2024 11:42:00, 67608808 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nv-vk64.json, 2/15/2024 11:42:00, 671 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvAIDVC.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:38, 4581408 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvAIDVCx.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:42, 4699656 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvAIHDR.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:46, 2854024 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvAIHDRx.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:48, 2981000 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvDecMFTMjpeg.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:36, 507424 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvDecMFTMjpegx.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:36, 657416 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvEncMFTH264.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:56, 914952 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvEncMFTH264x.dll, 31.00.0015.5161 (English), 2/17/2024 06:34:00, 1165832 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvEncMFThevc.dll, 31.00.0015.5161 (English), 2/17/2024 06:34:02, 919560 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvEncMFThevcx.dll, 31.00.0015.5161 (English), 2/17/2024 06:34:04, 1174552 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvcubins.bin, 2/15/2024 11:42:00, 24584224 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvcuda32.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:56, 22601328 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvcuda64.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:04, 10424440 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvd3dumx.dll, 31.00.0015.5161 (English), 2/17/2024 06:31:48, 37693768 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdlistx.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:04, 236624 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdlppx.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:10, 13420040 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdxdlkernels.dll, 2/17/2024 06:33:50, 121091104 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvgpucomp32.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:16, 29078680 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvgpucomp64.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:24, 36259160 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvidia-smi, 2/15/2024 11:42:00, 715296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumdx.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:36, 785168 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvml.dll, 8.17.0015.5161 (English), 2/17/2024 06:35:02, 1616504 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvoglv64.dll, 31.00.0015.5161 (English), 2/17/2024 06:35:20, 46177824 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvoptix.bin, 2/15/2024 11:42:00, 99616380 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvoptix.dll, 8.00.0000.0000 (English), 2/17/2024 06:35:44, 56386696 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvppe.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:38, 775200 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvppex.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:40, 1260064 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvptxJitCompiler32.dll, 31.00.0015.5161 (English), 2/17/2024 06:36:06, 17375864 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvptxJitCompiler64.dll, 31.00.0015.5161 (English), 2/17/2024 06:36:14, 20014192 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvrtum64.dll, 31.00.0015.5161 (English), 2/17/2024 06:36:22, 70175880 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvwgf2umx.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:00, 68358288 bytes Driver: C:\WINDOWS\system32\NvFBC64.dll, 6.14.0015.5161 (English), 2/17/2024 06:34:14, 2173448 bytes Driver: C:\WINDOWS\system32\NvIFR64.dll, 6.14.0015.5161 (English), 2/17/2024 06:34:42, 1541640 bytes Driver: C:\WINDOWS\system32\OpenCL.dll, 3.00.0003.0000 (English), 2/17/2024 06:38:26, 1487904 bytes Driver: C:\WINDOWS\system32\nvEncodeAPI64.dll, 31.00.0015.5161 (English), 2/17/2024 06:34:06, 1024032 bytes Driver: C:\WINDOWS\system32\nvapi64.dll, 31.00.0015.5161 (English), 2/17/2024 06:31:30, 6943344 bytes Driver: C:\WINDOWS\system32\nvcuda.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:16, 3721760 bytes Driver: C:\WINDOWS\system32\nvcudadebugger.dll, 0.00.0000.0000 (English), 2/17/2024 06:33:06, 5773448 bytes Driver: C:\WINDOWS\system32\nvcuvid.dll, 7.17.0015.5161 (English), 2/17/2024 06:33:26, 12928032 bytes Driver: C:\WINDOWS\system32\nvinfo.pb, 2/15/2024 11:42:00, 119184 bytes Driver: C:\WINDOWS\system32\nvml.dll, 8.17.0015.5161 (English), 2/17/2024 06:35:04, 1046152 bytes Driver: C:\WINDOWS\system32\nvofapi64.dll, 31.00.0015.5161 (English), 2/17/2024 06:35:08, 669816 bytes Driver: C:\WINDOWS\system32\vulkan-1-999-0-0-0.dll, 1.03.0275.0000 (English), 2/17/2024 06:38:32, 1445224 bytes Driver: C:\WINDOWS\system32\vulkan-1.dll, 1.03.0275.0000 (English), 2/17/2024 06:38:32, 1445224 bytes Driver: C:\WINDOWS\system32\vulkaninfo-1-999-0-0-0.exe, 1.03.0275.0000 (English), 2/17/2024 06:38:34, 2031464 bytes Driver: C:\WINDOWS\system32\vulkaninfo.exe, 1.03.0275.0000 (English), 2/17/2024 06:38:34, 2031464 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nv-vk32.json, 2/15/2024 11:42:00, 671 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvIccAdvancedColorIdentity.icm, 2/15/2024 11:42:00, 3288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvd3dum.dll, 31.00.0015.5161 (English), 2/17/2024 06:31:36, 36620288 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdispco64.exe, 1.00.0016.0000 (English), 2/17/2024 06:33:40, 1739296 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvdlist.dll, 31.00.0015.5161 (English), 2/17/2024 06:31:58, 200176 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvldumd.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:34, 623928 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvoglv32.dll, 31.00.0015.5161 (English), 2/17/2024 06:35:08, 32932976 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\nvwgf2um.dll, 31.00.0015.5161 (English), 2/17/2024 06:32:44, 51877624 bytes Driver: C:\WINDOWS\SysWow64\NvFBC.dll, 6.14.0015.5161 (English), 2/17/2024 06:34:12, 1625096 bytes Driver: C:\WINDOWS\SysWow64\NvIFR.dll, 6.14.0015.5161 (English), 2/17/2024 06:34:40, 1199112 bytes Driver: C:\WINDOWS\SysWow64\OpenCL.dll, 3.00.0003.0000 (English), 2/17/2024 06:38:20, 1227296 bytes Driver: C:\WINDOWS\SysWow64\nvEncodeAPI.dll, 31.00.0015.5161 (English), 2/17/2024 06:34:06, 786952 bytes Driver: C:\WINDOWS\SysWow64\nvapi.dll, 31.00.0015.5161 (English), 2/17/2024 06:31:24, 6030584 bytes Driver: C:\WINDOWS\SysWow64\nvcuda.dll, 31.00.0015.5161 (English), 2/17/2024 06:33:12, 6780528 bytes Driver: C:\WINDOWS\SysWow64\nvcuvid.dll, 7.17.0015.5161 (English), 2/17/2024 06:33:18, 16033824 bytes Driver: C:\WINDOWS\SysWow64\nvofapi.dll, 31.00.0015.5161 (English), 2/17/2024 06:35:06, 505456 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1-999-0-0-0.dll, 1.03.0275.0000 (English), 2/17/2024 06:38:32, 1295208 bytes Driver: C:\WINDOWS\SysWow64\vulkan-1.dll, 1.03.0275.0000 (English), 2/17/2024 06:38:32, 1295208 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo-1-999-0-0-0.exe, 1.03.0275.0000 (English), 2/17/2024 06:38:34, 1578752 bytes Driver: C:\WINDOWS\SysWow64\vulkaninfo.exe, 1.03.0275.0000 (English), 2/17/2024 06:38:34, 1578752 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_830091b3ebd4b98a\NvTelemetry64.dll, 14.03.0060.0000 (English), 2/17/2024 06:37:08, 4466120 bytes Name: Intel(R) PCI Express Root Port #17 - 7A40 Device ID: PCI\VEN_8086&DEV_7A40&SUBSYS_88821043&REV_11\3&11583659&0&D8 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.2861 (English), 12/14/2023 20:12:24, 579056 bytes Name: Intel(R) Serial IO I2C Host Controller - 7A4C Device ID: PCI\VEN_8086&DEV_7A4C&SUBSYS_88821043&REV_11\3&11583659&0&A8 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_e736c048ca307ed2\iaLPSS2_I2C_ADL.sys, 30.100.2237.0026 (English), 10/18/2022 04:20:10, 220224 bytes Name: Intel(R) PCIe RC 010 G5 - A70D Device ID: PCI\VEN_8086&DEV_A70D&SUBSYS_88821043&REV_01\3&11583659&0&08 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.2861 (English), 12/14/2023 20:12:24, 579056 bytes Name: Intel(R) LPC Controller/eSPI Controller - 7A04 Device ID: PCI\VEN_8086&DEV_7A04&SUBSYS_88821043&REV_11\3&11583659&0&F8 Driver: C:\WINDOWS\system32\DRIVERS\msisadrv.sys, 10.00.22621.0001 (English), 5/7/2022 00:19:04, 54608 bytes Name: Intel(R) Management Engine Interface #1 Device ID: PCI\VEN_8086&DEV_7A68&SUBSYS_88821043&REV_11\3&11583659&0&B0 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_f44b025d83c4bf24\x64\TeeDriverW10x64.sys, 2336.05.0002.0000 (English), 9/14/2023 02:37:32, 321128 bytes Name: PCI standard host CPU bridge Device ID: PCI\VEN_8086&DEV_A704&SUBSYS_88821043&REV_01\3&11583659&0&00 Driver: n/a Name: Intel(R) USB 3.20 eXtensible Host Controller - 1.20 (Microsoft) Device ID: PCI\VEN_8086&DEV_7A60&SUBSYS_88821043&REV_11\3&11583659&0&A0 Driver: C:\WINDOWS\system32\DRIVERS\USBXHCI.SYS, 10.00.22621.2506 (English), 10/26/2023 18:57:26, 677232 bytes Driver: C:\WINDOWS\system32\DRIVERS\UMDF\UsbXhciCompanion.dll, 10.00.22621.2506 (English), 10/26/2023 18:57:26, 170856 bytes Name: Intel(R) Platform Monitoring Technology Driver Device ID: PCI\VEN_8086&DEV_A77D&SUBSYS_88821043&REV_01\3&11583659&0&50 Driver: C:\WINDOWS\system32\DRIVERS\IntelPMT.sys, 10.00.22621.2506 (English), 10/26/2023 18:57:11, 91784 bytes Name: Intel RST VMD Controller A77F Device ID: PCI\VEN_8086&DEV_A77F&SUBSYS_88821043&REV_00\3&11583659&0&70 Driver: C:\WINDOWS\system32\DRIVERS\iaStorVD.sys, 19.05.0007.1058 (English), 7/24/2023 07:31:48, 1606816 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\iastorvd.inf_amd64_d0ba3dc7378fedf6\RstMwService.exe, 19.05.0007.1058 (English), 7/24/2023 07:31:50, 2056864 bytes Driver: C:\WINDOWS\system32\RstMwEventLogMsg.dll, 19.05.0007.1058 (English), 7/24/2023 07:31:50, 30880 bytes Name: Standard NVM Express Controller Device ID: PCI\VEN_15B7&DEV_5030&SUBSYS_503015B7&REV_01\4&6586F28&0&00DC Driver: C:\WINDOWS\system32\DRIVERS\stornvme.sys, 10.00.22621.3085 (English), 1/24/2024 20:11:23, 251376 bytes Name: High Definition Audio Controller Device ID: PCI\VEN_10DE&DEV_228B&SUBSYS_408F1458&REV_A1\4&256A0AA8&0&0108 Driver: C:\WINDOWS\system32\DRIVERS\hdaudbus.sys, 10.00.22621.2792 (English), 12/4/2023 20:14:01, 192512 bytes Driver: C:\WINDOWS\system32\DRIVERS\drmk.sys, 10.00.22621.2506 (English), 10/26/2023 18:57:10, 143360 bytes Driver: C:\WINDOWS\system32\DRIVERS\portcls.sys, 10.00.22621.2506 (English), 10/26/2023 18:57:10, 471040 bytes Name: Intel(R) SPI (flash) Controller - 7A24 Device ID: PCI\VEN_8086&DEV_7A24&SUBSYS_88821043&REV_11\3&11583659&0&FD Driver: n/a Name: Intel(R) PCI Express Root Port #1 - 7A38 Device ID: PCI\VEN_8086&DEV_7A38&SUBSYS_88821043&REV_11\3&11583659&0&E0 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.2861 (English), 12/14/2023 20:12:24, 579056 bytes Name: Intel(R) Serial IO I2C Host Controller - 7A4D Device ID: PCI\VEN_8086&DEV_7A4D&SUBSYS_88821043&REV_11\3&11583659&0&A9 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_e736c048ca307ed2\iaLPSS2_I2C_ADL.sys, 30.100.2237.0026 (English), 10/18/2022 04:20:10, 220224 bytes Name: Intel(R) PCI Express Root Port #9 - 7A30 Device ID: PCI\VEN_8086&DEV_7A30&SUBSYS_88821043&REV_11\3&11583659&0&E8 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.2861 (English), 12/14/2023 20:12:24, 579056 bytes Name: Intel(R) Shared SRAM - 7A27 Device ID: PCI\VEN_8086&DEV_7A27&SUBSYS_88821043&REV_11\3&11583659&0&A2 Driver: n/a Name: Intel(R) PCI Express Root Port #21 - 7A44 Device ID: PCI\VEN_8086&DEV_7A44&SUBSYS_88821043&REV_11\3&11583659&0&DC Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.2861 (English), 12/14/2023 20:12:24, 579056 bytes Name: Intel(R) PCI Express Root Port #3 - 7A3A Device ID: PCI\VEN_8086&DEV_7A3A&SUBSYS_88821043&REV_11\3&11583659&0&E2 Driver: C:\WINDOWS\system32\DRIVERS\pci.sys, 10.00.22621.2861 (English), 12/14/2023 20:12:24, 579056 bytes Name: Intel(R) Serial IO I2C Host Controller - 7A4E Device ID: PCI\VEN_8086&DEV_7A4E&SUBSYS_88821043&REV_11\3&11583659&0&AA Driver: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_e736c048ca307ed2\iaLPSS2_I2C_ADL.sys, 30.100.2237.0026 (English), 10/18/2022 04:20:10, 220224 bytes Name: Intel(R) Ethernet Controller I226-V Device ID: PCI\VEN_8086&DEV_125C&SUBSYS_88671043&REV_06\08BFB8FFFF3DF25400 Driver: C:\WINDOWS\System32\DriverStore\FileRepository\e2fn.inf_amd64_fcb868ac03f43b71\e2fn.sys, 2.01.0003.0015 (English), 7/3/2023 01:42:24, 1427528 bytes Driver: C:\WINDOWS\System32\DriverStore\FileRepository\e2fn.inf_amd64_fcb868ac03f43b71\e2fnmsg.dll, 0.00.0000.0006 (English), 7/3/2023 01:42:30, 84552 bytes ------------------ DirectShow Filters ------------------ DirectShow Filters: WMAudio Decoder DMO,0x00800800,1,1,WMADMOD.DLL,10.00.22621.2506 WMAPro over S/PDIF DMO,0x00600800,1,1,WMADMOD.DLL,10.00.22621.2506 WMSpeech Decoder DMO,0x00600800,1,1,WMSPDMOD.DLL,10.00.22621.2506 MP3 Decoder DMO,0x00600800,1,1,mp3dmod.dll,10.00.22621.2506 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.2506 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.2506 WM ASF Reader,0x00400000,0,0,qasf.dll,12.00.22621.0001 AVI Splitter,0x00600000,1,1,quartz.dll,10.00.22621.2506 VGA 16 Color Ditherer,0x00400000,1,1,quartz.dll,10.00.22621.2506 SBE2MediaTypeProfile,0x00200000,0,0,sbe.dll,10.00.22621.2861 Microsoft DTV-DVD Video Decoder,0x005fffff,2,4,msmpeg2vdec.dll,10.00.22621.3155 AC3 Parser Filter,0x00600000,1,1,mpg2splt.ax,10.00.22621.0001 StreamBufferSink,0x00200000,0,0,sbe.dll,10.00.22621.2861 MJPEG Decompressor,0x00600000,1,1,quartz.dll,10.00.22621.2506 MPEG-I Stream Splitter,0x00600000,1,2,quartz.dll,10.00.22621.2506 SAMI (CC) Parser,0x00400000,1,1,quartz.dll,10.00.22621.2506 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.2861 Microsoft MPEG-2 Video Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22621.2506 Internal Script Command Renderer,0x00800001,1,0,quartz.dll,10.00.22621.2506 MPEG Audio Decoder,0x03680001,1,1,quartz.dll,10.00.22621.2506 DV Splitter,0x00600000,1,2,qdv.dll,10.00.22621.0001 Video Mixing Renderer 9,0x00200000,1,0,quartz.dll,10.00.22621.2506 Microsoft MPEG-2 Encoder,0x00200000,2,1,msmpeg2enc.dll,10.00.22621.2506 ACM Wrapper,0x00600000,1,1,quartz.dll,10.00.22621.2506 Video Renderer,0x00800001,1,0,quartz.dll,10.00.22621.2506 MPEG-2 Video Stream Analyzer,0x00200000,0,0,sbe.dll,10.00.22621.2861 Line 21 Decoder,0x00600000,1,1,, Video Port Manager,0x00600000,2,1,quartz.dll,10.00.22621.2506 Video Renderer,0x00400000,1,0,quartz.dll,10.00.22621.2506 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.2506 Overlay Mixer2,0x00200000,1,1,, AVI Draw,0x00600064,9,1,quartz.dll,10.00.22621.2506 Microsoft MPEG-2 Audio Encoder,0x00200000,1,1,msmpeg2enc.dll,10.00.22621.2506 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.2506 StreamBufferSource,0x00200000,0,0,sbe.dll,10.00.22621.2861 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.2506 AVI/WAV File Source,0x00400000,0,2,quartz.dll,10.00.22621.2506 Wave Parser,0x00400000,1,1,quartz.dll,10.00.22621.2506 MIDI Parser,0x00400000,1,1,quartz.dll,10.00.22621.2506 Multi-file Parser,0x00400000,1,1,quartz.dll,10.00.22621.2506 File stream renderer,0x00400000,1,1,quartz.dll,10.00.22621.2506 Microsoft DTV-DVD Audio Decoder,0x005fffff,1,1,msmpeg2adec.dll,10.00.22621.2506 StreamBufferSink2,0x00200000,0,0,sbe.dll,10.00.22621.2861 AVI Mux,0x00200000,1,0,qcap.dll,10.00.22621.0001 Line 21 Decoder 2,0x00600002,1,1,quartz.dll,10.00.22621.2506 File Source (Async.),0x00400000,0,1,quartz.dll,10.00.22621.2506 File Source (URL),0x00400000,0,1,quartz.dll,10.00.22621.2506 Infinite Pin Tee Filter,0x00200000,1,1,qcap.dll,10.00.22621.0001 Enhanced Video Renderer,0x00200000,1,0,evr.dll,10.00.22621.2506 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.2506 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.2506 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.2506 PCM,0x00200000,1,1,quartz.dll,10.00.22621.2506 Microsoft ADPCM,0x00200000,1,1,quartz.dll,10.00.22621.2506 GSM 6.10,0x00200000,1,1,quartz.dll,10.00.22621.2506 CCITT A-Law,0x00200000,1,1,quartz.dll,10.00.22621.2506 CCITT u-Law,0x00200000,1,1,quartz.dll,10.00.22621.2506 MPEG Layer-3,0x00200000,1,1,quartz.dll,10.00.22621.2506 Audio Capture Sources: AI Noise-Canceling Microphone (ASUS Utility),0x00200000,0,0,qcap.dll,10.00.22621.0001 Microphone (HyperX Cloud Stinger Core Wireless + 7.1),0x00200000,0,0,qcap.dll,10.00.22621.0001 PBDA CP Filters: PBDA DTFilter,0x00600000,1,1,CPFilters.dll,10.00.22621.2715 PBDA ETFilter,0x00200000,0,0,CPFilters.dll,10.00.22621.2715 PBDA PTFilter,0x00200000,0,0,CPFilters.dll,10.00.22621.2715 Midi Renderers: Default MidiOut Device,0x00800000,1,0,quartz.dll,10.00.22621.2506 Microsoft GS Wavetable Synth,0x00200000,1,0,quartz.dll,10.00.22621.2506 WDM Streaming Capture Devices: Intelligo VAC (W),0x00200000,4,4,ksproxy.ax,10.00.22621.0001 Realtek HD Audio Line input,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 Realtek HD Audio Stereo input,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 Realtek HD Audio Mic input,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 HyperX Cloud Stinger Core Wireless + 7.1,0x00200000,2,2,ksproxy.ax,10.00.22621.0001 ,0x00000000,0,0,, WDM Streaming Rendering Devices: Intelligo VAC (W),0x00200000,4,4,ksproxy.ax,10.00.22621.0001 Realtek HD Audio output,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 Realtek HDA SPDIF Out,0x00200000,1,1,ksproxy.ax,10.00.22621.0001 Kingston USB Audio,0x00200000,2,2,ksproxy.ax,10.00.22621.0001 ,0x00000000,0,0,, 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 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 (HyperX Cloud Stinger Core Wireless + 7.1),0x00200000,1,0,quartz.dll,10.00.22621.2506 Default DirectSound Device,0x00800000,1,0,quartz.dll,10.00.22621.2506 Default WaveOut Device,0x00200000,1,0,quartz.dll,10.00.22621.2506 DirectSound: AI Noise-Canceling Speaker (ASUS Utility),0x00200000,1,0,quartz.dll,10.00.22621.2506 DirectSound: Realtek Digital Output (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.22621.2506 DirectSound: VX3258 series (NVIDIA High Definition Audio),0x00200000,1,0,quartz.dll,10.00.22621.2506 DirectSound: Speakers (HyperX Cloud Stinger Core Wireless + 7.1),0x00200000,1,0,quartz.dll,10.00.22621.2506 AI Noise-Canceling Speaker (ASUS Utility),0x00200000,1,0,quartz.dll,10.00.22621.2506 Realtek Digital Output (Realtek(R) Audio),0x00200000,1,0,quartz.dll,10.00.22621.2506 VX3258 series (NVIDIA High Definition Audio),0x00200000,1,0,quartz.dll,10.00.22621.2506 ---------------------------- 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.3155 mfreadwrite.dll, 10.00.22621.2506 mfcaptureengine.dll, 10.00.22621.0001 mfsensorgroup.dll, 10.00.22621.2506 windows.media.dll, 10.00.22621.2715 frameserver.dll, 10.00.22621.2792 frameserverclient.dll, 10.00.22621.2506 --------------------------- Media Foundation Transforms --------------------------- [HKEY_LOCAL_MACHINE\Software\Classes\MediaFoundation\Transforms] : , , , [, ], Video Decoders: NVIDIA MJPEG Video Decoder MFT, {70F36578-2741-454F-B494-E8563DDD1CB4}, 0x4, 8, nvDecMFTMjpegx.dll, 31.00.0015.5161 Microsoft MPEG Video Decoder MFT, {2D709E52-123F-49B5-9CBC-9AF5CDE28FB9}, 0x1, msmpeg2vdec.dll, 10.00.22621.3155 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.3155 WMV Screen decoder MFT, CLSID_CMSSCDecMediaObject, 0x1, wmvsdecd.dll, 10.00.22621.0001 WMVideo Decoder MFT, CLSID_CWMVDecMediaObject, 0x1, wmvdecod.dll, 10.00.22621.2506 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 HEIFImageExtension VP9VideoExtensionDecoder RawImageExtension WebpImageExtension Video Encoders: NVIDIA H.264 Encoder MFT, {60F44560-5A20-4857-BFEF-D29773CB8040}, 0x4, 8, nvEncMFTH264x.dll, 31.00.0015.5161 NVIDIA HEVC Encoder MFT, {966F107C-8EA2-425D-B822-E4A71BEF01D7}, 0x4, 8, nvEncMFThevcx.dll, 31.00.0015.5161 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.2506 HEIFImageExtension VP9VideoExtensionEncoder Video Effects: Frame Rate Converter, CLSID_CFrameRateConvertDmo, 0x1, mfvdsp.dll, 10.00.22621.0001 Resizer MFT, CLSID_CResizerDMO, 0x1, vidreszr.dll, 10.00.22621.2506 VideoStabilization MFT, {51571744-7FE4-4FF2-A498-2DC34FF74F1B}, 0x1, MSVideoDSP.dll, 10.00.22621.2506 Color Control, CLSID_CColorControlDmo, 0x1, mfvdsp.dll, 10.00.22621.0001 Color Converter MFT, CLSID_CColorConvertDMO, 0x1, colorcnv.dll, 10.00.22621.2506 Video Processor: Microsoft Video Processor MFT, {88753B26-5B24-49BD-B2E7-0C445C78C982}, 0x1, msvproc.dll, 10.00.22621.2506 Audio Decoders: Microsoft Dolby Digital Plus Decoder MFT, {177C0AFE-900B-48D4-9E4C-57ADD250B3D4}, 0x1, DolbyDecMFT.dll, 10.00.22621.3007 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.2506 Microsoft AAC Audio Decoder MFT, CLSID_CMSAACDecMFT, 0x1, MSAudDecMFT.dll, 10.00.22621.2792 A-law Wrapper MFT, {36CB6E0C-78C1-42B2-9943-846262F31786}, 0x1, mfcore.dll, 10.00.22621.3155 GSM ACM Wrapper MFT, {4A76B469-7B66-4DD4-BA2D-DDF244C766DC}, 0x1, mfcore.dll, 10.00.22621.3155 WMAPro over S/PDIF MFT, CLSID_CWMAudioSpdTxDMO, 0x1, WMADMOD.DLL, 10.00.22621.2506 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.2792 WMSpeech Decoder DMO, CLSID_CWMSPDecMediaObject, 0x1, WMSPDMOD.DLL, 10.00.22621.2506 G711 Wrapper MFT, {92B66080-5E2D-449E-90C4-C41F268E5514}, 0x1, mfcore.dll, 10.00.22621.3155 IMA ADPCM ACM Wrapper MFT, {A16E1BFF-A80D-48AD-AECD-A35C005685FE}, 0x1, mfcore.dll, 10.00.22621.3155 MP3 Decoder MFT, CLSID_CMP3DecMediaObject, 0x1, mp3dmod.dll, 10.00.22621.2506 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.3155 Dolby TrueHD IEC-61937 converter MFT, {CF5EEEDF-0E92-4B3B-A161-BD0FFE545E4B}, 0x1, mfaudiocnv.dll, 10.00.22621.2506 DTS IEC-61937 converter MFT, {D035E24C-C877-42D7-A795-2A8A339B472F}, 0x1, mfaudiocnv.dll, 10.00.22621.2506 Audio Encoders: LPCM DVD-Audio MFT, {068A8476-9229-4CC0-9D49-2FC699DCD30A}, 0x1, mfaudiocnv.dll, 10.00.22621.2506 MP3 Encoder ACM Wrapper MFT, {11103421-354C-4CCA-A7A3-1AFF9A5B6701}, 0x1, mfcore.dll, 10.00.22621.3155 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.2506 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.2506 Audio Effects: AEC, CLSID_CWMAudioAEC, 0x1, mfwmaaec.dll, 10.00.22621.0001 Resampler MFT, CLSID_CResamplerMediaObject, 0x1, resampledmo.dll, 10.00.22621.2506 Multiplexers: Microsoft MPEG2 Multiplexer MFT, {AB300F71-01AB-46D2-AB6C-64906CB03258}, 0x2, mfmpeg2srcsnk.dll, 10.00.22621.3085 Others: Microsoft H264 Video Remux (MPEG2TSToMP4) MFT, {05A47EBB-8BF0-4CBF-AD2F-3B71D75866F5}, 0x1, msmpeg2vdec.dll, 10.00.22621.3155 -------------------------------------------- Media Foundation Enabled Hardware Categories -------------------------------------------- [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Media Foundation\HardwareMFT] EnableDecoders = 1 EnableEncoders = 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 1279227800495122976, type 5 Event Name: StoreAgentInstallFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Update;ScanForUpdatesForUser P2: 80073d02 P3: 22631 P4: 3155 P5: Windows.Desktop P6: Z P7: P8: P9: P10: +++ WER1 +++: Fault bucket , type 0 Event Name: StoreAgentInstallFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Update;ScanForUpdatesForUser P2: 80073d02 P3: 22631 P4: 3155 P5: Windows.Desktop P6: Z P7: P8: P9: P10: +++ WER2 +++: Fault bucket 1846077036918960765, type 5 Event Name: StoreAgentInstallFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Update;ScanForUpdatesForUser P2: 80073d02 P3: 22631 P4: 3155 P5: Windows.Desktop P6: P P7: P8: P9: P10: +++ WER3 +++: Fault bucket , type 0 Event Name: StoreAgentInstallFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Update;ScanForUpdatesForUser P2: 80073d02 P3: 22631 P4: 3155 P5: Windows.Desktop P6: P P7: P8: P9: P10: +++ WER4 +++: Fault bucket 2054894418227704426, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: 3DMarkCPUProfile.exe P2: 1.1.0.1 P3: 60dc5313 P4: StackHash_2895 P5: 0.0.0.0 P6: 00000000 P7: PCH_77_FROM_unknown+0x0000000000000000 P8: c0000005 P9: 0000000000000008 P10: +++ WER5 +++: Fault bucket 1385965427907700332, type 5 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.Windows.Photos_2024.11010.23003.0_x64__8wekyb3d8bbwe P2: praid:App P3: 0.0.0.0 P4: 65b07b0a P5: Lightbox.dll P6: 2024.11010.23003.0 P7: 65b0796e P8: c0000005 P9: 0000000000466be1 P10: +++ WER6 +++: Fault bucket , type 0 Event Name: MoAppCrash Response: Not available Cab Id: 0 Problem signature: P1: Microsoft.Windows.Photos_2024.11010.23003.0_x64__8wekyb3d8bbwe P2: praid:App P3: 0.0.0.0 P4: 65b07b0a P5: Lightbox.dll P6: 2024.11010.23003.0 P7: 65b0796e P8: c0000005 P9: 0000000000466be1 P10: +++ WER7 +++: Fault bucket 1939480878545460415, type 5 Event Name: StoreAgentAcquireLicenseFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Update;ScanForUpdatesForUser P2: 80070520 P3: 22631 P4: 3155 P5: Windows.Desktop P6: P P7: P8: P9: P10: +++ WER8 +++: Fault bucket 2123562774008990089, type 5 Event Name: StoreAgentAcquireLicenseFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Update;ScanForUpdatesForUser P2: 80070520 P3: 22631 P4: 3155 P5: Windows.Desktop P6: V P7: P8: P9: P10: +++ WER9 +++: Fault bucket 2198190670636903957, type 5 Event Name: StoreAgentAcquireLicenseFailure1 Response: Not available Cab Id: 0 Problem signature: P1: Update;ScanForUpdatesForUser P2: 80070520 P3: 22631 P4: 3155 P5: Windows.Desktop P6: M P7: P8: P9: P10: ...#SSU#...