Windows – How to find out the total number of virtual core your CPU has

To answer your first question: http://www.richweb.com/cpu_info describes all the cpuinfo output in good detail with some interesting discussion following the article.

In your case it's reporting that your VM is configured to show itself to the OS as a two-physical-core VM. The bare metal under the VM might be 1 core or 100 cores but as far as the OS in the VM is concerned you've got a machine with two physical processors that it can play with. It knows nothing of how threads that it assigns to those processors are actually being run on the physical hardware underneath the VM.

To get somewhat similar information from a Windows CMD shell you can try the systeminfo command from a CMD shell. It displays a whole lot more than the /proc/cpuinfo stuff in Linux, but also not quite as much detail about the actual processors themselves.

I don't know the answer to your third question, sorry.

Given the description of the freeze you're describing, it does sounds like a hardware-level issue, however not necessarily caused by the CPU. That said, a multi-CPU system can definitely tangle itself into a deadlock on all cores, if each is running a thread or process that are each waiting on a resource the other thread/process has allocated. A search on "CPU deadlock" provides lots of details on possible conditions. A failure due to overheating or improper voltage settings could also cause intermittent behavior - although I've only seen systems shutdown or refuse to POST when this is the case.

FYI - I've seen similar problems on systems with bad memory sticks, and bad video cards. You might try running some burn-in diagnostics such as MemTest+, and/or benchmarking the system with different pieces of hardware removed to see if you can isolate the unstable component(s).