Skip to main content
Start a Conversation

Unsolved

jc6789

1 Rookie

 • 

4 Posts

 • 

14 Points

176

May 15th, 2026 19:51

Tower ECT1250 Blue Screen Error

Hi Everyone,

My Dell ECT1250 had been working well for 7 months until March 2026. Since then it crashed and rebooted frequently at least once a week.

Google search shows that this problem is very likely related to a Windows Update in March 2026, so I installed all windows updates and Dell updates to expect a later fix, but the problem still keeps happening.

Here is the information from the latest crash last night:

Bug check code : 0x0000003B

Bug check parameters :

  • 0x00000000c0000005
  • 0xfffff8063fc9b9dc
  • 0xffff868bad22e540
  • 0x0000000000000000

Device name: Base Win32k Kernel Driver

Driver version: 10.0.26100.8457

Driver path: C:\windows\System32\win32kbase.sys

Report id: 19a29a5f-5583-443d-8a99-3aedd9f26f9e

The details extracted from analyzing the dump file of the crash with WinDbg:

SYSTEM_SERVICE_EXCEPTION (3b)An exception happened while executing a system service routine.Arguments:Arg1: 00000000c0000005, Exception code that caused the BugCheckArg2: fffff8063fc9b9dc, Address of the instruction which caused the BugCheckArg3: ffff868bad22e540, Address of the context record for the exception that caused the BugCheckArg4: 0000000000000000, zero.Debugging Details:------------------KEY_VALUES_STRING: 1Key  : Analysis.CPU.mSecValue: 812Key  : Analysis.Elapsed.mSecValue: 891Key  : Analysis.IO.Other.MbValue: 0Key  : Analysis.IO.Read.MbValue: 1Key  : Analysis.IO.Write.MbValue: 0Key  : Analysis.Init.CPU.mSecValue: 453Key  : Analysis.Init.Elapsed.mSecValue: 94503Key  : Analysis.Memory.CommitPeak.MbValue: 92Key  : Analysis.Version.DbgEngValue: 10.0.29547.1002Key  : Analysis.Version.DescriptionValue: 10.2602.27.2 amd64freKey  : Analysis.Version.ExtValue: 1.2602.27.2Key  : Bugcheck.Code.LegacyAPIValue: 0x3bKey  : Bugcheck.Code.TargetModelValue: 0x3bKey  : Dump.Attributes.AsUlongValue: 0x21808Key  : Dump.Attributes.DiagDataWrittenToHeaderValue: 1Key  : Dump.Attributes.ErrorCodeValue: 0x0Key  : Dump.Attributes.KernelGeneratedTriageDumpValue: 1Key  : Dump.Attributes.LastLineValue: Dump completed successfully.Key  : Dump.Attributes.ProgressPercentageValue: 0Key  : Failure.BucketValue: AV_win32kbase!CoreMessagingK::ClientPortInfo::ReleaseKey  : Failure.Exception.IP.AddressValue: 0xfffff8063fc9b9dcKey  : Failure.Exception.IP.ModuleValue: win32kbaseKey  : Failure.Exception.IP.OffsetValue: 0xfb9dcKey  : Failure.HashValue: {78d78865-0e26-3bbd-dfd3-bb2e7f605e52}Key  : Faulting.IP.TypeValue: PagedKey  : Hypervisor.Enlightenments.ValueHexValue: 0x7417df84Key  : Hypervisor.Flags.AnyHypervisorPresentValue: 1Key  : Hypervisor.Flags.ApicEnlightenedValue: 0Key  : Hypervisor.Flags.ApicVirtualizationAvailableValue: 1Key  : Hypervisor.Flags.AsyncMemoryHintValue: 0Key  : Hypervisor.Flags.CoreSchedulerRequestedValue: 0Key  : Hypervisor.Flags.CpuManagerValue: 1Key  : Hypervisor.Flags.DeprecateAutoEoiValue: 1Key  : Hypervisor.Flags.DynamicCpuDisabledValue: 1Key  : Hypervisor.Flags.EpfValue: 0Key  : Hypervisor.Flags.ExtendedProcessorMasksValue: 1Key  : Hypervisor.Flags.HardwareMbecAvailableValue: 1Key  : Hypervisor.Flags.MaxBankNumberValue: 0Key  : Hypervisor.Flags.MemoryZeroingControlValue: 0Key  : Hypervisor.Flags.NoExtendedRangeFlushValue: 0Key  : Hypervisor.Flags.NoNonArchCoreSharingValue: 1Key  : Hypervisor.Flags.Phase0InitDoneValue: 1Key  : Hypervisor.Flags.PowerSchedulerQosValue: 0Key  : Hypervisor.Flags.RootSchedulerValue: 0Key  : Hypervisor.Flags.SynicAvailableValue: 1Key  : Hypervisor.Flags.UseQpcBiasValue: 0Key  : Hypervisor.Flags.ValueValue: 55185662Key  : Hypervisor.Flags.ValueHexValue: 0x34a10feKey  : Hypervisor.Flags.VpAssistPageValue: 1Key  : Hypervisor.Flags.VsmAvailableValue: 1Key  : Hypervisor.RootFlags.AccessStatsValue: 1Key  : Hypervisor.RootFlags.CrashdumpEnlightenedValue: 1Key  : Hypervisor.RootFlags.CreateVirtualProcessorValue: 1Key  : Hypervisor.RootFlags.DisableHyperthreadingValue: 0Key  : Hypervisor.RootFlags.HostTimelineSyncValue: 1Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabledValue: 0Key  : Hypervisor.RootFlags.IsHyperVValue: 1Key  : Hypervisor.RootFlags.LivedumpEnlightenedValue: 1Key  : Hypervisor.RootFlags.MapDeviceInterruptValue: 1Key  : Hypervisor.RootFlags.MceEnlightenedValue: 1Key  : Hypervisor.RootFlags.NestedValue: 0Key  : Hypervisor.RootFlags.StartLogicalProcessorValue: 1Key  : Hypervisor.RootFlags.ValueValue: 1015Key  : Hypervisor.RootFlags.ValueHexValue: 0x3f7Key  : WER.System.BIOSRevisionValue: 1.13.0.0BUGCHECK_CODE:  3bBUGCHECK_P1: c0000005BUGCHECK_P2: fffff8063fc9b9dcBUGCHECK_P3: ffff868bad22e540BUGCHECK_P4: 0FILE_IN_CAB:  051526-13312-01.dmpTAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202bDUMP_FILE_ATTRIBUTES: 0x21808Kernel Generated Triage DumpFAULTING_THREAD:  ffffaf001ccdc080CONTEXT:  ffff868bad22e540 -- (.cxr 0xffff868bad22e540)rax=fffff8063fc9a500 rbx=ffffaf001cb1dc48 rcx=0000000000000000rdx=0000000000000000 rsi=ffff868bad22f390 rdi=0000000000000024rip=fffff8063fc9b9dc rsp=ffff868bad22ef70 rbp=0000000000000000r8=0000000000000000  r9=ffffaf001ccdc1c0 r10=1fffff00c7f934a0r11=0000000100000000 r12=0000000000000024 r13=fffff80621a50000r14=fffff80621ad66e0 r15=ffff868bad22f240iopl=0         nv up ei ng nz na po nccs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282win32kbase!CoreMessagingK::ClientPortInfo::Release+0x4:fffff806`3fc9b9dc 8b4110          mov     eax,dword ptr [rcx+10h] ds:002b:00000000`00000010=????????Resetting default scopeBLACKBOXBSD: 1 (!blackboxbsd)BLACKBOXNTFS: 1 (!blackboxntfs)BLACKBOXPNP: 1 (!blackboxpnp)BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)CUSTOMER_CRASH_COUNT:  1
PROCESS_NAME:  dwm.exeIP_IN_PAGED_CODE:win32kbase!CoreMessagingK::ClientPortInfo::Release+4fffff806`3fc9b9dc 8b4110          mov     eax,dword ptr [rcx+10h]STACK_TEXT:ffff868b`ad22ef70 fffff806`3fc9a517     : ffff868b`ad22f390 00000000`00000000 00000000`00000005 fffff806`3fc9a822 : win32kbase!CoreMessagingK::ClientPortInfo::Release+0x4ffff868b`ad22efa0 fffff806`3fc9a889     : 00000000`00000000 ffffe78c`dd740500 00000000`00000000 00000000`00000000 : win32kbase!CoreMessagingK::ConnectionTargetInfo::OnDelete+0x17ffff868b`ad22efd0 fffff806`3fc9a766     : ffff868b`ad22f390 00000000`00000000 ffff868b`ad22f390 ffff868b`ad22f070 : win32kbase!CoreMessagingK::CoreMsgObject::OnCallback+0x45ffff868b`ad22f000 fffff806`3fc7b332     : 00000000`00000000 ffff868b`ad22f390 ffff868b`ad22f301 ffff868b`ad22f0a0 : win32kbase!CoreMsgObjectCallout+0x32ffff868b`ad22f030 fffff806`3fc7ad4f     : ffff868b`ad22f390 00000000`00000000 00000000`00000024 ffffaf00`1ccdc080 : win32kbase!W32CalloutDispatchWorker+0x5d6ffff868b`ad22f130 fffff806`21a65775     : ffffe78c`722b42f8 fffff806`9044a92a 00000000`00000008 ffff868b`ad22f290 : win32kbase!W32CalloutDispatch+0xfffff868b`ad22f160 fffff806`21a65f6a     : 00000000`00000000 00000000`00000000 00000000`00000024 00000000`00000000 : win32k!W32AttachToSessionAndExecute<<lambda_2da4d1a9eba595f4b36f293f0999afcd> >+0x1a5ffff868b`ad22f200 fffff806`21a64f63     : 00000000`00000000 00000000`00000090 ffffaf00`1ccdc9c0 00000000`00000024 : win32k!W32SessionAttachAndCalloutDispatch+0x66affff868b`ad22f2c0 fffff806`9052e539     : ffffe78c`78eddb38 ffff868b`ad22f390 00000000`00000000 ffff868b`ad22f340 : win32k!W32CalloutDispatchThunk+0x13ffff868b`ad22f330 fffff806`9052da84     : ffffaf00`1cb1dc10 ffff868b`ad22f3b0 ffffaf00`1cb1dc40 ffff868b`ad22f598 : nt!ExCallCallBack+0x3dffff868b`ad22f360 fffff806`90441778     : fffff806`00000001 ffffe78c`dd740560 00000000`00000074 fffff806`90453300 : nt!ExpWin32DeleteProcedure+0xa4ffff868b`ad22f3c0 fffff806`8ff1fa47     : 00000000`00000000 00000000`00000000 ffff868b`ad22f560 ffffaf00`1cb1dc40 : nt!ObpRemoveObjectRoutine+0x158ffff868b`ad22f420 fffff806`90452863     : ffffaf00`265cf1d0 00000000`00000000 ffffaf00`1cb1dc40 ffffaf00`265cf1d0 : nt!ObfDereferenceObject+0x107ffff868b`ad22f460 fffff806`90451d95     : ffff7c05`7b1cc2b3 fffff806`8ff22430 fffff806`3fde6d18 fffff806`3fbb7d2b : nt!ObInsertObjectEx+0x453ffff868b`ad22f730 fffff806`3fc9b932     : ffffe78d`22190400 00000000`00000000 00000000`00000000 00000000`00000001 : nt!ObInsertObject+0x25ffff868b`ad22f780 fffff806`3fc9a9ea     : ffffe78d`22190480 ffffaf00`1cb1dc40 ffffe78c`78eddb38 ffff868b`ad22f998 : win32kbase!CoreMessagingK::CoreMsgObject::Create+0xfaffff868b`ad22f820 fffff806`3fc9a5fa     : ffff868b`ad22f998 fffff806`21a697e9 00000000`00000000 ffff868b`ad22f998 : win32kbase!CoreMessagingK::ServerPorts::OpenConnection+0xf2ffff868b`ad22f890 fffff806`3fce7489     : 00000000`00000000 ffffe78c`78edd8a0 ffffaf0f`e59cd710 ffffaf00`0ab58c01 : win32kbase!CoreMsgOpenConnection+0x52ffff868b`ad22f8c0 fffff806`3fcc5594     : 00000000`00000000 00000000`00000010 ffff868b`ad22faa0 ffffaf0f`e5bae000 : win32kbase!InputExtensibilityCallout::CoreMsgOpenDestinationHandle+0xa5ffff868b`ad22f930 fffff806`21a5f4d9     : 00000000`00000010 000001e0`0fab56a0 000001e0`0fab56a0 00000024`d14ac000 : win32kbase!NtMITCoreMsgKOpenConnectionTo+0x134ffff868b`ad22f9f0 fffff806`902be241     : ffffaf00`1ccdc080 000001e0`0faff3e0 ffffaf00`1ccdc080 00000000`00000000 : win32k!NtMITCoreMsgKOpenConnectionTo+0x35ffff868b`ad22fa20 00007ff8`058d79f4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x49600000024`d18ff888 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`058d79f4SYMBOL_NAME:  win32kbase!CoreMessagingK::ClientPortInfo::Release+4MODULE_NAME: win32kbaseIMAGE_NAME:  win32kbase.sysIMAGE_VERSION:  10.0.26100.8246STACK_COMMAND: .cxr 0xffff868bad22e540 ; kbBUCKET_ID_FUNC_OFFSET:  4FAILURE_BUCKET_ID:  AV_win32kbase!CoreMessagingK::ClientPortInfo::ReleaseOSPLATFORM_TYPE:  x64OSNAME:  Windows 10FAILURE_ID_HASH:  {78d78865-0e26-3bbd-dfd3-bb2e7f605e52}Followup:     MachineOwner
---------

Will Dell/Microsoft release a new update to solve this issue?

Thanks for your help!

anne_droid

5 Journeyman

 • 

1.9K Posts

 • 

7.2K Points

May 17th, 2026 11:02

Hi

Step-by-step troubleshooting (follow in order)

  1. Install Windows updates and reboot

  • Make sure Windows is fully updated (some 0x3B bugs are fixed by OS updates). Then reboot and check if the BSOD returns.

  1. Repair Windows system files (SFC + DISM)

  • Open an elevated Command Prompt and run:

    • sfc /scannow

    • DISM /Online /Cleanup-Image /ScanHealth

    • DISM /Online /Cleanup-Image /RestoreHealth

  • Reboot after these complete; they repair corrupted system files that can cause win32kbase.sys crashes.

  1. Update or roll back graphics drivers

  • In Device Manager → Display adapters, update the GPU driver from the vendor (NVIDIA/AMD/Intel) — prefer the vendor site installer rather than Windows Update. If the crash started after a driver update, roll back to the previous driver. Many 0x3B crashes are driver-related.

  1. Boot to Safe Mode / test for third‑party driver conflicts

  • Boot to Safe Mode. If the BSOD stops, a third‑party driver/service is likely causing the issue. Use msconfig or Autoruns to disable non‑Microsoft services and drivers, then re-enable incrementally to find the culprit.

  1. Check Event Viewer and collect minidumps

  • Open Event Viewer and inspect System log around the crash time; save minidump files from C:\Windows\Minidump and the full MEMORY.DMP and share them if you need deeper analysis — they indicate the exact call stack and faulting module. Microsoft Q&A and forums commonly request these to pinpoint the driver.

  1. Test RAM and run hardware/firmware checks

  • Run Windows Memory Diagnostic (or memtest86) to rule out faulty RAM; enable BIOS defaults and update BIOS/UEFI firmware (some posts show BIOS or hardware stability fixes help 0x3B). If hardware errors appear, address them (swap RAM sticks, test one stick at a time).

  1. If recent changes preceded the problem, use System Restore or uninstall updates

  • If the BSOD began after an update (Windows or driver), try uninstalling the update or using a restore point to return to a known-good state.

jc6789

1 Rookie

 • 

4 Posts

 • 

14 Points

May 17th, 2026 16:59

Thanks, @anne_droid 

Yesterday I contacted Microsoft online support. The technical support did a Windows repair installation on my PC. Since this crash problem happens averagely once a week, I need to wait a few weeks to see if it is solved by the repair installation.

Your troubleshooting is very comprehensive. If the problem still happens, I'll definitely follow the steps one by one.

Thank you so much for your help!

jc6789

anne_droid

5 Journeyman

 • 

1.9K Posts

 • 

7.2K Points

May 18th, 2026 11:04

Prego.

Rashmik

1 Rookie

 • 

33 Posts

 • 

77 Points

May 22nd, 2026 13:08

“Bugcheck” is sort-of-official Windows nomenclature, or at least a shorthand term, for a BSOD. The bugcheck error in Event Viewer is simply the system’s record of the BSOD event and it usually contains a basic error code that can help identify what caused the BSOD. If minidumps are enabled in advanced system settings then Windows will also dump that same error code and further diagnostic information into a timestamped file (identical to, or close to, the timestamp of the bugcheck event) in %systemroot%\Minidump.

Was this post helpful?

View All

No Events found!

Top