Advertisement
Guest User

BSOD

a guest
Jul 12th, 2021
94
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 5.14 KB | None | 0 0
  1. Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Users\USER\OneDrive\Documents 30 Nov 2020\032721-6593-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8. Symbol search path is: srv*
  9. Executable search path is:
  10. Windows 10 Kernel Version 19041 MP (12 procs) Free x64
  11. Product: WinNt, suite: TerminalServer SingleUserTS Personal
  12. Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
  13. Machine Name:
  14. Kernel base = 0xfffff802`1fc00000 PsLoadedModuleList = 0xfffff802`2082a490
  15. Debug session time: Sat Mar 27 07:46:50.204 2021 (UTC + 7:00)
  16. System Uptime: 2 days 23:51:59.811
  17. Loading Kernel Symbols
  18. ...............................................................
  19. ................................................................
  20. .....................................................
  21. Loading User Symbols
  22. Loading unloaded module list
  23. ...........................
  24. For analysis of this file, run !analyze -v
  25. nt!KeBugCheckEx:
  26. fffff802`1fff5c50 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd60e`d8cc30d0=000000000000001a
  27. 6: kd> !analyze -v
  28. *******************************************************************************
  29. * *
  30. * Bugcheck Analysis *
  31. * *
  32. *******************************************************************************
  33.  
  34. MEMORY_MANAGEMENT (1a)
  35. # Any other values for parameter 1 must be individually examined.
  36. Arguments:
  37. Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
  38. the PTE. Parameters 3/4 contain the low/high parts of the PTE.
  39. Arg2: fffff9bffc11ca10
  40. Arg3: 0000008000000000
  41. Arg4: 0000000000000000
  42.  
  43. Debugging Details:
  44. ------------------
  45.  
  46.  
  47. KEY_VALUES_STRING: 1
  48.  
  49. Key : Analysis.CPU.mSec
  50. Value: 2656
  51.  
  52. Key : Analysis.DebugAnalysisManager
  53. Value: Create
  54.  
  55. Key : Analysis.Elapsed.mSec
  56. Value: 14881
  57.  
  58. Key : Analysis.Init.CPU.mSec
  59. Value: 530
  60.  
  61. Key : Analysis.Init.Elapsed.mSec
  62. Value: 49937
  63.  
  64. Key : Analysis.Memory.CommitPeak.Mb
  65. Value: 77
  66.  
  67. Key : MemoryManagement.PFN
  68. Value: 8000000
  69.  
  70. Key : WER.OS.Branch
  71. Value: vb_release
  72.  
  73. Key : WER.OS.Timestamp
  74. Value: 2019-12-06T14:06:00Z
  75.  
  76. Key : WER.OS.Version
  77. Value: 10.0.19041.1
  78.  
  79.  
  80. BUGCHECK_CODE: 1a
  81.  
  82. BUGCHECK_P1: 41792
  83.  
  84. BUGCHECK_P2: fffff9bffc11ca10
  85.  
  86. BUGCHECK_P3: 8000000000
  87.  
  88. BUGCHECK_P4: 0
  89.  
  90. MEMORY_CORRUPTOR: ONE_BIT
  91.  
  92. BLACKBOXBSD: 1 (!blackboxbsd)
  93.  
  94.  
  95. BLACKBOXNTFS: 1 (!blackboxntfs)
  96.  
  97.  
  98. BLACKBOXPNP: 1 (!blackboxpnp)
  99.  
  100.  
  101. BLACKBOXWINLOGON: 1
  102.  
  103. CUSTOMER_CRASH_COUNT: 1
  104.  
  105. PROCESS_NAME: GoogleCrashHandler64.exe
  106.  
  107. STACK_TEXT:
  108. ffffd60e`d8cc30c8 fffff802`1fe9d0fa : 00000000`0000001a 00000000`00041792 fffff9bf`fc11ca10 00000080`00000000 : nt!KeBugCheckEx
  109. ffffd60e`d8cc30d0 fffff802`1fe9b92f : ffffc406`b1284700 00000000`00000000 fffff9bf`00000002 00000000`00000000 : nt!MiDeleteVa+0x153a
  110. ffffd60e`d8cc31d0 fffff802`1fe6baf0 : 00000000`00000001 ffffd60e`00000000 ffffc406`b1284550 ffffc406`b28cc080 : nt!MiDeletePagablePteRange+0x48f
  111. ffffd60e`d8cc34e0 fffff802`202360f9 : ffffc406`c06a44c0 00000000`00000000 ffffc406`00000000 ffffc406`00000000 : nt!MiDeleteVad+0x360
  112. ffffd60e`d8cc35f0 fffff802`20235790 : ffffc406`c06a44c0 ffffc406`b56d2c40 ffffc406`b28cc080 00000000`00000000 : nt!MiUnmapVad+0x49
  113. ffffd60e`d8cc3620 fffff802`20233a5f : ffffc406`c06a3a20 ffffc406`c06a3a20 ffffc406`c06a44c0 ffffc406`b1284080 : nt!MiCleanVad+0x30
  114. ffffd60e`d8cc3650 fffff802`2025db44 : ffffffff`00000000 ffffffff`ffffffff 00000000`00000001 ffffc406`b1284080 : nt!MmCleanProcessAddressSpace+0x137
  115. ffffd60e`d8cc36d0 fffff802`20306b36 : ffffc406`b1284080 ffffae0b`98dbf6b0 ffffd60e`d8cc3920 00000000`00000000 : nt!PspRundownSingleProcess+0x20c
  116. ffffd60e`d8cc3760 fffff802`202d2888 : 00000000`000000ff 00000000`00000001 00000000`00000000 0000009b`3092b000 : nt!PspExitThread+0x5f6
  117. ffffd60e`d8cc3860 fffff802`1fe67fb7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x38
  118. ffffd60e`d8cc38a0 fffff802`1fffa1f0 : 00000000`00000000 ffffd60e`d8cc3950 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x487
  119. ffffd60e`d8cc3950 fffff802`2000765f : 00000000`0000024c fffff802`2022e0f5 ffffc406`b28cc080 ffffd60e`d8cc3aa8 : nt!KiInitiateUserApc+0x70
  120. ffffd60e`d8cc3a90 00007ff8`258ed764 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
  121. 0000009b`3074e4d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`258ed764
  122.  
  123.  
  124. MODULE_NAME: hardware
  125.  
  126. IMAGE_NAME: memory_corruption
  127.  
  128. STACK_COMMAND: .thread ; .cxr ; kb
  129.  
  130. FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
  131.  
  132. OS_VERSION: 10.0.19041.1
  133.  
  134. BUILDLAB_STR: vb_release
  135.  
  136. OSPLATFORM_TYPE: x64
  137.  
  138. OSNAME: Windows 10
  139.  
  140. FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
  141.  
  142. Followup: MachineOwner
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement