PC BSOD randomly Windows 10

Jake Dobson 0 Reputation points
2024-01-07T06:24:20.11+00:00

My computer randomly crashes and I dont know how to interpreate the dmp file, can someone help me understand what I should do? Thank you for any help

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   AllowNugetMSCredentialProviderInstall : true
   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.125 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\cwinn\Desktop\MEMORY 1 - Copy.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff804`3dc00000 PsLoadedModuleList = 0xfffff804`3e82a770
Debug session time: Thu Jan  4 22:48:29.620 2024 (UTC - 8:00)
System Uptime: 0 days 1:52:38.240
Loading Kernel Symbols
...............................................................
......Page 8095e2 not present in the dump file. Type ".hh dbgerr004" for details
..........................................................
..............................................................Page 18856d not present in the dump file. Type ".hh dbgerr004" for details
..
.............................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000002c`cd930018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`3dffd6f0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffc89`d2f4e260=0000000000000050
2: kd> !analyze -v
Page 810dd8 not present in the dump file. Type ".hh dbgerr004" for details
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffff804e6f5f5f0, memory referenced.
Arg2: 0000000000000010, X64: bit 0 set if the fault was due to a not-present PTE.
	bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the processor decided the fault was due to a corrupted PTE.
	bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
	- ARM64: bit 1 is set if the fault was due to a write, clear if a read.
	bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff804e6f5f5f0, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------

Page 810dd8 not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Execute

    Key  : Analysis.CPU.mSec
    Value: 3421

    Key  : Analysis.Elapsed.mSec
    Value: 3420

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 577

    Key  : Analysis.Init.Elapsed.mSec
    Value: 7327

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 90

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x50

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Failure.Bucket
    Value: AV_X_(null)_BAD_IP_bindflt!BfCombinedMappingLookup

    Key  : Failure.Hash
    Value: {963e3010-0d18-2b2b-984a-0bc0125a8755}

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 16908288

    Key  : Hypervisor.Flags.ValueHex
    Value: 1020000

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  50

BUGCHECK_P1: fffff804e6f5f5f0

BUGCHECK_P2: 10

BUGCHECK_P3: fffff804e6f5f5f0

BUGCHECK_P4: 0

FILE_IN_CAB:  MEMORY 1 - Copy.DMP

READ_ADDRESS:  fffff804e6f5f5f0 

MM_INTERNAL_CODE:  0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  Lethal Company.exe

TRAP_FRAME:  fffffc89d2f4e500 -- (.trap 0xfffffc89d2f4e500)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffc886bd242e20
rdx=ffffc886b9beb4b0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804e6f5f5f0 rsp=fffffc89d2f4e698 rbp=0000000000000000
 r8=ffffd90330e36d60  r9=0000000000000000 r10=fffff8043bf09d80
r11=fffffc89d2f4e630 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
fffff804`e6f5f5f0 ??              ???
Resetting default scope

