VirtualBox

Ticket #11274 (new defect)

Opened 17 months ago

Last modified 5 weeks ago

BSOD when Win7 goes to sleep or hibernation

Reported by: CaptainFlint Owned by:
Priority: blocker Component: network
Version: VirtualBox 4.2.4 Keywords:
Cc: Guest type: all
Host type: Windows

Description

Host OS: Windows 7 Pro SP1

After I install VirtualBox 4.2.4, sending the computer into Sleep or Hibernate often ends up with BSOD 0x9F (DRIVER_POWER_STATE_FAILURE). Analysing the crash dump with WinDbg indicates the network card driver in the blocked IRP stack. At first I thought it was a faulty Realtek driver, but after I deinstalled VirtualBox the problem disappeared completely. I also tried VB 4.2.2 for two weeks, and did not get any problem with this version. Only after I upgraded again to 4.2.4, the second attempt to hibernate the system gave the same BSOD again.

Attached is the WinDbg log of the crash dump with !analyze -v and !irp <blocked_IRP> commands executed.

Attachments

windbg-bsod-analysis.txt Download (4.6 KB) - added by CaptainFlint 17 months ago.
WinDbg analysis log
vista_dumps_and_ndis.rar Download (488.7 KB) - added by CaptainFlint 13 months ago.
BSOD minidumps from Vista plus ndis driver and symbols

Change History

Changed 17 months ago by CaptainFlint

WinDbg analysis log

comment:1 follow-up: ↓ 2 Changed 17 months ago by frank

Looks like a duplicate of #10021. Could you check the test build there?

comment:2 in reply to: ↑ 1 Changed 16 months ago by CaptainFlint

Replying to frank:

Looks like a duplicate of #10021. Could you check the test build there?

Hm… In my case it's not USB but network… But sure, I'll try that build.

PS: It seems my conclusion about 4.2.2 was incorrect, I got the same BSOD while having 4.2.2 installed, so it's reproduced not only with 4.2.4.

comment:3 Changed 16 months ago by CaptainFlint

Unfortunately, it did not fix the problem. I got the same BSOD when trying to hibernate computer with VB 4.2.5-82251 installed.

comment:4 follow-up: ↓ 5 Changed 16 months ago by mhanor

Have you tried updating your ethernet nic drivers by going to www.realtek.com ?

comment:5 in reply to: ↑ 4 Changed 16 months ago by CaptainFlint

Replying to mhanor:

Have you tried updating your ethernet nic drivers by going to www.realtek.com ?

Yes, sure. That was first thing I tried when I met this problem, because nothing pointed to VirtualBox. Unfortunately, the problem persisted with all driver versions I tried (including the very first version for my chip, the last version available, and the version published on the ASUS web-site — my motherboard manufacturer), so I had to search for other possible sources of the crashes.

comment:6 Changed 15 months ago by CaptainFlint

I found one more prerequisite that seems to be important: shortly before going into sleep/hibernation a significant load should be applied for network card. Unfortunately, I don't know exactly whether it's the amount of data or specific type of packets that causes the problem...

My typical scenario is the following: during the day qBittorrent is constantly running on my computer, actively seeding many files. In the evening I exit qBittorrent and then send the computer into hibernation. If I don't wait for at least several minutes before hibernation, the crash is ~99% reproducible. If I give the computer about half an hour of "rest" between qBittorrent exiting and going into hibernation, the crash quite rarely happens (though sometimes it still does, so there are probably other factors, or, maybe, something else generates traffic of the type and/or volume enough for triggering the problem).

If I deinstall VirtualBox and try the same scenario, I never get BSOD, even if I don't wait at all and send the computer into hibernation immediately after exiting qBittorrent.

PS: I'm testing VB 4.2.6 since it was released.

comment:7 follow-up: ↓ 8 Changed 15 months ago by mhanor

If you search the Internet, you'll find that this problem (BSOD 0x9F) was reported many times in the past, by others, many even relating to the Rt64win7 driver, without any mention of VirtualBox. In some threads, the driver with the blocked IRP, kept changing after each driver update/disabled device driver. At least, post your full system specs, attach some BSOD mindumps and check your system RAM with memtest, maybe even swapping the RAM DIMMs between them.

comment:8 in reply to: ↑ 7 Changed 15 months ago by CaptainFlint

Replying to mhanor:

If you search the Internet, you'll find that this problem (BSOD 0x9F) was reported many times in the past, by others, many even relating to the Rt64win7 driver, without any mention of VirtualBox.

