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?