Message boards :
Number crunching :
CMS no longer works after today's big Windows10 system update
Message board moderation
Author | Message |
---|---|
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,412,025 RAC: 102,477 |
Today's huge system update in my Windows10 must have ruined something with regard to CMS crunching: When I reastartet BOINC (and thus CMS), the two tasks that had run before, after a while showed "postponed: VM Hypervisor failed to enter an online state in a timely Fashion". So, the next two tasks startet, but the same thing happened with them, too, after several minutes (during which there was neither any CPU nor RAM load for CMS). Any advice as to how I can get the problem repaired? |
Send message Joined: 15 Jun 08 Posts: 2386 Credit: 222,969,891 RAC: 136,677 |
Today's huge system update in my Windows10 must have ruined something with regard to CMS crunching: You may check if the update has activated another hypervisor. Reinstall VirtualBox if necessary. <edit> I saw in you log that you use vbox version 5.1.6. You may update to the most recent version. </edit> |
Send message Joined: 27 Sep 08 Posts: 798 Credit: 644,794,858 RAC: 231,405 |
It broke the OpenCL/CUDA if you use those too, reinstall you video drivers to get it back again. |
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,412,025 RAC: 102,477 |
It broke the OpenCL/CUDA if you use those too, reinstall you video drivers to get it back again. yes, I found out when I tried to restart Folding@Home after the MS Update. That installed a newer graphic driver, but - as I have learned meanwhile - the graphic drivers in these MS updates are always only fragments of the full drivers as provided by the manufacturer (NVIDIA in my case - in order do keep the download size low. So I re-installed my previous NVIDIA driver, and Folding@Home worked well. However, it did NOT help for CMS. So, the MS Update must have ruined something else in my system :-( |
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,412,025 RAC: 102,477 |
You may check if the update has activated another hypervisor. how can I check this? |
Send message Joined: 29 Aug 05 Posts: 998 Credit: 6,264,307 RAC: 71 |
|
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,412,025 RAC: 102,477 |
General rule of thumb, from experiences in the SETI@Home forums, NEVER let Windows update an Nvidia driver. Always deselect them and hide them if you can. Ivan, I am 100% with you ! But, please let me know how I can deselect such a driver update in Windows10. Either I am overlooking something, or it's not possible. |
Send message Joined: 15 Jun 08 Posts: 2386 Credit: 222,969,891 RAC: 136,677 |
You may check if the update has activated another hypervisor. After an update that causes problems it's generally a good idea to systematically check all settings that are important for the software you want to run. 1. BIOS settings - VT-x enabled or disabled? - check also the corresponding entry in your client_state.xml 2. Hardware drivers - especially for graphic devices as already mentioned in this thread 3. Did the update install/activate software that was previously deinstalled/deactivated because it causes trouble with your software? - here: hypervisors check this page: https://blogs.technet.microsoft.com/ralfschnell/2009/05/08/hyper-v-deaktivieren-des-hypervisors/ it is in german language so you understand it 4. Reinstall additional software like VirtualBox - most recent versions should be preferred - it ensures that all access rights are set according to your needs 5. Check the BOINC folders - if necessary remove files that are suspect to cause troubles like orphaned vdi files in the slots dir 6. Detach from and reattach to the project 7. Reboot your host - and reboot again if necessary 8. Stay patient and keep your fingers crossed. - it's NOT a joke, it REALLY helps. |
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,412,025 RAC: 102,477 |
Thanks, computezrmle, for the many hints. At any rate, after deinstalling the VBox and re-installing (the latest version), CMS now works fine. So, this System Update had indeed crashed my VBox :-( |
Send message Joined: 15 Jun 08 Posts: 2386 Credit: 222,969,891 RAC: 136,677 |
Thanks, computezrmle, for the many hints. +1 Happy crunching. |
Send message Joined: 29 Aug 05 Posts: 998 Credit: 6,264,307 RAC: 71 |
General rule of thumb, from experiences in the SETI@Home forums, NEVER let Windows update an Nvidia driver. Always deselect them and hide them if you can. Yes, I know it's not easy in Win10 -- I currently have only one Win10 box (I bricked my tablet trying to remove updates...) so I'm not really an expert. If you are using WiFi you can tell Windows that you are on a metered connection, and then it will not download updates without approval; there is supposedly a way to do the same with wired connections but it involves a registry hack. |
Send message Joined: 29 Aug 05 Posts: 998 Credit: 6,264,307 RAC: 71 |
|
Send message Joined: 18 Dec 15 Posts: 1686 Credit: 100,412,025 RAC: 102,477 |
Yes, I know it's not easy in Win10 It sure isn't. Meanwhile, I found some instructions in a Windows Forum - but I need to study them first, looks rather complicated. On the other hand, such huge system updates like the recent one don't happen too often anyway; the "normal" ones so far did not do any harm to the crunching software on my PCs. |
©2024 CERN