The BMC system log was disabled. Apparently that is the default. I've enabled it but I have about 30 hours left before I can switch back to ESXi since I can't trust ESXi to last that long before the server disconnects from the network. I can upload the logs to somewhere and/or email them to you.
As for my BMC, I have it setup as a dedicated port. I think the default was failover, but I changed it because I had some weird issues with failover on a previous system build because the network switch wouldn't bring all ports online at the exact same time so it would failover when it didn't need to and then never switch back when a network link was "restored" seconds later. This behavior is documented on the web, so I just assume avoid the potential issue and make it dedicated.
I'll be honest, I'm very vague on what a CIM provider actually is. I've Googled it but I'm really not seeing how it could be my problem, but I will push the "I believe" button and accept your knowledge since I'm sure its more than mine. As far as I know I haven't installed any 3rd party CIM providers(hence my reason for not understanding how it could be a CIM provider issue). My issue seems to be ultra-rare at the least. And all of my ESXi using friends I have consulted with on the phone are at a loss to explain the actual issue except to say "it sucks to be you". LOL. Even my friend's system that is the same identical hardware(literally bought double of everything when we built the system) doesn't have this issue. I updated his ESXi build on Sunday night and he was at 37 days of uptime. He has the exact same VMs, but 1 more(small XP system for printing). I don't know how to download a log bundle, but I'm sure I can learn with some Google-fu and/or a call to my ESXi friend.
Supermicro's naming is confusing. My board is technically the X9SCM-F. The -O means non-retail box I believe. I instinctively add the -O because its technically the most accurate, although I guess it really adds no value(especially related to this problem).