FAILED_INSTRUCTION_ADDRESS: 
+0
fffff804`e6f5f5f0 ??              ???

STACK_TEXT:  
fffffc89`d2f4e258 fffff804`3e03be2d     : 00000000`00000050 fffff804`e6f5f5f0 00000000`00000010 fffffc89`d2f4e500 : nt!KeBugCheckEx
fffffc89`d2f4e260 fffff804`3de24660     : 00000000`00000000 00000000`00000010 fffffc89`d2f4e580 00000000`00000000 : nt!MiSystemFault+0x1d88cd
fffffc89`d2f4e360 fffff804`3e00d458     : ffffc886`b2feda20 ffffc886`a74cc2a8 fffff804`3bf08060 fffff804`3bee3b18 : nt!MmAccessFault+0x400
fffffc89`d2f4e500 fffff804`e6f5f5f0     : fffff804`a6f5138a fffffc89`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
fffffc89`d2f4e698 fffff804`a6f5138a     : fffffc89`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff804`e6f5f5f0
fffffc89`d2f4e6a0 fffff804`a6f687b2     : fffffc89`d2f4e820 ffffc886`c4e1eb08 00000000`00000001 00000000`00000004 : bindflt!BfCombinedMappingLookup+0x9a
fffffc89`d2f4e720 fffff804`3bee64cb     : 00000000`00000000 00000000`00000000 ffffc886`c4e1ea20 ffffc886`b9bebce0 : bindflt!BfPreCreate+0x4e2
fffffc89`d2f4eac0 fffff804`3bee4603     : fffffc89`d2f4ec00 ffffc886`a7353df2 fffffc89`d2f4ee00 fffff804`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x36b
fffffc89`d2f4ebe0 fffff804`3bf19941     : fffffc89`d2f50000 fffffc89`d2f49000 00000000`00000000 00000000`00000000 : FLTMGR!FltpPassThroughFastIo+0xc3
fffffc89`d2f4ec60 fffff804`3e2ecd2f     : 00000000`000000f8 fffff804`3e5b7074 00000000`00000003 ffffc886`c48a8a20 : FLTMGR!FltpFastIoQueryOpen+0x131
fffffc89`d2f4ed00 fffff804`3e255bfe     : ffffc886`00000000 ffffc886`a73168f0 ffffc886`c48a8e50 fffffc89`00000000 : nt!IopQueryInformation+0x14f
fffffc89`d2f4ed60 fffff804`3e24a4c7     : ffffc886`a73168f0 ffffc886`a7316800 ffffc886`bb308010 ffffd903`13591301 : nt!IopParseDevice+0xfae
fffffc89`d2f4eed0 fffff804`3e252c6a     : ffffc886`bb308001 fffffc89`d2f4f138 fffffc89`00000040 ffffc886`a05f7560 : nt!ObpLookupObjectName+0x1117
fffffc89`d2f4f0a0 fffff804`3e2eb9b5     : 00000000`00000000 0000002c`cdad4f10 00007ffb`35523098 0000002c`cdad4ee0 : nt!ObOpenObjectByNameEx+0x1fa
fffffc89`d2f4f1d0 fffff804`3e011238     : ffffc886`b1b21080 00000000`00000078 ffffc886`b1b21080 00000219`b7513db0 : nt!NtQueryAttributesFile+0x1c5
fffffc89`d2f4f480 00007ffb`8a54d784     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
0000002c`cdad4ea8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`8a54d784


SYMBOL_NAME:  bindflt!BfCombinedMappingLookup+9a

MODULE_NAME: bindflt

IMAGE_NAME:  bindflt.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  9a

FAILURE_BUCKET_ID:  AV_X_(null)_BAD_IP_bindflt!BfCombinedMappingLookup

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {963e3010-0d18-2b2b-984a-0bc0125a8755}

Followup:     MachineOwner
---------

Windows for business | Windows Client for IT Pros | User experience | Other
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Docs 16,821 Reputation points
    2024-01-07T09:34:33.4433333+00:00

    Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    https://www.elevenforum.com/t/bsod-posting-instructions.103/

    Make sure that links are available without sign in.

    .

    .

    .

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    .

    .

    .


  2. Docs 16,821 Reputation points
    2024-01-08T10:02:28.4566667+00:00

    Please perform the following steps: (in sequence)

    1)Run Tuneup plus > post a share link into this thread using one drive, drop box, or google drive

    (bat scripts by default prompt AV software and require manual overrides)

    https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

    https://www.tenforums.com/bsod-crashes-debugging/162488-batch-files-use-bsod-debugging-2.html#post2177966

    https://www.tenforums.com/bsod-crashes-debugging/162488-batch-files-use-bsod-debugging.html#Part3

    .

    .

    2)Run Sea Tools for Windows Long Generic test (all drives) > post share links into this thread using one drive, drop box, or google drive

    https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/support-content/downloads/seatools/_shared/downloads/100869623_B.pdf

    https://www.seagate.com/content/dam/seagate/migrated-assets/www-content/support-content/downloads/seatools/_shared/downloads/SeaToolsWindowsInstaller.exe

    .

    .

    3)Run HD Tune (free or trial) (all drives) > post share links into this thread using one drive, drop box, or google drive

    https://www.hdtune.com/

    a)Health

    b)Benchmark

    c)Full error scan

    .

    .

    4)Open administrative command prompt and copy and paste:

    chkdsk /b /v

    Run these chkdsk switches on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: etc.

    .

    Make sure that the Windows drive runs overnight while sleeping and during the next day as needed.

    .

    C:\WINDOWS\system32>chkdsk /b /v

    The type of the file system is NTFS.

    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another

    process. Would you like to schedule this volume to be

    checked the next time the system restarts? (Y/N)

    .

    Type: Y

    Reboot as needed.

    WD_BLACK SN850X 4000GB

    ST2000DM008-2FR102

    Samsung SSD 870 EVO 1TB

    .

    .

    5)All of the above tests / steps can run while in safe mode

    .

    6)Sea Tools long generic test and HD Tune can run simultaneously and overnight while sleeping

    .

    .

    7)Run Memtest86+ for 8 or more passes.

    https://www.memtest.org/

    The more the passes the better the testing conditions.

    It sometimes takes passes into the 20s to find malfunctioning RAM.

    Just one error is a test fail and testing can be aborted.

    Take pictures > post share links into this thread using one drive, drop box, or google drive

    https://www.tenforums.com/tutorials/14201-memtest86-test-ram.html

    .

    .

    .

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    .

    .

    .

    0 comments No comments

  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Anonymous
    2024-01-09T03:30:43.2+00:00

    Hello,

    The PAGE_FAULT_IN_NONPAGED_AREA (50) error typically occurs when Windows cannot locate certain data in memory that it needs. This could happen due to hardware faults, corrupt system files, outdated or corrupt drivers, or faulty software.

    Firstly, I suggest that if the software named Lethal company.exe could be updated.

    Then please refer to the information below:
    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x50--page-fault-in-nonpaged-area

    If the issue still insists, try to open driver verifier to capture the trace.

    Best Regards,
    Hania Lian

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

  5. Jake Dobson 0 Reputation points
    2024-01-10T03:20:01.8333333+00:00

    Here is that link https://drive.google.com/drive/folders/1U-gB1djJpyU_G0LaI90PR5lppc2NlnAq?usp=drive_link

    I didnt bother with the seatools results since my HDD and E: drive kept aborting, and it didnt give any information

    I assume with the results of the memtest that I need to replace my memory, so I already started an exchange with my sticks

    For my HDD, I have been meaning to replace it with an SSD, so I will likely do that sooner than later. Please let me know if should take any more action, or if what I am doing is enough is hopefully fix the BSOD issue. Thank you so much!

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.