CORELIQUID MPG K240 CPU Cooler Hardware damaging programing issue!

[GWraith]

I contacted MSI support today, Live Chat, to report the bug and they didn't seem concerned nor did they know that Windows 11 was even released to consumers. Was released October 5th 2021 and has been available in pre-production as a windows insider opt-in for about 6 months. I also tried to make a web ticket but the MSI website kept erroring when I selected this product in the support/warranty section

This is a major flaw in the MSI Center - Coreliquid software that can overheat and destroy your computer if you don't know to look for it.

The issue began after I did a clean install of the release version of Windows 11. Previously I was running insider builds with no issues noted on the MSI Center.

I have reinstalled the program twice, MSI no longer offers a standalone version of it, and the Dragon Center does not contain it either.

ISSUE: MSI Center - Coreliquid services are frozen after a reboot or resuming from sleep on Windows 11 resulting in the AIO no longer reading the temperature of the CPU.
AIO Mode: GI currently testing if this also happens in game mode.

Symptom: The CPU cooler stops reading the CPU temperature and stays stuck on the last temp it received.

Workaround: Use task manager to end every MSI service and task running in the system. Re-run MSI Center using admin credentials.

This is a very dangerous bug as the other day my CPU was at 80c playing a game and the cooler was only cooling for 50c. The fans and pump were not ramped up to handle the extra load. I also checked and yes all my other programs read the temp just fine when MSI is frozen but this directly keeps the cooler from cooling.

Please advise or fix ASAP. I can provide my system information from Hardware Info 64 at the request of a forum master or MSi technician.

This is a very concerning cause as MSI techs can see from my computer hardware warranty profile and I have a lot of MSI hardware and I paid $210 to get this cooler alone. I trust in MSI to do the right thing quickly to protect my hardware that if damaged by this bug will have to be replaced by them because its all MSI products in my rig. Live Chat techs should be more concerned when you present them with a computer destroying bug.

 

[GWraith]

Update: This occurs in any AIO cooling profile. Also occurs after a long time idle regardless of sleep or not.

MSI Center stops being able to read the CPU temp even in the hardware monitor section. I suspect this has to do with a service be blocked or killed by something in Windows 11.

 

[GWraith]

Created a quick little batch file to kill the MSI processes. Uses CMD or Powershell. You can also do this manually in the task manager, but one click is simpler than 10.

1. Use the task manager to "end task" on MSI Center
2. Run this batch as admin.
3. Relaunch MSI Center using admin credentials.

You will need to find your PIDs and put them in the script. Also unfortunately I cannot also run the MSI Center from the batch file due to the way Windows 11 manages "SYSTEM" apps. I can only launch it using the start menu shortcut.

For some reason, the MSI Center app does not show up as a process in CMD or PowerShell when frozen, could this be the root cause?. You'll have to "end task" on the open app manually.

If anyone wants to find a way to add an MSI Center open line to the batch that would make this all the easier.

Update: Removed file, PID change every time a service is stopped and started. The old-fashioned way it is.

 

[arbysseus]

Just wanted to add that I'm running Windows 10 Pro and I have the exact same issue. It's been happening since my last clean install in July. CPU temp will randomly stop updating. Prior to MSI Center 1.0.31 the service would just hang and restarting the program as admin would temporarily begin reporting. Now, MSI Center doesn't lock up, but the CPU value never updates past a certain point and services need to be restarted manually.

 

[keig42eb0614]

i recommend not to use the cooling anymore, i purchase one last year, the AIO cooler fail, remember the pump the cooler using is a magnetic type, even it show is spinning, that didn't mean the blade actually is, as i find out my system shut down all be itself for the last few week, i checked everything, i find the exhuast pump is hot but not the radiator or the input tube, that mean the water is not flowing smoothly all the pump stopped, i ended up installing the original AMD cooler and open the MSI cooler to check, thing i find

