F5F Stay Refreshed Software Operating Systems BSOD WatchDog alert—possible issue detected. Check for errors or system problems.

BSOD WatchDog alert—possible issue detected. Check for errors or system problems.

BSOD WatchDog alert—possible issue detected. Check for errors or system problems.

M
MrKryp
Senior Member
Find
643
08-31-2019, 06:15 PM
#1
I've tried to combat this problem by updating and reinstalling as many drivers and programs as possible. It's the ntoskrnl.exe with an address in stack of ntoskrnl.exe+ cfb320 and a Bug check code of 0x00000133 The crash will happen randomly. My computer can be idling or it could be while I'm working on something (i.e. word and multiple chrome tabs are open) The crash will happen, but the computer will never reboot on its own. I've left it for over an hour and had to manually turn it off. Here's the line from BlueScreen View ntoskrnl.exe ntoskrnl.exe+cfb320 fffff807`54c00000 fffff807`55c46000 0x01046000 0x90ee290b 1/19/2047 10:12:59 AM Microsoft® Windows® Operating System NT Kernel & System 10.0.19041.572 (WinBuild.160101.0800) C:\WINDOWS\system32\ntoskrnl.exe It's an Alienware 51m, I7 9700, 32 gb ram, rtx 2060 I have bitdefender installed as an antivirus (thought I'd include that incase it's important) Every driver and program is up to date, I've updated my BIOS and the firmware on everything including my SSD's I just don't know what the issue is at this point. It's been happening for months.
Reply
Reply
M
MrKryp
08-31-2019, 06:15 PM #1

I've tried to combat this problem by updating and reinstalling as many drivers and programs as possible. It's the ntoskrnl.exe with an address in stack of ntoskrnl.exe+ cfb320 and a Bug check code of 0x00000133 The crash will happen randomly. My computer can be idling or it could be while I'm working on something (i.e. word and multiple chrome tabs are open) The crash will happen, but the computer will never reboot on its own. I've left it for over an hour and had to manually turn it off. Here's the line from BlueScreen View ntoskrnl.exe ntoskrnl.exe+cfb320 fffff807`54c00000 fffff807`55c46000 0x01046000 0x90ee290b 1/19/2047 10:12:59 AM Microsoft® Windows® Operating System NT Kernel & System 10.0.19041.572 (WinBuild.160101.0800) C:\WINDOWS\system32\ntoskrnl.exe It's an Alienware 51m, I7 9700, 32 gb ram, rtx 2060 I have bitdefender installed as an antivirus (thought I'd include that incase it's important) Every driver and program is up to date, I've updated my BIOS and the firmware on everything including my SSD's I just don't know what the issue is at this point. It's been happening for months.

Reply
Reply
T
Treestub101
Junior Member
Find
12
09-01-2019, 12:47 PM
#2
Locate the minidump file to identify the problem location
Reply
Reply
T
Treestub101
09-01-2019, 12:47 PM #2

Locate the minidump file to identify the problem location

Reply
Reply
D
DiamondGaming4
Member
Find
131
09-04-2019, 03:42 PM
#3
This appears to be a dump file. If not, the minidump.txt is available.
Reply
Reply
D
DiamondGaming4
09-04-2019, 03:42 PM #3

This appears to be a dump file. If not, the minidump.txt is available.

Reply
Reply
D
Djmaster3000
Member
Find
66
09-07-2019, 11:48 PM
#4
The memory dump file is located in a specific folder, usually %SystemRoot%\Minidump. It generally measures around 1MB but may vary slightly in size, often ending with the .dmp extension.
Reply
Reply
D
Djmaster3000
09-07-2019, 11:48 PM #4

The memory dump file is located in a specific folder, usually %SystemRoot%\Minidump. It generally measures around 1MB but may vary slightly in size, often ending with the .dmp extension.

Reply
Reply
R
RugbyGames2200
Junior Member
Find
16
09-07-2019, 11:59 PM
#5
Confirm receipt of 110220-13062-01 - Copy.zip
Reply
Reply
R
RugbyGames2200
09-07-2019, 11:59 PM #5

Confirm receipt of 110220-13062-01 - Copy.zip

Reply
Reply
F
FIZZY258
Member
Find
248
09-08-2019, 03:19 AM
#6
Sure, take your time reviewing it. I'll get back to you once I've finished.
Reply
Reply
F
FIZZY258
09-08-2019, 03:19 AM #6

Sure, take your time reviewing it. I'll get back to you once I've finished.

