************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\VirtualMachine\QEMU\Windows10\MEMORY.DMP] Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available. ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 16299 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 16299.15.amd64fre.rs3_release.170928-1534 Kernel base = 0xfffff802`34c95000 PsLoadedModuleList = 0xfffff802`34ff6fd0 Debug session time: Sun Aug 20 04:59:06.095 2023 (UTC + 7:00) System Uptime: 0 days 0:00:29.996 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ........... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff802`34df87d0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc88f`0b3540e0=000000000000000a 3: kd> .sympath D:\VirtualMachine\QEMU\Windows10\Symbol\ Symbol search path is: D:\VirtualMachine\QEMU\Windows10\Symbol\ Expanded Symbol search path is: d:\virtualmachine\qemu\windows10\symbol\ ************* Path validation summary ************** Response Time (ms) Location OK D:\VirtualMachine\QEMU\Windows10\Symbol\ 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_CORRUPTED_EXPOOL (c5) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is caused by drivers that have corrupted the system pool. Run the driver verifier against any new (or suspect) drivers, and if that doesn't turn up the culprit, then use gflags to enable special pool. Arguments: Arg1: ffff9700b8f72032, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff80234f3b49d, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_IMAGE_DOS_HEADER *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_EPROCESS *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* KEY_VALUES_STRING: 1 Key : Analysis.Elapsed.mSec Value: 129 Key : Analysis.IO.Other.Mb Value: 10 Key : Analysis.IO.Read.Mb Value: 2 Key : Analysis.IO.Write.Mb Value: 20 Key : Analysis.Init.CPU.mSec Value: 1046 Key : Analysis.Init.Elapsed.mSec Value: 63731 Key : Analysis.Memory.CommitPeak.Mb Value: 95 Key : Bugcheck.Code.KiBugCheckData Value: 0xc5 Key : Bugcheck.Code.LegacyAPI Value: 0xc5 Key : Failure.Bucket Value: WRONG_SYMBOLS_X64_16299.15.amd64fre.rs3_release.170928-1534_TIMESTAMP_170929-015304_59CDA780_nt_wrong_symbols!59CDA7808D2000 Key : Failure.Hash Value: {a49de2b9-f890-3d6f-bf7d-8b108c8cb29f} Key : WER.OS.Branch Value: rs3_release Key : WER.OS.Version Value: 10.0.16299.15 BUGCHECK_CODE: c5 BUGCHECK_P1: ffff9700b8f72032 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff80234f3b49d FILE_IN_CAB: MEMORY.DMP ADDITIONAL_DEBUG_TEXT: You can run '.symfix; .reload' to try to fix the symbol path and load symbols. WRONG_SYMBOLS_TIMESTAMP: 59cda780 WRONG_SYMBOLS_SIZE: 8d2000 FAULTING_MODULE: fffff80234c95000 nt BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXPNP: 1 (!blackboxpnp) STACK_TEXT: ffffc88f`0b3540d8 fffff802`34e040e9 : 00000000`0000000a ffff9700`b8f72032 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffc88f`0b3540e0 fffff802`34e0247d : 00000000`80000009 ffffc88f`0b3542c0 00000000`00000000 30343831`33373041 : nt!setjmpex+0x4319 ffffc88f`0b354220 fffff802`34f3b49d : 37304146`30314546 ff000a30`34383133 ffff273a`3a9fb51c fffff802`34d1c081 : nt!setjmpex+0x26ad ffffc88f`0b3543b0 fffff801`101d3820 : 00000000`00000000 00000000`00000000 ffffc88f`00000335 fffff801`4f495667 : nt!ExFreePoolWithTag+0x3d ffffc88f`0b354480 fffff801`101d1cb5 : ffffe10f`a07318b8 ffffe10f`a0731010 ffffe10f`a0731010 fffff801`101e25ab : viogpu3d!operator delete[]+0x14 [C:\MSYS2\home\RedGreenBlue123\viogpu3d\kvm-guest-drivers-windows\viogpu\common\baseobj.cpp @ 67] ffffc88f`0b3544b0 fffff801`101dd434 : ffffe10f`a0731840 ffffe10f`a41e77c0 ffffe10f`a0730b20 00000000`80000009 : viogpu3d!VioGpuBuf::Close+0xd5 [C:\MSYS2\home\RedGreenBlue123\viogpu3d\kvm-guest-drivers-windows\viogpu\common\viogpu_queue.cpp @ 985] ffffc88f`0b3544e0 fffff801`101e1bb7 : ffffffff`ff676980 ffffe10f`a0730b20 ffffe10f`a0608100 ffffe10f`a0608180 : viogpu3d!VioGpuBuf::~VioGpuBuf+0x38 [C:\MSYS2\home\RedGreenBlue123\viogpu3d\kvm-guest-drivers-windows\viogpu\common\viogpu_queue.cpp @ 1119] ffffc88f`0b354510 fffff801`101dfa1d : ffffe10f`a0731010 ffffe10f`a0730b20 ffffe10f`a0731010 00000000`0000000a : viogpu3d!VioGpuAdapter::~VioGpuAdapter+0x77 [C:\MSYS2\home\RedGreenBlue123\viogpu3d\kvm-guest-drivers-windows\viogpu\viogpu3d\viogpu_adapter.cpp @ 135] ffffc88f`0b354540 fffff801`11c9dffc : 00000000`00000007 ffffe10f`a41e77c0 ffffe10f`a41e77c0 ffffe10f`74727044 : viogpu3d!VioGpu3DRemoveDevice+0x3d [C:\MSYS2\home\RedGreenBlue123\viogpu3d\kvm-guest-drivers-windows\viogpu\viogpu3d\driver.cpp @ 223] ffffc88f`0b354570 fffff801`11c9236d : 00000000`00000000 ffffe10f`a0608030 ffffe10f`00000935 00000000`74727044 : dxgkrnl!TdrUpdateDbgReport+0x419ac ffffc88f`0b3545b0 fffff801`11bb7d8c : ffffe10f`a0608102 ffffe10f`a41e77c0 00000000`c00000bb 00000000`0000000e : dxgkrnl!TdrUpdateDbgReport+0x35d1d ffffc88f`0b354600 fffff801`11b4d835 : ffffe10f`a0608102 ffffe10f`a0608030 00000000`00000000 ffffe10f`a41e77c0 : dxgkrnl!DxgkUnreferenceDxgAllocation+0x2cdcc ffffc88f`0b354640 fffff802`34ceb149 : 00000000`00000000 fffff802`34ced0c3 ffffe10f`a0608030 ffffe10f`a0608004 : dxgkrnl!DxgkUnreferenceDxgResource+0x355 ffffc88f`0b354760 fffff802`3510f4d1 : ffffe10f`a0608030 00000000`00000000 ffffc88f`0b354850 fffff802`3521f731 : nt!IofCallDriver+0x59 ffffc88f`0b3547a0 fffff802`3521f4df : 00000000`00000002 ffffc88f`0b354869 ffffe10f`9b26fa30 ffffe10f`9b26e060 : nt!IoBuildSynchronousFsdRequest+0x341 ffffc88f`0b354810 fffff802`34dad5db : ffff8486`05f5c200 ffffe10f`9b26fa30 00000000`0000000a ffffe10f`00000309 : nt!RtlCompareUnicodeStrings+0x261f ffffc88f`0b3548d0 fffff802`3521e4ca : ffffe10f`9b26fa30 00000000`0000002b 00000000`00000000 00000000`00000002 : nt!IoInvalidateDeviceRelations+0xe5b ffffc88f`0b354930 fffff802`3521e1f7 : 00000000`00000000 ffffc88f`0b3549b0 ffff8486`00941450 fffff802`34da8360 : nt!RtlCompareUnicodeStrings+0x160a ffffc88f`0b354970 fffff802`352651ed : ffffe10f`9b26e060 ffffe10f`00000002 ffffe10f`a2bf1b80 ffffe10f`9b26e000 : nt!RtlCompareUnicodeStrings+0x1337 ffffc88f`0b3549e0 fffff802`352650ff : ffffe10f`a2bf1b80 ffffc88f`0b354a60 ffffe10f`9b26e060 fffff802`35010e40 : nt!NtSetCachedSigningLevel+0x76d ffffc88f`0b354a30 fffff802`35264fd1 : ffffe10f`9b26e060 ffff8486`00b8a502 ffffe10f`a2bf1b80 fffff802`34d55874 : nt!NtSetCachedSigningLevel+0x67f ffffc88f`0b354a70 fffff802`34dae5f9 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : nt!NtSetCachedSigningLevel+0x551 ffffc88f`0b354aa0 fffff802`3521dc89 : ffffe10f`a2982150 ffffc88f`0b354ba9 ffff8486`00941450 ffff8486`00000001 : nt!IoReuseIrp+0x8a9 ffffc88f`0b354b20 fffff802`35113e42 : ffffc88f`0b354c70 ffff8486`06430c00 ffffe10f`a30e5700 00000000`00000002 : nt!RtlCompareUnicodeStrings+0xdc9 ffffc88f`0b354c10 fffff802`35111d1b : ffff8486`05f5c200 00000000`00000000 ffffe10f`9a2e3300 ffff8486`06430c30 : nt!IoBuildSynchronousFsdRequest+0x4cb2 ffffc88f`0b354c40 fffff802`34cef645 : ffffe10f`9a2e3380 ffffe10f`9a7f8580 fffff802`35111a80 ffffe10f`9a7f8580 : nt!IoBuildSynchronousFsdRequest+0x2b8b ffffc88f`0b354cc0 fffff802`34d783a7 : 00000000`00000000 00000000`00000080 ffffe10f`9a2ac040 ffffe10f`9a7f8580 : nt!ExQueueWorkItem+0x4f5 ffffc88f`0b354d50 fffff802`34dfdd66 : fffff802`33fc6180 ffffe10f`9a7f8580 fffff802`34d78360 00000000`00000000 : nt!RtlInterlockedSetClearRun+0x1f7 ffffc88f`0b354da0 00000000`00000000 : ffffc88f`0b355000 ffffc88f`0b34f000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x4626 FAULTING_SOURCE_LINE: C:\MSYS2\home\RedGreenBlue123\viogpu3d\kvm-guest-drivers-windows\viogpu\common\baseobj.cpp FAULTING_SOURCE_FILE: C:\MSYS2\home\RedGreenBlue123\viogpu3d\kvm-guest-drivers-windows\viogpu\common\baseobj.cpp FAULTING_SOURCE_LINE_NUMBER: 67 FAULTING_SOURCE_CODE: 63: { 64: 65: UNREFERENCED_PARAMETER(Size); 66: ::operator delete (pObject); > 67: } SYMBOL_NAME: nt_wrong_symbols!59CDA7808D2000 STACK_COMMAND: .cxr; .ecxr ; kb EXCEPTION_CODE_STR: 59CDA780 EXCEPTION_STR: WRONG_SYMBOLS PROCESS_NAME: ntoskrnl.wrong.symbols.exe IMAGE_NAME: ntoskrnl.wrong.symbols.exe MODULE_NAME: nt_wrong_symbols FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_16299.15.amd64fre.rs3_release.170928-1534_TIMESTAMP_170929-015304_59CDA780_nt_wrong_symbols!59CDA7808D2000 OS_VERSION: 10.0.16299.15 BUILDLAB_STR: rs3_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {a49de2b9-f890-3d6f-bf7d-8b108c8cb29f} Followup: MachineOwner ---------