Bluescreen on reboot of Acer Swift X (SFX14-41G-R7F3)

My wife's laptop is having blue screen everytime or almost everytime she restart. And secondary, when waking up from sleep bluetooth mouse or Wifi might not work. Means she has to restart -> bluescreen.

I think it's probably the same problem as this: https://community.acer.com/en/discussion/662892/acer-swift-x-sfx14-41g-r40l-bsod-kmode-exception-not-handled. But that site does not finish loading for me (neither Chrome or Edge) so I can post there. Pity, would be nice to know if a solution was found.

Here is the output of WinDbg:

*******************************************************************************

*                                                                             *
*                        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: 2452

    Key : Analysis.DebugAnalysisManager
    Value: Create

    Key : Analysis.Elapsed.mSec
    Value: 5241

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

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

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

    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: MEMORY.DMP

DUMP_FILE_ATTRIBUTES: 0x1800

BUGCHECK_CODE: 1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

PROCESS_NAME: System

TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:
fffff38d`c3eb2f28 fffff801`4a4d88a9     : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
fffff38d`c3eb2f30 fffff801`4a4291ce     : 00000000`00001000 fffff38d`c3eb37f0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1aa269
fffff38d`c3eb3610 fffff801`4a4251da     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x10e
fffff38d`c3eb37f0 00000000`00000000     : fffff801`5aa4da3e ffff9681`bf0c0180 fffff801`5aa87015 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

I noticed in the event viewer that the crash is almost precedet by a few other events:

Image: https://us.v-cdn.net/6029997/uploads/editor/u5/tf0wep70xuvx.png

Seems to be always this order and the timing is suspiciously close. Anything else I can check? I don't mind doing some digging. Not a windows guy here, as I said its my wife's laptop, personally I'm using Linux based OS's since +15 years. But I can read up on this stuff of course.

I think we'll try now to reset the windows to factory state, disable updates, install everthing she wants, then do a recovery point. Then allow updates again and see where it goes. At least I hope its possible to do this, not very firm on the windows features here xD.

Any help is appreciated. Thanks in adavance!

Accepted answers

Johannes1234123

billsey said:

Let us know what they find wrong with it...

Since it came back there have been no more BSOD. Report does not really say what the issue was. It just list what they did:

Restore windows OS
Flash BIOS
Update the Wifi driver (Mediatek)

I guess it was the Wifi driver, but I'll never know. Hope the problem does not come back.

All comments

Johannes1234123

I just realized I posted this in the wrong category. Its switch, not swift, sorry. Can moderators move it? Or I create it again there. I also have the same issue of loading the site with this post. But I figured out I can write on another Laptop that has firefox. Still the site is very slow.

billsey

I've asked the moderators to move it for you, but they likely won't get to it until Monday... Kernel mode failures are almost always caused by drivers, less often by applications. Do you have any non-standard hardware connected?

Johannes1234123

No, nothing. Today I reset the laptop 4 times, trying all combinations of

Reset, keep data
Complete factory reset
Reset using local
Reset with download of windows from internet

In each case I also disabled windows updates as soon as the assistant was done. Only software that was installed before it happened was Steam and Dota2.

The problem happened again in each case. Far as I can tell it happens after the laptop has gone to sleep and one tries to reboot.

Johannes1234123

Not sure what is wrong with this forum's interface, it is incredibly unresponsive. Acer mining crypto using my browser or what xD.

billsey

What drive is shown in the details for the volmgr error? If you go into Windows Updates, then Optional updates, is there an entry for a new driver?

Johannes1234123

Unfortunately I can't check anymore. I tried resetting the laptop one more time. Now its stuck in BSOD loop with Page Fault in NonPaged area. I'll send it in for repair. Its new, bought one month ago. This shouldn't happen.

billsey

Let us know what they find wrong with it...

Easwar

Hi @Johannes1234123,

Reset this PC and keep my files
1. Shutdown the unit. Press and hold alt+F10 key. Then turn ON the unit.
2. You will get a blue screen. Choose the option troubleshoot.

3 Ways to Reset Acer Laptop to Factory Settings without Password

3. Select Keep my files to refresh your PC and reinstall your operating system without removing your personal files. Click Next to continue. Important If you have apps installed on your PC, they will be removed.
4. Resetting the PC will reinstall Windows, change settings back to their factory defaults and remove all preinstalled apps and programs without removing your personal files. Click Reset to continue.
5. You will be shown the reset progress on the screen. The screen will turn off during the reset process.
6. The screen will turn back on when it is installing Windows. Your PC will restart several times during the reset process.
7. Follow the process until it completes.
8. When your PC has completed the reset process, Windows will have been reset back to its factory default settings without removing your personal files.