Windows 10: system service exception bsod why fails - fastfat.sys

my computer having bsod once in a week , os windows 10 2004 , exactly i dont know why these issues occurs


i am uploading my dump file here , please help me to fix issues


NO UPDATES AVAILABLE


Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\090320-56906-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time ms LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff807`14200000 PsLoadedModuleList = 0xfffff807`14e2a2f0Debug session time: Thu Sep 3 23:52:12.807 2020 UTC + 5:30System Uptime: 0 days 1:58:11.541Loading Kernel Symbols..Press ctrl-c cdb, kd, ntsd or ctrl-break windbg to abort symbol loads that take too long.Run !sym noisy before .reload to track down problems loading symbols..........................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list............................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff807`145ddf40 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffc87`9707e360=000000000000003b1: 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: fffff807324d6bc2, Address of the instruction which caused the bugcheckArg3: fffffc879707ec60, Address of the context record for the exception that caused the bugcheckArg4: 0000000000000000, zero.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 7874 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-59J9TF2 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 30720 Key : Analysis.Memory.CommitPeak.Mb Value: 81 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1OS_BUILD_LAYERS: 1DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_CODE: 3bBUGCHECK_P1: c0000005BUGCHECK_P2: fffff807324d6bc2BUGCHECK_P3: fffffc879707ec60BUGCHECK_P4: 0CONTEXT: fffffc879707ec60 -- .cxr 0xfffffc879707ec60rax=0000000000000502 rbx=ffffd8073fe82010 rcx=ffffd8073fe82710rdx=0000000000000000 rsi=ffffd8073fe82010 rdi=ffffd80740f07b00rip=fffff807324d6bc2 rsp=fffffc879707f660 rbp=0000000000000000 r8=0000000000000004 r9=ffffd80746591830 r10=fffff8071441f590r11=0000000000000000 r12=ffffd80727e31980 r13=0000000000000000r14=ffffd8073fe82710 r15=0000000000000000iopl=0 nv up ei pl nz na po nccs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050206fastfat!FatFsdWrite+0x62:fffff807`324d6bc2 663902 cmp word ptr [rdx],ax ds:002b:00000000`00000000=????Resetting default scopeCUSTOMER_CRASH_COUNT: 1PROCESS_NAME: svchost.exeSTACK_TEXT: fffffc87`9707f660 fffff807`14446d45 : ffffd807`5063ad20 ffffd807`3fe82010 ffffd807`3fe82010 ffffd807`40f07ba0 : fastfat!FatFsdWrite+0x62fffffc87`9707f6a0 fffff807`106b6ccf : 00000000`00000180 ffffd807`4da2ace0 00000000`00000000 ffffd807`4da2ad10 : nt!IofCallDriver+0x55fffffc87`9707f6e0 fffff807`106b48d3 : fffffc87`9707f770 00000000`00000000 00000000`00000001 ffffd807`27e6d3c0 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x28ffffffc87`9707f750 fffff807`14446d45 : ffffd807`3fe82010 00000000`00000000 00000000`00000000 00000000`00000000 : FLTMGR!FltpDispatch+0xa3fffffc87`9707f7b0 fffff807`1480eeb8 : 00000000`00000001 ffffd807`4da26ed0 00000000`00000001 ffffd807`3fe82758 : nt!IofCallDriver+0x55fffffc87`9707f7f0 fffff807`1482bbff : ffffd807`00000000 fffffc87`9707fa80 00000000`00000000 fffffc87`9707fa80 : nt!IopSynchronousServiceTail+0x1a8fffffc87`9707f890 fffff807`145ef875 : 00000000`000003b8 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x66ffffffc87`9707f990 00007ff8`05bcbec4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x250000003b`0807eac8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`05bcbec4SYMBOL_NAME: fastfat!FatFsdWrite+62MODULE_NAME: fastfatIMAGE_NAME: fastfat.SYSIMAGE_VERSION: 10.0.19041.208STACK_COMMAND: .cxr 0xfffffc879707ec60 ; kbBUCKET_ID_FUNC_OFFSET: 62FAILURE_BUCKET_ID: 0x3B_c0000005_fastfat!FatFsdWriteOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {fe1ecff2-0d33-3b32-4a7a-1b462833992e}Followup: MachineOwner--------

:)

 

BSOD system service exception. what failed: IGDKMD64.SYS

hello, for the past few days I had several BSOD. Two of them have been KMODE EXCEPTION NOT HANDLED and one SYSTEM SERVICE EXCEPTION but in both cases what failed was the same, igdkmd64.sys

after the last one I used driver verifier (Driver Verifier-- tracking down a mis-behaving driver.) to get memory dump files to see what happened.

here is the link to the files: https://1drv.ms/u/s!AqZNaSZvH57q8l0IvNcspcA7ZMXq

system information: https://1drv.ms/u/s!AqZNaSZvH57q8l_nC-PbwVlS3Jf7

 

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.