Advertisement
Guest User

dmp1

a guest
Jan 12th, 2022
225
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.05 KB | None | 0 0
  1.  
  2. Microsoft (R) Windows Debugger Version 10.0.22000.194 X86
  3. Copyright (c) Microsoft Corporation. All rights reserved.
  4.  
  5.  
  6. Loading Dump File [C:\Windows\Minidump\011022-4875-01.dmp]
  7. Mini Kernel Dump File: Only registers and stack trace are available
  8.  
  9. Symbol search path is: srv*
  10. Executable search path is:
  11. Windows 10 Kernel Version 19041 MP (12 procs) Free x64
  12. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  13. Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
  14. Machine Name:
  15. Kernel base = 0xfffff801`3aa00000 PsLoadedModuleList = 0xfffff801`3b62a1b0
  16. Debug session time: Mon Jan 10 23:37:24.378 2022 (UTC - 5:00)
  17. System Uptime: 0 days 0:53:10.998
  18. Loading Kernel Symbols
  19. ...............................................................
  20. ................................................................
  21. ................................................................
  22.  
  23. Loading User Symbols
  24. Loading unloaded module list
  25. ......
  26. For analysis of this file, run !analyze -v
  27. 5: kd> !analyze -v
  28. *******************************************************************************
  29. * *
  30. * Bugcheck Analysis *
  31. * *
  32. *******************************************************************************
  33.  
  34. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
  35. This is a very common bugcheck. Usually the exception address pinpoints
  36. the driver/function that caused the problem. Always note this address
  37. as well as the link date of the driver/image that contains this address.
  38. Some common problems are exception code 0x80000003. This means a hard
  39. coded breakpoint or assertion was hit, but this system was booted
  40. /NODEBUG. This is not supposed to happen as developers should never have
  41. hardcoded breakpoints in retail code, but ...
  42. If this happens, make sure a debugger gets connected, and the
  43. system is booted /DEBUG. This will let us see why this breakpoint is
  44. happening.
  45. Arguments:
  46. Arg1: ffffffffc0000005, The exception code that was not handled
  47. Arg2: fffff8013aff5ece, The address that the exception occurred at
  48. Arg3: fffff106c0ac2978, Exception Record Address
  49. Arg4: fffff106c0ac21b0, Context Record Address
  50.  
  51. Debugging Details:
  52. ------------------
  53.  
  54. *** WARNING: Unable to verify timestamp for win32k.sys
  55.  
  56. KEY_VALUES_STRING: 1
  57.  
  58. Key : AV.Dereference
  59. Value: NullPtr
  60.  
  61. Key : AV.Fault
  62. Value: Write
  63.  
  64. Key : Analysis.CPU.mSec
  65. Value: 3500
  66.  
  67. Key : Analysis.DebugAnalysisManager
  68. Value: Create
  69.  
  70. Key : Analysis.Elapsed.mSec
  71. Value: 6485
  72.  
  73. Key : Analysis.Init.CPU.mSec
  74. Value: 1577
  75.  
  76. Key : Analysis.Init.Elapsed.mSec
  77. Value: 57908
  78.  
  79. Key : Analysis.Memory.CommitPeak.Mb
  80. Value: 92
  81.  
  82. Key : WER.OS.Branch
  83. Value: vb_release
  84.  
  85. Key : WER.OS.Timestamp
  86. Value: 2019-12-06T14:06:00Z
  87.  
  88. Key : WER.OS.Version
  89. Value: 10.0.19041.1
  90.  
  91.  
  92. BUGCHECK_CODE: 7e
  93.  
  94. BUGCHECK_P1: ffffffffc0000005
  95.  
  96. BUGCHECK_P2: fffff8013aff5ece
  97.  
  98. BUGCHECK_P3: fffff106c0ac2978
  99.  
  100. BUGCHECK_P4: fffff106c0ac21b0
  101.  
  102. EXCEPTION_RECORD: fffff106c0ac2978 -- (.exr 0xfffff106c0ac2978)
  103. ExceptionAddress: fffff8013aff5ece (nt!ObpReferenceObjectByHandleWithTag+0x00000000000001fe)
  104. ExceptionCode: c0000005 (Access violation)
  105. ExceptionFlags: 00000000
  106. NumberParameters: 2
  107. Parameter[0]: 0000000000000001
  108. Parameter[1]: 0000000000000000
  109. Attempt to write to address 0000000000000000
  110.  
  111. CONTEXT: fffff106c0ac21b0 -- (.cxr 0xfffff106c0ac21b0)
  112. rax=0000000000000000 rbx=ffff9f8efcda7050 rcx=0000000000001000
  113. rdx=000000003245001e rsi=0000000000000000 rdi=ffffdd0ac0575bc0
  114. rip=fffff8013aff5ece rsp=fffff106c0ac2bb0 rbp=00000000001fffff
  115. r8=ffffdd0abba5f001 r9=fffff8013aa00000 r10=0000fffff8013b06
  116. r11=ffffbafaee200000 r12=fffff106c0ac2cd0 r13=0000000000000000
  117. r14=ffffcfc77e6d3828 r15=ffff9f8efef31040
  118. iopl=0 nv up ei pl zr na po nc
  119. cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
  120. nt!ObpReferenceObjectByHandleWithTag+0x1fe:
  121. fffff801`3aff5ece 0000 add byte ptr [rax],al ds:002b:00000000`00000000=??
  122. Resetting default scope
  123.  
  124. BLACKBOXBSD: 1 (!blackboxbsd)
  125.  
  126.  
  127. BLACKBOXNTFS: 1 (!blackboxntfs)
  128.  
  129.  
  130. BLACKBOXWINLOGON: 1
  131.  
  132. CUSTOMER_CRASH_COUNT: 1
  133.  
  134. PROCESS_NAME: System
  135.  
  136. WRITE_ADDRESS: fffff8013b6fb390: Unable to get MiVisibleState
  137. Unable to get NonPagedPoolStart
  138. Unable to get NonPagedPoolEnd
  139. Unable to get PagedPoolStart
  140. Unable to get PagedPoolEnd
  141. unable to get nt!MmSpecialPagesInUse
  142. 0000000000000000
  143.  
  144. ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
  145.  
  146. EXCEPTION_CODE_STR: c0000005
  147.  
  148. EXCEPTION_PARAMETER1: 0000000000000001
  149.  
  150. EXCEPTION_PARAMETER2: 0000000000000000
  151.  
  152. MISALIGNED_IP:
  153. nt!ObpReferenceObjectByHandleWithTag+1fe
  154. fffff801`3aff5ece 0000 add byte ptr [rax],al
  155.  
  156. EXCEPTION_STR: 0xc0000005
  157.  
  158. STACK_TEXT:
  159. fffff106`c0ac2bb0 fffff801`3aff5c81 : ffff9f8e`f2a8c040 00000000`00001000 ffff9f8e`f2a59e30 00000000`00000000 : nt!ObpReferenceObjectByHandleWithTag+0x1fe
  160. fffff106`c0ac2c40 fffff801`3b065314 : ffff9f8e`fcda7080 ffffdd0a`c0d52c68 fffff106`c0ac2d8c ffff9f8e`fcda7080 : nt!ObReferenceObjectByHandleWithTag+0x31
  161. fffff106`c0ac2c90 fffff801`3ae08ab8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryInformationProcess+0x34f4
  162. fffff106`c0ac3680 fffff801`3adfaf30 : fffff801`4c1bdc9e ffffdd0a`c0d52bf0 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
  163. fffff106`c0ac3888 fffff801`4c1bdc9e : ffffdd0a`c0d52bf0 00000000`00000000 00000000`00000000 ffffdd0a`c0c15ae0 : nt!KiServiceLinkage
  164. fffff106`c0ac3890 fffff801`3b0fb3b7 : ffffdd0a`c0c15ae0 ffffdd0a`baebd2a8 ffffdd0a`c0d9d8b0 ffff9f8e`00000000 : bam!BampThrottledProcessWakeNotificationCallback+0xbe
  165. fffff106`c0ac3ab0 fffff801`3b0fb1a5 : ffff9f8e`fef31040 fffff801`3b0fb180 ffff9f8e`f2aa3c40 00000000`00000000 : nt!ExpWnfDispatchKernelSubscription+0x1e3
  166. fffff106`c0ac3b40 fffff801`3acb85f5 : ffff9f8e`fef31040 fffff801`3b0fb180 ffff9f8e`f2aa3c40 ffff9f8f`00000000 : nt!ExpWnfWorkItemRoutine+0x25
  167. fffff106`c0ac3b70 fffff801`3ad55935 : ffff9f8e`fef31040 00000000`00000080 ffff9f8e`f2a8c040 00000000`00000001 : nt!ExpWorkerThread+0x105
  168. fffff106`c0ac3c10 fffff801`3adfe728 : ffffcb00`48a79180 ffff9f8e`fef31040 fffff801`3ad558e0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
  169. fffff106`c0ac3c60 00000000`00000000 : fffff106`c0ac4000 fffff106`c0abe000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
  170.  
  171.  
  172. SYMBOL_NAME: bam!BampThrottledProcessWakeNotificationCallback+be
  173.  
  174. IMAGE_VERSION: 10.0.19041.1030
  175.  
  176. STACK_COMMAND: .cxr 0xfffff106c0ac21b0 ; kb
  177.  
  178. MODULE_NAME: hardware
  179.  
  180. IMAGE_NAME: hardware
  181.  
  182. FAILURE_BUCKET_ID: IP_MISALIGNED
  183.  
  184. OS_VERSION: 10.0.19041.1
  185.  
  186. BUILDLAB_STR: vb_release
  187.  
  188. OSPLATFORM_TYPE: x64
  189.  
  190. OSNAME: Windows 10
  191.  
  192. FAILURE_ID_HASH: {201b0e5d-db2a-63d2-77be-8ce8ff234750}
  193.  
  194. Followup: MachineOwner
  195. ---------
  196.  
  197.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement