Host Win7, Guest Any, BSOD IRQL_NOT_LESS_OR_EQUAL

[MarionCobretti]

I am running Win7 x86_64 and have been experiencing BSOD on the host with IRQL_NOT_LESS_OR_EQUAL errors. Most other information on the BSOD seems useless, no driver in 4th section and memory address is x0000000000000. I have found that it is directly related to running the vm disks with SATA controller. When I switch them to IDE I dont have the any BSOD. However the performance hit is painful.

Host layout:
Dual Quad Xeon/32GB FSB ECC
SATAII System disk
SATAIII Software Mirror for VMs


I have seen this issue existed in the past with older version while researching it on the web. I am running current (4.3.10r93012). This problem has recently shown up as I have been running VBox for over a year without any issue on this machine and build (Maybe since build 4.3.8/4.3.9). Next step?

Thanks,
Marion-

[socratis]

directly related to running the vm disks with SATA controller. When I switch them to IDE I don't have the any BSOD. However the performance hit is painful.

a) SATA or IDE in the guest should not BSOD the host.
b) SATA or IDE in the guest does not affect guest performance.
c) Minimum information needed for assistance.

[MarionCobretti]

a) SATA or IDE in the guest should not BSOD the host.

Should not... but does appear to be.

b) SATA or IDE in the guest does not affect guest performance.

Strange as I see an immediate reduction in disk IO with the guest vm using IDE over SATA. I will take your word for that though contrary to what I am seeing.

With a single VM running and nothing else using the sata3 mirror, with guest selected SATA, i see 40-55 MB/s Avg under load on host disk. (This will run for an indefinite amount of time until BSOD)
With a single VM running and nothing else using the sata3 mirror, with guest selected IDE, i see 8-30 MB/s Avg under load on host disk. (Never BSOD)

Those benchmarks were on an Ubuntu 12.04 LTS Updated with Guest Extensions.

Minimum information needed for assistance.

I am running current (4.3.10r93012).

and current Guest Extensions and Additions.

I am running Win7 x86_64 and have been experiencing BSOD on the host

I will add that it is Pro version, and Guest OS doesnt matter. It happens with Win7 x86_64 Pro, Win7 x86_64 Ent, Ubuntu 12.04 x86/x86_64, FreeBSD v6.4, FreeBSD v9.1, Centos 6.5 x86/x86_64, Piston 2.x/3.0 x86_64, Whonix Gateway/Workstation current.

Which Guest OS logs would you like, as it is indeterminate of the Guest OS. The only thing I will say is that if I am running more with SATA mode, it will BSOD faster. So which Guest OS logs should i produce? I would argue that the issue would appear to be with how VBox is handling the Host OS (win7x64) SATA driver.

The machine has not BSOD without VBox running with at least one VM in SATA mode.

i have not yet been asked to provide guest settings nor the additional opt'ed information.

Thanks,
marion-

[MarionCobretti]

Code: Select all

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff880116c0000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032ddc40, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003513100
GetUlongFromAddress: unable to read from fffff800035131c0
 fffff880116c0000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!RtlCopyMemoryNonTemporal+40
