If it's not the developer's problem (somehow made it go into a loop on hitting some unaccounted-for system state that happens to be what your machine is in... see if anyone else has reported that issue, maybe?) then I'd try reinstalling (in case something went wrong with the first install, and VITAL.DLL or IMPORTANT.CFG is missing/corrupt in a not-instantly-fatal way). Could be revealed (and/or solved and/or made into a more 'hard error') if a disk-check and fix comes across signs of inappropriately cross-linked files from some data corruption. But that could mean a bigger problem.
You could fire up your OS's own process-listing thing (or a third-party app with this functionality), to see what might be running at 100% of a CPU (or effectively so, for any given core(s)), what files are currently being accessed, etc. But there are so many different ways of doing that and who knows what else you have running[1] to confuse the issue if you're not already familiar with their presence in the background. If it's not a known issue then you may be asked to check this kind of thing in whatever manner the developer thinks best, but it's a bit more of a shot in the dark without more intimate knowledge of what might be going wrong.
[1] These days, Anti-Virus programs are better at not running race-conditions in certain circumstances, but if you find that that is eating up processor cycles, without even giving you an actual report of anything nasty, I'm sure both the AV and game vendors would be interested. Once any more trivial examination has been made and not helped much.