Windows 10: BSOD System service Exception Ntfs.sys

I have this BSOD every 1 day after I install Norton Security in 3 computer with Win 10 pro last Update in my company. I try to debug the Dump file and the software say this:



Loading Dump File [F:\Downloads\Compressed\wetransfer-c976e6\013120-29000-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 18362 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff807`7ca00000 PsLoadedModuleList = 0xfffff807`7ce48150Debug session time: Fri Jan 31 16:00:40.098 2020 UTC + 1:00System Uptime: 1 days 23:58:56.723Loading Kernel Symbols.....................................................................................................................................................................................Loading User SymbolsLoading unloaded module list...........For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff807`7cbc14e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff950b`ce566e30=000000000000003b2: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************SYSTEM_SERVICE_EXCEPTION 3bAn exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the bugcheckArg2: fffff8077f62020c, Address of the instruction which caused the bugcheckArg3: ffff950bce567760, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------*** WARNING: Unable to verify timestamp for SRTSP64.SYS*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 4 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-I3NOUKQ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 30 Key : Analysis.Memory.CommitPeak.Mb Value: 74 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 3bBUGCHECK_P1: c0000005BUGCHECK_P2: fffff8077f62020cBUGCHECK_P3: ffff950bce567760BUGCHECK_P4: 0CONTEXT: ffff950bce567760 -- .cxr 0xffff950bce567760rax=0000000000000702 rbx=0000000000000000 rcx=ffff968a34c252e8rdx=ffffa70698b89d70 rsi=0000000000000001 rdi=0000000000000000rip=fffff8077f62020c rsp=ffff950bce568150 rbp=ffff968a34c252e8 r8=0000000000000001 r9=0000000000000000 r10=fffff8077cb00590r11=ffffa9ff76400000 r12=0000000000000000 r13=ffff968a34c252e8r14=0000000000000000 r15=ffff968a32f634d0iopl=0 nv up ei pl zr na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246Ntfs!NtfsAcquirePagingResourceExclusive+0x2c:fffff807`7f62020c 8b4710 mov eax,dword ptr [rdi+10h] ds:002b:00000000`00000010=????????Resetting default scopeBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: NortonSecurity.exeSTACK_TEXT: ffff950b`ce568150 fffff807`7f61728b : 00000000`00000001 ffff950b`ce568380 00000000`00000001 00000000`00000000 : Ntfs!NtfsAcquirePagingResourceExclusive+0x2cffff950b`ce568190 fffff807`7f61641c : ffff950b`ce568390 ffff968a`32f634d0 ffff950b`ce568390 ffff968a`34c252e8 : Ntfs!NtfsCommonRead+0xc5bffff950b`ce568350 fffff807`7ca31f79 : ffff968a`38499050 ffff968a`32f634d0 ffff968a`32f63948 ffff968a`2a923400 : Ntfs!NtfsFsdRead+0x20cffff950b`ce568410 fffff807`7eac55de : 00000000`00000020 00000000`00000000 ffff968a`38499138 ffff950b`ce568720 : nt!IofCallDriver+0x59ffff950b`ce568450 fffff807`7eac2bee : ffff950b`ce5684f0 ffff968a`2a941628 00000000`00000001 ffff968a`38499138 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15effff950b`ce5684d0 fffff807`7ead85fe : ffff968a`38499050 00000000`00000000 ffff950b`ce568611 00000000`00000000 : FLTMGR!FltPerformSynchronousIo+0x2eeffff950b`ce568570 fffff807`7ead8151 : ffffa706`9f2c7af0 fffff807`8091a6f4 ffffa706`9f2c7b40 00000000`00000000 : FLTMGR!FltReadFileEx+0x49effff950b`ce568660 fffff807`8096d7e7 : ffffa706`95f13080 ffff950b`ce568740 00000000`00010000 00000000`00000000 : FLTMGR!FltReadFile+0x51ffff950b`ce5686d0 ffffa706`95f13080 : ffff950b`ce568740 00000000`00010000 00000000`00000000 ffffc9ff`8a7d2040 : SRTSP64+0xad7e7ffff950b`ce5686d8 ffff950b`ce568740 : 00000000`00010000 00000000`00000000 ffffc9ff`8a7d2040 00000000`00000004 : 0xffffa706`95f13080ffff950b`ce5686e0 00000000`00010000 : 00000000`00000000 ffffc9ff`8a7d2040 00000000`00000004 ffff950b`ce568720 : 0xffff950b`ce568740ffff950b`ce5686e8 00000000`00000000 : ffffc9ff`8a7d2040 00000000`00000004 ffff950b`ce568720 00000000`00000000 : 0x10000SYMBOL_NAME: SRTSP64+ad7e7MODULE_NAME: SRTSP64IMAGE_NAME: SRTSP64.SYSSTACK_COMMAND: .cxr 0xffff950bce567760 ; kbBUCKET_ID_FUNC_OFFSET: ad7e7FAILURE_BUCKET_ID: 0x3B_c0000005_SRTSP64!unknown_functionOS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {8694e255-476c-ba56-ced4-927c99ae53fa}Followup: MachineOwner---------2: kd> !blackboxbsdStream size mismatch expected = 176, read = 1682: kd> !blackboxntfsNTFS Blackbox Data0 Slow I/O Timeout Records Found0 Oplock Break Timeout Records Found2: kd> !blackboxpnp PnpActivityId : {00000000-0000-0000-0000-000000000000} PnpActivityTime : 132249564175936719 PnpEventInformation: 3 PnpEventInProgress : 0 PnpProblemCode : 24 PnpVetoType : 0 DeviceId : SWD\DAFUPnPProvider\uuid:f52cd6af-0414-4795-aec5-bed0a672aa06 VetoString : 2: kd> lmvm SRTSP64Browse full module liststart end module namefffff807`808c0000 fffff807`8099e000 SRTSP64 T no symbols Loaded symbol image file: SRTSP64.SYS Image path: \SystemRoot\System32\drivers\NGCx64\1613090.03F\SRTSP64.SYS Image name: SRTSP64.SYS Browse all global symbols functions data Timestamp: Wed Oct 9 19:54:35 2019 5D9E2CEB CheckSum: 000E3254 ImageSize: 000DE000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Information from resource tables:2: kd> .cxr 0xffff950bce567760rax=0000000000000702 rbx=0000000000000000 rcx=ffff968a34c252e8rdx=ffffa70698b89d70 rsi=0000000000000001 rdi=0000000000000000rip=fffff8077f62020c rsp=ffff950bce568150 rbp=ffff968a34c252e8 r8=0000000000000001 r9=0000000000000000 r10=fffff8077cb00590r11=ffffa9ff76400000 r12=0000000000000000 r13=ffff968a34c252e8r14=0000000000000000 r15=ffff968a32f634d0iopl=0 nv up ei pl zr na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246Ntfs!NtfsAcquirePagingResourceExclusive+0x2c:fffff807`7f62020c 8b4710 mov eax,dword ptr [rdi+10h] ds:002b:00000000`00000010=????????


Here is the link of the dump files : https://1drv.ms/u/s!AtvjYooy6_a_lTXdOKHwGYHdiBg0?e=iswmlp

Thank You for your response

:)

 

SYSTEM SERVICE EXCEPTION (igdkmd64.sys)

Hi, I've been having BSOD errors. Usually it appears to be System Service Exception, but occasionally Kmode Exception Not Handled error would appear. Both have the same stop code (igdkmd64.sys). DMP and MSInfo files are available in the onedrive link below.

Thank you for your kind assistance!

Link: Files.zip

Regards,

Kenji

 

Dell Laptop, BSOD System Service Exception

Hi,

Outdated drivers is one of the common reasons why SYSTEM SERVICE EXCEPTION and
Wdf01000.sys error appears.

Considering that the driver verifier detected a violation, it is best to first check for available updates for your drivers. We suggest following the steps on this
article to update it.

Don't hesitate to update us with the result.

 

SYSTEM SERVICE EXCEPTION (igdkmd64.sys)

Hi, I've been having BSOD errors.
I'm using a Lenovo Ideapad 500S Laptop. Usually it appears to be System Service Exception, but occasionally Kmode Exception Not Handled error would appear. Both have the same stop code (igdkmd64.sys). DMP and MSInfo files are available in the onedrive
link below.

DMP and MSInfo files:

Link: Files.zip

DriverView Text File:

Link: DriverView Info.txt

Thank you for your kind assistance!

Regards,

Kenji