[SOLVED] Sudden BSODs - need assistance please (.dmp files included)

[Kaetastrophe]

Hey guys.

So I've had this prebuilt gaming desktop for a little over a year now that has ran perfectly up until this past week. I'm honestly not sure what changed but late last week I suddenly got the BSOD with an error code of "Kernal Security Check Failure". Then a second one of "Attempted_Execute_Of_NoExecute". I ended up reinstalling the OS fresh yesterday to rule it out being an OS/driver issue.

Thought I was in the clear after that as I played FFXIV for a good few hours with no issues but alas, BSOD again with "KMODE_Exception_Not_Handled" referring to FLTMGR.sys. I decided to run memtest and received no errors on my RAM. Went ahead and updated all of my drivers manually including my chipset and BIOS as well. Checked hard drive health for both my SSD and regular HDD and they came back healthy. About 5 minutes into playing FFXIV, it blue screened again with a System Exception Error and there was this screeching/buzzing noise coming from my tower. This sound happened one other instance as well, but not every time.

These are the most two recent .dmp files.

https://www.dropbox.com/s/25q9o6zcpc30ju8/040820-9015-01.dmp?dl=0

040820-16859-01.dmp

Shared with Dropbox

www.dropbox.com

Here are my computer specs. http://speccy.piriform.com/results/be8xa5mfXyIJtv1p4pYwQJp

Any help is greatly appreciated, I feel like I am losing my mind with this one

 

[Colif]

I will get a friend to convert dumps

 

[Kaetastrophe]

Thank you!

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://arcuatetea.htmlpasta.com/

File information:	040820-9015-01.dmp (Apr 8 2020 - 16:37:07)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: ffxiv_dx11.exe)
Uptime:	0 Day(s), 23 Hour(s), 46 Min(s), and 32 Sec(s)

File information:	040820-16859-01.dmp (Apr 8 2020 - 23:12:43)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: NVIDIA Share.exe)
Uptime:	0 Day(s), 0 Hour(s), 14 Min(s), and 51 Sec(s)

Possible Motherboard page: https://www.gigabyte.com/us/Motherboard/GA-AX370M-DS3H-rev-1x#kf
You recently updated your BIOS from F22 to F50a. You have the latest BIOS
installed.

Since NVIDIA is listed in the 2nd crash and DirectX is mentioned in the first crash, the first thing you should try is a clean install of your graphics driver. Download DDU and the latest version of the NVIDIA driver. Unplug internet. Reboot into Safe mode and run DDU to clear out old driver. Boot back into normal mode and install the latest NVIDIA driver. Reconnect to internet. Full instructions can be found here: https://forums.tomshardware.com/thr...n-install-of-your-video-card-drivers.3526772/

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Kaetastrophe]

Unfortunately got another BSOD after clean install of NVidia drivers. Again while playing FFXIV

oading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 0000025C017C9920 Handle: 5 Id: 5 - Error == 0x8000FFFF

