Are you seeing the blue screen of death on R2?
I'm getting seemingly random BSODs on a Windows Server 2008 R2 beta Hyper-V machine. I've filed Connect bug 405452, which was closed Resolved by Microsoft. The latest comment from Microsoft is that it is caused by antivirus software, which is incorrect because I don't have any antivirus software installed.
When I filed the bug originally, the title I gave was "BSOD appears - close laptop with OS running, come back later, open laptop, see BSOD" . I later amended the bug report and explained that closing the laptop had nothing to do with it. The problem has occured at least five times without the laptop being closed. In every case there is either been a running vm or a Hyper-V manager action has just been completed (start a vm, stop a vm, etc.).
I've uploaded machine dump files, but none of the dump files ever made it to 100%. See the reproduction of the screen capture below to see what I mean. The latest one only made it to 60. One of the dumps made it to 80. I'm concerned that the dumps are incomplete and thus possibly useless.A problem has been detected and Windows has been shut down to prevent damage
to your computer.
A clock interrupt was not received on a secondary processor within the allocated
time interval.
If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow
these steps:
Check to make sure any new hardware of software is properly installed.
If this is a new installation, ask your hardware or software manufacturer
for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware
or software. Disable BIOS memory options such as caching or shadowing.
If you need to use Safe Mode to remove or disable components, restart
your computer, press F8 to select Advanced Startup options, and then
select Safe Mode.
Technical information:
*** STOP: 0x00000101 (0x0000000000000061,0x0000000000000000,0xFFFFF880005EB180,0
x0000000000000001)
Collecting data for crash dump ...
Initializing disk for crash dump ...
Beginning dump of physical memory.
Dumping physical memory to disk: 60
Answers
- This BSOD is a known issue (http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/a7451e42-eb42-42cf-9c3b-3bf5cc392ee0).
- Marked As Answer byJohn Paul CookMVP, ModeratorWednesday, February 25, 2009 5:14 PM
All Replies
- John - Is your laptop attempting to hibernate?
Is you laptop going into a low power state (the clock interrupt on a secondary processor) and powering down certain components?
Brian Ehlert (hopefully you have found this useful) - Interesting question about hibernation. The laptop is set to a Balanced power plan.
- So, John - what does "balanced" mean?
And, is this is Power Management setting in the BIOS or the Parent partition? - since we have two levels.
I do realize that it is your laptop, so why not "always on"? That is what a server would be. With random powering down of NICs, Fans slowing down, etc. I wonder is your CPU is attempting to scale back.
Brian Ehlert (hopefully you have found this useful) - First I'll explain the Basic power plan settings.
A Balanced power plan under Windows Server 2008 R2 only affects when the display is turned off. There are two settings for turning off the display, one for when running on battery power and another for running on AC power.
Under a Windows 7 client OS, a balanced power plan has an additional setting for going into hibernation after a specified period of time.
There are also Advanced power plan settings.
It is interesting to note that a lid close action does by default on Windows Server 2008 R2 initiate - or try to initiate - a sleep state. However, my last five BSODs occurred when the lid was open. What is more interesting is that PC Wizard 2008 shows the processor frequency ranging from about 800 Mhz to 2400 MHz. This is the expected behavior when Intel SpeedStep is enabled. According to what I've read, when SpeedStep is enabled and the computer's properties page is brought up, two frequency values are displayed. If they are the same, then SpeedStep is not enabled. Both frequencies show up as the same. Whether or not SpeedStep is enabled, it does appear there is some type of cpu throttling occurring. The BSODs do appear to occur when the machine is idle. Someone else filed bug 416323 on Connect which reports BSODs on an idle machine. - Hi John,
It seems that you explained the causes of the problem.
When the computer goes to idle state, it make the Hyper-V host machine unstable.
Best regards,
Vincent Hu - Hi,
I have the same problem here, wasn't hibernation and power savings features turned off when Hyper-V Role is installed ? anyway I met this error randomly when the machine is working, so I don't think it's because of idle state, any other probable explanation? preferably with a solution to it.
- Further explanation is needed. Hibernation is not enabled, which is the implication of "A Balanced power plan under Windows Server 2008 R2 only affects when the display is turned off." To be explicit, a balanced power plan on R2 does not include hibernation. Hibernation just isn't possible under Windows Server 2008. SpeedStep is another matter entirely.
Intel SpeedStep is a power conserving feature that reduces the clock speed of a cpu when it is lightly loaded. It caused Virtual PC 2004 to freeze. A lightly loaded cpu isn't the same thing as an idle cpu - although with background processes, is a cpu ever idle? It's possible to be doing something such as using Notepad or scrolling an already loaded web page and have SpeedStep throttle back the processor. The machine doesn't have to be idle, just lightly used.
Many people believe that using Power Options to configure a machine for maximum performance disables SpeedStep. There are numerous reports that this is not actually true, at least for Vista users. The safest and surest way to disable SpeedStep is to go into the bios and turn it off there. I'm going to try that and see what happens. - This BSOD is a known issue (http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2virtualization/thread/a7451e42-eb42-42cf-9c3b-3bf5cc392ee0).
- Marked As Answer byJohn Paul CookMVP, ModeratorWednesday, February 25, 2009 5:14 PM
- i have the same poblem but i am having the problem with it on windows vsta home prem....
Is there any hotfixes for it???
for windows vista? - No, you are not having exactly the same problem. This is a Windows 2008 Hyper-V forum. Windows Vista does not support Hyper-V. Although your symptoms appear similar, the root cause is different. Please post your question to a Vista forum. Vista forums can be found here: http://social.technet.microsoft.com/forums/en-US/category/windowsvistaitpro/. I hope you can find answer there, good luck. Be sure that you have fully updated your Vista installation from Windows Update.
Further explanation is needed. Hibernation is not enabled, which is the implication of "A Balanced power plan under Windows Server 2008 R2 only affects when the display is turned off." To be explicit, a balanced power plan on R2 does not include hibernation. Hibernation just isn't possible under Windows Server 2008. SpeedStep is another matter entirely.
Intel SpeedStep is a power conserving feature that reduces the clock speed of a cpu when it is lightly loaded. It caused Virtual PC 2004 to freeze. A lightly loaded cpu isn't the same thing as an idle cpu - although with background processes, is a cpu ever idle? It's possible to be doing something such as using Notepad or scrolling an already loaded web page and have SpeedStep throttle back the processor. The machine doesn't have to be idle, just lightly used.
Many people believe that using Power Options to configure a machine for maximum performance disables SpeedStep. There are numerous reports that this is not actually true, at least for Vista users. The safest and surest way to disable SpeedStep is to go into the bios and turn it off there. I'm going to try that and see what happens.
It really blows when manufacturers of systems running Intel Speedstep processors neglect to add the ability to disable speedstep in the Bios.....- Yes, that is bad news, but it is understandable on laptops. Laptop users are obsessed with how long the machine will run on one battery charge. They can't imagine why anybody would want to deliberately run down the battery fast!
Bill
