Blue screen

It seems its erroring on Clfs.sys file which is a windows OS file. However, lets try to get some more info.

Download BlueScreenView
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
 
==================================================
Dump File : 041422-13500-01.dmp
Crash Time : 14.04.2022 18:31:15
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a023e6`713fd737
Parameter 2 : b3b7306c`c3be1fef
Parameter 3 : fffff805`838a8f80
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f7620
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f7620
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041422-13500-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 19041
Dump File Size : 1 872 332
Dump File Time : 14.04.2022 18:32:11
==================================================

==================================================
Dump File : 041322-12984-01.dmp
Crash Time : 13.04.2022 17:02:07
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a39fbfe0`e7e8d4fe
Parameter 2 : b3b6cc67`3a671db6
Parameter 3 : fffff807`33aa8f80
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f7620
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f7620
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041322-12984-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 19041
Dump File Size : 1 876 420
Dump File Time : 13.04.2022 17:03:03
==================================================

==================================================
Dump File : 041222-13281-02.dmp
Crash Time : 12.04.2022 20:24:56
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a3a000e8`20e8d4ef
Parameter 2 : b3b70d6e`73671da7
Parameter 3 : fffff805`53ca8f80
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f7620
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f7620
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041222-13281-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 19041
Dump File Size : 1 808 044
Dump File Time : 12.04.2022 20:25:51
==================================================

==================================================
Dump File : 041222-13281-01.dmp
Crash Time : 12.04.2022 15:34:55
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a39fe2db`ad3e2bff
Parameter 2 : b3b6ef61`ffbc74b7
Parameter 3 : fffff802`0f6a8f80
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f7620
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f7620
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041222-13281-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 19041
Dump File Size : 1 830 100
Dump File Time : 12.04.2022 15:35:52
==================================================

==================================================
Dump File : 041222-13062-01.dmp
Crash Time : 12.04.2022 13:47:05
Bug Check String :
Bug Check Code : 0x00000109
Parameter 1 : a39fe15e`ff08d805
Parameter 2 : b3b6ede5`518720bd
Parameter 3 : fffff806`350a8f80
Parameter 4 : 00000000`00000001
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+3f7620
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+3f7620
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041222-13062-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 19041
Dump File Size : 1 817 764
Dump File Time : 12.04.2022 13:48:01
==================================================
 
Please navigate to this directory.

C:\Windows\Minidump

Then copy and paste these files to a new folder on your desktop.

C:\Windows\Minidump\041422-13500-01.dmp
C:\Windows\Minidump\041322-12984-01.dmp

Then zip up that folder and attach it to your next post and I'll try debugging those dump files to see what is actually causing the bluescreen. Its erroring on the same thing it seems as its giving the same error on all the events you posted.
 
Are you doing anything specifically when it happens? If not, look at updating your drivers or you have possible failing hardware. You can run a diagnostic on the ram but I doubt that is it. My guess is that its driver related. It also looks like you are running an out of date build of windows 10. Looks like its build 2004 which came out almost 2 years ago. The latest version is 21H2. Updating to the latest version may help as well.

Microsoft (R) Windows Debugger Version 10.0.22000.194 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\John\Desktop\bluescreens\041422-13500-01\041322-12984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff807`33400000 PsLoadedModuleList = 0xfffff807`3402a2d0
Debug session time: Wed Apr 13 09:02:07.635 2022 (UTC - 5:00)
System Uptime: 0 days 20:36:40.383
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
...........................
For analysis of this file, run !analyze -v
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a39fbfe0e7e8d4fe, Reserved
Arg2: b3b6cc673a671db6, Reserved
Arg3: fffff80733aa8f80, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
8 : Object type
9 : A processor IVT
a : Modification of a system service function
b : A generic session data region
c : Modification of a session function or .pdata
d : Modification of an import table
e : Modification of a session import table
f : Ps Win32 callout modification
10 : Debug switch routine modification
11 : IRP allocator modification
12 : Driver call dispatcher modification
13 : IRP completion dispatcher modification
14 : IRP deallocator modification
15 : A processor control register
16 : Critical floating point control register modification
17 : Local APIC modification
18 : Kernel notification callout modification
19 : Loaded module list modification
1a : Type 3 process list corruption
1b : Type 4 process list corruption
1c : Driver object corruption
1d : Executive callback object modification
1e : Modification of module padding
1f : Modification of a protected process
20 : A generic data region
21 : A page hash mismatch
22 : A session page hash mismatch
23 : Load config directory modification
24 : Inverted function table modification
25 : Session configuration modification
26 : An extended processor control register
27 : Type 1 pool corruption
28 : Type 2 pool corruption
29 : Type 3 pool corruption
2a : Type 4 pool corruption
2b : Modification of a function or .pdata
2c : Image integrity corruption
2d : Processor misconfiguration
2e : Type 5 process list corruption
2f : Process shadow corruption
30 : Retpoline code page corruption
101 : General pool corruption
102 : Modification of win32k.sys

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 4561

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5074

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

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

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

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_CODE: 109

BUGCHECK_P1: a39fbfe0e7e8d4fe

BUGCHECK_P2: b3b6cc673a671db6

BUGCHECK_P3: fffff80733aa8f80

BUGCHECK_P4: 1

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

STACK_TEXT:
fffff68d`045ded28 00000000`00000000 : 00000000`00000109 a39fbfe0`e7e8d4fe b3b6cc67`3a671db6 fffff807`33aa8f80 : nt!KeBugCheckEx


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff80733aa90df-fffff80733aa90e0 2 bytes - nt!PpmSetProfilePolicySetting+15f
[ 0f 85:4f c1 ]
fffff80733aa90e6-fffff80733aa90ea 5 bytes - nt!PpmSetProfilePolicySetting+166 (+0x07)
[ 69 c4 b0 0a 00:50 c0 50 00 28 ]
fffff80733aa90ec-fffff80733aa90f1 6 bytes - nt!PpmSetProfilePolicySetting+16c (+0x06)
[ 48 8d 2d cd 5b 57:28 80 1e c0 1e 40 ]
13 errors : !nt (fffff80733aa90df-fffff80733aa90f1)

SYMBOL_NAME: nt!PpmSetProfilePolicySetting+0

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1586

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: 0x109_1_nt!PpmSetProfilePolicySetting

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ba469f46-25b7-25ce-3119-a68efbb8787b}

Followup: MachineOwner
---------
 
Go into your settings, click on system and then click on about at the bottom so that it shows you this screen.

What is listed down in windows specifications under version?

version of 10.jpg
 
You are on the latest version then. The minidump was reporting that it wasn't. If you go into windows update and then into optional updates, are there any driver updates listed?

I would also check the startup tab in task manager for any unnecessary programs running at bootup and disable them. When was the last time you scanned for malware? I would run Malwarebytes. This bluescreen issue isn't cut and dried, might take some time to track it down.
 
No driver updates listed. First thing after this issue happened checked for viruses and there wasn't any. And I doubt it has any because I am not using this laptop for long and didn't download much stuff.
 
Without taking it in and have someone actually look at it, not really.

Possibly resetting or reinstalling windows from scratch but thats a job in itself.
 
If this is still a live issue (or for anyone else), try sfc /scannow in an elevated command prompt.
 
You must log in or register to reply here.
Back
Top