Reply
Reply
X
xXSuhaibXx
Junior Member
Find
2
09-10-2019, 03:40 AM
#7
Okay, this is a fun one, I'm going to post the crash analysis, then at the end explain what I *think* went wrong. Ready? Here we go! ____ Microsoft ® Windows Debugger Version 10.0.19041.1 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [E:\110220-13062-01 - Copy.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 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff807`54c00000 PsLoadedModuleList = 0xfffff807`5582a310 Debug session time: Mon Nov 2 11:37:52.103 2020 (UTC - 5:00) System Uptime: 0 days 1:30:29.843 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................................... Loading User Symbols Loading unloaded module list .................. For analysis of this file, run !analyze -v 6: 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: fffff807558fb320, 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 Key : Analysis.CPU.Sec Value: 3 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on ASROCK Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 8 Key : Analysis.Memory.CommitPeak.Mb Value: 79 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff807558fb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffffb980`d71fce18 fffff807`55087a14 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffb980`d71fce20 fffff807`54f26993 : 00000ee1`8baccd45 ffffb980`d7200180 00000000`00000000 ffffb980`d7200180 : nt!KeAccumulateTicks+0x15dd24 ffffb980`d71fce80 fffff807`54f2647a : ffffa888`7a4ef260 fffff984`85286e40 fffff984`8527fa00 00000000`00000000 : nt!KeClockInterruptNotify+0x453 ffffb980`d71fcf30 fffff807`54e2ecd5 : ffffa888`7a4ef260 00000000`00000000 00000000`00000000 ffffce2b`797f285f : nt!HalpTimerClockIpiRoutine+0x1a ffffb980`d71fcf60 fffff807`54ff604a : fffff984`85286e40 ffffa888`7a4ef260 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffb980`d71fcfb0 fffff807`54ff65b7 : 0000000c`a46e0522 fffff807`58b182b0 fffff984`85286f88 00000000`00000010 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff984`85286dc0 fffff807`58a619be : 0000000c`aa63e622 ffffa888`7c4f7fb0 fffff984`85287038 fffff807`54e62aed : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff984`85286f50 0000000c`aa63e622 : ffffa888`7c4f7fb0 fffff984`85287038 fffff807`54e62aed 00000000`00000000 : iaStorAC+0xd19be fffff984`85286f58 ffffa888`7c4f7fb0 : fffff984`85287038 fffff807`54e62aed 00000000`00000000 ffffa888`7c4091a0 : 0x0000000c`aa63e622 fffff984`85286f60 fffff984`85287038 : fffff807`54e62aed 00000000`00000000 ffffa888`7c4091a0 00000008`00000015 : 0xffffa888`7c4f7fb0 fffff984`85286f68 fffff807`54e62aed : 00000000`00000000 ffffa888`7c4091a0 00000008`00000015 0000000c`a470677c : 0xfffff984`85287038 fffff984`85286f70 ffffa888`7c456fe8 : 00000000`00000002 ffffa888`00000001 00000000`00000000 fffff807`58ac4020 : nt!MmGetPhysicalAddress+0x1d fffff984`85286fa0 00000000`00000002 : ffffa888`00000001 00000000`00000000 fffff807`58ac4020 00000000`00000001 : 0xffffa888`7c456fe8 fffff984`85286fa8 ffffa888`00000001 : 00000000`00000000 fffff807`58ac4020 00000000`00000001 fffff807`58ac4020 : 0x2 fffff984`85286fb0 00000000`00000000 : fffff807`58ac4020 00000000`00000001 fffff807`58ac4020 fffff984`852870b0 : 0xffffa888`00000001 SYMBOL_NAME: iaStorAC+d19be MODULE_NAME: iaStorAC IMAGE_NAME: iaStorAC.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: d19be FAILURE_BUCKET_ID: 0x133_DPC_iaStorAC!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {6959f419-2954-fbde-7328-35f9ba64ee7a} Followup: MachineOwner --------- Okay, the actual BSoD is because of this: DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. What this basically means is Windows was expecting certain files to be processed in a given amount of time, and those files exceeded their allotted time, causing a crash. The crash was because of this file here: MODULE_NAME: iaStorAC Which is the Intel Rapid Storage module. So...either: (1) Your Intel Rapid Storage driver is way out of date (or mobo drivers in general) OR (2) You have a failing hard drive/ssd somewhere. IIRC (and I may very well be wrong, you'll have to research) the Intel RST driver is optional, assuming you're not running a RAID. But verify this before you wipe it out. Some tips to get you started: https://windowsreport.com/dpc-watchdog-v...windows-8/ https://answers.microsoft.com/en-us/wind...be7ea36d48 Let me know if I can be of further help. Good luck.
Reply
Reply
X
xXSuhaibXx
09-10-2019, 03:40 AM #7

