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 713165 Details for
Bug 923667
win8 (installed virtio-win-1.6.3 netkvm driver) virtio-net guest BSOD when shutdown
[?]
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.
dump info
win8.64-netkvm-bsod-when-shutdown.txt (text/plain), 5.42 KB, created by
CongLi
on 2013-03-20 10:05:12 UTC
(
hide
)
Description:
dump info
Filename:
MIME Type:
Creator:
CongLi
Created:
2013-03-20 10:05:12 UTC
Size:
5.42 KB
patch
obsolete
> >Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64 >Copyright (c) Microsoft Corporation. All rights reserved. > > >Loading Dump File [C:\Windows\Memory.dmp] >Kernel Bitmap Dump File: Full address space is available > >Symbol search path is: SRV*http://msdl.microsoft.com/download/symbols >Executable search path is: >Windows 8 Kernel Version 9200 MP (4 procs) Free x64 >Product: WinNt, suite: TerminalServer SingleUserTS >Built by: 9200.16384.amd64fre.win8_rtm.120725-1247 >Machine Name: >Kernel base = 0xfffff802`64208000 PsLoadedModuleList = 0xfffff802`644d2a60 >Debug session time: Wed Mar 20 17:18:50.424 2013 (UTC - 7:00) >System Uptime: 0 days 0:01:07.303 >Loading Kernel Symbols >............................................................... >................................................................ >........ >Loading User Symbols > >Loading unloaded module list >........ >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >Use !analyze -v to get detailed debugging information. > >BugCheck 7E, {ffffffffc0000005, fffff88003f1cc6e, fffff88004ced9b8, fffff88004ced1f0} > >*** ERROR: Module load completed but symbols could not be loaded for netkvm.sys >Probably caused by : netkvm.sys ( netkvm+3c6e ) > >Followup: MachineOwner >--------- > >2: kd> !analyze -v >******************************************************************************* >* * >* Bugcheck Analysis * >* * >******************************************************************************* > >SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) >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. >Arguments: >Arg1: ffffffffc0000005, The exception code that was not handled >Arg2: fffff88003f1cc6e, The address that the exception occurred at >Arg3: fffff88004ced9b8, Exception Record Address >Arg4: fffff88004ced1f0, Context Record Address > >Debugging Details: >------------------ > > >EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. > >FAULTING_IP: >netkvm+3c6e >fffff880`03f1cc6e 488b4108 mov rax,qword ptr [rcx+8] > >EXCEPTION_RECORD: fffff88004ced9b8 -- (.exr 0xfffff88004ced9b8) >ExceptionAddress: fffff88003f1cc6e (netkvm+0x0000000000003c6e) > ExceptionCode: c0000005 (Access violation) > ExceptionFlags: 00000000 >NumberParameters: 2 > Parameter[0]: 0000000000000000 > Parameter[1]: 0000000000000008 >Attempt to read from address 0000000000000008 > >CONTEXT: fffff88004ced1f0 -- (.cxr 0xfffff88004ced1f0) >rax=fffffa8003309000 rbx=fffffa8003289ab8 rcx=0000000000000000 >rdx=0000000000000000 rsi=fffffa8003c2adf0 rdi=fffffa80032897a0 >rip=fffff88003f1cc6e rsp=fffff88004cedbf0 rbp=fffffa80018dba20 > r8=0000000000000ff0 r9=0000000000000001 r10=0000000000000002 >r11=0000000000000000 r12=fffff8026428c770 r13=0000000050085d00 >r14=fffffa800196bbd0 r15=fffff8026448bfc0 >iopl=0 nv up ei ng nz na pe nc >cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 >netkvm+0x3c6e: >fffff880`03f1cc6e 488b4108 mov rax,qword ptr [rcx+8] ds:002b:00000000`00000008=???????????????? >Resetting default scope > >PROCESS_NAME: System > >CURRENT_IRQL: 0 > >ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. > >EXCEPTION_PARAMETER1: 0000000000000000 > >EXCEPTION_PARAMETER2: 0000000000000008 > >READ_ADDRESS: 0000000000000008 > >FOLLOWUP_IP: >netkvm+3c6e >fffff880`03f1cc6e 488b4108 mov rax,qword ptr [rcx+8] > >BUGCHECK_STR: AV > >DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE > >LAST_CONTROL_TRANSFER: from fffff88003f27e3c to fffff88003f1cc6e > >STACK_TEXT: >fffff880`04cedbf0 fffff880`03f27e3c : fffffa80`0307b8a0 fffff880`03aeb660 fffffa80`03e80090 fffff880`03b04f30 : netkvm+0x3c6e >fffff880`04cedc20 fffff802`6426e45b : fffffa80`0196bbd0 00000000`00000000 fffff880`0191205c 00000000`0000000a : netkvm+0xee3c >fffff880`04cedc50 fffff802`642bb391 : fffff802`6448c080 fffffa80`04054b00 fffff802`6426e3fc 00000000`00000000 : nt!IopProcessWorkItem+0x5f >fffff880`04cedcc0 fffff802`6422a521 : 00000000`00000000 00000000`00000080 fffff802`642bb250 fffffa80`04054b00 : nt!ExpWorkerThread+0x142 >fffff880`04cedd50 fffff802`64268dd6 : fffff880`02a5c180 fffffa80`04054b00 fffffa80`03602080 fffffa80`01886840 : nt!PspSystemThreadStartup+0x59 >fffff880`04cedda0 00000000`00000000 : fffff880`04cee000 fffff880`04ce8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 > > >SYMBOL_STACK_INDEX: 0 > >SYMBOL_NAME: netkvm+3c6e > >FOLLOWUP_NAME: MachineOwner > >MODULE_NAME: netkvm > >IMAGE_NAME: netkvm.sys > >DEBUG_FLR_IMAGE_TIMESTAMP: 50b73ae2 > >STACK_COMMAND: .cxr 0xfffff88004ced1f0 ; kb > >FAILURE_BUCKET_ID: AV_netkvm+3c6e > >BUCKET_ID: AV_netkvm+3c6e > >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 923667
: 713165 |
713598