1. coolant is slimy - coolant and distil water is not mix probably, bacteria is growing inside
2. pump is a magnetic free spinning type so it the pump pressure inside the radiator is too much for the blade to work, the system will still see the pump spinning
3. a lot of air within the loop - after 1 year of use (I keep my computer on 24/7) there is a lot of evaporation, there is a refilling hole on the radiator, but refilling is not as easy is putting the coolant in
4. as I drained the radiator, a lot of white flake is build up inside the loop, i think is the water used is not distil which is the separation product from the calcium in the water
5. then opened up the cpu block can see the white flake is blocking the flow though the cpu block, causing the the flow to go very slowly and some time the pump can't even start is the pressure is too great for the pump to overpower (the pump is one of the smallest one i seen)
6, when i flash the radiator more of the slime and white flake come out

from what i have find is recommended to replace another brand AIO, or what i did and replace the coolant and clean out the system, don't worry about claiming warranty, as them will just replace the system for you but, is still the same [***CENSORED***] inside

 

[GWraith]

i recommend not to use the cooling anymore, i purchase one last year, the AIO cooler fail, remember the pump the cooler using is a magnetic type, even it show is spinning, that didn't mean the blade actually is, as i find out my system shut down all be itself for the last few week, i checked everything, i find the exhuast pump is hot but not the radiator or the input tube, that mean the water is not flowing smoothly all the pump stopped, i ended up installing the original AMD cooler and open the MSI cooler to check, thing i find

1. coolant is slimy - coolant and distil water is not mix probably, bacteria is growing inside
2. pump is a magnetic free spinning type so it the pump pressure inside the radiator is too much for the blade to work, the system will still see the pump spinning
3. a lot of air within the loop - after 1 year of use (I keep my computer on 24/7) there is a lot of evaporation, there is a refilling hole on the radiator, but refilling is not as easy is putting the coolant in
4. as I drained the radiator, a lot of white flake is build up inside the loop, i think is the water used is not distil which is the separation product from the calcium in the water
5. then opened up the cpu block can see the white flake is blocking the flow though the cpu block, causing the the flow to go very slowly and some time the pump can't even start is the pressure is too great for the pump to overpower (the pump is one of the smallest one i seen)
6, when i flash the radiator more of the slime and white flake come out

from what i have find is recommended to replace another brand AIO, or what i did and replace the coolant and clean out the system, don't worry about claiming warranty, as them will just replace the system for you but, is still the same [***CENSORED***] inside

Wow, I almost feel like I was scammed if that's true.

 

[keig42eb0614]

if you do some search, i also posted the sekira 500x case, is was so bad in cooling, i have CPU throttling issue, i did modded the case to make it work, and ask gamernexus to do a review on the case, which he did
MSI Bought Its Awards: Hotbox Sekira 500X Case Review - YouTube
i can say the cooler do work base on design, but the coolant must change before use

 

[keig42eb0614]

MSI SEKIRA 500x mods idea | MSI Global English Forum - Index

 

[GWraith]

if you do some search, i also posted the sekira 500x case, is was so bad in cooling, i have CPU throttling issue, i did modded the case to make it work, and ask gamernexus to do a review on the case, which he did
MSI Bought Its Awards: Hotbox Sekira 500X Case Review - YouTube
i can say the cooler do work base on design, but the coolant must change before use

This is not a case issue. I have the same case I used my Corsair H100i in for my 7700K. this is an AIO MPG K240 / MSI Center issue.

 

[GWraith]

Found a sudo fix that bypasses MSI Center. Make sure that MSI Center can read the temp then go into coreliquid fan settings and make custom fan and pump profiles. Once applied even if MSI Center locks up the cooler will work independently.

 

[GWraith]

The workaround did work for long. Back to just killing all the services and relaunching as admin.

 

[arbysseus]

This is happening nearly daily for me. CPU temp in MSI center is showing 34C while other tools that read the temp directly from the mobo are reading 80C. Of course the radiator fan and pump are tied to MSI Center's readings and not the motherboard, so this is putting my hardware at serious risk.

 

[GWraith]

