蓝屏bdos，iastorac.sys导致的蓝屏问题

      加装了ZHITAI TiPlus5000 1TB后，频繁出现蓝屏，报错文件：iaStorAC.sys将Intel Chipset SATA/PCIe RST Premium Controller版本从17.11.0.1000回退至17.8.0.1065后问题没有解决希望知道如何解决🥺dump：||2:15: 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: fffff8012e2fb320, 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      Key  : Analysis.CPU.mSec     Value: 3452      Key  : Analysis.DebugAnalysisManager     Value: Create      Key  : Analysis.Elapsed.mSec     Value: 24124      Key  : Analysis.IO.Other.Mb     Value: 12      Key  : Analysis.IO.Read.Mb     Value: 1      Key  : Analysis.IO.Write.Mb     Value: 25      Key  : Analysis.Init.CPU.mSec     Value: 2108      Key  : Analysis.Init.Elapsed.mSec     Value: 216133      Key  : Analysis.Memory.CommitPeak.Mb     Value: 162      Key  : Bugcheck.Code.DumpHeader     Value: 0x133      Key  : Bugcheck.Code.Register     Value: 0x133      Key  : Dump.Attributes.AsUlong     Value: 8      Key  : Dump.Attributes.KernelGeneratedTriageDump     Value: 1   FILE_IN_CAB:  101322-11125-01.dmp  DUMP_FILE_ATTRIBUTES: 0x8   Kernel Generated Triage Dump  BUGCHECK_CODE:  133  BUGCHECK_P1: 0  BUGCHECK_P2: 501  BUGCHECK_P3: 500  BUGCHECK_P4: fffff8012e2fb320  DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED  CUSTOMER_CRASH_COUNT:  1  PROCESS_NAME:  System  STACK_TEXT:   ffffb981`a8f4fe18 fffff801`2da596fe     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffb981`a8f4fe20 fffff801`2d8d2973     : 000002b3`cc30101b ffffb981`a8efd180 00000000`00000000 ffffb981`a8efd180 : nt!KeAccumulateTicks+0x18452e ffffb981`a8f4fe80 fffff801`2d8d245a     : ffffa20b`1131e1c0 ffff8884`fd316db0 fffff801`31aa1600 00000011`00008101 : nt!KeClockInterruptNotify+0x453 ffffb981`a8f4ff30 fffff801`2d808a45     : ffffa20b`1131e1c0 00000000`00000000 00000000`00000000 ffff8ea5`e1b36ad1 : nt!HalpTimerClockIpiRoutine+0x1a ffffb981`a8f4ff60 fffff801`2d9faa4a     : ffff8884`fd316db0 ffffa20b`1131e1c0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffb981`a8f4ffb0 fffff801`2d9fafb7     : 00000000`00000000 00000000`00000000 ffff8884`fd316f90 fffff801`2d9fafc4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffff8884`fd316d30 fffff801`2d81bfe7     : 00000000`00000010 00000000`00000202 ffff8884`fd316ee8 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffff8884`fd316ec0 fffff801`2d85bd6a     : ffffa20b`18099000 fffff801`2d935262 00000000`00000000 8a000008`400009e3 : nt!KeYieldProcessorEx+0x17 ffff8884`fd316ef0 fffff801`2d85bd2f     : ffff9b51`2028dc77 ffff9b4d`a882c600 ffff9b4d`a6d44160 ffff9b4d`a6d36a20 : nt!KxWaitForLockOwnerShip+0x2a ffff8884`fd316f20 fffff801`30f71753     : ffff8884`fd317050 ffffa20b`18099000 00000000`00000000 fffff801`2d9351ed : nt!KeAcquireInStackQueuedSpinLock+0x7f ffff8884`fd316f50 ffff8884`fd317050     : ffffa20b`18099000 00000000`00000000 fffff801`2d9351ed 00000000`00000000 : iaStorAC+0xd1753 ffff8884`fd316f58 ffffa20b`18099000     : 00000000`00000000 fffff801`2d9351ed 00000000`00000000 ffffa20b`180031a0 : 0xffff8884`fd317050 ffff8884`fd316f60 00000000`00000000     : fffff801`2d9351ed 00000000`00000000 ffffa20b`180031a0 00000008`40099000 : 0xffffa20b`18099000   SYMBOL_NAME:  iaStorAC+d1753  MODULE_NAME: iaStorAC  IMAGE_NAME:  iaStorAC.sys  STACK_COMMAND:  .cxr; .ecxr ; kb  BUCKET_ID_FUNC_OFFSET:  d1753  FAILURE_BUCKET_ID:  0x133_DPC_iaStorAC!unknown_function  OSPLATFORM_TYPE:  x64  OSNAME:  Windows 10  FAILURE_ID_HASH:  {6959f419-2954-fbde-7328-35f9ba64ee7a}  Followup:     MachineOwner ---------      您好！感谢您联系本站支持平台!了解到您目前遇到Windows操作系统出现蓝屏，您不用担心，此问题一般是由于系统中某些应用所属进程或驱动出现问题导致系统宕机引起的，需要您提供您的Minidump文件本身来分析您系统故障的原因，您可以通过以下方案收集您的Dump日志文件：打开控制面板>>系统>>高级系统设置>>高级>>启动和故障恢复>>设置，写入调试信息>>选择“小内存转储（256KB）”，路径选择默认，确定并重启您的计算机。再次异常关机后，前往C:\Windows\Minidump提取即可。再将您收集到的Minidump文件通过私信提供给。当收到私人消息时，可以通过收到的邮件直接进入私人消息界面，或在本站点头像，点击“我的个人资料”右侧的“.”，选择“查看私人消息”进入私人消息界面。另外，也