Mobile and Desktop Processors
Intel® Core™ processors, Intel Atom® processors, tools, and utilities
17363 Discussions

Blue screen for process Intel Connectivity Network Service

abruno
Beginner
‎07-06-2026 06:02 AM
388 Views

This happens on boot up on a HP laptop.


 
Updating Media

 

9: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.....................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000b2`ceaf1018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff807f93a32a0, The address that the exception occurred at
Arg3: ffff98019b6ef2a8, Parameter 0 of the exception
Arg4: ffff98019b6eeab0, Parameter 1 of the exception

Debugging Details:
------------------
KEY_VALUES_STRING: 1

    Key  : AV.Page.Physical
    Value: 0x5113c0000

    Key  : AV.Page.Virtual
    Value: 0xffff98019b6e0000

    Key  : AV.Type
    Value: Unknown

    Key  : Analysis.CPU.mSec
    Value: 1765

    Key  : Analysis.Elapsed.mSec
    Value: 1785

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x1e

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Dump.Attributes.AsUlong
    Value: 0x21800

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

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

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: AV_nt!ExpPoolTrackerChargeEntry

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff807f93a32a0

    Key  : Failure.Exception.IP.Module
    Value: nt

    Key  : Failure.Exception.IP.Offset
    Value: 0x3a32a0

    Key  : Failure.Hash
    Value: {6f13343d-8edf-14f9-0269-6df067c74f57}

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    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: 1

    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: 55447806

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34e10fe

    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: 0x3f7

    Key  : SecureKernel.HalpHvciEnabled
    Value: 1

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 5.3.0.0


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff807f93a32a0

BUGCHECK_P3: ffff98019b6ef2a8

BUGCHECK_P4: ffff98019b6eeab0

FILE_IN_CAB:  MEMORY.DMP

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21800

FAULTING_THREAD:  ffffd285b1093080

EXCEPTION_PARAMETER1:  ffff98019b6ef2a8

EXCEPTION_PARAMETER2:  ffff98019b6eeab0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


PROCESS_NAME:  IntelConnectivityNetworkService.exe

IP_IN_PAGED_CODE: 
nt!ExpPoolTrackerChargeEntry+40
fffff807`f93a32a0 f04b0fc12c06    lock xadd qword ptr [r14+r8],rbp

