Docker causes my computer to blue screen

ericallenpaul · September 25, 2019, 7:39pm

We have several Dell Precision 5810 desktops. All have 1TB mirrored SSD drives and 32GB of RAM.
I have done all of the recommended updates and am using the latest version of windows.

After installing docker desktop my computer starting blue screening on a regular;are basis. There are 2 of us here with the problem. Mostly the BSOD seems to happen when were idle or away from the computer, but sometimes it happens while were working on it. The other guy here uninstalled docker desktop and has not had any BSODs. Unfortuntley, uninstalling is not an option since we need it for development.
I’ve gone as far with DELL support as I can. The minute I related the above data point to the tech they washed their hands of the whole problem. So my own troubleshooting gave them the excuse they needed to dump the case. Not their problem, talk to Microsoft or Docker.

The actual DLL reported on the BSOD is iaStorB.sys which is part of the Intel rapid storage drivers and the raid controller built into the motherboard. I have updated to the latest Intel Driver (both the latest from dell and the latest from Intel directly) but it hasn’t helped. The mini dump file revealed the following:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80731777218, address which referenced memory
 
Debugging Details:
------------------
 
*** WARNING: Unable to verify timestamp for iaStorB.sys
*** WARNING: Unable to verify timestamp for win32k.sys

So the only thing we really know so far is if we uninstall docker completely the problem seems to go away. Anyone have any idea of something we can try to fix the problem?

mccollough67 · October 4, 2019, 12:01pm

Have you seen any movement on this? I’m experiencing the same issue on my home PC.

ericallenpaul · October 7, 2019, 11:33am

Nothing so far. I posted an issue in the Intel forums and have had a few comments. I’m going on vacation this week so I’m going to uninstall docker and see if my computer blue-screens while I’m gone. Uninstalling docker worked for my co-worker and I’m just going to verify that it works for me too.

ericallenpaul · October 7, 2019, 11:42am

Here is a link to the post in the Intel forums:
https://forums.intel.com/s/question/0D50P00004SCWVmSAP/docker-windows-10-v1903-intel-rapid-storage-mirrored-ssds-frequent-bsods?language=en_US&t=1570448096768

ericallenpaul · October 7, 2019, 11:43am

Also… Updating to the latest Intel Rapid storage drivers made the BSODs a little less frequent,

ericallenpaul · October 7, 2019, 6:26pm

OK With Docker uninstalled my computer still blue-screens. So this is not a docker issue. I’m closing this one.

mccollough67 · October 18, 2019, 4:22pm

I moved to the Docker Desktop Edge channel and into the Fast ring for Windows Insider.

I’m pretty sure JUST the Docker Edge build fixed the crashing issue however. I’m currently running 2.1.4.0 from the Edge channel and everything is running great.

abrienne · December 20, 2019, 12:07pm

Some files of docker must be missing that is interrupting to run docker or windows.
There can be various other causes for the blue screen of Death.

also read here:
tenforums/bsod-crashes-debugging/2198-bsod-posting-instructions
bleepingcomputer/forums/f/233/windows-crashes-and-blue-screen-of-death-bsod-help-and-support/
community.hackernoon/t/how-i-solved-blue-screen-of-death-issues-on-my-windows-pc-story/22422

m4cm3nz · November 25, 2020, 12:14pm

I am having the same problem of BSOD IRQL_NOT_LESS_OR_EQUAL after install docker on windows. If I uninstall docker and required components, the erro sotops.
Ive already formatted my notebook, update windows, drivers, bios but nothing solve the problem.

Anyone can help me?

lord9000 · February 23, 2024, 9:36pm

I have some problem

                   Bugcheck Analysis                                    *

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the BugCheck
Arg2: fffff8002ea6ebc4, Address of the instruction which caused the BugCheck
Arg3: ffff8201114b7900, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:

*** WARNING: Check Image - Checksum mismatch - Dump: 0x20f835, File: 0x20f8bd - C:\ProgramData\Dbg\sym\BTHport.sys\5DA12F75203000\BTHport.sys

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2092

Key  : Analysis.Elapsed.mSec
Value: 8396

Key  : Analysis.IO.Other.Mb
Value: 1

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 1