This is happening nearly daily for me. CPU temp in MSI center is showing 34C while other tools that read the temp directly from the mobo are reading 80C. Of course the radiator fan and pump are tied to MSI Center's readings and not the motherboard, so this is putting my hardware at serious risk.

Yeah, this is seeming to plague anyone who did a fresh install of 1.0.31.0 and didn't have a previous version installed. I'm now in the habit of killing all of it and relaunching before I do any strenuous gaming or video editing. I can't believe something this serious and affecting their top-end CPU coolers still has not been hot-fixed. Look like I can mark MSI AIO off my build list in the future and go with tried and true.

 

[GWraith]

SO I completely removed the MSI SDK and the MSI Center. I also removed registry entries leftover and folders leftover. I restarted my computer. Then I went right into the Microsoft Store and instead MSI Center from there instead of the MSI standalone installer from their site.

The program and cooling have been working solidly for about 6 hours now. Give it a shot and let me know your results.

 

[GWraith]

I locked the computer and went and watched some TV. When I came back it was frozen again. Looks like it froze the second I locked the computer.

 

[GWraith]

So I tried not locking the computer last night and it again froze so it must be windows killing some sort of service.

 

[GWraith]

Ok, so I did some tinkering. I made the service MSI Central Server an automatic process that starts with the computer. I also put in my custom fan curve and applied it. Then I went into the bottom right panel area on the desktop and fully exited MSI Center. The AIO is continuing to run and read temperature and respond over several locks, unlocks, and extended idle times. I'm not sure if what I changed fixed the issue but it doesn't seem to be locking up with MSI Center closed completely.

These are the following services I put to "Automatic" instead of "Manual":

MSI Central Service
Sensor Data Service
Sensor Monitoring Service
Sensor Service

One service I put to "Manual" because I'm never going to use it:

MSI Voice Control - (Manual)

 

[arbysseus]

I can tell when mine crashes because in the log directory C:\Program Files (x86)\MSI\MSI Center\Log\Coreliquid you start seeing errors in the log files. I've been sending log packages to MSI support the past few days whenever it occurs, but no luck yet.

 

[GWraith]

Now that I made the above changes it is doing it way less but it still happens when the computer has been idle for a long time.

I'm only finding these issues.