STACK_TEXT:  
ffff9801`9b6ee1f8 fffff807`f95ad9ff     : 00000000`0000001e ffffffff`c0000005 fffff807`f93a32a0 ffff9801`9b6ef2a8 : nt!KeBugCheckEx
ffff9801`9b6ee200 fffff807`f96c9a66     : ffff9801`9b6eeab0 fffff807`f942b0e8 ffff9801`9b6ee880 fffff807`f92adb94 : nt!KiFatalFilter+0x1f
ffff9801`9b6ee240 fffff807`f94f809c     : ffff9801`00000002 ffff9801`9b6ef2a8 ffff9801`9b6e9000 ffff9801`9b6f0000 : nt!KeExpandKernelStackAndCalloutInternal$filt$0+0x16
ffff9801`9b6ee280 fffff807`f96b2a6f     : ffff9801`9b6ef2a8 ffff9801`9b6ee880 00000000`00000000 00000000`00000000 : nt!_C_specific_handler+0x9c
ffff9801`9b6ee2f0 fffff807`f92ac7b2     : ffff9801`9b6ee380 fffff807`f9000000 fffff807`f92adb94 fffff807`f90e67f4 : nt!RtlpExecuteHandlerForException+0xf
ffff9801`9b6ee320 fffff807`f93deecf     : ffff9801`9b6eeab0 ffff9801`9b6eefb0 ffff9801`9b6eeab0 ffff9801`9b6ef170 : nt!RtlDispatchException+0x2d2
ffff9801`9b6eea80 fffff807`f96bd545     : ffff9801`9b6ef1b0 ffff9801`9b6ef206 00000000`00000001 ffff8709`c8a79030 : nt!KiDispatchException+0x35f
ffff9801`9b6ef170 fffff807`f96b8225     : 00000000`00000030 fffff807`f9b73850 ffff9801`9b6ef510 00000000`00000000 : nt!KiExceptionDispatch+0x145
ffff9801`9b6ef350 fffff807`f93a32a0     : ffff9801`9b6ef7f0 ffffd285`74100000 00000000`00000000 00000000`000001d0 : nt!KiGeneralProtectionFault+0x365
ffff9801`9b6ef4e0 fffff807`f92090d3     : 00000000`00000040 ffffd285`c342a070 ffffbc00`7d81bd50 00000009`00030001 : nt!ExpPoolTrackerChargeEntry+0x40
ffff9801`9b6ef530 fffff807`f9207cc2     : 00000000`00000000 00000000`00000591 00000000`34364d43 00000000`00000000 : nt!ExAllocateHeapPool+0x13a3
ffff9801`9b6ef690 fffff807`f9b7317a     : 00000000`00000040 ffff9801`9b6efa10 00000000`00020019 fffff807`f9846f6e : nt!ExpAllocatePoolWithTagFromNode+0x52
ffff9801`9b6ef6d0 fffff807`f93d902d     : 00000000`00000000 fffff807`f9845c4b 00000000`00000000 000000b2`d0ffcc18 : nt!ExAllocatePool2+0x8a
ffff9801`9b6ef730 fffff807`f96f30b7     : ffff9801`00000016 ffff8709`c74bf790 ffff9801`9b6ef7c8 00000000`00000000 : nt!CmpAllocatePool+0x9
ffff9801`9b6ef760 fffff807`f99e8872     : ffffd285`00000007 000000b2`d0ffcc28 ffff870a`00000000 ffff8709`c74bf790 : nt!CmpAllocateParseContext+0x1b
ffff9801`9b6ef790 fffff807`f96f308d     : 00000000`00000000 00000000`00000000 00000000`00020019 ffff9801`00000000 : nt!CmOpenKey+0x1d2
ffff9801`9b6ef8b0 fffff807`f92adb94     : 00000000`00000000 fffff807`f96f3060 00000000`00000000 00000000`00000000 : nt!CmOpenKeyCallout+0x2d
ffff9801`9b6ef8f0 fffff807`f92abde5     : fffff807`f96f3060 ffff9801`9b6ef9d8 000000b2`d0ffcd08 000000b2`d0ffcfb8 : nt!KeExpandKernelStackAndCalloutInternal+0xd4
ffff9801`9b6ef960 fffff807`f9a43820     : 000000b2`d0ffcc78 fffff807`f96bcb26 00000000`00000000 00000000`00000000 : nt!KeExpandKernelStackAndCallout+0x15
ffff9801`9b6ef9a0 fffff807`f96bca55     : ffffd285`b1093080 00000000`00000002 ffffd285`b1093080 00000000`00000000 : nt!NtOpenKeyEx+0x80
ffff9801`9b6efa20 00007ffd`856e25c4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000b2`d0ffcc08 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`856e25c4


SYMBOL_NAME:  nt!ExpPoolTrackerChargeEntry+40

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND: .process /r /p 0xffffd285b060d080; .thread /r /p 0xffffd285b1093080 ; kb

BUCKET_ID_FUNC_OFFSET:  40

FAILURE_BUCKET_ID:  AV_nt!ExpPoolTrackerChargeEntry

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6f13343d-8edf-14f9-0269-6df067c74f57}

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


 

 

Preview file
145 KB
0 Kudos

Link Copied

1 Reply
TimLawless
Beginner
‎07-11-2026 09:53 AM
275 Views

This appears to be related to an issue under investigation on Microsoft's forums: https://learn.microsoft.com/en-us/answers/questions/5921413/recurring-0x1e-bugcheck-in-nt-exppooltrackercharge

 

It appears it is a crash being caused by faulty 275HX processors when they hit that particular instruction under some unknown precondition. 

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.