Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 910274 Details for
Bug 1111051
[virtio-win][netkvm]win7-32 guest bsod(8e) while performing long (several hours) netperf transfer with mq=on
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
analyze -v info for the first bsod
file_1111051.txt (text/plain), 5.36 KB, created by
lijin
on 2014-06-19 06:58:06 UTC
(
hide
)
Description:
analyze -v info for the first bsod
Filename:
MIME Type:
Creator:
lijin
Created:
2014-06-19 06:58:06 UTC
Size:
5.36 KB
patch
obsolete
>1: kd> !analyze -v >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e) >This is a very common bugcheck. Usually the exception address pinpoints >the driver/function that caused the problem. Always note this address >as well as the link date of the driver/image that contains this address. >Some common problems are exception code 0x80000003. This means a hard >coded breakpoint or assertion was hit, but this system was booted >/NODEBUG. This is not supposed to happen as developers should never have >hardcoded breakpoints in retail code, but ... >If this happens, make sure a debugger gets connected, and the >system is booted /DEBUG. This will let us see why this breakpoint is >happening. >Arguments: >Arg1: c0000420, The exception code that was not handled >Arg2: 8298520c, The address that the exception occurred at >Arg3: 9a1d3294, Trap Frame >Arg4: 00000000 > >Debugging Details: >------------------ > >Page 20240 not present in the dump file. Type ".hh dbgerr004" for details > >EXCEPTION_CODE: (NTSTATUS) 0xc0000420 - An assertion failure has occurred. > >FAULTING_IP: >nt!ViCtxCheckAndReleaseXSaveData+59 >8298520c cd2c int 2Ch > >TRAP_FRAME: 9a1d3370 -- (.trap 0xffffffff9a1d3370) >ErrCode = 00000000 >eax=9a1d341c ebx=84c2ce01 ecx=8277b700 edx=00000001 esi=9a1d341c edi=84420c38 >eip=826e602c esp=9a1d33e4 ebp=9a1d33fc iopl=0 nv up ei ng nz na po nc >cs=0008 ss=0010 ds=347c es=6f23 fs=0000 gs=341c efl=00000282 >nt!FindNodeOrParent+0x3: >826e602c 8bec mov ebp,esp >Resetting default scope > >DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT > >BUGCHECK_STR: 0x8E > >PROCESS_NAME: netperf.exe > >CURRENT_IRQL: a > >EXCEPTION_RECORD: 8a071500 -- (.exr 0xffffffff8a071500) >ExceptionAddress: 826ceb1e (nt!KiInterruptMessageDispatch) > ExceptionCode: 02780016 > ExceptionFlags: 8a071504 >NumberParameters: -2103947071 > Parameter[0]: 00000001 > Parameter[1]: 89e4ddc8 > Parameter[2]: 00000000 > Parameter[3]: ffffffff > Parameter[4]: 8e9acd84 > Parameter[5]: 8267e740 > Parameter[6]: 000000a0 > Parameter[7]: 01000a09 > Parameter[8]: 00000001 > Parameter[9]: 00000001 > Parameter[10]: 00000001 > Parameter[11]: 00000000 > Parameter[12]: 00000000 > Parameter[13]: ffffffff > Parameter[14]: 00000000 > >LAST_CONTROL_TRANSFER: from 826f908c to 82722f20 > >STACK_TEXT: >9a1d33e4 826ec685 9a1d3434 9a1d341c 00000001 nt!FindNodeOrParent+0x3 >9a1d33fc 826f8820 84420c38 9a1d3434 9a1d341c nt!RtlLookupElementGenericTableFullAvl+0x16 >9a1d3414 8265409b 84420c38 9a1d3434 00000000 nt!RtlLookupElementGenericTableAvl+0x18 >9a1d3440 827548c0 8277b700 84c2ce01 00000001 nt!VfAvlLookupTreeNode+0x79 >9a1d3460 8297ec0d 84c2ce01 84c2ce01 82976c63 nt!VfTargetDriversGetNode+0x35 >9a1d346c 82976c63 88e46c80 88e46cc0 00000000 nt!VfTargetDriversGetVerifierData+0x3d >9a1d3490 829768be 00000080 000001a0 6c624e55 nt!VeAllocatePoolWithTagPriority+0x150 >9a1d34ac 84c2ce01 00000000 000001a0 6c624e55 nt!VerifierExAllocatePoolWithTagPriority+0x1f >9a1d34c4 84c2becc 00000000 00000190 6c624e55 ndis!ndisAllocateFromNPagedPool+0x1d >9a1d34ec 84c2c157 88e46c80 00000040 9a1d3514 ndis!ndisPplAllocate+0x65 >9a1d350c 84ce58de 00000001 00000010 00000000 ndis!NdisAllocateNetBufferList+0x39 >9a1d3524 84e8c179 88e46c80 00000050 00000008 NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+0x14 >9a1d3710 84e846e9 00000000 00000000 891ab158 tcpip!UdpSendMessagesOnPathCreation+0x13a >9a1d3814 84e84895 89df8648 001d3904 00000000 tcpip!UdpSendMessages+0x595 >9a1d3828 826cd654 9a1d38b8 be3e0774 00000000 tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x13 >9a1d3890 84e8c93b 84e84882 9a1d38b8 00000000 nt!KeExpandKernelStackAndCalloutEx+0x132 >9a1d38d0 8b6509ba 891ab158 9a1d3904 89c27008 tcpip!UdpTlProviderSendMessages+0x67 >9a1d38e8 8b67027f 89082a30 9a1d3904 89082a30 afd!AfdTLSendMessages+0x27 >9a1d3940 8b6708e2 89082a30 89c27008 1178c9ec afd!AfdTLFastDgramSend+0x7d >9a1d39b0 8b6603e1 89082a30 9a1d3a6c 00000400 afd!AfdFastDatagramSend+0x5d3 >9a1d3b28 82872797 89158d01 00000001 0012f998 afd!AfdFastIoDeviceControl+0x3dc >9a1d3bd0 828b93f4 89fbd548 00000054 00000000 nt!IopXxxControlFile+0x2d0 >9a1d3c04 826821ea 0000005c 00000054 00000000 nt!NtDeviceIoControlFile+0x2a >9a1d3c04 779670b4 0000005c 00000054 00000000 nt!KiFastCallEntry+0x12a >WARNING: Frame IP not in any known module. Following frames may be wrong. >0012fa54 00000000 00000000 00000000 00000000 0x779670b4 > > >STACK_COMMAND: .trap 0xffffffff9a1d3370 ; kb > >FOLLOWUP_IP: >NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+14 >84ce58de 8bd8 mov ebx,eax > >SYMBOL_STACK_INDEX: b > >SYMBOL_NAME: NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+14 > >FOLLOWUP_NAME: MachineOwner > >MODULE_NAME: NETIO > >IMAGE_NAME: NETIO.SYS > >DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78963 > >FAILURE_BUCKET_ID: 0x8E_VRF_NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+14 > >BUCKET_ID: 0x8E_VRF_NETIO!NetioAllocateAndReferenceNetBufferListNetBufferMdlAndData+14 > >Followup: MachineOwner >--------- >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1111051
: 910274 |
910275
|
910276