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 910275 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 second bsod
file_1111051.txt (text/plain), 4.12 KB, created by
lijin
on 2014-06-19 06:58:58 UTC
(
hide
)
Description:
analyze -v info for the second bsod
Filename:
MIME Type:
Creator:
lijin
Created:
2014-06-19 06:58:58 UTC
Size:
4.12 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: 8295720c, The address that the exception occurred at >Arg3: 807e2c8c, Trap Frame >Arg4: 00000000 > >Debugging Details: >------------------ > >Page 23ac3 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 >8295720c cd2c int 2Ch > >TRAP_FRAME: 807e2d6c -- (.trap 0xffffffff807e2d6c) >ErrCode = 00000000 >eax=0000fffb ebx=8c96ef70 ecx=22bbb4d4 edx=0001df74 esi=9f34eef8 edi=8c9aef98 >eip=84c409e7 esp=807e2de0 ebp=807e2de8 iopl=0 nv up ei pl zr na pe nc >cs=0008 ss=0010 ds=8f90 es=2db4 fs=cde8 gs=cac5 efl=00000246 >ndis!NdisMFreeNetBufferSGList+0x9c: >84c409e7 5f pop edi >Resetting default scope > >DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT > >BUGCHECK_STR: 0x8E > >PROCESS_NAME: explorer.exe > >CURRENT_IRQL: a > >TAG_NOT_DEFINED_c000000f: FFFFFFFF807E3000 > >EXCEPTION_RECORD: 8b8c6780 -- (.exr 0xffffffff8b8c6780) >ExceptionAddress: 826a0b1e (nt!KiInterruptMessageDispatch) > ExceptionCode: 02780016 > ExceptionFlags: 8b8c6784 >NumberParameters: -2104135487 > Parameter[0]: 00000000 > Parameter[1]: 8b8dcec0 > Parameter[2]: 00000000 > Parameter[3]: ffffffff > Parameter[4]: 8c9aad84 > Parameter[5]: 82650740 > Parameter[6]: 000000b0 > Parameter[7]: 01000a0a > 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 826cb08c to 826f4f20 > >STACK_TEXT: >807e2de8 8bd14a5c 8c9aef98 95b8cde8 9f34eef8 ndis!NdisMFreeNetBufferSGList+0x9c >WARNING: Stack unwind information not available. Following frames may be wrong. >807e2e00 8bd15e2e 9e85afe8 8b86e0e0 00000001 netkvm+0x6a5c >807e2e18 8bd16329 8c96ef70 807e2e60 8c8e2854 netkvm+0x7e2e >807e2e34 8bd143f1 807e2e84 807e2e94 8bd14e40 netkvm+0x8329 >807e2e40 8bd14e40 8c8e2850 807e2e93 807e2e9c netkvm+0x63f1 >807e2e94 8bd10afc 00000001 8c8e21a8 807e2f10 netkvm+0x6e40 >807e2eac 8bd18d72 00000020 8c8e23fc 00000000 netkvm+0x2afc >807e2ee0 84c92892 8c8e21a8 00000001 00000000 netkvm+0xad72 >807e2f20 84c3da0f 8c9aae54 009aad00 00000001 ndis!ndisMiniportDpc+0xda >807e2f48 8268e1b5 8c9aae54 8c9aad00 00000001 ndis!ndisInterruptDpc+0xaf >807e2fa4 8268e018 807c2120 9aa12670 00000000 nt!KiExecuteAllDpcs+0xf9 >807e2ff4 8268d7dc 9a3ef9e0 00000000 00000000 nt!KiRetireDpcList+0xd5 >807e2ff8 9a3ef9e0 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c >8268d7dc 00000000 0000001a 00d6850f bb830000 0x9a3ef9e0 > > >STACK_COMMAND: .trap 0xffffffff807e2d6c ; kb > >FOLLOWUP_IP: >netkvm+6a5c >8bd14a5c c3 ret > >SYMBOL_STACK_INDEX: 1 > >SYMBOL_NAME: netkvm+6a5c > >FOLLOWUP_NAME: MachineOwner > >MODULE_NAME: netkvm > >IMAGE_NAME: netkvm.sys > >DEBUG_FLR_IMAGE_TIMESTAMP: 538f1b50 > >FAILURE_BUCKET_ID: 0x8E_VRF_netkvm+6a5c > >BUCKET_ID: 0x8E_VRF_netkvm+6a5c > >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