Windows 10: I been having issues with my computer locking up for a moment then recovering (no BSOD) I...

I ran WINdbg and got this:

I believe it's iaStorAC.sys which I know which driver it is I;'m just not sure what my next steps should be.

Any help would be greatly appreciated


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


Loading Dump File [C:\Users\windy\Desktop\083119-14968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 18362 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff806`5aa00000 PsLoadedModuleList = 0xfffff806`5ae46490
Debug session time: Sat Aug 31 23:10:42.037 2019 (UTC - 4:00)
System Uptime: 0 days 4:21:18.735
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
7: 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: fffff8065af71350, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*** WARNING: Unable to verify timestamp 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8065af71350

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: 1068

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: WINDYPRIME

ANALYSIS_SESSION_TIME: 09-01-2019 15:39:07.0340

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

LAST_CONTROL_TRANSFER: from fffff8065abedb41 to fffff8065abbfcc0

STACK_TEXT:
ffff9e81`3e776af8 fffff806`5abedb41 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9e81`3e776b00 fffff806`5aa1ebaf : 00001bba`5fd26563 ffff9e81`3e800180 00000000`00000286 00000000`000f4faf : nt!KeAccumulateTicks+0x1cb841
ffff9e81`3e776b60 fffff806`5a9601e1 : 00000000`00000000 ffffc389`b5efb600 ffff9284`ea297250 ffffc389`b5efb6b0 : nt!KeClockInterruptNotify+0xcf
ffff9e81`3e776f30 fffff806`5aa029e5 : ffffc389`b5efb600 00000000`00000000 00000000`00000000 ffffb9f8`2026d7e7 : hal!HalpTimerClockIpiRoutine+0x21
ffff9e81`3e776f60 fffff806`5abc175a : ffff9284`ea297250 ffffc389`b5efb600 00000000`00000001 ffffc389`b5efb600 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9e81`3e776fb0 fffff806`5abc1cc7 : 00000000`00000002 fffff806`5aaa7ee0 ffff9284`00000000 00001f80`0000020c : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9284`ea2971d0 fffff806`5a95e712 : ffffffff`ffffffd2 fffff806`5d0bcec0 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9284`ea297360 fffff806`5dbb6310 : 00000024`813e9f2c 00000000`00000025 00000000`00000001 00000000`00000000 : hal!KeStallExecutionProcessor+0x112
ffff9284`ea2973e0 fffff806`5d0bcc5a : 00000000`00000025 00000000`00000000 00000000`00000001 00000000`00000000 : storport!StorPortStallExecution+0x10
ffff9284`ea297410 00000000`00000025 : 00000000`00000000 00000000`00000001 00000000`00000000 fffff806`00000001 : iaStorAC+0xbcc5a
ffff9284`ea297418 00000000`00000000 : 00000000`00000001 00000000`00000000 fffff806`00000001 ffffc389`00010000 : 0x25


THREAD_SHA1_HASH_MOD_FUNC: f7237437dc4231397fab354459ccb99524f9ba5e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1d141fce1dd6eb2ff3778b98ba0ffd14bd27c34e

THREAD_SHA1_HASH_MOD: c867aa379652786e2a5d3199dc918f969b5d444c

FOLLOWUP_IP:
iaStorAC+bcc5a
fffff806`5d0bcc5a 448ae6 mov r12b,sil

FAULT_INSTR_CODE: 41e68a44

SYMBOL_STACK_INDEX: 9

SYMBOL_NAME: iaStorAC+bcc5a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: iaStorAC

IMAGE_NAME: iaStorAC.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5d239818

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: bcc5a

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-09-01T03:10:42.000Z

OSBUILD: 18362

OSSERVICEPACK: 295

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 1998-05-30 17:12:57

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 43d6

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_iastorac!unknown_function

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

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

:)

 

Refreshing or Recovering my computer

Hi Kendall,

I highly appreciate your efforts and time.

You will lose applications and drivers or updates installed if you refresh or recover.

• What is the make and model of the computer?
• Did you make any changes prior to this issue?
• What and all steps have you tried so far?

Recovery options in Windows 10:

http://windows.microsoft.com/en-us/windows-10/windows-10-recovery-options

I suggest you to try the steps provided in the link below.

Fix network connection issues:
http://windows.microsoft.com/en-us/windows-10/fix-network-connection-issues

Hope this helps in resolving the issue. If the issue persists, do get back to us. We will be happy to assist you.

Thank you.

 

Lock Screen Image Issue

Hi Kirby,

Thank you for posting the query on Microsoft Community. I am glad to assist you on this.

I would suggest you to set the default pictures as the Lock Screen picture from the PC and check if it works or not.

Follow the steps below:

• In start type "settings" and press enter.
• Select Personalize
• From the left click on "Lock screen"
• Select the default picture and conform by preview.

Please do get back to us to assist you better with issue you are facing.

Thank You.

 

Lock screen not working properly on Windows 10 computer.

Hi Oshith,



I realize the inconvenience you are experiencing with Windows 10. I will certainly help you.



This issue might occur if there is change in lock screen settings.

To assist you better, please provided us the information below:

• When you say that "It is not flapped over to password when clicking", you tried to check the issue by clicking through external mouse?
• Have you made any changes to the computer prior to the issue?

I suggest you to follow the steps below to change the picture of the lock screen and also try to update Display Adapter driver.

Step 1: I suggest you to follow the steps below to set the lock screen pictures.

1. Right click on Desktop screen.

2. Then click on Personalize.

3. Click on Lock Screen.

4. Try to select the lock screen picture.

Step 2: I recommend you to update the latest driver for display adapter in Device Manager.

1. Press Windows Key + R Key.

2. Then type “devmgmt.msc” without the quotes and hit on
Enter Key.

3. Expand Display Adapter.

4. Right click on the driver and click on Update driver software.





Please get back to us with an update on issue with lock screen, we will be happy to help.



Thank you.