Key  : Analysis.Init.CPU.mSec
Value: 233

Key  : Analysis.Init.Elapsed.mSec
Value: 5422

Key  : Analysis.Memory.CommitPeak.Mb
Value: 97

Key  : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key  : Dump.Attributes.AsUlong
Value: 1808

Key  : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key  : Dump.Attributes.ErrorCode
Value: 0

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key  : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key  : Dump.Attributes.ProgressPercentage
Value: 0

Key  : Failure.Bucket
Value: IP_MISALIGNED_AuthenticAMD.sys

Key  : Failure.Hash
Value: {716d112a-8330-4bbb-160c-ec98297019d2}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key  : Hypervisor.Flags.ApicEnlightened
Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key  : Hypervisor.Flags.Phase0InitDone
Value: 1

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 1

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 4853999

Key  : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key  : Hypervisor.Flags.VpAssistPage
Value: 1

Key  : Hypervisor.Flags.VsmAvailable
Value: 1

Key  : Hypervisor.RootFlags.AccessStats
Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key  : Hypervisor.RootFlags.Value
Value: 1015

Key  : Hypervisor.RootFlags.ValueHex
Value: 3f7

BUGCHECK_CODE: 3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff8002ea6ebc4

BUGCHECK_P3: ffff8201114b7900

BUGCHECK_P4: 0

FILE_IN_CAB: 022424-8484-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

CONTEXT: ffff8201114b7900 – (.cxr 0xffff8201114b7900)
rax=0000000000000023 rbx=ffffd20c6707e080 rcx=0000000000005f23
rdx=ffffd20c68293158 rsi=ffff820111496180 rdi=0000000000000002
rip=fffff8002ea6ebc4 rsp=ffffcf89703d4980 rbp=0000000000000001
r8=0000000000000002 r9=0000000000000000 r10=0000000000000001
r11=ffff71f9e1200000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=ffffd20c6707e180
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!KiCommitThreadWait+0x144:
fffff800`2ea6ebc4 c4 ???
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: ApCent.exe

MISALIGNED_IP:
nt!KiCommitThreadWait+144
fffff800`2ea6ebc4 c4 ???

STACK_TEXT:
ffffcf89703d4980 fffff8002ea734a9 : 0000000000000000 0000000000000001 ffffd20c00000023 000000017c8e3847 : nt!KiCommitThreadWait+0x144
ffffcf89703d4a30 fffff8002eee65b0 : 0000000001282000 0000000009e2f074 0000000000000000 0000000000000002 : nt!KeDelayExecutionThread+0xf9
ffffcf89703d4ab0 fffff8002ec2bce8 : ffffcf89703d4b60 0000000009d2ecf0 ffffffffffe17b80 0000000000000000 : nt!NtDelayExecution+0x60
ffffcf89703d4ae0 00000000771f1cf3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
0000000009d2ece8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x771f1cf3

SYMBOL_NAME: nt!KiCommitThreadWait+144

IMAGE_VERSION: 10.0.22621.3155

STACK_COMMAND: .cxr 0xffff8201114b7900 ; kb

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD.sys

FAILURE_BUCKET_ID: IP_MISALIGNED_AuthenticAMD.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {716d112a-8330-4bbb-160c-ec98297019d2}

Followup: MachineOwner

meyay · February 23, 2024, 10:35pm

Please format your post according these guidelines, so it gets easier to read.

johnny004 · February 27, 2024, 1:30am

make sure you using the latest version of docker. because newier version include fix bugs…

Topic		Replies	Views
Blue Screen of Death always when i start my computer, after install docker Docker Desktop docker , windows	3	7715	March 29, 2017
Docker with idling images causing Windows 10 blue screen? Docker Desktop	1	2201	January 19, 2018
Blue screen randomly happens on container (re)start Docker Desktop	0	1634	November 9, 2018
Is Docker for Windows known to increase the frequency of BSoD on Windows 10? Docker Desktop	0	1183	October 29, 2016
BSOD - KERNEL_MODE_HEAP_CORRUPTION after update Docker Desktop docker , windows11	0	88	July 13, 2024

Docker causes my computer to blue screen

Debugging Details:

Followup: MachineOwner

Related topics