Okay, this is a fun one, I'm going to post the crash analysis, then at the end explain what I *think* went wrong. Ready? Here we go! ____ Microsoft ® Windows Debugger Version 10.0.19041.1 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [E:\110220-13062-01 - Copy.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 19041 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff807`54c00000 PsLoadedModuleList = 0xfffff807`5582a310 Debug session time: Mon Nov 2 11:37:52.103 2020 (UTC - 5:00) System Uptime: 0 days 1:30:29.843 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................................... Loading User Symbols Loading unloaded module list .................. For analysis of this file, run !analyze -v 6: 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: fffff807558fb320, 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 Key : Analysis.CPU.Sec Value: 3 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on ASROCK Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 8 Key : Analysis.Memory.CommitPeak.Mb Value: 79 Key : Analysis.System Value: CreateObject BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff807558fb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffffb980`d71fce18 fffff807`55087a14 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffb980`d71fce20 fffff807`54f26993 : 00000ee1`8baccd45 ffffb980`d7200180 00000000`00000000 ffffb980`d7200180 : nt!KeAccumulateTicks+0x15dd24 ffffb980`d71fce80 fffff807`54f2647a : ffffa888`7a4ef260 fffff984`85286e40 fffff984`8527fa00 00000000`00000000 : nt!KeClockInterruptNotify+0x453 ffffb980`d71fcf30 fffff807`54e2ecd5 : ffffa888`7a4ef260 00000000`00000000 00000000`00000000 ffffce2b`797f285f : nt!HalpTimerClockIpiRoutine+0x1a ffffb980`d71fcf60 fffff807`54ff604a : fffff984`85286e40 ffffa888`7a4ef260 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffb980`d71fcfb0 fffff807`54ff65b7 : 0000000c`a46e0522 fffff807`58b182b0 fffff984`85286f88 00000000`00000010 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff984`85286dc0 fffff807`58a619be : 0000000c`aa63e622 ffffa888`7c4f7fb0 fffff984`85287038 fffff807`54e62aed : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff984`85286f50 0000000c`aa63e622 : ffffa888`7c4f7fb0 fffff984`85287038 fffff807`54e62aed 00000000`00000000 : iaStorAC+0xd19be fffff984`85286f58 ffffa888`7c4f7fb0 : fffff984`85287038 fffff807`54e62aed 00000000`00000000 ffffa888`7c4091a0 : 0x0000000c`aa63e622 fffff984`85286f60 fffff984`85287038 : fffff807`54e62aed 00000000`00000000 ffffa888`7c4091a0 00000008`00000015 : 0xffffa888`7c4f7fb0 fffff984`85286f68 fffff807`54e62aed : 00000000`00000000 ffffa888`7c4091a0 00000008`00000015 0000000c`a470677c : 0xfffff984`85287038 fffff984`85286f70 ffffa888`7c456fe8 : 00000000`00000002 ffffa888`00000001 00000000`00000000 fffff807`58ac4020 : nt!MmGetPhysicalAddress+0x1d fffff984`85286fa0 00000000`00000002 : ffffa888`00000001 00000000`00000000 fffff807`58ac4020 00000000`00000001 : 0xffffa888`7c456fe8 fffff984`85286fa8 ffffa888`00000001 : 00000000`00000000 fffff807`58ac4020 00000000`00000001 fffff807`58ac4020 : 0x2 fffff984`85286fb0 00000000`00000000 : fffff807`58ac4020 00000000`00000001 fffff807`58ac4020 fffff984`852870b0 : 0xffffa888`00000001 SYMBOL_NAME: iaStorAC+d19be MODULE_NAME: iaStorAC IMAGE_NAME: iaStorAC.sys STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: d19be FAILURE_BUCKET_ID: 0x133_DPC_iaStorAC!unknown_function OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {6959f419-2954-fbde-7328-35f9ba64ee7a} Followup: MachineOwner --------- Okay, the actual BSoD is because of this: DPC_WATCHDOG_VIOLATION (133) The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. What this basically means is Windows was expecting certain files to be processed in a given amount of time, and those files exceeded their allotted time, causing a crash. The crash was because of this file here: MODULE_NAME: iaStorAC Which is the Intel Rapid Storage module. So...either: (1) Your Intel Rapid Storage driver is way out of date (or mobo drivers in general) OR (2) You have a failing hard drive/ssd somewhere. IIRC (and I may very well be wrong, you'll have to research) the Intel RST driver is optional, assuming you're not running a RAID. But verify this before you wipe it out. Some tips to get you started: https://windowsreport.com/dpc-watchdog-v...windows-8/ https://answers.microsoft.com/en-us/wind...be7ea36d48 Let me know if I can be of further help. Good luck.

Reply
Reply
L
LarsMatena
Senior Member
Find
602
09-11-2019, 08:15 PM
#8
I don’t use RAID setup. I only have a boot NVMe for games, a dedicated NVMe drive, and a standard HDD. I updated the RST driver to check if that fixes the issue, but if a crash happens again I’ll uninstall it and try another approach. I’ve looked into my SSD and HDD, but found no visible problems. Thanks for your help!
Reply
Reply
L
LarsMatena
09-11-2019, 08:15 PM #8

I don’t use RAID setup. I only have a boot NVMe for games, a dedicated NVMe drive, and a standard HDD. I updated the RST driver to check if that fixes the issue, but if a crash happens again I’ll uninstall it and try another approach. I’ve looked into my SSD and HDD, but found no visible problems. Thanks for your help!

Reply
Reply
I
iron_finder1
Posting Freak
Find
750
09-11-2019, 09:30 PM
#9
The issue might be due to a defective SATA cable. It happened to me, I replaced the cable and the problem disappeared after about six years (my PC is 11 years old).
Reply
Reply
I
iron_finder1
09-11-2019, 09:30 PM #9

The issue might be due to a defective SATA cable. It happened to me, I replaced the cable and the problem disappeared after about six years (my PC is 11 years old).

Reply
Reply