Occasional Bluescreens

greg_stelmack · ‎08-30-2025

Over the last month or two I've been getting occasional bluescreens while using Fusion 360. I haven't been doing much else, so it's hard to know if these would occur when not using it. I finally decided to check the windows problem report lists and use WinDbg to open the dmp file and see what driver was causing it. However it cannot find a driver when using KiBugCheckDriver, and !analyze -v thinks it is coming from Fusion. Reporting it in case there is something going on, although also willing to acknowledge I could have something going on with the machine (13th gen Core i9 processor, or could be something with RAM).

nt!KeBugCheckEx:
fffff801`adafec10 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffe081`68c86450=000000000000003b
10: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000098`c202e018).  Type ".hh dbgerr001" for details
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff801ad87af4d, Address of the instruction which caused the BugCheck
Arg3: ffffe08168c86d90, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1046

    Key  : Analysis.Elapsed.mSec
    Value: 3935

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_nt!ExpSetTimerObject

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

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

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

    Key  : Failure.Hash
    Value: {31c0275a-852c-faf0-83a4-fbd606fe9cd8}


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff801ad87af4d

BUGCHECK_P3: ffffe08168c86d90

BUGCHECK_P4: 0

FILE_IN_CAB:  083025-12718-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffce8e32948080

CONTEXT:  ffffe08168c86d90 -- (.cxr 0xffffe08168c86d90)rax=ffffce8e32111878 rbx=fffffffff00574c0 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=ffffce8e32111770
rip=fffff801ad87af4d rsp=ffffe08168c877e0 rbp=ffffe08168c87aa0
 r8=0000000000000001  r9=0000000000000000 r10=fffff8013da6a180
r11=fffff8013da6e280 r12=0000000000000000 r13=0000000000000001
r14=ffffce8e28cca080 r15=fffff801ad600000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!ExpSetTimerObject+0xeed:
fffff801`ad87af4d 48394208        cmp     qword ptr [rdx+8],rax ds:002b:00000000`00000008=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Fusion360.exe

STACK_TEXT:  
ffffe081`68c877e0 fffff801`ad879c78     : 00000000`00000000 00000000`00000000 00000000`0000071c 00000000`00000001 : nt!ExpSetTimerObject+0xeed
ffffe081`68c87910 fffff801`adcb7c55     : ffffce8e`32948080 00000098`c4fffa18 ffffe081`68c879c8 00000000`00000000 : nt!NtSetTimer+0x158
ffffe081`68c879b0 00007ffd`344a34e4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000098`c4fff9f8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`344a34e4


SYMBOL_NAME:  nt!ExpSetTimerObject+eed

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.4946

STACK_COMMAND: .cxr 0xffffe08168c86d90 ; kb

BUCKET_ID_FUNC_OFFSET:  eed

FAILURE_BUCKET_ID:  AV_nt!ExpSetTimerObject

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {31c0275a-852c-faf0-83a4-fbd606fe9cd8}

Followup:     MachineOwner

TimelesslyTiredYouth · ‎08-30-2025

I'm usually okay with code, but this really dumbfounded me, Windows hates making things easy for people to understand ISTG.

From what I see, that SYSTEM_SERVICE_EXCEPTION 0x3B while Fusion360.exe was running usually points to either a software hiccup or a driver/kernel issue.

Important -> Everything I say now is either researched based, me asking colleges for their comment, or prior knowledge that I have long left in the past.

Even though WinDbg didn’t flag a driver, GPU drivers (Intel or NVIDIA) are the usual suspects for 3D apps, and RAM can also cause this. I’d try updating Fusion 360, making sure all GPU drivers are current, running a memory test, and checking Windows updates. If it keeps happening, maybe try Fusion in safe mode or with add-ins off to see if it stabilizes.

If it does work in Safe mode, then I'd advice to you to go into the Boot up settings and manually add one driver in at a time that isn't compulsory and see if that causes an issue with Fusion as I don't think this is something wrong with your system as a i9 in a PC is quite strong (I'm presuming PC as it's more common unless you have a Zephyrus or gaming laptop. Can I ask for your specifications, like the GPU, and RAM specifically.

Just a few suggestions...

Ricky

greg_stelmack · ‎08-30-2025

I do keep my drivers pretty up-to-date although I’ll double-check everything. Running a memory check right now. I mention the 13th gen Core i9 because I know there have been some failures, I updated the BIOS to the fix versions a while ago but I’ve also had the processor for a few years. My system is core i9-13900k, 64GB DDR5, gigabyte z790 Gaming X AX motherboard, gigabyte nvidia 4090 GPU, all 2 years old. I’ll keep doing the typical troubleshooting, I mostly posted here when WinDbg did not point a finger at a driver and instead was indicating a null pointer in a timer, just in case there was something going on in Fusion. Definitely lots of other possible culprits.

greg_stelmack · ‎08-31-2025

Finally had it happen outside of Fusion, so definitely a false alarm here. Drivers are all up to date, memory checker was clean, swapping RAM now, then next step is a clean windows install. If THAT fails, I either need to go back to an older driver of something (likely starting with the GPU), or I need a new CPU. Thanks for the input here.

TimelesslyTiredYouth · ‎08-31-2025

You could try a window restore, and go back to before the last major update to see if that has anything to do with it.

Good luck

Ricky

Community

Occasional Bluescreens

Occasional Bluescreens

Occasional Bluescreens