VirtualBox

Opened 13 years ago

Closed 8 years ago

#9401 closed defect (obsolete)

IRQL_NOT_LESS_OR_EQUAL BSOD — at Version 12

Reported by: Bruce Williamson Owned by:
Component: guest additions Version: VirtualBox 4.1.0
Keywords: Cc:
Guest type: Windows Host type: Linux

Description (last modified by Frank Mehnert)

Upgraded to V4.1.0 Installed Oracle_VM_VirtualBox_Extension_Pack VM booted without a problem Upgraded Guest Additions to V4.1.0 VM fails to boot with the following error IRQL_NOT_LESS_OR_EQUAL

Change History (19)

by Bruce Williamson, 13 years ago

Attachment: IRQL_NOT_LESS_OR_EQUAL.jpeg added

BSOD

by Bruce Williamson, 13 years ago

Attachment: VBoxSVC.log added

VBoxSVC

by Bruce Williamson, 13 years ago

Attachment: VBox.log added

VBox

comment:1 by misha, 13 years ago

Could you attach a minidump for the crash?

by Bruce Williamson, 13 years ago

Attachment: Win-VM.xml added

comment:2 by Matt, 13 years ago

Not sure if this is the same or similar issue, but in ticket #9110 I tried installing 64-bit Windows 7 Professional with Service Pack 1 into a VirtualBox 4.1.0 guest and, though Windows setup completed without issue, any time I would try logging in or sometimes just before the login screen would appear the following IRQL_NOT_LESS_OR_EQUAL blue screen would occur:

Problem signature:
  Problem Event Name:	BlueScreen
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033

Additional information about the problem:
  BCCode:	a
  BCP1:	FFFFF683217FCF80
  BCP2:	0000000000000000
  BCP3:	0000000000000000
  BCP4:	FFFFF800026D6822
  OS Version:	6_1_7601
  Service Pack:	1_0
  Product:	256_1

In my case, this cannot be attributed to Guest Additions because it was a brand new Windows installation and I wasn't yet able to even log in to try installing the Additions. I will attach a minidump of this error.

by Matt, 13 years ago

Attachment: 081411-26878-01.dmp added

Before Windows 7 login screen, IRQL_NOT_LESS_OR_EQUAL minidump

by Bruce Williamson, 13 years ago

Attachment: BAD_POOL_CALLER.jpeg added

BAD_POOL_CALLER

by Bruce Williamson, 13 years ago

Attachment: VBox.2.log added

comment:3 by Bruce Williamson, 13 years ago

Core dump sent to Frank, subject: Ticket #9401 - Core Dump

@bacon, after the initial BSOD I booted into safe mode and uninstalled the Guest Additions and rebooted into normal mode but continued to receive the BSOD.

Now when I try to boot into safe mode I get a different BSOD details of which are above.

I've sent this additional core dump sent to Frank, subject: Ticket #9401 - Core Dump BAD_POOL_CALLER

comment:4 by Frank Mehnert, 13 years ago

aztrix, the core dumps do not make sense here as this is a problem only visible inside the guest, not on the host. From analyzing your core dump I saw that you forced the VM process to dump a core. But Misha was asking for a minidump from the guest.

comment:5 by Bruce Williamson, 13 years ago

so how do i get a minidump from the guest if i can't boot into it?

comment:6 by Bruce Williamson, 13 years ago

i'm not questioning your knowledge but according to:

http://www.virtualbox.org/newticket ...

If you want to report a crash on a Windows host, please attach a minidump if possible.

i'm running a win xp guest on a linux host.

i'm a little confused, please correct my understanding of the procedure so i can give you the right info first time ... hopefully :-)

comment:7 by Matt, 13 years ago

After my guest would blue screen during normal boot, I was able to boot using "Safe mode with networking" and copy the resulting minidump to a network share. Since you're not able to boot into safe mode, either, can you boot some kind of LiveCD with NTFS support and copy the minidump from the %WinDir%\minidump directory to a network share? You could also try attaching the system disk to a bootable guest to access the minidump.

in reply to:  5 comment:8 by misha, 13 years ago

Replying to aztrix:

so how do i get a minidump from the guest if i can't boot into it?

You can attach the vdi image to another VM (as a secondary disk), boot that VM and access that disk data from there

in reply to:  6 comment:9 by misha, 13 years ago

Replying to aztrix:

i'm a little confused, please correct my understanding of the procedure so i can give you the right info first time ... hopefully :-)

Unless you changed the defaults, the minidump should be in %windir%\Minudump directory.

comment:10 by Bruce Williamson, 13 years ago

Minudump directory doesn't exist when I log into win xp natively.

comment:11 by Frank Mehnert, 12 years ago

Wild guess: Does changing the chipset type from ICH9 to PIIX3 change anything?

comment:12 by Frank Mehnert, 8 years ago

Description: modified (diff)
Resolution: obsolete
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use