Advertisement
Guest User

10/24/2019

a guest
Oct 24th, 2019
169
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.78 KB | None | 0 0
  1.  
  2. Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Windows\Minidump\102419-8015-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9.  
  10. ************* Path validation summary **************
  11. Response Time (ms) Location
  12. Deferred srv*
  13. Symbol search path is: srv*
  14. Executable search path is:
  15. Windows 10 Kernel Version 18362 MP (12 procs) Free x64
  16. Product: WinNt, suite: TerminalServer SingleUserTS
  17. Machine Name:
  18. Kernel base = 0xfffff800`07200000 PsLoadedModuleList = 0xfffff800`07648210
  19. Debug session time: Thu Oct 24 17:41:47.375 2019 (UTC - 6:00)
  20. System Uptime: 0 days 0:10:14.125
  21. Loading Kernel Symbols
  22. ...............................................................
  23. ................................................................
  24. ................................................................
  25. .............
  26. Loading User Symbols
  27. Loading unloaded module list
  28. .........
  29. For analysis of this file, run !analyze -v
  30. nt!KeBugCheckEx:
  31. fffff800`073c1220 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc00`f7467230=000000000000000a
  32. 10: kd> !analyze -v
  33. *******************************************************************************
  34. * *
  35. * Bugcheck Analysis *
  36. * *
  37. *******************************************************************************
  38.  
  39. DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
  40. An attempt was made to access a pageable (or completely invalid) address at an
  41. interrupt request level (IRQL) that is too high. This is usually
  42. caused by drivers using improper addresses.
  43. If kernel debugger is available get stack backtrace.
  44. Arguments:
  45. Arg1: 000000005b8bc8c3, memory referenced
  46. Arg2: 0000000000000002, IRQL
  47. Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
  48. Arg4: fffff80020878231, address which referenced memory
  49.  
  50. Debugging Details:
  51. ------------------
  52.  
  53.  
  54. KEY_VALUES_STRING: 1
  55.  
  56. Key : Analysis.CPU.Sec
  57. Value: 1
  58.  
  59. Key : Analysis.DebugAnalysisProvider.CPP
  60. Value: Create: 8007007e on DESKTOP-1CBU1CD
  61.  
  62. Key : Analysis.DebugData
  63. Value: CreateObject
  64.  
  65. Key : Analysis.DebugModel
  66. Value: CreateObject
  67.  
  68. Key : Analysis.Elapsed.Sec
  69. Value: 2
  70.  
  71. Key : Analysis.Memory.CommitPeak.Mb
  72. Value: 72
  73.  
  74. Key : Analysis.System
  75. Value: CreateObject
  76.  
  77.  
  78. DUMP_FILE_ATTRIBUTES: 0x8
  79. Kernel Generated Triage Dump
  80.  
  81. BUGCHECK_CODE: d1
  82.  
  83. BUGCHECK_P1: 5b8bc8c3
  84.  
  85. BUGCHECK_P2: 2
  86.  
  87. BUGCHECK_P3: 1
  88.  
  89. BUGCHECK_P4: fffff80020878231
  90.  
  91. WRITE_ADDRESS: fffff800077733b8: Unable to get MiVisibleState
  92. Unable to get NonPagedPoolStart
  93. Unable to get NonPagedPoolEnd
  94. Unable to get PagedPoolStart
  95. Unable to get PagedPoolEnd
  96. fffff8000762a3c8: Unable to get Flags value from nt!KdVersionBlock
  97. fffff8000762a3c8: Unable to get Flags value from nt!KdVersionBlock
  98. unable to get nt!MmSpecialPagesInUse
  99. 000000005b8bc8c3
  100.  
  101. CUSTOMER_CRASH_COUNT: 1
  102.  
  103. PROCESS_NAME: System
  104.  
  105. TRAP_FRAME: fffffc00f7467370 -- (.trap 0xfffffc00f7467370)
  106. NOTE: The trap frame does not contain all registers.
  107. Some register values may be zeroed or incorrect.
  108. rax=fffff80021115180 rbx=0000000000000000 rcx=0000000000800001
  109. rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
  110. rip=fffff80020878231 rsp=fffffc00f7467500 rbp=fffffc00f7467670
  111. r8=0000000000000007 r9=0000000000000000 r10=fffff80020f4ef18
  112. r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
  113. r14=0000000000000000 r15=0000000000000000
  114. iopl=0 nv up ei ng nz na pe nc
  115. nvlddmkm+0xe8231:
  116. fffff800`20878231 008bc3c88b5b add byte ptr [rbx+5B8BC8C3h],cl ds:00000000`5b8bc8c3=??
  117. Resetting default scope
  118.  
  119. STACK_TEXT:
  120. fffffc00`f7467228 fffff800`073d30e9 : 00000000`0000000a 00000000`5b8bc8c3 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
  121. fffffc00`f7467230 fffff800`073cf42b : 00000001`0000000b 00000000`00000000 00000000`00000fff 00000000`00000000 : nt!KiBugCheckDispatch+0x69
  122. fffffc00`f7467370 fffff800`20878231 : 00000000`00000000 fffffc00`f7467670 ffffcc84`fbc5d030 00000000`00000000 : nt!KiPageFault+0x46b
  123. fffffc00`f7467500 00000000`00000000 : fffffc00`f7467670 ffffcc84`fbc5d030 00000000`00000000 fffffc00`f7467670 : nvlddmkm+0xe8231
  124.  
  125.  
  126. SYMBOL_NAME: nvlddmkm+e8231
  127.  
  128. MODULE_NAME: nvlddmkm
  129.  
  130. IMAGE_NAME: nvlddmkm.sys
  131.  
  132. STACK_COMMAND: .thread ; .cxr ; kb
  133.  
  134. BUCKET_ID_FUNC_OFFSET: e8231
  135.  
  136. FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function
  137.  
  138. OSPLATFORM_TYPE: x64
  139.  
  140. OSNAME: Windows 10
  141.  
  142. FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}
  143.  
  144. Followup: MachineOwner
  145. ---------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement