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 910276 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 third bsod
file_1111051.txt (text/plain), 4.35 KB, created by
lijin
on 2014-06-19 06:59:35 UTC
(
hide
)
Description:
analyze -v info for the third bsod
Filename:
MIME Type:
Creator:
lijin
Created:
2014-06-19 06:59:35 UTC
Size:
4.35 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: 8299220c, The address that the exception occurred at >Arg3: 86e8493c, Trap Frame >Arg4: 00000000 > >Debugging Details: >------------------ > > >EXCEPTION_CODE: (NTSTATUS) 0xc0000420 - An assertion failure has occurred. > >FAULTING_IP: >nt!ViCtxCheckAndReleaseXSaveData+59 >8299220c cd2c int 2Ch > >TRAP_FRAME: 86e84a18 -- (.trap 0xffffffff86e84a18) >ErrCode = 00000000 >eax=00000000 ebx=00000009 ecx=8261cda0 edx=00000000 esi=807c2498 edi=00000001 >eip=8261cda2 esp=86e84a8c ebp=86e84aa8 iopl=0 nv up di pl nz na pe nc >cs=0008 ss=0010 ds=b8c4 es=2000 fs=0008 gs=4c80 efl=00000006 >hal!HalpGenerateInterrupt+0x2ce: >8261cda2 c3 ret >Resetting default scope > >DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT > >BUGCHECK_STR: 0x8E > >PROCESS_NAME: System > >CURRENT_IRQL: a > >EXCEPTION_RECORD: 8b66f780 -- (.exr 0xffffffff8b66f780) >ExceptionAddress: 826dbb1e (nt!KiInterruptMessageDispatch) > ExceptionCode: 02780016 > ExceptionFlags: 8b66f784 >NumberParameters: -2103893823 > Parameter[0]: 00000000 > Parameter[1]: 8b698bb8 > Parameter[2]: 00000000 > Parameter[3]: ffffffff > Parameter[4]: 8e30ad84 > Parameter[5]: 8268b740 > 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 8270608c to 8272ff20 > >STACK_TEXT: >86e844a4 8270608c 0000008e c0000420 8299220c nt!KeBugCheckEx+0x1e >86e848cc 8268fdd6 86e848e8 00000000 86e8493c nt!KiDispatchException+0x1ac >86e84934 8268fd72 86e849bc 8299220e badb0d00 nt!CommonDispatchException+0x4a >86e8495c 8271607f 82748f10 00000000 00000000 nt!KiExceptionExit+0x17a >86e849bc 829920f6 84c9090e 8b66f780 8e30ad84 nt!vDbgPrintExWithPrefixInternal+0x2ff >86e849d8 826dbb30 8b66f780 8b698bb8 00000000 nt!ViCtxIsrMessageBased+0x35 >86e849ec 8268b7ad 8b66f780 8b698bb8 86e84a18 nt!KiInterruptMessageDispatch+0x12 >86e849ec 8261cda2 8b66f780 8b698bb8 86e84a18 nt!KiInterruptDispatch+0x6d >86e84a88 8261fa4d 807c398c 00000000 00000000 hal!HalpGenerateInterrupt+0x2ce >86e84aa8 8261fba0 00000001 9d6f9000 86e84adc hal!HalpLowerIrqlHardwareInterrupts+0xf5 >86e84ab8 82688c42 00000002 00000000 83da6a58 hal!KfLowerIrql+0x58 >86e84adc 82771431 9d6f9000 00000000 86e84b44 nt!KeFlushMultipleRangeTb+0x2e4 >86e84bc8 82772ef1 9d6f8000 00002000 00000000 nt!MiFreePoolPages+0x42c >86e84c30 8298c5a4 9d6f8000 00000000 00000000 nt!ExFreePoolWithTag+0x436 >86e84c50 8285af5e 82792c60 a4becce0 00000000 nt!ViPoolDelayFreeTrimThreadRoutine+0x35 >86e84c90 82702219 8298c56f 82792c60 00000000 nt!PspSystemThreadStartup+0x9e >00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 > > >STACK_COMMAND: kb > >FOLLOWUP_IP: >nt!ViCtxCheckAndReleaseXSaveData+59 >8299220c cd2c int 2Ch > >SYMBOL_STACK_INDEX: 0 > >SYMBOL_NAME: nt!ViCtxCheckAndReleaseXSaveData+59 > >FOLLOWUP_NAME: MachineOwner > >MODULE_NAME: nt > >IMAGE_NAME: ntkrpamp.exe > >DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78a09 > >FAILURE_BUCKET_ID: 0x8E_VRF_nt!ViCtxCheckAndReleaseXSaveData+59 > >BUCKET_ID: 0x8E_VRF_nt!ViCtxCheckAndReleaseXSaveData+59 > >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