Custom Query (16363 matches)
Results (1129 - 1131 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2929 | fixed | BSOD on XP caused by VBoxNetFlt.sys driver => fixed in SVN | ||
| Description |
*
* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) 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 kernel debugger is available get stack backtrace. Arguments: Arg1: 00000000, memory referenced Arg2: 00000002, IRQL Arg3: 00000001, value 0 = read operation, 1 = write operation Arg4: b6c75193, address which referenced memory Debugging Details: WRITE_ADDRESS: 00000000 CURRENT_IRQL: 2 FAULTING_IP: VBoxNetFlt+4193 b6c75193 8902 mov dword ptr [edx],eax DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System TRAP_FRAME: 9f62fc88 -- (.trap 0xffffffff9f62fc88) ErrCode = 00000002 eax=00000000 ebx=00000000 ecx=89bc1160 edx=00000000 esi=89570414 edi=89570434 eip=b6c75193 esp=9f62fcfc ebp=9f62fd08 iopl=0 nv up ei ng nz ac pe cy cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297 VBoxNetFlt+0x4193: b6c75193 8902 mov dword ptr [edx],eax ds:0023:00000000=???????? Resetting default scope LAST_CONTROL_TRANSFER: from b6c75193 to 805446f0 STACK_TEXT: 9f62fc88 b6c75193 badb0d00 00000000 b705f841 nt!KiTrap0E+0x238 WARNING: Stack unwind information not available. Following frames may be wrong. 9f62fd08 b9c2012a 89570414 89570434 c00000bb VBoxNetFlt+0x4193 9f62fd30 b9c20362 89570434 895702e0 89bc1130 NDIS!ndisMSyncQueryInformationCompl ete+0x15e 9f62fd58 b9c1ca11 895702e0 89bc1130 89570434 NDIS!ndisMDoRequests+0x30c 9f62fd74 b9c203a6 895702e0 89570434 82c2d2a0 NDIS!ndisMRequest+0xfc 9f62fd98 b9c0dbaa 82c2d288 00000000 829d9958 NDIS!ndisMRundownRequests+0x32 9f62fdac 805cff70 82c2d290 00000000 00000000 NDIS!ndisWorkerThread+0x75 9f62fddc 805460ee b9c0db85 82c2d290 00000000 ntPspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 ntKiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetFlt+4193 b6c75193 8902 mov dword ptr [edx],eax SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: VBoxNetFlt+4193 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4948ccb9 FAILURE_BUCKET_ID: 0xD1_W_VBoxNetFlt+4193 BUCKET_ID: 0xD1_W_VBoxNetFlt+4193 Followup: MachineOwner |
|||
| #14122 | obsolete | BSOD on first run of VM, reboot, then working | ||
| Description |
Windows 8.1 64bit |
|||
| #7740 | obsolete | BSOD on guest when installing XP | ||
| Description |
Running VBox 3.2.10 r66523 on Ubuntu Maverick 64-bit (10.10) *). Host is Intel Core 2 Duo T9900 @3.06GHz. 8 GB host memory. Guest is Windows XP (32-bit), slipstreamed (with MS ServicePack) up to SP3. *) I observe same symptoms when running VBox on Win7 64-bit. I've had troubles installing XP Guest with SATA support without getting BSOD. The main problem for me was to A) find which SATA I could use B) what version of the driver and C) what product to select during installation. So after reading on the web I found A) Intel AHCI a.k.a Intel Matrix Storage Manager driver and C) use the ICH8M-E/M driver. However, VBox seems picky about which version of the SATA driver you pick. Hence: iaStor.sys version:
When installing all versions accepts the driver during the F6 phase and XP is capable of discovering the harddrive. However, the installation dies with BSOD when it is 32 minutes or so remaining. The BSOD has no message (no IRQL_xxx or similar), and the STOP is 0x000000F4 (0x00000003, ...) I have not experimented with using other variants like ICH9 or ICH10 SATA drivers. IMHO a notice should be available somewhere in docs/website to indicate which iaStor driver and version to use for XP Guest. |
|||