* Path validation summary **
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff8003ea00000 PsLoadedModuleList = 0xfffff8003ee48170
Debug session time: Fri Apr 10 14:52:28.998 2020 (UTC - 7:00)
System Uptime: 0 days 6:38:13.654
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000009dabb85018). Type ".hh dbgerr001" for details Loading unloaded module list ........ nt!KeBugCheckEx: fffff8003ebc2360 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffca0fb5732970=000000000000001e ||1:4: kd> !analyze -v ******************************************************************************* [LIST] [*]* [*]Bugcheck Analysis * [*]* [/LIST] ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffffc0000005, The exception code that was not handled Arg2: fffff80043f287bb, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 8 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-JHLB2NJ Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 20 Key : Analysis.Memory.CommitPeak.Mb Value: 91 Key : Analysis.System Value: CreateObject ADDITIONAL_XML: 1 BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80043f287bb BUGCHECK_P3: 0 BUGCHECK_P4: ffffffffffffffff READ_ADDRESS: ffffffffffffffff EXCEPTION_PARAMETER2: ffffffffffffffff BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: audiodg.exe STACK_TEXT: ffffca0fb5732968 fffff8003ec5ad71 : 000000000000001e ffffffffc0000005 fffff80043f287bb 0000000000000000 : nt!KeBugCheckEx ffffca0fb5732970 fffff8003ebd431d : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDispatchException+0x15c681 ffffca0fb5733020 fffff8003ebd00a0 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExceptionDispatch+0x11d ffffca0fb5733200 fffff80043f287bb : 0000000000000050 ffffce0c5a010000 0000000000000000 ffffffffffffffff : nt!KiGeneralProtectionFault+0x320 ffffca0fb5733390 fffff80043f27f57 : 0000000000000000 ffffce0c6583ed40 0000000000000000 ffffce0c69038a58 : storport!RaidStartIoPacket+0x5fb ffffca0fb57334a0 fffff80043f27cea : ffffce0c6583ed40 fffff8003ea21f20 0000000000000000 0000000000000040 : storport!RaUnitScsiIrp+0x227 ffffca0fb5733540 fffff8003eb0a929 : ffffce0c6a6e7410 ffffce0c5d1dd050 0000000000004000 0000000000000000 : storport!RaDriverScsiIrp+0x5a ffffca0fb5733580 fffff80044be9308 : ffffce0c670aa848 ffffce0c6a6e7410 ffffce0c5d1dd050 0000000000004000 : nt!IofCallDriver+0x59 ffffca0fb57335c0 fffff80044be8677 : 0000000000000000 0000000000000000 0000000000000000 0000000000004000 : CLASSPNP!SubmitTransferPacket+0x288 ffffca0fb5733600 fffff80044be842e : ffffce0c6a6e7410 ffffca0fb5733700 ffffce0c5d84b100 fffff80000020000 : CLASSPNP!ServiceTransferRequest+0x207 ffffca0fb5733690 fffff80044be17c3 : 000000000000ff01 0000000000000000 0000000000000000 fffff8003ea1f114 : CLASSPNP!ClassReadWrite+0x92e ffffca0fb57337c0 fffff8003eb0a929 : fffff78000000008 fffff8003ea1d846 ffffffff000016c8 ffffce0c670aa460 : CLASSPNP!ClassGlobalDispatch+0x23 ffffca0fb57337f0 fffff80043d51c3c : ffffce0c5cafc210 0000000000000000 ffffce0c670aa608 ffffce0c5d63fa20 : nt!IofCallDriver+0x59 ffffca0fb5733830 fffff80043d51eef : 0000000100000001 00000037a1e1038e 0000000000000000 fffff8003eb1254d : partmgr!PmIo+0xdc ffffca0fb57338b0 fffff8003eb0a929 : ffffccd00000002b 0000000000000020 fffff80000000000 fffff8003f4b88f8 : partmgr!PmGlobalDispatch+0x1f ffffca0fb57338e0 fffff80043d5174d : 0000000000000000 ffffccd08705b000 ffffffffffffffff fffff8003eaa502c : nt!IofCallDriver+0x59 ffffca0fb5733920 fffff80043d51eef : 0000000000004000 ffffce0c670aa650 ffffca0fb5733b69 ffffce0c5d865180 : partmgr!PartitionIo+0x1dd ffffca0fb57339d0 fffff8003eb0a929 : ffffce0c670aa6b0 fffff80043d51f71 0000000000000000 ffffce0c5d868190 : partmgr!PmGlobalDispatch+0x1f ffffca0fb5733a00 fffff80043e41109 : ffffce0c5d64da40 0000000000000001 00000037a1e10380 fffff80000004000 : nt!IofCallDriver+0x59 ffffca0fb5733a40 fffff8003eb0a929 : ffffca0fb5733b69 fffff800449d1d88 ffffce0c670aa460 0000000000000000 : volmgr!VmReadWrite+0xf9 ffffca0fb5733a80 fffff800449c39f0 : 0000000000000000 ffffca0fb5733b69 ffffce0c670aa460 fffff80044b84d6e : nt!IofCallDriver+0x59 ffffca0fb5733ac0 fffff800449c30b7 : 0000000000000000 ffffca0fb5733c70 0000000000000001 0000000000000000 : fvevol!FveFilterRundownReadWrite+0x920 ffffca0fb5733bd0 fffff8003eb0a929 : ffffccd0867a2d00 ffffca0fb5733d59 ffffce0c62ce2a90 fffff8003eb110b9 : fvevol!FveFilterRundownRead+0x27 ffffca0fb5733c00 fffff80044b83ca3 : 0000000000000000 ffffce0c5d65aa20 0000000000000000 0000000000000000 : nt!IofCallDriver+0x59 ffffca0fb5733c40 fffff80044b84f2d : 0000000000000002 ffffca0fb5733d80 0000000000000000 ffffcc99ae820cb1 : iorate!IoRateIssueAndRecordIo+0x7f ffffca0fb5733c80 fffff80044b85120 : ffffcc99ae87f3f0 ffffce0c5d867180 ffffce0c659cd080 ffffca0f00000001 : iorate!IoRateProcessIrpWrapper+0x19d ffffca0fb5733dc0 fffff8003eb0a929 : 0000000000000035 ffffcc99aef4fc1d ffffcc99af1d67a0 ffffca0fb5733ec0 : iorate!IoRateDispatchReadWrite+0x80 ffffca0fb5733e00 fffff80044a81033 : ffffce0c5d849670 fffff80044a94340 0000000000000001 ffffce0c66574c00 : nt!IofCallDriver+0x59 ffffca0fb5733e40 fffff8003eb0a929 : ffffce0c5d867180 fffff80044aae294 0000000000000018 0000015070c8acc0 : volume!VolumePassThrough+0x23 ffffca0fb5733e70 fffff80044a969d4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IofCallDriver+0x59 ffffca0fb5733eb0 fffff80044a912c9 : ffffca0fb2e990d8 0000000000000000 0000000000000000 0000000000000000 : volsnap!VolSnapReadFilter+0x56f4 ffffca0fb5733ee0 fffff8003eb0a929 : 000001506bfb8000 0000000000000000 0000000000000000 0000000000000000 : volsnap!VolSnapRead+0x19 ffffca0fb5733f10 fffff800440e327c : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IofCallDriver+0x59 ffffca0fb5733f50 fffff8003ebc5c1e : 0000000000000401 0000000000000000 0000001de7efc598 00000000000001c1 : Ntfs!NtfsStorageDriverCallout+0x1c ffffca0fb5733f80 fffff8003ebc5bdc : ffffca0fb5733fd0 ffffce0c659cd080 ffffca0fb5734000 fffff8003eac042e : nt!KxSwitchKernelStackCallout+0x2e ffffca0fb2e98ec0 fffff8003eac042e : ffffca0fb5733fd0 ffffca0fb5734000 0000000000000001 0000000000000000 : nt!KiSwitchKernelStackContinue ffffca0fb2e98ee0 fffff8003eac022c : fffff800440e3260 ffffca0fb2e990d8 0000400000000002 0000010000000000 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x18e ffffca0fb2e98f80 fffff8003eac00a3 : ffffca0fb2e99210 ffffca0fb2e992e0 0000000000000000 0000000000000000 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xdc ffffca0fb2e98ff0 fffff8003eac005d : fffff800440e3260 ffffca0fb2e990d8 0000000000000001 ffffce0c5d61dd78 : nt!KeExpandKernelStackAndCalloutInternal+0x33 ffffca0fb2e99060 fffff800440d1690 : ffffce0c5d61dd78 ffffce0c670aa460 ffffca0fb2e99150 ffffce0c670aa460 : nt!KeExpandKernelStackAndCalloutEx+0x1d ffffca0fb2e990a0 fffff800440d0229 : ffffca0fb2e99150 ffffce0c5d61dd78 00000000001dde00 00000000001d9e00 : Ntfs!NtfsMultipleAsync+0x110 ffffca0fb2e99110 fffff800440d6e58 : ffffca0fb2e995b0 0000000000008000 0000000000000001 ffffce0c670aa460 : Ntfs!NtfsNonCachedIo+0x3f9 ffffca0fb2e993c0 fffff800440d641c : ffffca0fb2e995c0 ffffce0c670aa460 ffffca0fb2e995c0 ffffce0c5d61dd78 : Ntfs!NtfsCommonRead+0x828 ffffca0fb2e99580 fffff8003eb0a929 : ffffce0c6c8f5730 ffffce0c670aa460 ffffce0c670aa800 ffffffffffffff00 : Ntfs!NtfsFsdRead+0x20c ffffca0fb2e99640 fffff800436e55de : 0000000000000000 ffffca0fb2e99720 ffffce0c670aa460 ffffca0fb2e99730 : nt!IofCallDriver+0x59 ffffca0fb2e99680 fffff800436e3f16 : ffffca0fb2e99720 fffff8003ead0768 ffffca0fb2e99801 ffff9f840cfdeee0 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x15e ffffca0fb2e99700 fffff8003eb0a929 : ffffce0c670aa460 fffff8003ea21c6b 0000000100000000 0000000000000005 : FLTMGR!FltpDispatch+0xb6 ffffca0fb2e99760 fffff8003ea21853 : 0000000000000005 ffffce0c670aa460 ffffce0c66a1c3b0 ffffce0c66a1c470 : nt!IofCallDriver+0x59 ffffca0fb2e997a0 fffff8003eb048c9 : ffffce0c66a1c360 0000000000000000 ffffce0c66a1c3c0 ffffce0c66a1c380 : nt!IoPageReadEx+0x1d3 ffffca0fb2e99810 fffff8003eb05449 : 0000000000000003 ffffca0fb2e998f0 ffffca0fb2e99a58 fffff8003eacb1b6 : nt!MiIssueHardFaultIo+0xc1 ffffca0fb2e99860 fffff8003eac926b : 00000000c0033333 0000000000000001 00007ffce0c0c8a0 0000000000000000 : nt!MiIssueHardFault+0x489 ffffca0fb2e99960 fffff8003ebd041e : 0000000000000350 ffffce0c659cd080 0000000000000000 ffffce0c680c5360 : nt!MmAccessFault+0x40b ffffca0fb2e99b00 00007ffcfebbcd03 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x35e 0000009dabdfeaa0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffcfebbcd03


SYMBOL_NAME: partmgr!PmIo+dc

MODULE_NAME: partmgr

IMAGE_NAME: partmgr.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: dc

FAILURE_BUCKET_ID: 0x1E_c0000005_R_partmgr!PmIo

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ab1c70d2-a87c-dcd7-d247-c223a804db8e}

Followup: MachineOwner
---------

 

[Colif]

stack text mentions storport.sys and classpnp.sys. latter is used for scsi operations which in modern hardware is used for ssd.
So try running Samsung Magician on the ssd and see if its healthy/needs new firmware - https://www.samsung.com/semiconductor/minisite/ssd/download/tools/
partmgr.sys - windows Partition manager. More clues its something to do with drives.

are you running raid?

storport!RaidStartIoPacket+0x5f

250gb ssd, 2tb hdd

might help to check toshiba hdd as well. I am just assuming it was writing to the ssd.