fffff800`032ddc40 4c8b0c11        mov     r9,qword ptr [rcx+rdx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  VirtualBox.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF88003122FB0

TRAP_FRAME:  fffff880031226a0 -- (.trap 0xfffff880031226a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000001000 rbx=0000000000000000 rcx=fffff880065db000
rdx=000000000b0e5000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032ddc40 rsp=fffff88003122838 rbp=0000000000000002
 r8=0000000000000000  r9=0000000000000000 r10=fffffa801a2844d0
r11=fffff88003122820 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!RtlCopyMemoryNonTemporal+0x40:
fffff800`032ddc40 4c8b0c11        mov     r9,qword ptr [rcx+rdx] ds:fffff880`116c0000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032db169 to fffff800032dbbc0

STACK_TEXT:  
fffff880`03122558 fffff800`032db169 : 00000000`0000000a fffff880`116c0000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03122560 fffff800`032d9de0 : 00000000`00000000 fffffa80`1a2a01b0 fffffa80`1a2866a8 fffff880`116c0000 : nt!KiBugCheckDispatch+0x69
fffff880`031226a0 fffff800`032ddc40 : fffff800`0321fe08 fffff880`116c0000 00000000`00000002 fffffa80`1d4ded30 : nt!KiPageFault+0x260
fffff880`03122838 fffff800`0321fe08 : fffff880`116c0000 00000000`00000002 fffffa80`1d4ded30 fffff880`00d99d40 : nt!RtlCopyMemoryNonTemporal+0x40
fffff880`03122840 fffff800`0321f593 : fffffa80`1a2844d0 fffffa80`1a284400 00000000`00000000 00000000`00000000 : hal!HalpDmaSyncMapBuffers+0x1b0
fffff880`031228f0 fffff800`032224fb : fffffa80`24481c68 fffffa80`1a2844d0 fffffa80`1d4ded30 00000000`00000001 : hal!HalpDmaMapScatterTransfer+0xa3
fffff880`03122940 fffff800`03222472 : fffffa80`24481c68 fffffa80`24481c60 00000000`00004000 00000000`00000000 : hal!HalpMapTransfer+0x7b
fffff880`031229d0 fffff800`0322194f : 00000000`00000000 fffff800`0321efb9 00000000`00000000 00000000`00000004 : hal!IoMapTransfer+0x8e
fffff880`03122a10 fffff800`0322213d : fffffa80`1a278520 fffffa80`1a2844d0 fffffa80`1a284401 00000000`00000000 : hal!HalpAllocateAdapterCallback+0xc7
fffff880`03122ab0 fffff800`0322171f : fffffa80`24481c20 00000000`00004000 fffffa80`1a2844d0 fffffa80`1d4ded30 : hal!HalAllocateAdapterChannel+0x101
fffff880`03122af0 fffff880`00e3f0d3 : fffffa80`24481b80 fffff880`00e3f12c fffffa80`000000a0 fffffa80`1a2844d0 : hal!HalBuildScatterGatherList+0x2f3
fffff880`03122b60 fffff880`010dcb6f : fffffa80`24481b80 fffffa80`1a2a01b0 fffffa80`1a2851a0 fffffa80`24481b80 : PCIIDEX!BmSetup+0x6b
fffff880`03122bc0 fffff880`010db81f : fffffa80`1a286500 fffffa80`1a2a01b0 fffffa80`1a286500 fffffa80`1a2851a0 : ataport!IdeDispatchChannelRequest+0xef
fffff880`03122bf0 fffff880`010db352 : 00000000`00000001 fffffa80`24481b80 00000000`00000001 fffffa80`24481b80 : ataport!IdeStartChannelRequest+0x113
fffff880`03122c70 fffff880`010dd5b6 : fffffa80`1a2851a0 00000000`00000000 fffffa80`1a2a01b0 fffffa80`2280c6f0 : ataport!IdeStartNextDeviceRequest+0x18e
fffff880`03122d10 fffff880`010dd120 : fffffa80`1a2851a0 00000000`00000000 fffffa80`1a2851a0 fffffa80`2280c6f0 : ataport!IdeProcessCompletedRequests+0x26a
fffff880`03122e40 fffff800`032e630c : fffff880`009e4180 fffffa80`0542625f fffffa80`1a285050 fffffa80`1a285118 : ataport!IdePortCompletionDpc+0x1a8
fffff880`03122f00 fffff800`032ded15 : 00000000`00000000 fffffa80`20af4060 00000000`00000000 fffff880`010dcf78 : nt!KiRetireDpcList+0x1bc
fffff880`03122fb0 fffff800`032deb2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0a42c780 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
PCIIDEX!BmSetup+6b
fffff880`00e3f0d3 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  b

SYMBOL_NAME:  PCIIDEX!BmSetup+6b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: PCIIDEX

IMAGE_NAME:  PCIIDEX.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc114

IMAGE_VERSION:  6.1.7600.16385

FAILURE_BUCKET_ID:  X64_0xA_PCIIDEX!BmSetup+6b

BUCKET_ID:  X64_0xA_PCIIDEX!BmSetup+6b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xa_pciidex!bmsetup+6b

FAILURE_ID_HASH:  {35170e54-8a46-486d-7aa5-6e5a52856b85}

Followup: MachineOwner
---------

PROCESS_NAME: VirtualBox.exe

It looks to me like a conflict with PCIIDEX.SYS that VirtualBox is triggering/causing. So this isn't particularly a VirtualBox problem, its a Virtualization problem that VirtualBox/Guests are triggering with my windows 7 x64 drivers.


*UPDATE* I have run

Code: Select all

sfc /scannow

from an admin prompt which claims to have cleaned up some issues with the disk drivers. There was also a suggestion to check the BIOS setting of SATA AHCI being enabled. Mine in fact was disabled for some reason and neither was SATA RAID mode which also pushes AHCI. This means that I was most likely running in SATA Legacy though no option exists for it, with the others disabled I guess it implies legacy. I did not enable the RAID setting even to use them as JBOD because the RAID Controller doesnt support the size disks that I have and was the reason I initially disabled that before.

I will post later today to see if i have BSOD and update with status.

**UPDATE**
So far so good. Been 10 hours and havent seen the BSOD. I am going to call this a success... hopefully not mistakenly.


Anyone hit this before?