Computer issue when shutting down Carbide Motion

Have an unusual problem with Carbide Motion. After I finish my project, if I turn off the CNC (Shapeoko) with Carbide Motion still tied to the CNC, I get an error message on my computer and it shuts down. This causes me to lose any unsaved data on other programs that may be minimized. But if I shut Carbide Motion down first, then turn the CNC off, no problem. I do this on a regular basis now to avoid data loss. Has anyone else experienced this?

unusual problem indeed. What does the error message say ?

It’s a Windows generated error message, something to the effect that Windows has experienced a problem and needs to shut down. Been dealing with this for quite some time. The first laptop that I was using had this problem and now with a new laptop, still getting the same error. With the way I now back out of a project, (shut the software down FIRST, then the CNC machine), I get around the problem, so it’s not urgent. Just curious about what’s causing this.

Have you tried checking the system event viewer to get information on what is causing the shutdown ?

Didn’t think of that, but it’s my experience that the messages in the event viewer are jibberish to me. Will look and see it I can get some useful info out of the log.

If you are using windows 10, the window showing the event should have a link you can go to and get more understandable information.

Am using 10, so will try that. Thanks.

What are you using for a computer?

Here is the jibberish that the dmp file created when the computer shut down.
Microsoft (R) Windows Debugger Version 10.0.22415.1003 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.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff80005000000 PsLoadedModuleList = 0xfffff80005c2a270
Debug session time: Thu Oct 28 14:00:18.219 2021 (UTC - 4:00)
System Uptime: 4 days 3:31:46.622
Loading Kernel Symbols

Loading User Symbols
PEB is paged out (Peb.Ldr = 0000000000987018). Type ".hh dbgerr001" for details Loading unloaded module list .............................................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff800053f71b0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffcb0e`91ff0650=000000000000010d
0: kd> !analyze -v

  •                                                                         *
  •                    Bugcheck Analysis                                    *
  •                                                                         *

The Kernel-Mode Driver Framework was notified that Windows detected an error
in a framework-based driver. In general, the dump file will yield additional
information about the driver that caused this BugCheck.
Arg1: 000000000000000a, A fatal error has occurred while processing a request on the
Arg2: ffffcb0e91ff06b0, Pointer to a WDF_QUEUE_FATAL_ERROR_DATA structure.
Arg3: 0000000000000000, Reserved.
Arg4: ffffa70ced85e9a0, Reserved.

Debugging Details:

Page 26f7f not present in the dump file. Type “.hh dbgerr004” for details
Page 26f7f not present in the dump file. Type “.hh dbgerr004” for details


Key  : Analysis.CPU.mSec
Value: 8093

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 12359

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

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

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

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1



BUGCHECK_P2: ffffcb0e91ff06b0


BUGCHECK_P4: ffffa70ced85e9a0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)


PROCESS_NAME: carbidemotion.exe

ffffcb0e91ff0648 fffff80009a08920 : 000000000000010d 000000000000000a ffffcb0e91ff06b0 0000000000000000 : nt!KeBugCheckEx
ffffcb0e91ff0650 fffff80009a257d9 : ffffcb0e91ff06b0 fffff80000000001 0000000000000300 0000000000000000 : Wdf01000!FxVerifierBugCheckWorker+0x24 [minkernel\wdf\framework\shared\object\fxverifierbugcheck.cpp @ 68]
ffffcb0e91ff0690 fffff80009a23bbf : ffffa70ceedb6de0 fffff8000685f000 fffff80002bac180 000000006e657645 : Wdf01000!FxIoQueue::FatalError+0x35 [minkernel\wdf\framework\shared\irphandlers\io\fxioqueue.cpp @ 6375]
ffffcb0e91ff06e0 fffff80006864c24 : ffffa70ced4f7be0 fffff8000685f000 fffff8000685d4a8 ffffa70cec91a080 : Wdf01000!imp_WdfIoQueuePurgeSynchronously+0x4f [minkernel\wdf\framework\shared\irphandlers\io\fxioqueueapi.cpp @ 1202]
ffffcb0e91ff0710 fffff800099d4302 : ffffa70cee621070 ffffa70cf065e7b0 0000000000000000 0000000020707249 : usbser!UsbSerEvtDeviceFileCleanup+0x114
ffffcb0e91ff0750 fffff800099ba866 : ffffa70cec8fda50 0000000000000000 0000000000000000 ffffa70ced78a4d0 : Wdf01000!FxPkgGeneral::Dispatch+0x1d672 [minkernel\wdf\framework\shared\irphandlers\general\fxpkggeneral.cpp @ 793]
ffffcb0e91ff0820 fffff8000528f6f5 : ffffa70cec91a080 0000000000000000 ffffa70cec8fda50 ffffa70ceddb0950 : Wdf01000!FxDevice::DispatchWithLock+0x156 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
ffffcb0e91ff0880 fffff80005675d4a : 0000000000000000 ffffa70ceddb0950 0000000000000000 0000000000040000 : nt!IofCallDriver+0x55
ffffcb0e91ff08c0 fffff800055f39cf : ffffa70cec91a080 0000000000000001 ffffe18a00000000 ffffa70ceddb0920 : nt!IopCloseFile+0x17a
ffffcb0e91ff0950 fffff800055f79ac : 000000000000066c 000000000100e9a8 ffffcb0e91ff0aa8 0000000000000000 : nt!ObCloseHandleTableEntry+0x51f
ffffcb0e91ff0a90 fffff80005408bb8 : ffffa70ceebd9000 0000000000000000 ffffcb0e91ff0b80 ffffa70cf19d8ef0 : nt!NtClose+0xec
ffffcb0e91ff0b00 0000000077811cfc : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000000100f2b8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x77811cfc

SYMBOL_NAME: usbser!UsbSerEvtDeviceFileCleanup+114


IMAGE_NAME: usbser.sys

STACK_COMMAND: .thread ; .cxr ; kb


FAILURE_BUCKET_ID: 0x10D_a_usbser!UsbSerEvtDeviceFileCleanup

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release


OSNAME: Windows 10

FAILURE_ID_HASH: {df5d7f30-5191-cff4-5ba6-668658dc3183}

Followup: MachineOwner

The bugcheck is quite informative. The driver for communicating over USB (usbser.sys) is accessing an area of memory that has been paged out - it was written to disk to make room for something else.

This is a built in driver to Windows, not something supplied by Carbide 3D, so this is a Windows bug.

Since it’s been paged out, this means you are low on RAM. Closing Carbide Motion first pulls that area of memory back into RAM, and then shuts down the serial connection, so the bad access doesn’t occur.

The fault analysis is sent automatically to MS, it will likely get fixed in a future update.


Thank you very much. That all makes sense now. The laptop I am using is a “low end” HP with only 4 gigs of ram. It was the most inexpensive laptop I could find for use on my CNC. Other than the discussed problem, it works as long as I don’t ask it to do much else at the same time. Again, thanks.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.