Share via

laptop crashes regularly

P N 0 Reputation points
2026-02-07T16:46:17.7533333+00:00

Hello,

My PC crashes regularly and I can't find the cause.

I did all the Windows updates and drivers I foun.

I did a full memory check with Memtest86, and a full scan of the hard drive. No problem.

I have several DUMs but I'm not advanced enough to find the cause in the dumps Can you help me please?

Thank you

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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: fffff803849b9a15, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ExceptionRecord                               ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: ContextRecord                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : AV.Page.Virtual
    Value: 0xffffffffffff0000

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 3656

    Key  : Analysis.Elapsed.mSec
    Value: 5402

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Failure.Bucket
    Value: AV_VRF_nt!KiIpiInterrupt

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff803849b9a15

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x6a9a15

    Key  : Failure.Hash
    Value: {7a9b6851-3bcb-8a55-ab28-1e39c9b4fa81}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Stack.Pointer
    Value: PRCBException

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 1.68.0.0


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff803849b9a15

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB:  020626-26734-01.dmp

FAULTING_THREAD:  ffff9d892d7b8280

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff803852d44c0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff 

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_PAGED_CODE: 
nt!KiIpiInterrupt+2f5
fffff803`849b9a15 0f2945f0        movaps  xmmword ptr [rbp-10h],xmm0

STACK_TEXT:  
ffffcf81`e91548b8 fffff803`846e950b     : 00000000`0000001e ffffffff`c0000005 fffff803`849b9a15 00000000`00000000 : nt!KeBugCheckEx
ffffcf81`e91548c0 fffff803`849b23d2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x92b
ffffcf81`e9154fb0 fffff803`849b23a0     : fffff803`849c623e ffffcf81`e9132180 ffffcf81`e913aa10 ffff8983`8d899850 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffff8983`8d899728 fffff803`849c623e     : ffffcf81`e9132180 ffffcf81`e913aa10 ffff8983`8d899850 fffff803`845608bb : nt!KiExceptionDispatchOnExceptionStackContinue
ffff8983`8d899730 fffff803`849c0f25     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x13e
ffff8983`8d899910 fffff803`849b9a15     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x365
ffff8983`8d899aa8 00000000`00000801     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x2f5
00000000`00040286 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x801


SYMBOL_NAME:  nt!KiIpiInterrupt+2f5

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.7623

STACK_COMMAND: .process /r /p 0xfffff803852def00; .thread 0xffff9d892d7b8280 ; kb

BUCKET_ID_FUNC_OFFSET:  2f5

FAILURE_BUCKET_ID:  AV_VRF_nt!KiIpiInterrupt

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7a9b6851-3bcb-8a55-ab28-1e39c9b4fa81}

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


Windows for home | Windows 11 | Devices and drivers
{count} votes

2 answers

Sort by: Most helpful
  1. Ivan B 100.6K Reputation points Independent Advisor
    2026-02-07T17:17:53.4433333+00:00

    Hi ,

    If it is a laptop or desktop, if possible, could you provide the laptop model or your desktop configuration?

    Access the c:\windows\minidump folder, copy the files to your desktop, then upload them to OneDrive or Google Drive and post the link here for analysis.

    Thanks


  2. 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

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.