BSOD Multiple Random Crashes Daily

Desktop PC running 24/7 acting as a Plex Media server. Has been rock solid for well over a year, recently started having multiple crashes daily (anywhere from 3-8 per day). Not experienced enough to pinpoint if this is hardware, software, driver related. Several things have updated since the problem began. Have tried several things, including disk check, memory check, restoring to previous version, disable fast start etc. Reliability score has gone from a consistent 10 down to a 1. Uploading log collector here. Thanks in advance for any help.

STOP 0x133 - The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

Code:

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


Loading Dump File [F:\040319-6906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SymCache*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 17134 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`c7c06000 PsLoadedModuleList = 0xfffff803`c7fb4150
Debug session time: Wed Apr  3 12:23:40.423 2019 (UTC + 2:00)
System Uptime: 0 days 3:26:18.374
Loading Kernel Symbols
...............................................................
................................................................
............................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {0, 501, 500, fffff803c8053378}

*** WARNING: Unable to verify timestamp for iaStorAC.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorAC.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************
Probably caused by : iaStorAC.sys ( iaStorAC+b6437 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff803c8053378, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0419

BIOS_DATE:  10/17/2017

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  ROG STRIX Z370-E GAMING

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff803c8053378

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 6

CPU_MHZ: e10

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CPU_MICROCODE: 6,9e,a,0 (F,M,S,R)  SIG: 84'00000000 (cache) 84'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

ANALYSIS_SESSION_HOST:  MICHAL

ANALYSIS_SESSION_TIME:  04-03-2019 21:54:19.0253

ANALYSIS_VERSION: 10.0.17763.132 amd64fre

LAST_CONTROL_TRANSFER:  from fffff803c7ddb0f7 to fffff803c7db00a0

STACK_TEXT:  
fffff803`caa12bc8 fffff803`c7ddb0f7 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff803`caa12bd0 fffff803`c7c483ba : 00002894`c7702648 fffff803`c55ad180 00000000`00000282 00000000`00000000 : nt!KeAccumulateTicks+0x1903f7
fffff803`caa12c30 fffff803`c855c51b : 00002894`c76f8f50 fffff803`c7d0da65 00000000`00000000 fffff803`c85bbbb0 : nt!KeClockInterruptNotify+0x9da
fffff803`caa12f40 fffff803`c7d0da65 : fffff803`c85bbbb0 00002894`ba071726 ffff9608`750eeb34 fffff803`c7db16ff : hal!HalpTimerClockIpiRoutine+0x1b
fffff803`caa12f70 fffff803`c7db195a : fffff803`caa0b230 fffff803`c85bbbb0 00000000`00000001 ffffd76b`38908d76 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`caa12fb0 fffff803`c7db1e47 : ffff9608`750eebb4 fffff803`caa0b238 00000000`00000000 00001f80`00000203 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff803`caa0b1b0 fffff803`c855aa8c : ffff9608`750eeb34 fffff801`8de661c7 00000000`01c9c380 00000000`00000004 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff803`caa0b340 fffff801`8cc0d93a : ffff9608`750eeb34 ffff9608`750eeb34 fffff801`8deaa000 00000000`00000004 : hal!KeStallExecutionProcessor+0x10c
fffff803`caa0b3d0 fffff801`8de66437 : 0000001c`d213bf16 ffff9608`750eda60 fffff803`00000025 00000000`00000000 : storport!StorPortStallExecution+0xa
fffff803`caa0b400 0000001c`d213bf16 : ffff9608`750eda60 fffff803`00000025 00000000`00000000 ffff9608`750eeb01 : iaStorAC+0xb6437
fffff803`caa0b408 ffff9608`750eda60 : fffff803`00000025 00000000`00000000 ffff9608`750eeb01 fffff801`8de66b29 : 0x0000001c`d213bf16
fffff803`caa0b410 fffff803`00000025 : 00000000`00000000 ffff9608`750eeb01 fffff801`8de66b29 ffff9608`750eeb00 : 0xffff9608`750eda60
fffff803`caa0b418 00000000`00000000 : ffff9608`750eeb01 fffff801`8de66b29 ffff9608`750eeb00 ffff9608`750eeb00 : 0xfffff803`00000025


THREAD_SHA1_HASH_MOD_FUNC:  f7237437dc4231397fab354459ccb99524f9ba5e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  597109b070c74ba475d165ff7bb9688b1db39c38

THREAD_SHA1_HASH_MOD:  c867aa379652786e2a5d3199dc918f969b5d444c

FOLLOWUP_IP: 
iaStorAC+b6437
fffff801`8de66437 32c0            xor     al,al

FAULT_INSTR_CODE:  8348c032

SYMBOL_STACK_INDEX:  9

SYMBOL_NAME:  iaStorAC+b6437

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: iaStorAC

IMAGE_NAME:  iaStorAC.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5c769134

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  b6437

FAILURE_BUCKET_ID:  0x133_DPC_iaStorAC!unknown_function

BUCKET_ID:  0x133_DPC_iaStorAC!unknown_function

PRIMARY_PROBLEM_CLASS:  0x133_DPC_iaStorAC!unknown_function

TARGET_TIME:  2019-04-03T10:23:40.000Z

OSBUILD:  17134

OSSERVICEPACK:  648

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2019-03-06 09:32:15

BUILDDATESTAMP_STR:  180410-1804

BUILDLAB_STR:  rs4_release

BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME:  ad0c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x133_dpc_iastorac!unknown_function

FAILURE_ID_HASH:  {6959f419-2954-fbde-7328-35f9ba64ee7a}

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

All crash dumps look the same. Since the disk and RAM are operational, please send a full kernel memory dump, maybe something can be found there

Thank you. Would I be selecting the Kernel Memory Dump or Complete Memory Dump option in Startup and Recovery options? Also, would I need to wait for another crash to obtain this file?

Edit: Found memory.dmp file. Uploading now.

- - - Updated - - -

Seems that memory.dmp is too large (even when zipped) to upload to this site?

Perform the following steps:

1) Update the specs in the "My Computer" section:

System Specs - Fill in at Ten Forums | Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)


