5
0
I have been trying to install virtual systems on VMWare for a while now and encountered strange behaviour from my PC.
The behaviour is as follows:
On "automatic" virtualization mode it either outputs a cryptic error message (can MAYBE give later, if I can reproduce) right on startup (before even the BIOS) or it resets the complete HOST system (blackscreen, bios...)
If I install a Windows XP on it it works well on "binary translation" mode.
If I try installing Linux on it, in "binary translation" mode it crashes 1 or 2 seconds after I hit enter on the GRUB selection screen (after the first page of kernel messages rolled in)
Using VirtualBox it crashes right in the BIOS. It gave me a Bluescreen though! 0x00000101: CLOCK_WATCHDOG_TIMEOUT: a clock interrupt was not received on a secondary processor within the allocated time interval
NEWS: I tried VirtualBox again and it did not completely crash the computer this time. It gave me a critical error and a log file: http://pastebin.com/yKZSDs91
In conclusion, it will crash instantly if VT-x is activated. If not, it seemingly only crashed if I try to install something with 64 bits.
Another update: Yes, it ONLY crashes when the guest is 64 bit!
On Linux using VirtualBox, it crashes with a Kernel Panic.
What I tried:
- Reinstalling Windows (my Windows installation was quite broken so it seemed natural. Didn't work though.)
- New BIOS
What I am certain of:
- Virtualization extensions are activated in the BIOS
What my computer specs are:
- ASUS P8P67 LE mainboard, newest BIOS/EFI firmware
- Intel Core i5 2500k
- Ati Radeon HD 5770
- 16 GB Corsair 1333mhz DDR3 RAM, 4 X 4 GB
Are you using dual channel or a single stick? – HaydnWVN – 2011-11-08T16:35:36.990
4 sticks a 4gb in total – sinni800 – 2011-11-08T16:47:01.037
You can try VirtualBox to see if it gives the same error. – Joe Internet – 2011-11-08T16:58:28.987
@JoeInternet Seems that I have to. – sinni800 – 2011-11-08T17:16:44.557
1VirtualBox crashes in similar ways. Right in the BIOS for example. BUT I have finally gotten a bluescreen: 0x00000101: CLOCK_WATCHDOG_TIMEOUT. Hell – sinni800 – 2011-11-08T21:25:49.503
I got a VirtualBox log! YES! – sinni800 – 2011-11-10T16:55:01.183
@sinni800: You're using a K edition processor. Is it overclocked? VT-x may reduce the effective speed you can run the CPU at if the total number of gates per cycle that need to switch are greater (which is probably the case, particularly when nested page tables get involved) – Billy ONeal – 2011-11-15T03:27:57.360
@BillyONeal No, I never overclock. I bought the K because it was the same price and I MIGHT want to overclock later, but practically, I never do. But what can I do about it? – sinni800 – 2011-11-15T13:46:58.977
@sinni800: I would consider returning the CPU and motherboard for replacement if you can. If you can't... if you've already tried reinstalling the host OS I'm out of ideas. Sounds like hardware to me though. You might want to debug the crash dump with Windbg to see if it'll finger a specific driver for you: http://forums.majorgeeks.com/showthread.php?t=35246
– Billy ONeal – 2011-11-15T15:55:32.847I couldn't even get the debugging tools to install. I'll try more. Until then, replacing the hardware is the answer.. – sinni800 – 2011-11-18T16:34:38.520
BillyONeal was pretty much first in suggesting to replace the motherboard, but he didn't post an answer. So I will have to give the reputation, which will end in one hour, to @Solignis, he was second fastest in suggesting to replace. – sinni800 – 2011-11-18T16:38:23.057