MSI Center:
USB Deletion Event : \\*COMPUTERNAME*\root\cimv2:Win32_PnPEntity.DeviceID="SWD\\MMDEVAPI\\{0.0.0.00000000}.{E1C3058E-212F-43DF-A0E6-E08C651CB249}
USB Deletion Event : VID_1462&PID_7C92
Server Launch : Only one usage of each socket address (protocol/network address/port) is normally permitted
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2021-10-18 09:30:03.431 =============================================================
2021-10-18 09:30:03.432 SDK Version : 3.2021.0924.01
2021-10-18 09:30:03.433 UTC : 2021-10-18 13:30:03.433
2021-10-18 09:30:03.433 UTC offset : -4
2021-10-18 09:30:03.739 Download File : BaseUrl.dat
2021-10-18 09:30:03.739 Date : Mon, 18 Oct 2021 13:30:03 GMT
2021-10-18 09:30:03.740 Content-Length : 914
2021-10-18 09:30:03.740 StatusCode : 200
2021-10-18 09:30:03.758 Download File : DefineBaseV1.dat
2021-10-18 09:30:03.759 Date : Mon, 18 Oct 2021 13:30:03 GMT
2021-10-18 09:30:03.760 Content-Length : 17168
2021-10-18 09:30:03.760 StatusCode : 200
2021-10-18 09:30:03.793 Parse BIOS RAWData.
2021-10-18 09:30:03.831 Parse Platform Information.
2021-10-18 09:30:04.167 Server Launch : Only one usage of each socket address (protocol/network address/port) is normally permitted
2021-10-18 10:23:00.008 Initialized : 1 (OK).
2021-10-18 10:23:00.143 Load component Gaming Gear 2.0.0.19.
2021-10-18 10:23:00.168 Initialized : 1 (OK).
2021-10-18 10:23:00.231 Load component Coreliquid 3.0.0.19.
2021-10-18 10:23:01.965 Initialized : 1 (OK).
2021-10-18 10:23:02.036 Permission : 3
2021-10-18 10:23:02.036 Monitor Power Event
2021-10-18 10:23:02.170 Monitor USB Event
2021-10-18 10:23:02.281 Session Change Event : WTS_REMOTE_CONNECT (3)
2021-10-18 10:23:02.286 Session Change Event End.
2021-10-18 10:23:02.288 MSI.CentralServer is ready.
2021-10-18 10:23:02.288 Check point : 000:0,001:207,002:392,003:313,004:888,005:108,006:492,007:252,All:2652
2021-10-18 10:23:02.426 Session Change Event : WTS_REMOTE_DISCONNECT (4)
2021-10-18 10:23:02.436 Session Change Event End.
2021-10-18 10:23:02.437 Session Change Event : WTS_CONSOLE_DISCONNECT (2)
2021-10-18 10:23:02.438 Session Change Event End.
2021-10-18 10:23:03.034 Session Change Event : WTS_CONSOLE_CONNECT (1)
2021-10-18 10:23:03.034 Session Change Event End.
2021-10-18 10:23:03.518 Session Change Event : WTS_CONSOLE_DISCONNECT (2)
2021-10-18 10:23:03.521 Session Change Event End.
2021-10-18 10:23:03.736 Session Change Event : WTS_CONSOLE_CONNECT (1)
2021-10-18 10:23:03.741 Session Change Event End.
2021-10-18 10:23:10.671 Session Change Event : WTS_SESSION_LOGON (5)
2021-10-18 10:23:10.847 Current username : defaultuser100000
2021-10-18 10:23:10.847 Current account type : NoExist
2021-10-18 10:23:10.918 Current user profile path : C:\Users\defaultuser100000
2021-10-18 10:23:10.918 Watch UI release : C:\Users\defaultuser100000
2021-10-18 10:23:10.918 Watch UI packages error : The directory name C:\Users\defaultuser100000\AppData\Local\Packages\ is invalid.
2021-10-18 10:23:10.919 Launch TerminalServer (Checking).
2021-10-18 10:23:11.056 TerminalServer is not ready.
2021-10-18 10:23:11.063 user account active counts : 1
2021-10-18 10:23:11.064 Launch TerminalServer.
2021-10-18 10:23:11.064 Execute : C:\Program Files (x86)\MSI\MSI Center\MSI.TerminalServer.exe , Launch (2)
2021-10-18 10:23:11.664 Execute [Run].
2021-10-18 10:23:11.738 TerminalServer get platformInfo.
2021-10-18 10:23:11.773 Execute [RUNNING].
2021-10-18 10:23:11.854 Using general power method.
2021-10-18 10:23:12.411 is support HID device [VID_0DB0&PID_B130].
2021-10-18 10:23:12.611 Server Launch Completed.
2021-10-18 10:23:14.010 Session Change Event End.
2021-10-18 10:23:14.010 Session Change Event : WTS_SESSION_LOCK (7)
2021-10-18 10:23:14.015 Session Change Event End.
2021-10-18 10:23:52.814 Session Change Event : WTS_CONSOLE_DISCONNECT (2)
2021-10-18 10:23:52.819 Session Change Event End.
2021-10-18 10:23:52.982 Session Change Event : WTS_CONSOLE_CONNECT (1)
2021-10-18 10:23:52.986 Session Change Event End.
2021-10-18 10:23:53.634 Session Change Event : WTS_SESSION_UNLOCK (8)
2021-10-18 10:23:53.841 Display Settings Changed.
2021-10-18 10:23:53.873 Current username : ******
2021-10-18 10:23:53.874 Current account type : Administrator
2021-10-18 10:23:54.017 Current user profile path : C:\Users\******
2021-10-18 10:23:54.018 Watch UI registed : C:\Users\******
2021-10-18 10:23:54.018 Launch TerminalServer (Checking).
2021-10-18 10:23:54.135 TerminalServer is ready.
2021-10-18 10:23:54.136 Session Change Event End.
2021-10-18 10:23:56.190 Session Change Event : WTS_SESSION_LOGOFF (6)
2021-10-18 10:23:56.193 Session Change Event End.
2021-10-18 10:23:56.850 USB Creation Event : \\*COMPUTERNAME*\root\cimv2:Win32_PnPEntity.DeviceID="SWD\\MMDEVAPI\\{0.0.0.00000000}.{E1C3058E-212F-43DF-A0E6-E08C651CB249}"
2021-10-18 10:23:57.861 USB Creation Event : \\*COMPUTERNAME*\root\cimv2:Win32_PnPEntity.DeviceID="SWD\\MMDEVAPI\\{0.0.1.00000000}.{5A3F4757-823D-4EB0-9CD7-8049196216F9}"
2021-10-18 10:24:00.285 Response component information for UI.
2021-10-18 13:02:49.181 USB Deletion Event : \\*COMPUTERNAME*\root\cimv2:Win32_PnPEntity.DeviceID="SWD\\MMDEVAPI\\{0.0.0.00000000}.{E1C3058E-212F-43DF-A0E6-E08C651CB249}"
2021-10-18 13:02:49.415 USB Deletion Event : \\*COMPUTERNAME*\root\cimv2:Win32_PnPEntity.DeviceID="SWD\\MMDEVAPI\\{0.0.1.00000000}.{5A3F4757-823D-4EB0-9CD7-8049196216F9}"
2021-10-18 13:42:40.012 USB Deletion Event : VID_0951&PID_1603
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
USB Drive Removal:
2021-10-18 13:42:40.238 USB Deletion Event : \\*COMPUTERNAME*T\root\cimv2:Win32_PnPEntity.DeviceID="USBSTOR\\DISK&VEN_KINGSTON&PROD_DATATRAVELER_2.0&REV_1.00\\0010000000000000000002CD&0"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Coreliquid:
Thread Error : The media is write protected.
Memory clear
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2021-10-18 09:30:08.068 new Coreliquid : Engine ok
2021-10-18 09:30:08.111 init
2021-10-18 09:30:08.111 Set Fan
2021-10-18 09:30:08.115 Customize
2021-10-18 09:30:08.118 iMode : 3
2021-10-18 09:30:08.652 default
2021-10-18 09:30:08.657 Set_OLED_ShowHWMonitor - cancel
2021-10-18 09:30:09.677 Set_OLED_ShowHWMonitor - Setting
2021-10-18 09:30:09.677 new Coreliquid : Initialization ok
2021-10-18 09:30:09.687 new Coreliquid : VGA Engine ok
2021-10-18 09:30:09.687 new Coreliquid : Monitor ok
2021-10-18 10:03:14.833 Thread Error : The media is write protected.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Middle of the night when the computer is idle and locked.

021-10-18 02:05:34.409 Memory clear
2021-10-18 05:10:21.900 Memory clear

MSI Central Service:
2021/10/18 09:30:03.321 SERVICE START.
2021/10/18 10:03:06.528 SERVICE LOGOFF.
2021/10/18 10:03:11.206 SERVICE STOP. <- WHY?
2021/10/18 10:22:43.232 SERVICE START.
2021/10/18 10:22:43.567 SERVICE LOGON.
2021/10/18 10:22:43.878 SERVICE LOCK.
2021/10/18 10:23:10.671 SERVICE LOGON.
2021/10/18 10:23:11.591 SERVICE LOCK.
2021/10/18 10:23:53.634 SERVICE UNLOCK.
2021/10/18 10:23:56.191 SERVICE LOGOFF.

 

[GWraith]

I got on chat again with MSI. They have sent me the MSI_uninstaller.exe and the older version of MSI Center, (1.0.26.0). I'm going to test these out and see if the issues are resolved with the older version.