#7601 closed defect (fixed)
BSOD 0x0000007F in VBoxNetFlt.sys UNEXPECTED_KERNEL_MODE_TRAP
回報者: | dumghen | 負責人: | |
---|---|---|---|
元件: | network/hostif | 版本: | VirtualBox 3.2.10 |
關鍵字: | 副本: | ||
Guest type: | Linux | Host type: | Windows |
描述 (由 作最後更新)
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80042000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from a7847ec3 to 8050684f STACK_TEXT: a63b3000 a7847ec3 8a92e52c 8a92e000 8a879740 nt!MmBuildMdlForNonPagedPool+0x5 a63b3018 a7847ed9 8a879700 8a92e000 00000000 tcpip!MdppBuildNextMdl+0x68 a63b3038 a784688c 8a879700 a63b306c a63b3074 tcpip!MdpAllocateAtDpcLevel+0x81 a63b3048 a7846caf 8a85d768 a63b306c 0000000e tcpip!GetARPBufferAtDpcLevel+0x2c a63b3074 a7846916 8a85d768 89e5d1a0 89ef2918 tcpip!ARPSendData+0x85 a63b30a0 a784665a 8a85d768 a63b3002 00000001 tcpip!ARPTransmit+0x193 a63b30d0 a784679f 8a17ad50 4900040a 89e5d1a0 tcpip!SendIPPacket+0x193 a63b321c a784763b a7884b98 00000000 8aaca180 tcpip!IPTransmit+0x289e a63b3268 a784a058 02b62008 00000000 00000002 tcpip!SendACK+0x2d8 a63b3288 a7843a0e 00000002 00000002 a63b32b4 tcpip!ProcessPerCpuTCBDelayQ+0xc6 a63b32bc a7843955 00000002 a7843901 a78433d6 tcpip!ProcessTCBDelayQ+0xc4 a63b32c8 a78433d6 00000000 8a9dd130 a78437f8 tcpip!TCPRcvComplete+0x20 a63b32d4 a78437f8 b9e3cc40 8a85d768 c000009a tcpip!IPRcvComplete+0x21 a63b32d8 b9e3cc40 8a85d768 c000009a 8a9dd130 tcpip!ARPRcvComplete+0x5 WARNING: Stack unwind information not available. Following frames may be wrong. a63b3328 b8f0945c c000009a a63b334c 00000001 NDIS+0x22c40 a63b3354 b9e3cef2 018083e0 89df6e18 89f63760 psched!ClReceiveIndication+0xa0 a63b33bc b8ea48f0 c000009a a63b33d8 00000001 NDIS+0x22ef2 a63b3484 b8ea4d3d 89df6e18 00000001 8872cf10 VBoxNetFlt+0x48f0 a63b34a0 b8ea5263 89f636d0 8aa96838 89f63668 VBoxNetFlt+0x4d3d a63b34c0 b9e3cef2 018136fc 89f636d0 89f63760 VBoxNetFlt+0x5263 a63b3528 b9e2fed4 c000009a a63b3548 00000001 NDIS+0x22ef2 a63b3550 b9e1a99d 00000001 8a8136fc 89e5dda8 NDIS+0x15ed4 a63b356c b8ea61f4 8a427cd0 8872cf10 00000001 NDIS+0x99d a63b3584 b8ea62b7 a0f60001 89e5dd58 00000103 VBoxNetFlt+0x61f4 a63b35a4 b9e1cf87 00000000 a63b35d8 00000001 VBoxNetFlt+0x62b7 a63b35cc b8f0a528 8a883f40 89e5dda8 89e5dd40 NDIS+0x2f87 a63b3608 b9e1a985 8a8083e0 89e5dda8 00000002 psched!MpSend+0x706 a63b3630 a7846d40 8a45b450 89e5dda8 8a85d768 NDIS+0x985 a63b3658 a7846916 8a85d768 89e5dda8 89819890 tcpip!ARPSendData+0x198 a63b3684 a784665a 8a85d768 a63b3602 00000001 tcpip!ARPTransmit+0x193 a63b36b4 a784679f 8a17ad50 9600040a 89e5dda8 tcpip!SendIPPacket+0x193 a63b3800 a784763b a7884b98 00000000 8aaca2e0 tcpip!IPTransmit+0x289e a63b384c a785062a 02e0b008 8abec008 8a637018 tcpip!SendACK+0x2d8 a63b38c8 a7844ef5 8a88c818 9a00040a 9600040a tcpip!TCPRcv+0x17a3 a63b3928 a7844b19 00000020 8a88c818 a78470b6 tcpip!DeliverToUser+0x18e a63b39a4 a7844836 a78848f0 8a88c818 8a637018 tcpip!DeliverToUserEx+0x95e a63b3a5c a7843928 8a88c818 8a63702c 0000001a tcpip!IPRcvPacket+0x6cb a63b3a9c a7843853 00000000 8929d468 8a63700a tcpip!ARPRcvIndicationNew+0x149 a63b3ad8 b9e3cb9f 8a85d768 00000000 b8f0eb40 tcpip!ARPRcvPacket+0x68 a63b3b2c b8f0901d 00890f88 892fc650 00000004 NDIS+0x22b9f a63b3b40 b8f091b4 8a9dd130 892fc650 00000004 psched!PsFlushReceiveQueue+0x15 a63b3b64 b8f093e9 8a8083e8 00000000 8a9dd130 psched!PsEnqueueReceivePacket+0xda a63b3b90 b9e3cef2 8a8083e0 89df6658 89b4ae40 psched!ClReceiveIndication+0x2d a63b3bf8 b8ea48f0 c000009a a63b3c14 00000008 NDIS+0x22ef2 a63b3cc0 b8ea4d3d 89df6658 00000001 8872cd20 VBoxNetFlt+0x48f0 a63b3cdc b8ea5263 89b4adb0 8aa96838 89b4ad48 VBoxNetFlt+0x4d3d a63b3cfc b9e3cef2 018136fc 89b4adb0 89b4ae40 VBoxNetFlt+0x5263 a63b3d64 b9e2fed4 c000009a a63b3d84 00000001 NDIS+0x22ef2 a63b3d8c b9e1a99d 00000001 8a8136fc 888ed3d0 NDIS+0x15ed4 a63b3da8 b8ea61f4 8a427cd0 8872cd20 00000001 NDIS+0x99d a63b3dc0 b8ea62b7 a0f50001 888ed380 00000103 VBoxNetFlt+0x61f4 a63b3de0 b9e1cf87 00000000 a63b3e14 00000001 VBoxNetFlt+0x62b7 a63b3e08 b8f0a528 8a883f40 888ed3d0 888ed368 NDIS+0x2f87 a63b3e44 b9e1a985 8a8083e0 888ed3d0 00000002 psched!MpSend+0x706 a63b3e6c a7846d40 8a45b450 888ed3d0 8a85d768 NDIS+0x985 a63b3e94 a7846916 8a85d768 888ed3d0 8a3aa348 tcpip!ARPSendData+0x198 a63b3ec0 a784665a 8a85d768 a63b3f02 00000001 tcpip!ARPTransmit+0x193 a63b3ef0 a784679f 8a17ad50 c300040a 888ed3d0 tcpip!SendIPPacket+0x193 a63b403c 00000000 00000000 00000000 00000000 tcpip!IPTransmit+0x289e STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetFlt+48f0 b8ea48f0 ?? ??? SYMBOL_STACK_INDEX: 11 SYMBOL_NAME: VBoxNetFlt+48f0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4caf235e FAILURE_BUCKET_ID: 0x7f_8_VBoxNetFlt+48f0 BUCKET_ID: 0x7f_8_VBoxNetFlt+48f0 Followup: MachineOwner
Reproduction: Nothing special, no special command, just a random BSOD when host is in locked screen state. Host: Windows XP SP3 Guest: CentOS (Linux version 2.6.18-194.17.1.el5 (mockbuild@…) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Wed Sep 29 12:51:33 EDT 2010)
附加檔案 (13)
更動歷史 (65)
14 年 前 由 編輯
附檔: | 新增 Mini101810-01.dmp |
---|
comment:3 14 年 前 由 編輯
UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80042000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ GetContextState failed, 0x80070026 Unable to read selector for PCR for processor 1 GetContextState failed, 0x80070026 Unable to read selector for PCR for processor 2 GetContextState failed, 0x80070026 Unable to read selector for PCR for processor 3 GetContextState failed, 0x80070026 Unable to read selector for PCR for processor 1 GetContextState failed, 0x80070026 Unable to read selector for PCR for processor 2 GetContextState failed, 0x80070026 Unable to read selector for PCR for processor 3 WARNING: Process directory table base BD300880 doesn't match CR3 00314000 Unable to get PEB pointer WARNING: Process directory table base BD300880 doesn't match CR3 00314000 Unable to get PEB pointer BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=89e5de1e ebx=00000028 ecx=00000028 edx=8a0b3600 esi=89e5de1e edi=89e5de1e eip=a7b105ad esp=a6346000 ebp=a6346084 iopl=0 nv up ei ng nz ac po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292 tcpip!IPRcvPacket+0xd: a7b105ad 57 push edi Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from a7b0f928 to a7b105ad STACK_TEXT: a6346084 a7b0f928 8aa131d0 89e5de1e 00000028 tcpip!IPRcvPacket+0xd a63460c4 a7b146ef 00000000 89e5dd80 89e5de10 tcpip!ARPRcvIndicationNew+0x149 a63460f4 b9e3cef2 8a0b35b8 89e5dd80 89e5de10 tcpip!ARPRcv+0x42 WARNING: Stack unwind information not available. Following frames may be wrong. a634615c b904545c c000009a a6346180 00000001 NDIS+0x22ef2 a6346188 b9e3cef2 014e3c50 89206f10 89e5de10 psched!ClReceiveIndication+0xa0 a63461f0 b8f408e2 c000009a a6346210 00000001 NDIS+0x22ef2 a63462bc b8f40d0c 89206f10 00000001 00000000 VBoxNetFlt+0x48e2 a63462d4 b8f41231 89e5dd80 8aa9f130 89e5dd18 VBoxNetFlt+0x4d0c a63462f4 b9e3cef2 014e7bcc 89e5dd80 89e5de10 VBoxNetFlt+0x5231 a634635c b9e2fed4 c000009a a634637c 00000001 NDIS+0x22ef2 a6346384 b9e1a99d 00000001 8a4e7bcc 89e37ec0 NDIS+0x15ed4 a63463a0 b8f421a4 8a4e7a08 89e26a38 00000001 NDIS+0x99d a63463b8 b8f42267 26700001 89e37e70 00000103 VBoxNetFlt+0x61a4 a63463d8 b9e1cf87 00000000 a634640c 00000001 VBoxNetFlt+0x6267 a6346400 b9046528 8a4e0c78 89e37ec0 89e37e58 NDIS+0x2f87 a634643c b9e1a985 8a4e3c50 89e37ec0 00000002 psched!MpSend+0x706 a6346464 a7b12d40 8a1ea1d0 89e37ec0 8a0b35b8 NDIS+0x985 a634648c a7b12916 8a0b35b8 89e37ec0 88e58d48 tcpip!ARPSendData+0x198 a63464b8 a7b1265a 8a0b35b8 a6346402 00000001 tcpip!ARPTransmit+0x193 a63464e8 a7b1279f 8a0a58c8 c700040a 89e37ec0 tcpip!SendIPPacket+0x193 a6346634 a7b1363b a7b50b98 00000000 891a5910 tcpip!IPTransmit+0x289e a6346680 a7b16058 02254ce8 00000000 00000003 tcpip!SendACK+0x2d8 a63466a0 a7b0fa0e 00000002 00000002 a63466cc tcpip!ProcessPerCpuTCBDelayQ+0xc6 a63466d4 a7b0f955 00000002 a7b0f901 a7b0f3d6 tcpip!ProcessTCBDelayQ+0xc4 a63466e0 a7b0f3d6 00000000 8aa33130 a7b0f7f8 tcpip!TCPRcvComplete+0x20 a63466ec a7b0f7f8 b9e3cc40 8a0b35b8 c000009a tcpip!IPRcvComplete+0x21 a63466f0 b9e3cc40 8a0b35b8 c000009a 8aa33130 tcpip!ARPRcvComplete+0x5 a6346740 b904545c c000009a a6346764 00000001 NDIS+0x22c40 a634676c b9e3cef2 014e3c50 89206b30 89eefdb0 psched!ClReceiveIndication+0xa0 a63467d4 b8f408e2 c000009a a63467f4 00000001 NDIS+0x22ef2 a63468a0 b8f40d0c 89206b30 00000001 00000000 VBoxNetFlt+0x48e2 a63468b8 b8f41231 89eefd20 8aa9f130 89eefcb8 VBoxNetFlt+0x4d0c a63468d8 b9e3cef2 014e7bcc 89eefd20 89eefdb0 VBoxNetFlt+0x5231 a6346940 b9e2fed4 c000009a a6346960 00000001 NDIS+0x22ef2 a6346968 b9e1a99d 00000001 8a4e7bcc 89e37718 NDIS+0x15ed4 a6346984 b8f421a4 8a4e7a08 89e26b30 00000001 NDIS+0x99d a634699c b8f42267 266f0001 89e376c8 00000103 VBoxNetFlt+0x61a4 a63469bc b9e1cf87 00000000 a63469f0 00000001 VBoxNetFlt+0x6267 a63469e4 b9046528 8a4e0c78 89e37718 89e376b0 NDIS+0x2f87 a6346a20 b9e1a985 8a4e3c50 89e37718 00000002 psched!MpSend+0x706 a6346a48 a7b12d40 8a1ea1d0 89e37718 8a0b35b8 NDIS+0x985 a6346a70 a7b12916 8a0b35b8 89e37718 88eda2f0 tcpip!ARPSendData+0x198 a6346a9c a7b1265a 8a0b35b8 a6346a02 00000001 tcpip!ARPTransmit+0x193 a6346acc a7b1279f 8a0a58c8 6f00040a 89e37718 tcpip!SendIPPacket+0x193 a6346c18 a7b1363b a7b50b98 00000000 891a5650 tcpip!IPTransmit+0x289e a6346c64 a7b16058 02c7e838 00000000 00000000 tcpip!SendACK+0x2d8 a6346c84 a7b0fa0e 00000002 00000002 a6346cb0 tcpip!ProcessPerCpuTCBDelayQ+0xc6 a6346cb8 a7b0f955 00000002 a7b0f901 a7b0f3d6 tcpip!ProcessTCBDelayQ+0xc4 a6346cc4 a7b0f3d6 00000000 8aa33130 a7b0f7f8 tcpip!TCPRcvComplete+0x20 a6346cd0 a7b0f7f8 b9e3cc40 8a0b35b8 c000009a tcpip!IPRcvComplete+0x21 a6346cd4 b9e3cc40 8a0b35b8 c000009a 8aa33130 tcpip!ARPRcvComplete+0x5 a6346d24 b904545c c000009a a6346d48 00000001 NDIS+0x22c40 a6346d50 b9e3cef2 014e3c50 89206658 88f701d0 psched!ClReceiveIndication+0xa0 a6346db8 b8f408e2 c000009a a6346dd8 00000001 NDIS+0x22ef2 a6346e84 b8f40d0c 89206658 00000001 00000000 VBoxNetFlt+0x48e2 a6346e9c b8f41231 88f70140 8aa9f130 88f700d8 VBoxNetFlt+0x4d0c a6346ebc b9e3cef2 014e7bcc 88f70140 88f701d0 VBoxNetFlt+0x5231 a6346f24 b9e2fed4 c000009a a6346f44 00000001 NDIS+0x22ef2 a6346f4c b9e1a99d 00000001 8a4e7bcc 89e37da8 NDIS+0x15ed4 a6346f68 b8f421a4 8a4e7a08 89e26c28 00000001 NDIS+0x99d a6346f80 b8f42267 266e0001 89e37d58 00000103 VBoxNetFlt+0x61a4 a6346fa0 b9e1cf87 00000000 a6346fd4 00000001 VBoxNetFlt+0x6267 a6346fc8 b9046528 8a4e0c78 89e37da8 89e37d40 NDIS+0x2f87 a6347004 b9e1a985 8a4e3c50 89e37da8 00000002 psched!MpSend+0x706 a634702c a7b12d40 8a1ea1d0 89e37da8 8a0b35b8 NDIS+0x985 a6347054 a7b12916 8a0b35b8 89e37da8 89232308 tcpip!ARPSendData+0x198 a6347080 a7b1265a 8a0b35b8 a6347002 00000001 tcpip!ARPTransmit+0x193 a63470b0 a7b1279f 8a0a58c8 ae00040a 89e37da8 tcpip!SendIPPacket+0x193 a63471fc a7b1363b a7b50b98 00000000 891a5d30 tcpip!IPTransmit+0x289e a6347248 a7b16058 024420c8 00000000 00000000 tcpip!SendACK+0x2d8 a6347268 a7b0fa0e 00000002 00000002 a6347294 tcpip!ProcessPerCpuTCBDelayQ+0xc6 a634729c a7b0f955 00000002 a7b0f901 a7b0f3d6 tcpip!ProcessTCBDelayQ+0xc4 a63472a8 a7b0f3d6 00000000 8aa33130 a7b0f7f8 tcpip!TCPRcvComplete+0x20 a63472b4 a7b0f7f8 b9e3cc40 8a0b35b8 b904ab40 tcpip!IPRcvComplete+0x21 a63472b8 b9e3cc40 8a0b35b8 b904ab40 8a4e3c50 tcpip!ARPRcvComplete+0x5 STACK_COMMAND: .tss 0x28 ; kb FOLLOWUP_IP: VBoxNetFlt+48e2 b8f408e2 5f pop edi SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: VBoxNetFlt+48e2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c5aa99f FAILURE_BUCKET_ID: 0x7f_8_VBoxNetFlt+48e2 BUCKET_ID: 0x7f_8_VBoxNetFlt+48e2 Followup: MachineOwner
====================================================
Same problem on VirtualBox 3.2.8 after few days.
Guest OS lan is configured as Bridged Adapter.
14 年 前 由 編輯
附檔: | 新增 Mini102610-01.dmp |
---|
跟進: 5 comment:4 14 年 前 由 編輯
I have exactly the same problem for several month ! When I use Firefox with numerous tabs open, my computer crashes in 2 ways. 1 / The screen is frozen and nothing works, 2 / A blue screen of death appears and a report is created in c: / windows / minidump. I have put the latest report as an attachment (Mini102810-01.dmp) Restarting is possible only with reset button. I have already had this problem (numerous times) with version 3.1.8 since september 2010 and still have the problem with version 3.2.10 (updated yesterday). Is there a patch to eliminate this problem? I thank you in advance for your help. GrosLap
comment:5 14 年 前 由 編輯
I have exactly the same problem for several month.
When I use Firefox with numerous tabs open, my computer crashes in 2 ways.
1 / The screen is frozen and nothing works,
2 / A blue screen of death appears and a report is created in c: / windows / minidump.
I have put the latest report as an attachment (Mini102810-01.dmp).
Restarting is possible only with reset button.
I have already had this problem (numerous times) with version 3.1.8 since september 2010 and still have the problem with version 3.2.10 (updated yesterday).
Is there a patch to eliminate this problem?
I thank you in advance for your help.
GrosLap
14 年 前 由 編輯
附檔: | 新增 Mini102910-01.dmp |
---|
comment:6 14 年 前 由 編輯
Same problem:
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: 80042000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT LAST_CONTROL_TRANSFER: from a7dd2836 to a7dd2923 STACK_TEXT: a764704c a7dd2836 8a3c4288 8a3c4288 8ab5b10e tcpip!DeliverToUserEx+0xa a7647104 a7dd1928 8a3c4288 8ab5b122 00000014 tcpip!IPRcvPacket+0x6cb a7647144 a7dd66ef 00000000 8ab5b070 8ab5b100 tcpip!ARPRcvIndicationNew+0x149 a7647174 b9e3cef2 8a886008 8ab5b070 8ab5b100 tcpip!ARPRcv+0x42 WARNING: Stack unwind information not available. Following frames may be wrong. a76471dc b930745c c000009a a7647200 00000001 NDIS+0x22ef2 a7647208 b9e3cef2 01436a88 893b3e18 8ab5b100 psched!ClReceiveIndication+0xa0 a7647270 b92028e2 c000009a a7647290 00000001 NDIS+0x22ef2 a764733c b9202d0c 893b3e18 00000001 00000000 VBoxNetFlt+0x48e2 a7647354 b9203231 8ab5b070 8aa83ad0 8ab5b008 VBoxNetFlt+0x4d0c a7647374 b9e3cef2 01439404 8ab5b070 8ab5b100 VBoxNetFlt+0x5231 a76473dc b9e2fed4 c000009a a76473fc 00000001 NDIS+0x22ef2 a7647404 b9e1a99d 00000001 8a439404 89432830 NDIS+0x15ed4 a7647420 b92041a4 8a439280 89262278 00000001 NDIS+0x99d a7647438 b9204267 2b8d0001 894327e0 00000103 VBoxNetFlt+0x61a4 a7647458 b9e1cf87 00000000 a764748c 00000001 VBoxNetFlt+0x6267 a7647480 b9308528 8a8b5da8 89432830 894327c8 NDIS+0x2f87 a76474bc b9e1a985 8a436a88 89432830 00000002 psched!MpSend+0x706 a76474e4 a7dd4d40 8a3ba730 89432830 8a886008 NDIS+0x985 a764750c a7dd4916 8a886008 89432830 89d0b8e8 tcpip!ARPSendData+0x198 a7647538 a7dd465a 8a886008 a7647502 00000001 tcpip!ARPTransmit+0x193 a7647568 a7dd479f 8a3b8d50 7300040a 89432830 tcpip!SendIPPacket+0x193 a76476b4 a7dd563b a7e12b98 00000000 892139c0 tcpip!IPTransmit+0x289e a7647700 a7dd8058 02a977b0 00000000 00000000 tcpip!SendACK+0x2d8 a7647720 a7dd1a0e 00000002 00000002 a764774c tcpip!ProcessPerCpuTCBDelayQ+0xc6 a7647754 a7dd1955 00000002 a7dd1901 a7dd13d6 tcpip!ProcessTCBDelayQ+0xc4 a7647760 a7dd13d6 00000000 8aa0e130 a7dd17f8 tcpip!TCPRcvComplete+0x20 a764776c a7dd17f8 b9e3cc40 8a886008 c000009a tcpip!IPRcvComplete+0x21 a7647770 b9e3cc40 8a886008 c000009a 8aa0e130 tcpip!ARPRcvComplete+0x5 a76477c0 b930745c c000009a a76477e4 00000001 NDIS+0x22c40 a76477ec b9e3cef2 01436a88 893b3d20 89dd8340 psched!ClReceiveIndication+0xa0 a7647854 b92028e2 c000009a a7647874 00000001 NDIS+0x22ef2 a7647920 b9202d0c 893b3d20 00000001 00000000 VBoxNetFlt+0x48e2 a7647938 b9203231 89dd82b0 8aa83ad0 89dd8248 VBoxNetFlt+0x4d0c a7647958 b9e3cef2 01439404 89dd82b0 89dd8340 VBoxNetFlt+0x5231 a76479c0 b9e2fed4 c000009a a76479e0 00000001 NDIS+0x22ef2 a76479e8 b9e1a99d 00000001 8a439404 894321a0 NDIS+0x15ed4 a7647a04 b92041a4 8a439280 89262180 00000001 NDIS+0x99d a7647a1c b9204267 2b8c0001 89432150 00000103 VBoxNetFlt+0x61a4 a7647a3c b9e1cf87 00000000 a7647a70 00000001 VBoxNetFlt+0x6267 a7647a64 b9308528 8a8b5da8 894321a0 89432138 NDIS+0x2f87 a7647aa0 b9e1a985 8a436a88 894321a0 00000002 psched!MpSend+0x706 a7647ac8 a7dd4d40 8a3ba730 894321a0 8a886008 NDIS+0x985 a7647af0 a7dd4916 8a886008 894321a0 8aa95560 tcpip!ARPSendData+0x198 a7647b1c a7dd465a 8a886008 a7647b02 00000001 tcpip!ARPTransmit+0x193 a7647b4c a7dd479f 8a3b8d50 8900040a 894321a0 tcpip!SendIPPacket+0x193 a7647c98 a7dd563b a7e12b98 00000000 892130d0 tcpip!IPTransmit+0x289e a7647ce4 a7dd8058 02f37de8 00000000 00000000 tcpip!SendACK+0x2d8 a7647d04 a7dd1a0e 00000002 00000002 a7647d30 tcpip!ProcessPerCpuTCBDelayQ+0xc6 a7647d38 a7dd1955 00000002 a7dd1901 a7dd13d6 tcpip!ProcessTCBDelayQ+0xc4 a7647d44 a7dd13d6 00000000 8aa0e130 a7dd17f8 tcpip!TCPRcvComplete+0x20 a7647d50 a7dd17f8 b9e3cc40 8a886008 c000009a tcpip!IPRcvComplete+0x21 a7647d54 b9e3cc40 8a886008 c000009a 8aa0e130 tcpip!ARPRcvComplete+0x5 a7647da4 b930745c c000009a a7647dc8 00000001 NDIS+0x22c40 a7647dd0 b9e3cef2 01436a88 893b3180 8aae8228 psched!ClReceiveIndication+0xa0 a7647e38 b92028e2 c000009a a7647e58 00000001 NDIS+0x22ef2 a7647f04 b9202d0c 893b3180 00000001 00000000 VBoxNetFlt+0x48e2 a7647f1c b9203231 8aae8198 8aa83ad0 8aae8130 VBoxNetFlt+0x4d0c a7647f3c b9e3cef2 01439404 8aae8198 8aae8228 VBoxNetFlt+0x5231 a7647fa4 b9e2fed4 c000009a a7647fc4 00000001 NDIS+0x22ef2 a7647fcc b9e1a99d 00000001 8a439404 894323d0 NDIS+0x15ed4 a7647fe8 b92041a4 8a439280 89262658 00000001 NDIS+0x99d a7648000 00000000 00000000 00000000 00000000 VBoxNetFlt+0x61a4 STACK_COMMAND: kb FOLLOWUP_IP: VBoxNetFlt+48e2 b92028e2 ?? ??? SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: VBoxNetFlt+48e2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c5aa99f FAILURE_BUCKET_ID: 0x7f_8_VBoxNetFlt+48e2 BUCKET_ID: 0x7f_8_VBoxNetFlt+48e2 Followup: MachineOwner
comment:7 14 年 前 由 編輯
I could share a full memory dump (compressed) if this could help to solve this annoying problem. Thanks!
comment:8 14 年 前 由 編輯
The minidumps attached should be enough so far. We'll have a look into this, thanks.
14 年 前 由 編輯
附檔: | 新增 Mini103110-01.dmp |
---|
comment:9 14 年 前 由 編輯
As a suggestion, in most cases, Windows crashes when computer wasn't used, I mean when no one was using it. It may be related to the states of the network card (maybe it was going to a some "standby" state). Windows standby/hibernation options were disabled, meaning that system is not going to "sleep", though crashes are still issuing.
comment:10 14 年 前 由 編輯
Here is daily crash:
UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: ba348d70 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffd500c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=a67aa04c ebx=8a9ee130 ecx=00000041 edx=8ac28802 esi=8a8bdc9c edi=00000001 eip=b9e3ca30 esp=a67a9ff4 ebp=a67aa02c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 NDIS!ethFilterDprIndicateReceivePacket+0xf: b9e3ca30 53 push ebx Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: idea.exe LAST_CONTROL_TRANSFER: from b90638e2 to b9e3ca30 STACK_TEXT: a67aa02c b90638e2 8a9ee130 a67aa04c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0xf WARNING: Stack unwind information not available. Following frames may be wrong. a67aa0f8 b9063d0c 89d37f10 00000001 00000000 VBoxNetFlt+0x48e2 a67aa110 b9064231 89fc4a60 8aaa4ad0 89fc49f8 VBoxNetFlt+0x4d0c a67aa130 b9e3cef2 018bdbcc 89fc4a60 89fc4af0 VBoxNetFlt+0x5231 a67aa198 b9e2fed4 c000009a a67aa1b8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a67aa1c0 b9e1a99d 00000001 8a8bdbcc 89cd2088 NDIS!ndisMLoopbackPacketX+0x154 a67aa1dc b90651a4 8a95cda8 8996f180 00000001 NDIS!ndisMSendX+0x181 a67aa1f4 b9065267 58530001 89cd2038 00000103 VBoxNetFlt+0x61a4 a67aa214 b9e1cf87 00000000 a67aa248 00000001 VBoxNetFlt+0x6267 a67aa23c b9169528 8ab22cb0 89cd2088 89cd2020 NDIS!ndisMSendX+0x1bd a67aa278 b9e1a985 8a7a6008 89cd2088 00000002 psched!MpSend+0x706 a67aa2a0 a7c35d40 8a8e7be8 89cd2088 8a954008 NDIS!ndisMSendX+0x1d6 a67aa2c8 a7c35916 8a954008 89cd2088 8993a700 tcpip!ARPSendData+0x198 a67aa2f4 a7c3565a 8a954008 a67aa302 00000001 tcpip!ARPTransmit+0x193 a67aa324 a7c3579f 8a9d29e8 7300040a 89cd2088 tcpip!SendIPPacket+0x193 a67aa470 a7c3663b a7c73b98 00000000 89b2a2e0 tcpip!IPTransmit+0x289e a67aa4bc a7c39058 024e8930 000000c0 00000000 tcpip!SendACK+0x2d8 a67aa4dc a7c32a0e 00000002 00000002 a67aa508 tcpip!ProcessPerCpuTCBDelayQ+0xc6 a67aa510 a7c32955 00000002 a7c32901 a7c323d6 tcpip!ProcessTCBDelayQ+0xc4 a67aa51c a7c323d6 00000000 8aa2e130 a7c327f8 tcpip!TCPRcvComplete+0x20 a67aa528 a7c327f8 b9e3cc40 8a954008 c000009a tcpip!IPRcvComplete+0x21 a67aa52c b9e3cc40 8a954008 c000009a 8aa2e130 tcpip!ARPRcvComplete+0x5 a67aa57c b916845c c000009a a67aa5a0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4 a67aa5a8 b9e3cef2 017a6008 89d37848 8a0b9fc8 psched!ClReceiveIndication+0xa0 a67aa610 b90638e2 c000009a a67aa630 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a67aa6dc b9063d0c 89d37848 00000001 00000000 VBoxNetFlt+0x48e2 a67aa6f4 b9064231 8a0b9f38 8aaa4ad0 8a0b9ed0 VBoxNetFlt+0x4d0c a67aa714 b9e3cef2 018bdbcc 8a0b9f38 8a0b9fc8 VBoxNetFlt+0x5231 a67aa77c b9e2fed4 c000009a a67aa79c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a67aa7a4 b9e1a99d 00000001 8a8bdbcc 89cd2b78 NDIS!ndisMLoopbackPacketX+0x154 a67aa7c0 b90651a4 8a95cda8 8996fb30 00000001 NDIS!ndisMSendX+0x181 a67aa7d8 b9065267 58520001 89cd2b28 00000103 VBoxNetFlt+0x61a4 a67aa7f8 b9e1cf87 00000000 a67aa82c 00000001 VBoxNetFlt+0x6267 a67aa820 b9169528 8ab22cb0 89cd2b78 89cd2b10 NDIS!ndisMSendX+0x1bd a67aa85c b9e1a985 8a7a6008 89cd2b78 00000002 psched!MpSend+0x706 a67aa884 a7c35d40 8a8e7be8 89cd2b78 8a954008 NDIS!ndisMSendX+0x1d6 a67aa8ac a7c35916 8a954008 89cd2b78 8a0baae8 tcpip!ARPSendData+0x198 a67aa8d8 a7c3565a 8a954008 a67aa902 00000001 tcpip!ARPTransmit+0x193 a67aa908 a7c3579f 8a9d29e8 ac00040a 89cd2b78 tcpip!SendIPPacket+0x193 a67aaa54 a7c3663b a7c73b98 00000000 89b2a700 tcpip!IPTransmit+0x289e a67aaaa0 a7c39058 02de8640 000000c0 00000000 tcpip!SendACK+0x2d8 a67aaac0 a7c32a0e 00000002 00000002 a67aaaec tcpip!ProcessPerCpuTCBDelayQ+0xc6 a67aaaf4 a7c32955 00000002 a7c32901 a7c323d6 tcpip!ProcessTCBDelayQ+0xc4 a67aab00 a7c323d6 00000000 8aa2e130 a7c327f8 tcpip!TCPRcvComplete+0x20 a67aab0c a7c327f8 b9e3cc40 8a954008 c000009a tcpip!IPRcvComplete+0x21 a67aab10 b9e3cc40 8a954008 c000009a 8aa2e130 tcpip!ARPRcvComplete+0x5 a67aab60 b916845c c000009a a67aab84 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4 a67aab8c b9e3cef2 017a6008 89d37a38 89eb4fc8 psched!ClReceiveIndication+0xa0 a67aabf4 b90638e2 c000009a a67aac14 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a67aacc0 b9063d0c 89d37a38 00000001 00000000 VBoxNetFlt+0x48e2 a67aacd8 b9064231 89eb4f38 8aaa4ad0 89eb4ed0 VBoxNetFlt+0x4d0c a67aacf8 b9e3cef2 018bdbcc 89eb4f38 89eb4fc8 VBoxNetFlt+0x5231 a67aad60 b9e2fed4 c000009a a67aad80 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a67aad88 b9e1a99d 00000001 8a8bdbcc 89cd2c90 NDIS!ndisMLoopbackPacketX+0x154 a67aada4 b90651a4 8a95cda8 8996fa38 00000001 NDIS!ndisMSendX+0x181 a67aadbc b9065267 58510001 89cd2c40 00000103 VBoxNetFlt+0x61a4 a67aaddc b9e1cf87 00000000 a67aae10 00000001 VBoxNetFlt+0x6267 a67aae04 b9169528 8ab22cb0 89cd2c90 89cd2c28 NDIS!ndisMSendX+0x1bd a67aae40 b9e1a985 8a7a6008 89cd2c90 00000002 psched!MpSend+0x706 a67aae68 a7c35d40 8a8e7be8 89cd2c90 8a954008 NDIS!ndisMSendX+0x1d6 a67aae90 a7c35916 8a954008 89cd2c90 8a026560 tcpip!ARPSendData+0x198 a67aaebc a7c3565a 8a954008 a67aae02 00000001 tcpip!ARPTransmit+0x193 a67aaeec a7c3579f 8a9d29e8 b600040a 89cd2c90 tcpip!SendIPPacket+0x193 a67ab038 a7c3663b a7c73b98 00000000 89b2a650 tcpip!IPTransmit+0x289e a67ab084 a7c39058 02ca2490 000000c0 00000000 tcpip!SendACK+0x2d8 a67ab0a4 a7c32a0e 00000002 00000002 a67ab0d0 tcpip!ProcessPerCpuTCBDelayQ+0xc6 a67ab0d8 a7c32955 00000002 a7c32901 a7c323d6 tcpip!ProcessTCBDelayQ+0xc4 a67ab0e4 a7c323d6 00000000 8aa2e130 a7c327f8 tcpip!TCPRcvComplete+0x20 a67ab0f0 a7c327f8 b9e3cc40 8a954008 c000009a tcpip!IPRcvComplete+0x21 a67ab0f4 b9e3cc40 8a954008 c000009a 8aa2e130 tcpip!ARPRcvComplete+0x5 a67ab144 b916845c c000009a a67ab168 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4 a67ab170 b9e3cef2 017a6008 89d37d20 89e21b78 psched!ClReceiveIndication+0xa0 a67ab1d8 b90638e2 c000009a a67ab1f8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a67ab2a4 b9063d0c 89d37d20 00000001 00000000 VBoxNetFlt+0x48e2 a67ab2bc b9064231 89e21ae8 8aaa4ad0 89e21a80 VBoxNetFlt+0x4d0c STACK_COMMAND: .tss 0x28 ; kb FOLLOWUP_IP: VBoxNetFlt+48e2 b90638e2 5f pop edi SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: VBoxNetFlt+48e2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4c5aa99f FAILURE_BUCKET_ID: 0x7f_8_VBoxNetFlt+48e2 BUCKET_ID: 0x7f_8_VBoxNetFlt+48e2 Followup: MachineOwner
comment:11 14 年 前 由 編輯
Here's daily crash:
UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: ba338d70 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=0000c245 ebx=00000000 ecx=8a8ac0a8 edx=a5d27098 esi=00000014 edi=8ab46130 eip=a7c746e9 esp=a5d26fe8 ebp=a5d27034 iopl=0 nv up ei ng nz ac pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296 ipnat+0x156e9: a7c746e9 53 push ebx Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: idea.exe LAST_CONTROL_TRANSFER: from a7cb1d86 to a7c746e9 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. a5d27034 a7cb1d86 a5d270cc 00000002 a5d27080 ipnat+0x156e9 a5d270a8 a7cae836 00000000 8ab46130 89cb6f3e tcpip!DeliverToUserEx+0x22a a5d27160 a7cad928 8ab46130 89cb6f52 00000014 tcpip!IPRcvPacket+0x6cb a5d271a0 a7cb26ef 00000000 89cb6ea0 89cb6f30 tcpip!ARPRcvIndicationNew+0x149 a5d271d0 b9e3cef2 8a096318 89cb6ea0 89cb6f30 tcpip!ARPRcv+0x42 a5d27238 b91e345c c000009a a5d2725c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a5d27264 b9e3cef2 014c7c50 88fc7180 89cb6f30 psched!ClReceiveIndication+0xa0 a5d272cc b90de8e2 c000009a a5d272ec 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a5d27398 b90ded0c 88fc7180 00000001 00000000 VBoxNetFlt+0x48e2 a5d273b0 b90df231 89cb6ea0 8aa91130 89cb6e38 VBoxNetFlt+0x4d0c a5d273d0 b9e3cef2 014cba4c 89cb6ea0 89cb6f30 VBoxNetFlt+0x5231 a5d27438 b9e2fed4 c000009a a5d27458 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a5d27460 b9e1a99d 00000001 8a4cba4c 880af088 NDIS!ndisMLoopbackPacketX+0x154 a5d2747c b90e01a4 8a4cb7f8 8904d750 00000001 NDIS!ndisMSendX+0x181 a5d27494 b90e0267 e8fa0001 880af038 00000103 VBoxNetFlt+0x61a4 a5d274b4 b9e1cf87 00000000 a5d274e8 00000001 VBoxNetFlt+0x6267 a5d274dc b91e4528 8a4c4c78 880af088 880af020 NDIS!ndisMSendX+0x1bd a5d27518 b9e1a985 8a4c7c50 880af088 00000002 psched!MpSend+0x706 a5d27540 a7cb0d40 8a9cc880 880af088 8a096318 NDIS!ndisMSendX+0x1d6 a5d27568 a7cb0916 8a096318 880af088 8829dd10 tcpip!ARPSendData+0x198 a5d27594 a7cb065a 8a096318 a5d27502 00000001 tcpip!ARPTransmit+0x193 a5d275c4 a7cb079f 8a088998 ac00040a 880af088 tcpip!SendIPPacket+0x193 a5d27710 a7cb163b a7ceeb98 00000000 8a10ebd0 tcpip!IPTransmit+0x289e a5d2775c a7cb4058 020f1e68 00000040 00000000 tcpip!SendACK+0x2d8 a5d2777c a7cada0e 00000002 00000002 a5d277a8 tcpip!ProcessPerCpuTCBDelayQ+0xc6 a5d277b0 a7cad955 00000002 a7cad901 a7cad3d6 tcpip!ProcessTCBDelayQ+0xc4 a5d277bc a7cad3d6 00000000 8a9e0130 a7cad7f8 tcpip!TCPRcvComplete+0x20 a5d277c8 a7cad7f8 b9e3cc40 8a096318 c000009a tcpip!IPRcvComplete+0x21 a5d277cc b9e3cc40 8a096318 c000009a 8a9e0130 tcpip!ARPRcvComplete+0x5 a5d2781c b91e345c c000009a a5d27840 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4 a5d27848 b9e3cef2 014c7c50 88fc7e18 894e8100 psched!ClReceiveIndication+0xa0 a5d278b0 b90de8e2 c000009a a5d278d0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a5d2797c b90ded0c 88fc7e18 00000001 00000000 VBoxNetFlt+0x48e2 a5d27994 b90df231 894e8070 8aa91130 894e8008 VBoxNetFlt+0x4d0c a5d279b4 b9e3cef2 014cba4c 894e8070 894e8100 VBoxNetFlt+0x5231 a5d27a1c b9e2fed4 c000009a a5d27a3c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a5d27a44 b9e1a99d 00000001 8a4cba4c 880af948 NDIS!ndisMLoopbackPacketX+0x154 a5d27a60 b90e01a4 8a4cb7f8 8904df10 00000001 NDIS!ndisMSendX+0x181 a5d27a78 b90e0267 e8f90001 880af8f8 00000103 VBoxNetFlt+0x61a4 a5d27a98 b9e1cf87 00000000 a5d27acc 00000001 VBoxNetFlt+0x6267 a5d27ac0 b91e4528 8a4c4c78 880af948 880af8e0 NDIS!ndisMSendX+0x1bd a5d27afc b9e1a985 8a4c7c50 880af948 00000002 psched!MpSend+0x706 a5d27b24 a7cb0d40 8a9cc880 880af948 8a096318 NDIS!ndisMSendX+0x1d6 a5d27b4c a7cb0916 8a096318 880af948 89e35ec8 tcpip!ARPSendData+0x198 a5d27b78 a7cb065a 8a096318 a5d27b02 00000001 tcpip!ARPTransmit+0x193 a5d27ba8 a7cb079f 8a088998 ba00040a 880af948 tcpip!SendIPPacket+0x193 a5d27cf4 a7cb163b a7ceeb98 00000000 8a10e4f0 tcpip!IPTransmit+0x289e a5d27d40 a7cb4058 02ddeb80 00000040 00000000 tcpip!SendACK+0x2d8 a5d27d60 a7cada0e 00000002 00000002 a5d27d8c tcpip!ProcessPerCpuTCBDelayQ+0xc6 a5d27d94 a7cad955 00000002 a7cad901 a7cad3d6 tcpip!ProcessTCBDelayQ+0xc4 a5d27da0 a7cad3d6 00000000 8a9e0130 a7cad7f8 tcpip!TCPRcvComplete+0x20 a5d27dac a7cad7f8 b9e3cc40 8a096318 c000009a tcpip!IPRcvComplete+0x21 a5d27db0 b9e3cc40 8a096318 c000009a 8a9e0130 tcpip!ARPRcvComplete+0x5 a5d27e00 b91e345c c000009a a5d27e24 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x5a4 a5d27e2c b9e3cef2 014c7c50 88fc7a38 88888100 psched!ClReceiveIndication+0xa0 a5d27e94 b90de8e2 c000009a a5d27eb4 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a5d27f60 b90ded0c 88fc7a38 00000001 00000000 VBoxNetFlt+0x48e2 a5d27f78 b90df231 88888070 8aa91130 88888008 VBoxNetFlt+0x4d0c a5d27f98 b9e3cef2 014cba4c 88888070 88888100 VBoxNetFlt+0x5231 a5d28000 b9e2fed4 c000009a a5d28020 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a5d28028 b9e1a99d 00000001 8a4cba4c 880af600 NDIS!ndisMLoopbackPacketX+0x154 a5d28044 b90e01a4 8a4cb7f8 8904d658 00000001 NDIS!ndisMSendX+0x181 a5d2805c b90e0267 e8f80001 880af5b0 00000103 VBoxNetFlt+0x61a4 a5d2807c b9e1cf87 00000000 a5d280b0 00000001 VBoxNetFlt+0x6267 a5d280a4 b91e4528 8a4c4c78 880af600 880af598 NDIS!ndisMSendX+0x1bd a5d280e0 b9e1a985 8a4c7c50 880af600 00000002 psched!MpSend+0x706 a5d28108 a7cb0d40 8a9cc880 880af600 8a096318 NDIS!ndisMSendX+0x1d6 a5d28130 a7cb0916 8a096318 880af600 89fd38d0 tcpip!ARPSendData+0x198 a5d2815c a7cb065a 8a096318 a5d28102 00000001 tcpip!ARPTransmit+0x193 a5d2818c a7cb079f 8a088998 e001040a 880af600 tcpip!SendIPPacket+0x193 a5d282d8 a7cb163b a7ceeb98 00000000 8a10ed30 tcpip!IPTransmit+0x289e a5d28324 a7cb4058 024c3998 00000040 00000000 tcpip!SendACK+0x2d8 a5d28344 a7cada0e 00000002 00000002 a5d28370 tcpip!ProcessPerCpuTCBDelayQ+0xc6 a5d28378 a7cad955 00000002 a7cad901 a7cad3d6 tcpip!ProcessTCBDelayQ+0xc4 a5d28384 a7cad3d6 00000000 8a9e0130 a7cad7f8 tcpip!TCPRcvComplete+0x20 STACK_COMMAND: .tss 0x28 ; kb FOLLOWUP_IP: ipnat+156e9 a7c746e9 53 push ebx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ipnat+156e9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ipnat IMAGE_NAME: ipnat.sys DEBUG_FLR_IMAGE_TIMESTAMP: 48025786 FAILURE_BUCKET_ID: 0x7f_8_ipnat+156e9 BUCKET_ID: 0x7f_8_ipnat+156e9 Followup: MachineOwner
comment:12 14 年 前 由 編輯
The problems seems to appear when more than one application are using network (firefox/chrome/winamp streaming, and so on...) alongside with VirtualBox.
comment:13 14 年 前 由 編輯
Some important details:
- My computer crash same if VirtualBox is off (not running),
- The problem appears every time I browse with Firefox,
- Since few days, I use Chrome exclusively, I have not had a problem.
GrosLap
comment:14 14 年 前 由 編輯
We've made some fixes that should solve the bsods you're seeing. Please drop me a mail at mikhail dot sennikovsky at oracle dot com I'll then send you a link to the test build with the fix.
comment:15 14 年 前 由 編輯
MAYBE A SOLUTION FOR MY PROBLEM
After several days of using Google Chrome and no crash, the questioning of Firefox was obvious.
Now, I testing the following solution :
- Uninstalling of Firefox (and such 49 plugins !)
- Cleaning the registry with jv16 Power Tools
- Reinstalling of Firefox V3.6.12 (and only 10 plugins !)
and no crash since November 6, 2010.
I will inform you regularly on my tests.
GrosLap
跟進: 18 comment:17 14 年 前 由 編輯
Hi misha!
Last weeks I'm running VirtualBox without having Chrome/Firefox/Thunderbird/IMs running and BSODs are issuing less than before.
comment:18 14 年 前 由 編輯
Replying to dumghen: Please try the test build with the fix (see link in comment 16).
comment:19 14 年 前 由 編輯
I HAVE NO LONGER PROBLEM
Since the complete reinstallation of Firefox (6/11/2010),
I have no the slightest problem [[BR]]
GROSLAP
comment:20 14 年 前 由 編輯
摘要: | BSOD 0x0000007F in VBoxNetFlt.sys UNEXPECTED_KERNEL_MODE_TRAP → BSOD 0x0000007F in VBoxNetFlt.sys UNEXPECTED_KERNEL_MODE_TRAP => Fixed in SVN |
---|
I'll mark it as fixed. Please let me know if you still have this issue with the latest test build mentioned in this ticket.
comment:22 14 年 前 由 編輯
Hi all,
I was running VirtualBox for few weeks without having Chrome/Firefox/Thunderbird/IMs running and it seems that BSODs were gone. Now I'm installing the new version of VirtualBox, so, if something happens, I'll write here.
Cheers!
跟進: 24 comment:23 14 年 前 由 編輯
I WILL TEST THIS WEEKEND
Since reinstalling Firefox, I have no problem.
So, I have not tested the temporary version 3.2.11-r67823-multiarch
Also, I will test VBox 3.2.12 this weekend
GrosLap
comment:24 14 年 前 由 編輯
Replying to GrosLap: Testing 3.2.12 only should be ok since it contains all fixes the temporary version has.
comment:25 14 年 前 由 編輯
Testing VirtualBox 3.2.12
No problems found after installation and 2 hours of use.
Thank you to the VirtualBox Team
Merry Christmas and Happy New Year
GrosLap
comment:26 14 年 前 由 編輯
狀態: | closed → reopened |
---|---|
處理結果: | fixed |
comment:27 14 年 前 由 編輯
When did those occur? I.e. were some VMs with either bridged or host-only networking running? What sort of things were you doing in host & guest when the crash occurred?
comment:28 14 年 前 由 編輯
VirtualBox was not running,
I was surfing with Firefox,
So, after the second restart, I disabled Firefox as default browser,
And now, I surfing with Google Chrome.
Like the last time...
comment:29 14 年 前 由 編輯
Close the ticket
This time, I think we can close this ticket.
Since early January, I have restart the surfing with Firefox and no crash.
GrosLap
comment:30 14 年 前 由 編輯
狀態: | reopened → closed |
---|---|
處理結果: | → fixed |
Great. Thanks for the feedback. Hope that other reporters are happy as well (please always check with 4.0.2 before considering to reopen this ticket).
comment:31 14 年 前 由 編輯
狀態: | closed → reopened |
---|---|
處理結果: | fixed |
Crashed when opened an youtube video in Chrome.
UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: ba338d70 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=ba4d101f ebx=89fc66a8 ecx=00000004 edx=892b8718 esi=892b8718 edi=00000000 eip=b90ec7fb esp=ba4d1000 ebp=ba4d1010 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 psched!PsDupPacketNoContext+0x11: b90ec7fb ff15bc100fb9 call dword ptr [psched!_imp__NdisIMGetCurrentPacketStack (b90f10bc)] ds:0023:b90f10bc={NDIS!NdisIMGetCurrentPacketStack (b9e1a580)} Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: Idle LAST_CONTROL_TRANSFER: from b90ed581 to b90ec7fb STACK_TEXT: ba4d1010 b90ed581 89fc66a8 892b8718 ba4d1060 psched!PsDupPacketNoContext+0x11 ba4d1054 b9e1a985 89fc66a8 892b8718 00000002 psched!MpSend+0x75f ba4d107c a7c52d40 8ac0e948 892b8718 89b7f1c8 NDIS!ndisMSendX+0x1d6 ba4d10a4 a7c52916 89b7f1c8 892b8718 8a83a218 tcpip!ARPSendData+0x198 ba4d10d0 a7c5265a 89b7f1c8 ba4d1102 00000001 tcpip!ARPTransmit+0x193 ba4d1100 a7c5279f 89d2a5c8 0600040a 892b8718 tcpip!SendIPPacket+0x193 ba4d124c a7c5363b a7c90b98 00000000 89b66860 tcpip!IPTransmit+0x289e ba4d1298 a7c8ceec 02aa8748 00000000 805409e0 tcpip!SendACK+0x2d8 ba4d12b4 a7c7c4c9 8aaa8748 82bf5b87 8ab57534 tcpip!SendSackInACK+0x169 ba4d1334 a7c50ef5 8a7e0628 9a00040a 564f4c52 tcpip!TCPRcv+0x1874 ba4d1394 a7c50b19 00000020 8a7e0628 a7c530b6 tcpip!DeliverToUser+0x18e ba4d1410 a7c50836 a7c908f0 8a7e0628 8a676018 tcpip!DeliverToUserEx+0x95e ba4d14c8 a7c4f928 8a7e0628 8a67602c 00000500 tcpip!IPRcvPacket+0x6cb ba4d1508 a7c4f853 00000000 89be2180 8a67600a tcpip!ARPRcvIndicationNew+0x149 ba4d1544 b9e3cb9f 89b7f1c8 00000000 b90f1b40 tcpip!ARPRcvPacket+0x68 ba4d1598 b90ec01d 0096d208 8a82e7a0 00000005 NDIS!ethFilterDprIndicateReceivePacket+0x1c2 ba4d15ac b90ec1b4 8aa17130 8a82e7a0 00000005 psched!PsFlushReceiveQueue+0x15 ba4d15d0 b90ec3e9 89fc66b0 00000000 8aa17130 psched!PsEnqueueReceivePacket+0xda ba4d15fc b9e3cef2 89fc66a8 89f95180 89a57100 psched!ClReceiveIndication+0x2d ba4d1664 a58858e3 c000009a ba4d1684 00000002 NDIS!ethFilterDprIndicateReceivePacket+0x1ff WARNING: Stack unwind information not available. Following frames may be wrong. ba4d1730 a5885d0b 89d35074 89f95180 00000001 VBoxNetFlt+0x48e3 ba4d174c a5886231 89a57070 8aa93130 89a57008 VBoxNetFlt+0x4d0b ba4d176c b9e3cef2 01d35074 89a57070 89a57100 VBoxNetFlt+0x5231 ba4d17d4 b9e2fed4 c000009a ba4d17f4 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff ba4d17fc b9e1a99d 00000001 89d35074 892b83d0 NDIS!ndisMLoopbackPacketX+0x154 ba4d1818 a58871c4 8a127cc0 88fb9180 00000001 NDIS!ndisMSendX+0x181 ba4d1830 a5887287 e13b0001 892b8380 00000103 VBoxNetFlt+0x61c4 ba4d1850 b9e1cf87 00000000 ba4d1884 00000001 VBoxNetFlt+0x6287 ba4d1878 b90ed528 893c9ab8 892b83d0 892b8368 NDIS!ndisMSendX+0x1bd ba4d18b4 b9e1a985 89fc66a8 892b83d0 00000002 psched!MpSend+0x706 ba4d18dc a7c52d40 8ac0e948 892b83d0 89b7f1c8 NDIS!ndisMSendX+0x1d6 ba4d1904 a7c52916 89b7f1c8 892b83d0 8a83a218 tcpip!ARPSendData+0x198 ba4d1930 a7c5265a 89b7f1c8 ba4d1902 00000001 tcpip!ARPTransmit+0x193 ba4d1960 a7c5279f 89d2a5c8 0600040a 892b83d0 tcpip!SendIPPacket+0x193 ba4d1aac a7c5363b a7c90b98 00000000 89b66700 tcpip!IPTransmit+0x289e ba4d1af8 a7c8ceec 02aa8748 00000000 805409e0 tcpip!SendACK+0x2d8 ba4d1b14 a7c7c4c9 8aaa8748 82bf4cc3 8ab57534 tcpip!SendSackInACK+0x169 ba4d1b94 a7c50ef5 8a7e0628 9a00040a 564f4c52 tcpip!TCPRcv+0x1874 ba4d1bf4 a7c50b19 00000020 8a7e0628 a7c530b6 tcpip!DeliverToUser+0x18e ba4d1c70 a7c50836 a7c908f0 8a7e0628 8a67d018 tcpip!DeliverToUserEx+0x95e ba4d1d28 a7c4f928 8a7e0628 8a67d02c 00000500 tcpip!IPRcvPacket+0x6cb ba4d1d68 a7c4f853 00000000 89be2750 8a67d00a tcpip!ARPRcvIndicationNew+0x149 ba4d1da4 b9e3cb9f 89b7f1c8 00000000 b90f1b40 tcpip!ARPRcvPacket+0x68 ba4d1df8 b90ec01d 009720d8 8a9e4ae0 00000003 NDIS!ethFilterDprIndicateReceivePacket+0x1c2 ba4d1e0c b90ec1b4 8aa17130 8a9e4ae0 00000003 psched!PsFlushReceiveQueue+0x15 ba4d1e30 b90ec3e9 89fc66b0 00000000 8aa17130 psched!PsEnqueueReceivePacket+0xda ba4d1e5c b9e3cef2 89fc66a8 89be2088 899f4f30 psched!ClReceiveIndication+0x2d ba4d1ec4 a58858e3 c000009a ba4d1ee4 00000004 NDIS!ethFilterDprIndicateReceivePacket+0x1ff ba4d1f90 a5885d0b 89d35074 89be2088 00000001 VBoxNetFlt+0x48e3 ba4d1fac a5886231 899f4ea0 8aa93130 899f4e38 VBoxNetFlt+0x4d0b ba4d1fcc b9e3cef2 01d35074 899f4ea0 899f4f30 VBoxNetFlt+0x5231 ba4d2034 b9e2fed4 c000009a ba4d2054 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff ba4d205c b9e1a99d 00000001 89d35074 892b84e8 NDIS!ndisMLoopbackPacketX+0x154 ba4d2078 a58871c4 8a127cc0 88fb9468 00000001 NDIS!ndisMSendX+0x181 ba4d2090 a5887287 e13a0001 892b8498 00000103 VBoxNetFlt+0x61c4 ba4d20b0 b9e1cf87 00000000 ba4d20e4 00000001 VBoxNetFlt+0x6287 ba4d20d8 b90ed528 893c9ab8 892b84e8 892b8480 NDIS!ndisMSendX+0x1bd ba4d2114 b9e1a985 89fc66a8 892b84e8 00000002 psched!MpSend+0x706 ba4d213c a7c52d40 8ac0e948 892b84e8 89b7f1c8 NDIS!ndisMSendX+0x1d6 ba4d2164 a7c52916 89b7f1c8 892b84e8 8a83a218 tcpip!ARPSendData+0x198 ba4d2190 a7c5265a 89b7f1c8 ba4d2102 00000001 tcpip!ARPTransmit+0x193 ba4d21c0 a7c5279f 89d2a5c8 0600040a 892b84e8 tcpip!SendIPPacket+0x193 ba4d230c a7c5363b a7c90b98 00000000 89b66a70 tcpip!IPTransmit+0x289e ba4d2358 a7c8ceec 02aa8748 00000000 805409e0 tcpip!SendACK+0x2d8 ba4d2374 a7c7c4c9 8aaa8748 82beea53 8ab57534 tcpip!SendSackInACK+0x169 ba4d23f4 a7c50ef5 8a7e0628 9a00040a 564f4c52 tcpip!TCPRcv+0x1874 ba4d2454 a7c50b19 00000020 8a7e0628 a7c530b6 tcpip!DeliverToUser+0x18e ba4d24d0 a7c50836 a7c908f0 8a7e0628 8a6a5018 tcpip!DeliverToUserEx+0x95e ba4d2588 a7c4f928 8a7e0628 8a6a502c 00000500 tcpip!IPRcvPacket+0x6cb ba4d25c8 a7c4f853 00000000 88f43468 8a6a500a tcpip!ARPRcvIndicationNew+0x149 ba4d2604 b9e3cb9f 89b7f1c8 00000000 b90f1b40 tcpip!ARPRcvPacket+0x68 ba4d2658 b90ec01d 0077fbe8 8ab26af0 00000010 NDIS!ethFilterDprIndicateReceivePacket+0x1c2 ba4d266c b90ec1b4 8aa17130 8ab26af0 00000010 psched!PsFlushReceiveQueue+0x15 ba4d2690 b90ec3e9 89fc66b0 00000000 8aa17130 psched!PsEnqueueReceivePacket+0xda ba4d26bc b9e3cef2 89fc66a8 89be2f10 8958f580 psched!ClReceiveIndication+0x2d STACK_COMMAND: .tss 0x28 ; kb FOLLOWUP_IP: VBoxNetFlt+48e3 a58858e3 5f pop edi SYMBOL_STACK_INDEX: 14 SYMBOL_NAME: VBoxNetFlt+48e3 FOLLOWUP_NAME: MachineOwner MODULE_NAME: VBoxNetFlt IMAGE_NAME: VBoxNetFlt.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4cf64319 FAILURE_BUCKET_ID: 0x7f_8_VBoxNetFlt+48e3 BUCKET_ID: 0x7f_8_VBoxNetFlt+48e3 Followup: MachineOwner
Again happened, with 3.2.12 version of VirtualBox.
comment:32 14 年 前 由 編輯
Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, ba338d70, 0, 0} *** ERROR: Module load completed but symbols could not be loaded for ipnat.sys *** ERROR: Symbol file could not be found. Defaulted to export symbols for VBoxNetFlt.sys - PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details Probably caused by : ipnat.sys ( ipnat+156e9 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000008, EXCEPTION_DOUBLE_FAULT Arg2: ba338d70 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details PEB is paged out (Peb.Ldr = 7ffdd00c). Type ".hh dbgerr001" for details BUGCHECK_STR: 0x7f_8 TSS: 00000028 -- (.tss 0x28) eax=0000b40e ebx=00000014 ecx=8ab2c558 edx=a634e08c esi=00000000 edi=8a885a78 eip=a7b0f6e9 esp=a634dfdc ebp=a634e028 iopl=0 nv up ei ng nz ac po nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292 ipnat+0x156e9: a7b0f6e9 53 push ebx Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: rvd.exe LAST_CONTROL_TRANSFER: from a7b21a8d to a7b0f6e9 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. a634e028 a7b21a8d a634e098 00000002 a634e06c ipnat+0x156e9 a634e09c a7b21836 8ab2c558 8a885a78 8a44f018 tcpip!DeliverToUserEx+0x7e6 a634e154 a7b20928 8a885a78 8a44f02c 00000500 tcpip!IPRcvPacket+0x6cb a634e194 a7b20853 00000000 8993a940 8a44f00a tcpip!ARPRcvIndicationNew+0x149 a634e1d0 b9e3cb9f 89f6fe70 00000000 b9035b40 tcpip!ARPRcvPacket+0x68 a634e224 b903001d 007fec70 89e10e40 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1c2 a634e238 b90301b4 8a690ad0 89e10e40 00000001 psched!PsFlushReceiveQueue+0x15 a634e25c b90303e9 8a2574f8 00000000 8a690ad0 psched!PsEnqueueReceivePacket+0xda a634e288 b9e3cef2 8a2574f0 8993a848 89a43100 psched!ClReceiveIndication+0x2d a634e2f0 b8f2b8e3 c000009a a634e310 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a634e3bc b8f2bd0b 8a25c64c 8993a848 00000001 VBoxNetFlt+0x48e3 a634e3d8 b8f2c231 89a43070 8aa3c130 89a43008 VBoxNetFlt+0x4d0b a634e3f8 b9e3cef2 0125c64c 89a43070 89a43100 VBoxNetFlt+0x5231 a634e460 b9e2fed4 c000009a a634e480 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a634e488 b9e1a99d 00000001 8a25c64c 8995eec0 NDIS!ndisMLoopbackPacketX+0x154 a634e4a4 b8f2d1c4 8a25c4c8 89964a38 00000001 NDIS!ndisMSendX+0x181 a634e4bc b8f2d287 79930001 8995ee70 00000103 VBoxNetFlt+0x61c4 a634e4dc b9e1cf87 00000000 a634e510 00000001 VBoxNetFlt+0x6287 a634e504 b9031528 8a2569e0 8995eec0 8995ee58 NDIS!ndisMSendX+0x1bd a634e540 b9e1a985 8a2574f0 8995eec0 00000002 psched!MpSend+0x706 a634e568 a7b23d40 8a886a78 8995eec0 89f6fe70 NDIS!ndisMSendX+0x1d6 a634e590 a7b23916 89f6fe70 8995eec0 89c8b660 tcpip!ARPSendData+0x198 a634e5bc a7b2365a 89f6fe70 a634e502 00000001 tcpip!ARPTransmit+0x193 a634e5ec a7b2379f 89f13860 4901040a 8995eec0 tcpip!SendIPPacket+0x193 a634e738 a7b2463b a7b61b98 00000000 88f304f0 tcpip!IPTransmit+0x289e a634e784 a7b5deec 0292da78 00000000 805409e0 tcpip!SendACK+0x2d8 a634e7a0 a7b4d4c9 8a92da78 5288bb95 8ab4de14 tcpip!SendSackInACK+0x169 a634e820 a7b21ef5 8a885a78 9a00040a 4901040a tcpip!TCPRcv+0x1874 a634e880 a7b21b19 00000020 8a885a78 a7b240b6 tcpip!DeliverToUser+0x18e a634e8fc a7b21836 a7b618f0 8a885a78 8a450018 tcpip!DeliverToUserEx+0x95e a634e9b4 a7b20928 8a885a78 8a45002c 00000500 tcpip!IPRcvPacket+0x6cb a634e9f4 a7b20853 00000000 8a25ad20 8a45000a tcpip!ARPRcvIndicationNew+0x149 a634ea30 b9e3cb9f 89f6fe70 00000000 b9035b40 tcpip!ARPRcvPacket+0x68 a634ea84 b903001d 00f12f08 8a9bfed8 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1c2 a634ea98 b90301b4 8a690ad0 8a9bfed8 00000001 psched!PsFlushReceiveQueue+0x15 a634eabc b90303e9 8a2574f8 00000000 8a690ad0 psched!PsEnqueueReceivePacket+0xda a634eae8 b9e3cef2 8a2574f0 8993aa38 8a75cd80 psched!ClReceiveIndication+0x2d a634eb50 b8f2b8e3 c000009a a634eb70 00000002 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a634ec1c b8f2bd0b 8a25c64c 8993aa38 00000001 VBoxNetFlt+0x48e3 a634ec38 b8f2c231 8a75ccf0 8aa3c130 8a75cc88 VBoxNetFlt+0x4d0b a634ec58 b9e3cef2 0125c64c 8a75ccf0 8a75cd80 VBoxNetFlt+0x5231 a634ecc0 b9e2fed4 c000009a a634ece0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a634ece8 b9e1a99d 00000001 8a25c64c 898e0718 NDIS!ndisMLoopbackPacketX+0x154 a634ed04 b8f2d1c4 8a25c4c8 89964278 00000001 NDIS!ndisMSendX+0x181 a634ed1c b8f2d287 79920001 898e06c8 00000103 VBoxNetFlt+0x61c4 a634ed3c b9e1cf87 00000000 a634ed70 00000001 VBoxNetFlt+0x6287 a634ed64 b9031528 8a2569e0 898e0718 898e06b0 NDIS!ndisMSendX+0x1bd a634eda0 b9e1a985 8a2574f0 898e0718 00000002 psched!MpSend+0x706 a634edc8 a7b23d40 8a886a78 898e0718 89f6fe70 NDIS!ndisMSendX+0x1d6 a634edf0 a7b23916 89f6fe70 898e0718 89c8b660 tcpip!ARPSendData+0x198 a634ee1c a7b2365a 89f6fe70 a634ee02 00000001 tcpip!ARPTransmit+0x193 a634ee4c a7b2379f 89f13860 4901040a 898e0718 tcpip!SendIPPacket+0x193 a634ef98 a7b2463b a7b61b98 00000000 88f305a0 tcpip!IPTransmit+0x289e a634efe4 a7b5deec 0292da78 00000000 805409e0 tcpip!SendACK+0x2d8 a634f000 a7b4d4c9 8a92da78 5288b6b5 8ab4de14 tcpip!SendSackInACK+0x169 a634f080 a7b21ef5 8a885a78 9a00040a 4901040a tcpip!TCPRcv+0x1874 a634f0e0 a7b21b19 00000020 8a885a78 a7b240b6 tcpip!DeliverToUser+0x18e a634f15c a7b21836 a7b618f0 8a885a78 8a452018 tcpip!DeliverToUserEx+0x95e a634f214 a7b20928 8a885a78 8a45202c 00000500 tcpip!IPRcvPacket+0x6cb a634f254 a7b20853 00000000 8a25aa38 8a45200a tcpip!ARPRcvIndicationNew+0x149 a634f290 b9e3cb9f 89f6fe70 00000000 b9035b40 tcpip!ARPRcvPacket+0x68 a634f2e4 b903001d 00813f08 8a7f9a98 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1c2 a634f2f8 b90301b4 8a690ad0 8a7f9a98 00000001 psched!PsFlushReceiveQueue+0x15 a634f31c b90303e9 8a2574f8 00000000 8a690ad0 psched!PsEnqueueReceivePacket+0xda a634f348 b9e3cef2 8a2574f0 8a25a180 89d34fb8 psched!ClReceiveIndication+0x2d a634f3b0 b8f2b8e3 c000009a a634f3d0 00000002 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a634f47c b8f2bd0b 8a25c64c 8a25a180 00000001 VBoxNetFlt+0x48e3 a634f498 b8f2c231 89d34f28 8aa3c130 89d34ec0 VBoxNetFlt+0x4d0b a634f4b8 b9e3cef2 0125c64c 89d34f28 89d34fb8 VBoxNetFlt+0x5231 a634f520 b9e2fed4 c000009a a634f540 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x1ff a634f548 b9e1a99d 00000001 8a25c64c 898e01a0 NDIS!ndisMLoopbackPacketX+0x154 a634f564 b8f2d1c4 8a25c4c8 89964b30 00000001 NDIS!ndisMSendX+0x181 a634f57c b8f2d287 79910001 898e0150 00000103 VBoxNetFlt+0x61c4 a634f59c b9e1cf87 00000000 a634f5d0 00000001 VBoxNetFlt+0x6287 a634f5c4 b9031528 8a2569e0 898e01a0 898e0138 NDIS!ndisMSendX+0x1bd STACK_COMMAND: .tss 0x28 ; kb FOLLOWUP_IP: ipnat+156e9 a7b0f6e9 53 push ebx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: ipnat+156e9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ipnat IMAGE_NAME: ipnat.sys DEBUG_FLR_IMAGE_TIMESTAMP: 48025786 FAILURE_BUCKET_ID: 0x7f_8_ipnat+156e9 BUCKET_ID: 0x7f_8_ipnat+156e9 Followup: MachineOwner
3.2.12
comment:33 13 年 前 由 編輯
same/similar BSOD every time my Opera opens multiple tabs (on a restart) and Vbox is running. I don't have a dump (no pagefile) BSOD says STOP: 0x...7F (0x...8, 0x...80050031, 0x...6F8, 0xFFFFFADF26A6B931) VBoxNetFlt.sys - Address FFFFFADF26A6B931 base at FFFFFADF26A64000, DateStamp 4e048b76
OS: WinXPx64 SP2 Network: Marvell Yukon 88E8056; driver version 11.41.4.3 VirtualBox: 4.0.10 Network in VBox: Paravirtualized Network (bridged with the Marvell adapter)
Had this problem in all 4.x versions so far. On my last installation of windows a downgrade to 3.2.12 helped. Going to try it again...
Anything else?
comment:34 13 年 前 由 編輯
Could you try 4.1 Beta to see if it is fixed: http://download.virtualbox.org/virtualbox/4.1.0_BETA2
13 年 前 由 編輯
comment:35 13 年 前 由 編輯
Just tried. It crashed before I could test it :)
The log is attached.
I've installed the Beta and the Extension Pack, but not the Guest Additions. I don't want to ruin the Guest OS with experiments. But if it's important, I'll make a copy. Just tell.
comment:39 13 年 前 由 編輯
Ok, just got a BSOD from 3.2.12: created new tab, typed an address, enter, address doesn't exist (typo), corrected it, enter, BSOD. Same error, similar addresses and datestamp (can provide you with exact data).
Looks quite random to me. Had no issues with the old version so far.
Now activated a small pagefile and turned minidump on, so you'll get some more info on that next time ;)
If this wont be solved, I'll have to move to other virtualization software :/
13 年 前 由 編輯
附檔: | 新增 Mini071911-01.dmp |
---|
comment:40 13 年 前 由 編輯
Now had the time to cause some damage to my host :)
Created minidump is attached. Tried to read it with WinDbg, no success. Maybe you'll have more luck with it.
Activated full memory dump for next BSOD. Couldn't create a BSOD for now... Boot - start Opera (with ~50 tabs :) - close Opera - start VM, boot WinXP - restart Opera - no crash.
Usually I start Opera after the VM, maybe it's related.
Someone suggested a defect memory module. Although I can't replace all 4x2GB modules and my modules were tested my memtest for a day, I'll do a short run with some spare modules (probably 2x1GB) next week.
comment:41 13 年 前 由 編輯
I'm unable to read your minidump either. What VBox version caused the crash? Did you try the new 4.1 release?
comment:42 13 年 前 由 編輯
It was the old 3.2.12 and no, I didn't tried the release of v4.1. But I seriously doubt something will change, since the cause is unknown. So a 'fix' would be accidental ;) But sure, I'll try it next week.
About dumps: weird enough, I wasn't able to read any of the minidumps my WinXP x64 created, ever (or at least those I tried to read :) That's why I've decided to activate a full dump.
I think I'll also try the last Server Version of Windows as the host (thanks to MSDNAA :) Again, next week.
comment:43 13 年 前 由 編輯
摘要: | BSOD 0x0000007F in VBoxNetFlt.sys UNEXPECTED_KERNEL_MODE_TRAP => Fixed in SVN → BSOD 0x0000007F in VBoxNetFlt.sys UNEXPECTED_KERNEL_MODE_TRAP |
---|
Even if the cause is unknown it is still worth a try because that driver got some major rewrite for version 4.1.
13 年 前 由 編輯
附檔: | 新增 Mini073011-01.dmp |
---|
comment:44 13 年 前 由 編輯
Crash made by 3.2.12
I couldn't get the spare RAM, but I run memtest - over 6 passes - no errors.
Now installing 4.1 ...
comment:45 13 年 前 由 編輯
Ok... After the installation of 4.1 my windows got screwed and wouldn't start properly. I think the installation itself wasn't source of the problem, but it sure triggered it.
However: I had to reinstall my windows (same version). Now I've found the time to test it again. Installed the 4.1 and upgraded the guest additions within my VMs. No errors so far.
comment:46 13 年 前 由 編輯
Ok, please reopen this ticket if you still experience these crashes. You also might want to upgrade to VBox 4.1.2.
comment:47 13 年 前 由 編輯
狀態: | reopened → closed |
---|---|
處理結果: | → fixed |
comment:48 13 年 前 由 編輯
狀態: | closed → reopened |
---|---|
處理結果: | fixed |
Here it comes...
VBox 4.1.2 Windows Server 2008 R2
Minidump attached. Had to uninstall VBox to get the system running again.
13 年 前 由 編輯
附檔: | 新增 112111-17503-01.dmp |
---|
13 年 前 由 編輯
附檔: | 新增 112111-17238-01.dmp |
---|
comment:49 13 年 前 由 編輯
HackAR, this minidump was taken when running VBox 4.1.2, right? Does the same problem happen with VBox 4.1.6?
comment:50 13 年 前 由 編輯
- Yes, Vbox 4.1.2 on windows Server 2008 R2 as host.
- Not tested.
As I've told, I had to uninstall VBox. Maybe I'll try it again in the future... But these dump can be read, so maybe you'll find the error. And I've got a full dump from 1st crash (at least I think its complete - 2.75Gb). If you need to extract some information from it, tell me. I can keep it for some time.
P.S. Happened after installing Windows updates from last 23 days. Maybe related... The first dump was taken in same situation as described above (VBox running, starting Opera with lots of tabs). Second after the reboot, VBox not running.
comment:51 12 年 前 由 編輯
描述: | 修改 (差異) |
---|---|
狀態: | reopened → closed |
處理結果: | → fixed |
Please reopen if still relevant with VBox 4.2.12.
comment:52 7 年 前 由 編輯
Reproduced with vbox 5.1.28r117968. Workaround: disable networking completely in VM properties. Guest OS lan is configured as nat. Guest is XP x32 SP3. Host is Mint 18.2 x64.
Reproduction: Nothing special, no special command, just a random BSOD when host is in locked screen state.
I downgraded to version 3.2.8 and problem seems to be gone. (if this is could help)