Share via

BSOD error fix

Krisztian Kasoni 0 Reputation points
2024-11-22T11:23:36.0966667+00:00

Hello, i ve lately been getting a BSOD randomly. Sometimes it happens while i play games but rarely but most of the time if i don t open any game and just sit on youtube it keeps crashing my pc. Sometimes i get the BSOD with the message IRQL_NOT_LESS_OR_EQUAL or i don t get the bsod screen at all and it just keeps restarting my laptop.

Here's the last minidump file . Can someone help me fast ?

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- 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.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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


Loading Dump File [C:\Windows\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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff804`36200000 PsLoadedModuleList = 0xfffff804`36e2a900
Debug session time: Thu Nov 21 04:04:54.125 2024 (UTC + 2:00)
System Uptime: 0 days 3:30:36.758
Loading Kernel Symbols
...............................................................
.......Page 3c4dc1 not present in the dump file. Type ".hh dbgerr004" for details
.........................................................
................................................................
................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`365fe580 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffff8b07`a31630c0=000000000000007e
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80436475f5e, The address that the exception occurred at
Arg3: ffff8b07a31640b8, Exception Record Address
Arg4: ffff8b07a31638f0, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : AV.Dereference
    Value: NullClassPtr

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1812

    Key  : Analysis.Elapsed.mSec
    Value: 8774

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x7e

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x7e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x7e

    Key  : Failure.Bucket
    Value: AV_ndis!ndisReferencePackage

    Key  : Failure.Hash
    Value: {d394b50a-1528-1d87-bd4e-0a848459981e}

    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:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80436475f5e

BUGCHECK_P3: ffff8b07a31640b8

BUGCHECK_P4: ffff8b07a31638f0

FILE_IN_CAB:  MEMORY.DMP

FAULTING_THREAD:  ffff8f81ce91f040

EXCEPTION_RECORD:  ffff8b07a31640b8 -- (.exr 0xffff8b07a31640b8)
ExceptionAddress: fffff80436475f5e (nt!MiLockPagableImageSection+0x00000000000000be)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000014
Attempt to read from address 0000000000000014

CONTEXT:  ffff8b07a31638f0 -- (.cxr 0xffff8b07a31638f0)
rax=0000000000000000 rbx=fffff8043aa00318 rcx=00000000000000f8
rdx=fffff8043aa00318 rsi=fffff8043aa00000 rdi=ffff8f81c1069c60
rip=fffff80436475f5e rsp=ffff8b07a31642f0 rbp=0000000000000001
 r8=0000000000000000  r9=ffff8b07a3164328 r10=0000000000000000
r11=ffff88c462311000 r12=0000000000000000 r13=ffff8f81cf4cb1a0
r14=ffff8f81cf4cb1a0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!MiLockPagableImageSection+0xbe:
fffff804`36475f5e 0fb74814        movzx   ecx,word ptr [rax+14h] ds:002b:00000000`00000014=????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

READ_ADDRESS: unable to get nt!PspSessionIdBitmap
 0000000000000014 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000014

EXCEPTION_STR:  0xc0000005

STACK_TEXT:  
ffff8b07`a31642f0 ffff8b07`a31643c0     : 00000000`00000008 ffffdb09`1ba9f450 ffff8f81`cf4cb1a0 ffff8b07`a31644d0 : nt!MiLockPagableImageSection+0xbe
ffff8b07`a3164340 00000000`00000008     : ffffdb09`1ba9f450 ffff8f81`cf4cb1a0 ffff8b07`a31644d0 fffff804`3aae4090 : 0xffff8b07`a31643c0
ffff8b07`a3164348 ffffdb09`1ba9f450     : ffff8f81`cf4cb1a0 ffff8b07`a31644d0 fffff804`3aae4090 fffff804`3685ea7e : 0x8
ffff8b07`a3164350 ffff8f81`cf4cb1a0     : ffff8b07`a31644d0 fffff804`3aae4090 fffff804`3685ea7e 00000000`00000000 : 0xffffdb09`1ba9f450
ffff8b07`a3164358 ffff8b07`a31644d0     : fffff804`3aae4090 fffff804`3685ea7e 00000000`00000000 ffff8f81`cf4c4a20 : 0xffff8f81`cf4cb1a0
ffff8b07`a3164360 fffff804`3aae4090     : fffff804`3685ea7e 00000000`00000000 ffff8f81`cf4c4a20 ffff8f81`c750f010 : 0xffff8b07`a31644d0
ffff8b07`a3164368 fffff804`3685ea7e     : 00000000`00000000 ffff8f81`cf4c4a20 ffff8f81`c750f010 00000000`00000000 : ndis!ndisPkgs
ffff8b07`a3164370 fffff804`3aa06da5     : ffff8f81`cf4c000e ffff8b07`a31643f8 00000000`00000008 00000000`00000000 : nt!MmLockPagableSectionByHandle+0xe
ffff8b07`a31643a0 fffff804`3ab3be7f     : ffffdb09`1dad1790 ffff8b07`a31644d0 ffff8f81`cf4c4a20 ffff8f81`c750f010 : ndis!ndisReferencePackage+0x29
ffff8b07`a31643d0 fffff804`3ab2153c     : ffffdb09`00000000 fffff804`3aae4048 ffff8f81`cf4cb1a0 ffff8f81`cf4cb1a0 : ndis!ndisUnbindProtocolOpen+0x8f
ffff8b07`a3164550 fffff804`3ab12cc4     : 00000000`00000000 ffff8b07`a31646a0 ffff8f81`cf4cb1a0 ffff8f81`cf4cc590 : ndis!ndisUnbindEachProtocolOpenOnMiniport+0xcc
ffff8b07`a31645a0 fffff804`3ab05708     : ffff8f81`cf4cb1a0 ffff8f81`cf4cb1a0 ffff8f81`cf4cc608 ffff8f81`cf4cc590 : ndis!Ndis::BindEngine::Iterate+0xd510
ffff8b07`a3164720 fffff804`3aafedce     : ffff8f81`cf4cc590 ffff8b07`a3164a00 00000000`00000000 00000000`00000000 : ndis!Ndis::BindEngine::UpdateBindings+0x98
ffff8b07`a3164770 fffff804`3aafee34     : ffff8f81`cf4cc590 00000000`00000000 ffff8c42`ff6250e6 fffff804`3aa1912d : ndis!Ndis::BindEngine::DispatchPendingWork+0x76
ffff8b07`a31647a0 fffff804`3aafc33c     : ffff8f81`cf4cb1a0 ffff8b07`a3164a80 ffff8f81`c778ede0 00000000`00000000 : ndis!Ndis::BindEngine::ApplyBindChanges+0x54
ffff8b07`a31647f0 fffff804`3aa13e97     : ffff8f81`cf740e70 ffff8f81`cf4cb1a0 ffff8f81`cf4cb1a0 ffff8f81`c778ede0 : ndis!ndisIssueNetEventSetPowerEvent+0x8c
ffff8b07`a31648f0 fffff804`3aa13e2d     : 00000000`00000000 ffff8f81`cf4cb1a0 ffff8f81`cf4cb1a0 fffff804`3aafec72 : ndis!ndisPrepForLowPowerCommon+0x3b
ffff8b07`a31649e0 fffff804`3aa14989     : 00000000`00000005 ffff8f81`c778ede0 ffff8f81`cf4cb1a0 fffff804`3aa0dfa8 : ndis!ndisPrepForLowPower+0x1d
ffff8b07`a3164a30 fffff804`3aa1522e     : 00000000`00000000 ffff8f81`00000004 ffff8f81`cf4cb1a0 ffff8f81`c778eef8 : ndis!ndisSetSystemPower+0x191
ffff8b07`a3164ab0 fffff804`3aa16634     : ffff8f81`c778ede0 ffff8f81`cf0882a0 ffff8f81`c778eef8 ffff8f81`cf4cb1a0 : ndis!ndisSetPower+0x10a
ffff8b07`a3164b10 fffff804`3659cf69     : ffff8f81`ce91f040 ffff8b07`a3164bf0 ffff8f81`c778ede0 ffff8f81`cf4cb050 : ndis!ndisPowerDispatch+0x114
ffff8b07`a3164b70 fffff804`3655a025     : ffffffff`fa0a1f00 fffff804`3659cd90 ffff8f81`d02f6f30 00000000`00000122 : nt!PopIrpWorker+0x1d9
ffff8b07`a3164c10 fffff804`36607588     : ffff9f80`b0900180 ffff8f81`ce91f040 fffff804`36559fd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff8b07`a3164c60 00000000`00000000     : ffff8b07`a3165000 ffff8b07`a315f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  ndis!ndisReferencePackage+29

MODULE_NAME: ndis

IMAGE_NAME:  ndis.sys

STACK_COMMAND:  .cxr 0xffff8b07a31638f0 ; kb

BUCKET_ID_FUNC_OFFSET:  29

FAILURE_BUCKET_ID:  AV_ndis!ndisReferencePackage

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {d394b50a-1528-1d87-bd4e-0a848459981e}

Followup:     MachineOwner
---------
Windows 10 Security
Windows 10 Security
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Security: The precautions taken to guard against crime, attack, sabotage, espionage, or another threat.
2,940 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Wesley Li 10,325 Reputation points
    2024-11-22T18:53:12.3366667+00:00

    Hello

    The SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) error is a common BugCheck that usually indicates a system thread generated an exception that was not caught by the error handler. This specific error often points to a problematic driver or function. In your case, the exception code 0xc0000005 suggests an access violation, and the address fffff80436475f5e pinpoints the location where the exception occurred, which is within the ndis.sys module.

     

    Here are some steps you can take to troubleshoot and resolve this issue:

     

    Identify the Faulty Driver: The exception address can help identify the driver or function causing the problem. In your case, it points to ndis.sys, which is related to network drivers.

     

    Update Drivers: Ensure all hardware drivers are up-to-date, especially those related to network components. Updating the ndis.sys driver might resolve the issue.

     

    Check for Memory Issues: Run memory diagnostic tools like MemTest86 to check for RAM errors. Memory issues can sometimes cause access violations.

     

    Boot in Safe Mode: If the system is unstable, boot into Safe Mode to perform troubleshooting steps. Safe Mode loads only essential drivers, which can help isolate the problematic driver.

     

    Use System Restore: If the problem started recently, you can use System Restore to revert the system to a previous state when it was stable.

     

    Check for Windows Updates: Ensure your system is up-to-date with the latest Windows updates. Sometimes, Microsoft releases patches that fix issues with specific drivers or system functions.

    0 comments

Your answer

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