2) Open administrative command prompt and type or copy and paste:
3) sfc /scannow
4) dism /online /cleanup-image /restorehealth
5) chkdsk /scan
6) wmic recoveros set autoreboot = false
7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

8) Make sure that there is no over clocking while troubleshooting.

9) Sometimes there are problems in the bios that produce bsod.

The BIOS: Version/Date American Megatrends Inc. 0419, 10/17/2017

Upgrade the BIOS: 0419 > 11.8.60.3561
ROG STRIX Z370-E GAMING Driver & Tools | Motherboards | ASUS USA


10) To ensure that there are no improper bios settings please reset the bios.

11) Sometimes there can be failure to boot after resetting the bios.

12) Backup the computer files to another drive or to the cloud.

13) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free:
Macrium Software | Macrium Reflect Free

14) Create a brand new restore point.
Create System Restore Point in Windows 10 | Tutorials

How to Clear Your Computers CMOS to Reset BIOS Settings:
https://www.howtogeek.com/131623/how...bios-settings/
3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

15) Update the Intel chipset drivers: iastorac.sys
Intel(R) Chipset SATA/PCIe RST Premium Controller
Intel(R) 300 Series Chipset Family SATA AHCI Controller

Updating a driver. - Microsoft Community

Code:

Name	Intel(R) 300 Series Chipset Family SATA AHCI Controller
Manufacturer	Intel Corporation
Status	OK
PNP Device ID	PCI\VEN_8086&DEV_A282&SUBSYS_86941043&REV_00\3&11583659&0&B8
Memory Address	0xF7448000-0xF7449FFF
Memory Address	0xF744C000-0xF744C0FF
I/O Port	0x0000F090-0x0000F097
I/O Port	0x0000F080-0x0000F083
I/O Port	0x0000F060-0x0000F07F
Memory Address	0xF744B000-0xF744B7FF
IRQ Channel	IRQ 4294967287
Driver	c:\windows\system32\drivers\iastorac.sys (16.8.2.1002, 1.04 MB (1,094,000 bytes), 3/7/2019 7:30 PM)

Code:

iastorac	Intel(R) Chipset SATA/PCIe RST Premium Controller	c:\windows\system32\drivers\iastorac.sys	Kernel Driver	Yes	Boot	Running	OK	Normal	No	Yes

Code:

iaStorA      Intel(R) Chipset SATA/ Intel(R) Chipset SATA/ Kernel        Manual     Stopped    OK         FALSE       FALSE        4,096             790,528     0          7/13/2017 10:35:49 AM  C:\WINDOWS\system32\drivers\iaStorA.sys

Thank you. Some progress:
1) Done
2-7) Pasted below
8) Have never overclocked this chip
Will work on the BIOS next. Meantime, here is the cmd dump.

Microsoft Windows [Version 10.0.17134.648]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.648

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
932096 file records processed.
File verification completed.
10887 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
936 reparse records processed.
1572532 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
936 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
320219 data files processed.
CHKDSK is verifying Usn Journal...
38391488 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

249587388 KB total disk space.
183032096 KB in 542888 files.
387820 KB in 320220 indexes.
0 KB in bad sectors.
1049428 KB in use by the system.
65536 KB occupied by the log file.
65118044 KB available on disk.

4096 bytes in each allocation unit.
62396847 total allocation units on disk.
16279511 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\2018-COFFEELAKE\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition1"'
Property(s) update successful.