Windows 10 Help fixing a crash with .dmp analysis

  • Thread starter Thread starter Kitty259
  • Start date Start date
K

Kitty259

Hey everyone! So I have an issue with my computer right now, where there is a file folder that I can not delete, because trying to delete it causes my pc to crash. I get the BSOD with:

Stop code: SYSTEM_SERVICE_EXCEPTION

What failed: cldflt.sys


This was probably accidentally caused when my file explorer completely stopped responding while I was trying to move files and nothing I could do would stop the task. It was starting to run my CPU usage way up and I wanted to preserve my hardware, so I had no choice but to turn off the computer. I waited for like 30 minutes for it to do something, and it just wouldn't. The rest of windows was still responding, just not the moving files exception, since it couldn't find the files for some reason. Unfortunately, I believe this is what caused the system to start crashing while trying to delete this 'phantom folder.' Which says it doesn't take up any disk space, however still exists on my desktop and I can't get rid of it.


Quick note: This isn't happening while moving, deleting, or modifying any other files within my OneDrive, just this one. I already deleted the folder from my OneDrive online, yet the folder is still on my desktop, and when trying to delete it (before it crashes) says it is an online only folder. Also after a few crashes, it now won't even open that pop-up and just crashes when trying to click delete.


So, my troubleshooting thus far has been:

1. System Restore- I couldn't because this computer is new and I hadn't set up auto backup images yet...
2. Windows update- I figured this would work, I hadn't installed the new version of Windows (20H2 Update) yet, so I did and this is still happening.
3. I'm scared I'm going to mess something up by trying to replace the cldflt.sys file, as instructed by this post.

4. I used WinDbg Preview to open the dump file, to ask others (that are more experienced with this than me) what could be causing the crashes.

And here is what the analysis found:


[COLOR=rgba(30, 30, 30, 1)]SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff801696a4dfd, Address of the instruction which caused the bugcheck
Arg3: fffff402da1460f0, 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: 2483

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9887

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

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

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


DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff801696a4dfd

BUGCHECK_P3: fffff402da1460f0

BUGCHECK_P4: 0

CONTEXT: fffff402da1460f0 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.cxr 0xfffff402da1460f0)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]rax=00000000c0000225 rbx=ffffdb092a94aa30 rcx=0000000000000000
rdx=0000000000000001 rsi=fffff80169682170 rdi=0000000000000000
rip=fffff801696a4dfd rsp=fffff402da146af0 rbp=fffff402da146bf0
r8=00000000ffffffff r9=7fffdb0934214438 r10=fffff8010f3599a0
r11=ffffdb0933abe760 r12=0000000000000000 r13=ffffdb0932ec8290
r14=ffffdb0939abdbc0 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
cldflt!HsmpSetupContexts+0x130d:
fffff801`696a4dfd 49837f2003 cmp qword ptr [r15+20h],3 ds:002b:00000000`00000020=????????????????
Resetting default scope

BLACKBOXBSD: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxbsd[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXNTFS: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXPNP: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxpnp[/COLOR][COLOR=rgba(30, 30, 30, 1)])


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: explorer.exe

STACK_TEXT:
fffff402`da146af0 fffff801`696d723d : ffffdb09`00100180 ffffdb09`360bb010 00000000`00000000 fffff402`da146c80 : cldflt!HsmpSetupContexts+0x130d
fffff402`da146c50 fffff801`696bba1e : 00000000`00000000 fffff402`da146dc0 ffffdb09`39c73718 fffff402`da146f78 : cldflt!HsmiInfoPopulatePlaceholderOnRename+0x4d
fffff402`da146cc0 fffff801`696bb95a : ffffdb09`32ec8290 ffffffff`80002ac0 fffff402`da147028 00000000`00001620 : cldflt!HsmpRecurseDirectory+0xaa
fffff402`da146e50 fffff801`696680f6 : fffff402`da147028 ffffc78b`00200020 00000000`00000000 00000000`00000000 : cldflt!HsmpRecurseDirectoryCallout+0x4a
fffff402`da146eb0 fffff801`696bbc9a : 00000000`00000000 fffff402`da148000 fffff402`da141000 00000000`00000000 : cldflt!HsmExpandKernelStackAndCallout+0x4e
fffff402`da146ef0 fffff801`696a24dc : ffffdb09`32ec8290 ffffffff`80004788 00000000`00e18940 ffffc78b`00000410 : cldflt!HsmpRecurseDirectory+0x326
fffff402`da147080 fffff801`696a2d4b : 00000000`00000001 ffffdb09`33abe801 00000000`00000000 ffffdb09`00e18940 : cldflt!HsmiInfoRenameNotificationCallback+0x73c
fffff402`da147170 fffff801`696a1b50 : ffffc78b`00000005 ffffdb09`3ae4c970 00000000`00000030 ffffc78b`b3e46460 : cldflt!HsmpCldNotifyPreOperation+0x83
fffff402`da147240 fffff801`6969fdcf : ffffdb09`32ec8290 ffffdb09`2a94aa01 fffff402`da1475d8 00000000`00000000 : cldflt!HsmFltPreSetRenameInformation+0x1000
fffff402`da1474d0 fffff801`0e67608c : ffffc78b`b2e8f5f0 ffffdb09`39c73630 ffffdb09`32ec8290 ffffdb09`2a94ae70 : cldflt!HsmFltPreSET_INFORMATION+0x27f
fffff402`da147540 fffff801`0e675b37 : fffff402`da147700 fffff801`0f62b106 ffffdb09`26e41d00 00000000`00000000 : FLTMGR!FltpPerformPreCallbacksWorker+0x36c
fffff402`da147660 fffff801`0e674b46 : fffff402`da148000 fffff402`da141000 00000000`00000000 fffff402`da147780 : FLTMGR!FltpPassThroughInternal+0xc7
fffff402`da1476b0 fffff801`0e6748bb : ffffdb09`3ae4ddc0 00000000`00000000 ffffdb09`36f664b4 00000000`00000028 : FLTMGR!FltpPassThrough+0x1d6
fffff402`da147750 fffff801`0f252f55 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : FLTMGR!FltpDispatch+0x8b
fffff402`da1477b0 fffff801`0f27ae10 : 01d72c45`3dcd1f22 00000000`00000430 ffff0da2`6e04e73e 00000000`000000ac : nt!IofCallDriver+0x55
fffff402`da1477f0 fffff801`0f2539a4 : fffff402`da147a80 ffffdb09`379c5e60 00000000`0000000a ffffdb09`3ae4c970 : nt!IopCallDriverReference+0xd0
fffff402`da147860 fffff801`0f4075b5 : 00000000`00002e5c 00000000`0925e480 00000000`0c050050 00000000`000000ac : nt!NtSetInformationFile+0x514
fffff402`da147990 00007ffd`e274d0f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0925e3c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`e274d0f4


SYMBOL_NAME: cldflt!HsmpSetupContexts+130d

MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]cldflt

[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: cldflt.sys

IMAGE_VERSION: 10.0.19041.870

STACK_COMMAND: .cxr 0xfffff402da1460f0 ; kb

BUCKET_ID_FUNC_OFFSET: 130d

FAILURE_BUCKET_ID: 0x3B_c0000005_cldflt!HsmpSetupContexts

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {40558969-97b2-f05e-1690-358c4aa37600}[/COLOR]


If anyone can tell me what this means and how to fix it, it would be greatly appreciated. I really want to fix it, since it is quite annoying and I don't want it to lead to any other system failures. As far as I know, nothing else is crashing the system except attempting to delete that folder. Thank you to anyone who replies!

Continue reading...
 
Back
Top