At first, I too didn't know VirtualBox had something to do with it, since nothing pointed to it. Luckily, I had the crash dumps and by the timestamp of the first one I searched for the applications installed just before the crashes started to happen. It was VirtualBox and PerfectDisk. I deinstalled both, and crashes stopped. I installed VirtualBox back, and crashes returned. That's plain facts.

At the moment I have both applications deinstalled (for testing whether crashes were reproducible with the same high network load). I'll try to install PerfectDisk back without VB and see what happens.

In some threads, the driver with the blocked IRP, kept changing after each driver update/disabled device driver.

Not in my case. I analyzed all the dumps, and they all looked identical, otherwise I would attach all the analyses, of course.

At least, post your full system specs, attach some BSOD mindumps and check your system RAM with memtest, maybe even swapping the RAM DIMMs between them.

RAM is already tested with three different tools (memtest including), not a glitch. Unfortunately, the dumps are already deleted, but I'll generate some more of them for attaching. My system specs are:

MB: ASUS Sabertooth 990FX
CPU: AMD FX 8350
RAM: 4 x 4096 MB Geil Black Dragon GB316GB1600C9QC
HDD: System: SSD Plextor PX-256M3; additional: WD 2002FAEX (2 TB), WD 1001FALS (1 TB), WD 5000AAKS (500 GB)
Power supply: Seasonic X660 Gold
OS: Windows 7 Pro x64 SP1, all updates installed.
BIOS and SSD firmware are the latest.

comment:9 Changed 13 months ago by anshul makkar

Please share detailed memory dump and , if possible, with checked version of ndis.sys. Its not reproducible in our lab.

comment:10 Changed 13 months ago by CaptainFlint

Sorry for the delay. Unfortunately, I've had no access to the computer where all this happened. As soon as I get to it I'll try to collect the necessary information.

In the meantime, the same problem occurred also twice on another computer with completely different environment: notebook with Windows Vista Business. It too is no longer available for reproducing the problem (the OS was reinstalled to Win7, and till now the reported BSOD did not occur), but luckily I have the files from the old disk, so I could get the two minidumps from these crashes. I attach the archive with those two dumps, and also put there the ndis.sys driver from that Vista system and the corresponding ndis.pdb. Of course, it's not the checked version, but this is all I have on hands ATM…

Changed 13 months ago by CaptainFlint

BSOD minidumps from Vista plus ndis driver and symbols

comment:11 follow-up: ↓ 14 Changed 13 months ago by anshul makkar

Thanks for the dump.

Please can you upload full memory dump with checked version of ndis.sys .

comment:12 Changed 12 months ago by anshul makkar

Is, it possible to try out the test build that I can share ?

Thanks Anshul Makkar

comment:13 Changed 12 months ago by CaptainFlint

Sorry, I still have no access to the problematic machine. :-( In a month or so, I hope, I will eventually get it and then I'll be able to collect crash dumps and check test builds.

BTW, how do I get a checked version of ndis.sys? Do I need to extract it from a checked image of Windows distribution, or is it available somewhere separately?

comment:14 in reply to: ↑ 11 Changed 7 months ago by CaptainFlint

Replying to anshul makkar:

Please can you upload full memory dump with checked version of ndis.sys .

I have finally got my computer back. Sorry it took so long…
Now I updated the Realtek drivers to the latest version and installed VB 4.2.18. Still, Windows gives BSODs on Sleep/Hibernate. I replaced ndis.sys with the checked version and created the kernel dump, its size is ~170 Mb (archvied). (Tell me if full dump is really required — I have 16 Gb RAM, so it may be very large.) Where can I upload it? I'm not sure it doesn't contain sensitive data and don't want to publish it in the open.

P.S. In addition to the reported kind of crash, I've got another BSODs caused by VBoxNetAdp driver. It's not clear for me if this is caused by the same problem or not. Should I create a new ticket or add information to this one?

comment:15 Changed 6 months ago by bobs

This could be a similar problem to what I'm seeing - I've just updated #11608 with a memory dump using a checked build of ndis.sys, in the hope this will help solve it.

comment:16 Changed 5 weeks ago by SgtPooki

What's funny is I was researching this issue months ago, regarding my Asus G75V, and there are no real definitive solutions. I also attempted to update my drivers to no avail.

I haven't hibernated since, but I am definitely going to try to uninstall virtualbox and see if that solves the issue.

comment:17 Changed 5 weeks ago by CaptainFlint

At the moment, when I need to hibernate the computer, I go to Device Manager and disable the following devices:

(and enable them back after waking, of course). Sure, not so handy as simply go to hibernate, but in most cases better than shutdown. Doing this for several months already, no BSODs. If I leave any of the listed devices enabled, I get BSOD (not always, but quite often).

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use