Does anyone have a machine with the new v4 chips yet?
We are encountering some weird issues, like not being able to set affinity in task manager, and also ‘Runtimebroker.exe’ going bonkers and using up one core all the time.
thanks for any help
Peter
Hm, no idea yet, could be related to processor groups since these have so many logical cores.
But anyway, something quick to try, do you run the latest Bios/Uefi ? Sometimes motherboards arrive on market sooner than final CPUs.
Also what Windows is this ? And does it have all the latest updates ?
Hi Juraj
windows 10 pro, all windows updates installed. The people who put the computer together assure me the bios is fully up to date
Can you better describe “not being able to set affinity” ? At what step does the issue occur ?
as soon as you click set affinity, you get the error attached
Oh ok, this should be classic Windows elevation issues.
You could either escalate Task manager by clicking “show processes from all users”, or typing “r”(run) and then "taskmgr ". Alternatively, you’re running an application that running with Admin rights, so you could un-check that.
I have the same problem, seems to be Windows issue. Only workaround is setting the # of threads in Corona Performance settings to the amount of cores you want to use at the time. I think this happens with computer with over 64 cores.
Had a similar runtime broker issue after installing win 10, non xeon cpu related issue. This helped: https://www.youtube.com/watch?v=3Yg_ZdhE4rI
Although, I ended up uninstalling half of windows 10 including cortana, search indexing etc., so I cant recreate or help.
Hope this is not bad info.
Is your UAC completely turned off ? (should be). And do you use elevated task manager ?
UAC slider at bottom (can you turn it off even more?) elevated task manager - same story.
@sairesart already turned off all notifications, even uninstalled all ‘metro’ apps from windows 10.
runtimebroker still constantly uses 2.6% of the cpu which means the whole of the windows 10 UI feels a bit sluggish.
starting to suspect windows 10 just doesnt work well with these new chips and its simply a problem they need to fix.
maybe i should turn off hyperthreading and see if windows 10 prefers having less than 64 logical processors???
You can only disable UAC through registry, and it yields some drawbacks.
If this doesn’t correct the issue though, I suggest to take it back. (I think this step requires restart to work…or not, not sure)
pretty big performance hit disabling hyper threading sadly (on the benchmark i went from 39s to 55s)
i havent had any runtimebroker nonsense since though…
would be VERY annoying if this is an issue with windows 10 and new xeon chips with more than 64 cores…
ps. Juraj, i check the bios and its the latest one (which supports the e5 2697 v4 )
We have an e5-2690 v1 system (no problems with setting affinity on 36 cores) and e5 2699 v3 (problems with setting affiniti on 72 cores). I`m sure its windows limit issue.
Hello mate. I spoke with Kern over at Scan about this a while ago and he mentioned that there were BIOS issues with these new chips, so we decided to hold off buying one. I would guess that this is the problem and that an update is needed from the mobo manufacturer (asus?). Although I imagine you’ve already been onto scan about this. We’re thinking of plumping for the same chips you did so keen to find out what the problem is!
Hi Alex, feels like this is a Windows issue rather than a motherboard driver issue. 3dsmax and corona work great, it’s just a couple of annoying things with win10
Ah right. Glad those two are working properly. That’s what matters most I guess.
So refreshing when just for once it’s not our problem 
anyone else got one of these new chips yet? curious to see if you have the same problem as us?