Are you seeing a BSOD after an idle period?
- I originally posted this here: http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/b52b2926-0369-4cb6-bfb1-603b7f25ed14
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.
It is interesting to note that a lid close action on Windows Server 2008 R2 initiates - or ties 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 actually is enabled, it does appear there is some type of cpu throttling going on. 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.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
- We believe this is a known issue with the beta release (though caused by power management - and not by Antivirus).
Cheers,
Benjamin Armstrong
============================
Windows Virtualization
Senior Lead Program Manager
This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.- Marked As Answer byJohn Paul CookMVPWednesday, February 25, 2009 5:14 PM
- We expect that this issue will be resolved with post-beta builds (ie, Windows Server 2008 R2 RC). However, I don't have a date that I can share.
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byMike Sterling [MSFT]MSFT, ProprietárioTuesday, April 14, 2009 8:11 PM
All Replies
- We believe this is a known issue with the beta release (though caused by power management - and not by Antivirus).
Cheers,
Benjamin Armstrong
============================
Windows Virtualization
Senior Lead Program Manager
This posting is provided AS IS with no warranties, and confers no rights. You assume all risk for your use.- Marked As Answer byJohn Paul CookMVPWednesday, February 25, 2009 5:14 PM
- Are there any workarounds to avoid this BSOD with the Beta? I've tried switching to High Performance power option and also disabling SpeedStep. Neither seems to work and BSOD happens a few minutes after working with my Hyper-V machine. I've tried both clean build native Hyper-V VHDs and ones ported from VPC2007SP1 - both cause BSOD. I don't boot any Hyper-V machines I can happily work with no issue.
If I revert back to Win2008SP1 will this issue go away? - Hi,
Same here. BSOD. I had Nod32 installed, but uninstalled it, and am having same issues + very slow performance.
I wanted to give R2 a chance, but I'm having a hard time accepting the lack of technical info on this issue.
My next step here is to disable SpeedStep in BIOS, after that, revert to 2008SP1.
ANYONE have any ideas?
MMayo - Okay, I disabled SpeedStep in BIOS, don't have anti-virus (Server 2008 doesn't like anti-virus???)... Can't afford any more trials with R2...
Good-bye R2 D2!!
Server 2008 SP1 will you please take me back??
MMayo - Anyone find any fixes for this. I recently installed R2 on my laptop recently for some testing and to use Hyper-V for testing and I am having the same issue. One of my other collegues is having the same issue, and I was hoping it was a hardware issue with his mchine. Someone post if you could if there has been any update otherwise back to Server 2008 sp1 :(
Thanks all - We expect that this issue will be resolved with post-beta builds (ie, Windows Server 2008 R2 RC). However, I don't have a date that I can share.
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byMike Sterling [MSFT]MSFT, ProprietárioTuesday, April 14, 2009 8:11 PM
- I had the same problem about once a day (for 2 weeks) on my brand new HP desktop with the lower powered P7. Unfortunately, I am a total idiot when it comes to computers...the machine would freeze at times and I didn't know you could hold the power button down for 5 seconds and get it to turn off, so when it also gave me this error message and then froze, I didn't know what else to do except disconnect the power! Eventually HP remote diagnosed a problem with the mother board, but after numerous freezes and power disconnects I apparently had corrupted Vista beyond self-repair - actually the tech tried the self repair thing, and when it finished it said it couldn't repair the machine...but then it wouldn't start at all!!!
It pisses me off to no end that MSFT ships such buggy ____, and that I was stupid enough to order a Vista machine...I figured that they would have the bugs out by now - My Error there. Tried to save a bit of money and bought a MSFT PC instead of an Apple like I should have. Am sending machine back to HP and getting my money back...will spend a bit more this time and get the Apple. You guys are amazing, and still have trouble...what chance do computer dopes have with PCs (?)...in retrospect, guess I should have bought one of the few machines I could still get with XP. I have had it with Microsoft junk....maybe if the machine came with a big red sticker that said: "Expect to have problems and actual freezes....if machine freezes DON'T disconnect power, instead hold the power button down for 5 seconds and the machine will shut down properly. Or maybe they just shouldn't be allowed to sell MSFT products to dummies.
