Acer Swift X (SFX14-41G-R40L) BSOD: KMODE_EXCEPTION_NOT_HANDLED

Hey all, new user here.

My Acer Swift X started acting weird about a week or two ago, when the wifi driver was disabled and I could not connect to wifi. I reset the laptop but the issue was not fixed until I fixed it manually via downloading the driver from the website.

Recently, after I downloaded a driver for my Wacom drawing tablet, the laptop went into a BSOD. I removed the driver and it worked fine for a while before going into another BSOD. Now I am unable to find the issue since the BSOD does not state any error code, just KMODE_EXCEPTION_NOT_HANDLED.

Long story short, I encountered a BSOD on my Acer Swift X and I am not sure of the issue. I’ve been using it for almost 2 months without any issue. Using it mainly for games (and schoolwork in the future).

Thanks

Accepted answers

All comments

ILikedogs4288

As a addon to the post, I’ve reset the laptop everytime it goes into BSOD and it worked fine for a while as I redownloaded the programs I used. It will go into BSOD the next day.

dawless

Hey, I've been having the exact same issue too. Just wanted to ask what version of windows you are using, is it 10 or 11?
This error is happening on Windows 11 for me and I'm going to downgrade to Windows 10 to see if it will fix the issue.

billsey

KMODE_EXCEPTION_NOT_HANDLED is almost always driver related. Can you take a picture of the actual BSOD? They usually have some more data in the fine print. If not let's look into doing some debug on the mini-dump file.

dawless

Image: https://us.v-cdn.net/6029997/uploads/editor/it/6h9t8jcuwokh.jpg

How do I get into the mini-dump file?

billsey

There is a utility from Microsoft called WinDbg that will analyze the crash files for you. The link will help step you through the process.

dawless

*******************************************************************************
*                                                                             *
*                        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: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, 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  : Analysis.CPU.mSec
    Value: 7452

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 29796

    Key  : Analysis.Init.CPU.mSec
    Value: 702

    Key  : Analysis.Init.Elapsed.mSec
    Value: 6439

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 83

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1


FILE_IN_CAB:  032422-10281-01.dmp

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

BLACKBOXNTFS: 1 (!blackboxntfs)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:  
ffffd18f`c35ccf28 fffff805`4e4d88a9     : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffffd18f`c35ccf30 fffff805`4e4291ce     : 00000000`00001000 ffffd18f`c35cd7f0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1aa269
ffffd18f`c35cd610 fffff805`4e4251da     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x10e
ffffd18f`c35cd7f0 00000000`00000000     : fffff805`5394da3e 00000000`ffffffff fffff805`53987015 00000000`00000000 : nt!KiPageFault+0x41a


SYMBOL_NAME:  nt!KiDispatchException+1aa269

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.556

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1aa269

FAILURE_BUCKET_ID:  AV_nt!KiDispatchException

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {00781d15-b897-afab-75cd-f83221cbf387}

Followup:     MachineOwner
---------

2: kd> lmvm nt
Browse full module list
start             end                 module name
fffff805`4e000000 fffff805`4f047000   nt         (pdb symbols)          C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\DCC3FFCBE9C59B5668C1DE2BD6CBC6DF1\ntkrnlmp.pdb
    Loaded symbol image file: ntkrnlmp.exe
    Mapped memory image file: C:\ProgramData\Dbg\sym\ntkrnlmp.exe\50C56FA51047000\ntkrnlmp.exe
    Image path: ntkrnlmp.exe
    Image name: ntkrnlmp.exe
    Browse all global symbols  functions  data
    Image was built with /Brepro flag.
    Timestamp:        50C56FA5 (This is a reproducible build file hash, not a timestamp)
    CheckSum:         00B3C56B
    ImageSize:        01047000
    File version:     10.0.22000.556
    Product version:  10.0.22000.556
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        1.0 App
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   10.0.22000.556
        FileVersion:      10.0.22000.556 (WinBuild.160101.0800)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.

billsey

Not a lot there that helps, the kernel is pretty far down the stack but should have been pretty resistant to driver issues. You might just want to backup your data and do a fresh install of the factory image, then the updates since then. I'd guess something is corrupted, but without a smoking gun it's tough to tell what it is.