Share via

BSOD W10 Ent 1809 since February 19, 2021

Michael 21 Reputation points
2021-02-28T21:51:31.373+00:00

My system has become unstable since February 19, 2021. Many different Blue Screen codes I have run all hardware test from Dell, including memory test in Windows I have rolled back the February update and then reinstalled I have rolled back the Intel AC 9240 wifi driver. etc. I am unable to find a stable point or pin down what is causing the sudden blue screens. Nothing I can determine happened on February 19, 2021 all updates were installed on February 12th and no issues until the 19th. Can someone see something in these minidumps I am not seeing?? Minidumps: https://asub-my.sharepoint.com/:f:/g/personal/mwgoodman_asub_edu/EhtBxxjlaylPhogstDY61S4B0LEfzG8Jo5sKQN3Ho5FrZA?e=6hGRwO

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
11,195 questions
0 comments
Accepted answer
  1. Teemo Tang 11,376 Reputation points
    2021-03-02T01:53:04.27+00:00

    Intelppm.sys is the processor driver, since you have workaround the problem temporarily by disabling Intelppm, that’s good. You could pause update still the March updates release then install the latest one manually, you know the newer updates will include the content of old updates.
    After install the March update, update Intel process driver from manufacturer website and re-enable Intelppm for test.
    You are welcome, I am happy to assist you with Windows update issue.

    -------------------------------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Teemo Tang 11,376 Reputation points
    2021-03-01T02:15:15.953+00:00

    I downloaded four dump files from your OneDrive share to analyze, all of them mentioned IMAGE_NAME: ntkrnlmp.exe, and 022821-10453-01.dump file mentioned PROCESS_NAME: chrome.exe. 

    *******************************************************************************  
*                                                                             *  
*                        Bugcheck Analysis                                    *  
*                                                                             *  
*******************************************************************************  
  
IRQL_NOT_LESS_OR_EQUAL (a)  
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 a kernel debugger is available get the stack backtrace.  
Arguments:  
Arg1: 000000000000000c, memory referenced  
Arg2: 00000000000000ff, IRQL  
Arg3: 0000000000000032, bitfield :  
	bit 0 : value 0 = read operation, 1 = write operation  
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)  
Arg4: fffff8067444c4f2, address which referenced memory  
  
Debugging Details:  
------------------  
  
  
KEY_VALUES_STRING: 1  
  
    Key  : Analysis.CPU.mSec  
    Value: 2343  
  
    Key  : Analysis.DebugAnalysisProvider.CPP  
    Value: Create: 8007007e on WX-69143  
  
    Key  : Analysis.DebugData  
    Value: CreateObject  
  
    Key  : Analysis.DebugModel  
    Value: CreateObject  
  
    Key  : Analysis.Elapsed.mSec  
    Value: 30340  
  
    Key  : Analysis.Memory.CommitPeak.Mb  
    Value: 76  
  
    Key  : Analysis.System  
    Value: CreateObject  
  
    Key  : Dump.Attributes.InsufficientDumpfileSize  
    Value: 1  
  
    Key  : Dump.Attributes.RequiredDumpfileSize  
    Value: 0x8153d0e9  
  
  
ADDITIONAL_XML: 1  
  
OS_BUILD_LAYERS: 1  
  
DUMP_FILE_ATTRIBUTES: 0xc  
  Insufficient Dumpfile Size  
  Kernel Generated Triage Dump  
  
BUGCHECK_CODE:  a  
  
BUGCHECK_P1: c  
  
BUGCHECK_P2: ff  
  
BUGCHECK_P3: 32  
  
BUGCHECK_P4: fffff8067444c4f2  
  
READ_ADDRESS: fffff80674611f08: Unable to get Flags value from nt!KdVersionBlock  
GetUlongFromAddress: unable to read from fffff806746d6540  
fffff80674751390: Unable to get MiVisibleState  
Unable to get NonPagedPoolStart  
Unable to get NonPagedPoolEnd  
Unable to get PagedPoolStart  
Unable to get PagedPoolEnd  
fffff80674611f08: Unable to get Flags value from nt!KdVersionBlock  
 000000000000000c   
  
BLACKBOXBSD: 1 (!blackboxbsd)  
  
  
BLACKBOXPNP: 1 (!blackboxpnp)  
  
  
CUSTOMER_CRASH_COUNT:  1  
  
PROCESS_NAME:  System  
  
TRAP_FRAME:  fffff886cee7f5d0 -- (.trap 0xfffff886cee7f5d0)  
NOTE: The trap frame does not contain all registers.  
Some register values may be zeroed or incorrect.  
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000046  
rdx=ffffc089bc022a00 rsi=0000000000000000 rdi=0000000000000000  
rip=fffff8067444c4f2 rsp=fffff886cee7f760 rbp=0000000000000000  
 r8=00000000ffffffff  r9=0000000000000000 r10=0000000000000001  
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000  
r14=0000000000000000 r15=0000000000000000  
iopl=0         nv up di pl nz na po nc  
nt!PpmIdleExecuteTransition+0x1242b2:  
fffff806`7444c4f2 4038680c        cmp     byte ptr [rax+0Ch],bpl ds:00000000`0000000c=??  
Resetting default scope  
  
STACK_TEXT:    
fffff886`cee7f488 fffff806`743dcce9     : 00000000`0000000a 00000000`0000000c 00000000`000000ff 00000000`00000032 : nt!KeBugCheckEx  
fffff886`cee7f490 fffff806`743d90d4     : 00000083`aacb8323 00000000`00000004 ffff8680`a4be1180 00000000`00000000 : nt!KiBugCheckDispatch+0x69  
fffff886`cee7f5d0 fffff806`7444c4f2     : 00000000`00000000 00000000`00000000 ffffc089`b87317c0 00000000`00000099 : nt!KiPageFault+0x454  
fffff886`cee7f760 fffff806`743280af     : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000008 : nt!PpmIdleExecuteTransition+0x1242b2  
fffff886`cee7fa80 fffff806`743cee5c     : 00000000`00000000 ffff8680`a4be1180 ffff8680`a4bf1300 ffffc089`c4561080 : nt!PoIdle+0x33f  
fffff886`cee7fbe0 00000000`00000000     : fffff886`cee80000 fffff886`cee79000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c  
  
  
SYMBOL_NAME:  nt!PpmIdleExecuteTransition+1242b2  
  
MODULE_NAME: nt  
  
IMAGE_NAME:  ntkrnlmp.exe  
  
IMAGE_VERSION:  10.0.17763.1790  
  
STACK_COMMAND:  .thread ; .cxr ; kb  
  
BUCKET_ID_FUNC_OFFSET:  1242b2  
  
FAILURE_BUCKET_ID:  AV_CODE_AV_nt!PpmIdleExecuteTransition  
  
OSPLATFORM_TYPE:  x64  
  
OSNAME:  Windows 10  
  
FAILURE_ID_HASH:  {3d77750b-80a6-c195-659c-ebcffecd3d05}  
  
Followup:     MachineOwner  
---------  
  
  
*******************************************************************************  
*                                                                             *  
*                        Bugcheck Analysis                                    *  
*                                                                             *  
*******************************************************************************  
  
HYPERVISOR_ERROR (20001)  
The hypervisor has encountered a fatal error.  
Arguments:  
Arg1: 0000000000000011  
Arg2: 00000000002eefbd  
Arg3: 0000000000001005  
Arg4: 0000010000c03a70  
  
Debugging Details:  
------------------  
  
  
KEY_VALUES_STRING: 1  
  
    Key  : Analysis.CPU.mSec  
    Value: 2468  
  
    Key  : Analysis.DebugAnalysisProvider.CPP  
    Value: Create: 8007007e on WX-69143  
  
    Key  : Analysis.DebugData  
    Value: CreateObject  
  
    Key  : Analysis.DebugModel  
    Value: CreateObject  
  
    Key  : Analysis.Elapsed.mSec  
    Value: 15910  
  
    Key  : Analysis.Memory.CommitPeak.Mb  
    Value: 75  
  
    Key  : Analysis.System  
    Value: CreateObject  
  
    Key  : WER.OS.Branch  
    Value: rs5_release  
  
    Key  : WER.OS.Timestamp  
    Value: 2018-09-14T14:34:00Z  
  
    Key  : WER.OS.Version  
    Value: 10.0.17763.1  
  
  
ADDITIONAL_XML: 1  
  
OS_BUILD_LAYERS: 1  
  
BUGCHECK_CODE:  20001  
  
BUGCHECK_P1: 11  
  
BUGCHECK_P2: 2eefbd  
  
BUGCHECK_P3: 1005  
  
BUGCHECK_P4: 10000c03a70  
  
BLACKBOXBSD: 1 (!blackboxbsd)  
  
  
BLACKBOXPNP: 1 (!blackboxpnp)  
  
  
CUSTOMER_CRASH_COUNT:  1  
  
PROCESS_NAME:  chrome.exe  
  
IRP_ADDRESS: ffffffffffffff88  
  
BAD_STACK_POINTER:  ffffbd802dbf0f78  
  
STACK_TEXT:    
ffffbd80`2dbf0f78 fffff801`6c32ee8b     : 00000000`00020001 00000000`00000011 00000000`002eefbd 00000000`00001005 : nt!KeBugCheckEx  
ffffbd80`2dbf0f80 fffff801`6c344c28     : 00000000`00000001 00000000`00000000 ffffbd80`2dbe1180 fffff801`6c353ea0 : nt!HvlSkCrashdumpCallbackRoutine+0x6b  
ffffbd80`2dbf0fc0 fffff801`6c27e702     : ffffad8a`7c2abc20 ffffbd80`2dbf11d0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xe8  
ffffbd80`2dbf1010 fffff801`6c27e4c6     : ffffad8a`7c2abc20 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxNmiInterrupt+0x82  
ffffbd80`2dbf1150 fffff801`6c0fb0fc     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x206  
ffffea07`80fcf730 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopCompleteRequest+0x7bc  
  
  
SYMBOL_NAME:  nt!HvlSkCrashdumpCallbackRoutine+6b  
  
MODULE_NAME: nt  
  
IMAGE_NAME:  ntkrnlmp.exe  
  
IMAGE_VERSION:  10.0.17763.1790  
  
STACK_COMMAND:  .thread ; .cxr ; kb  
  
BUCKET_ID_FUNC_OFFSET:  6b  
  
FAILURE_BUCKET_ID:  0x20001_11_2eefbd_STACKPTR_ERROR_nt!HvlSkCrashdumpCallbackRoutine  
  
OS_VERSION:  10.0.17763.1  
  
BUILDLAB_STR:  rs5_release  
  
OSPLATFORM_TYPE:  x64  
  
OSNAME:  Windows 10  
  
FAILURE_ID_HASH:  {ad02133f-61c0-6cdb-ea17-785f4e9a2ee9}  
  
Followup:     MachineOwner  
---------

    Try to uninstall graphics adapter driver from Device Manager, remove Chrome browser from Control Panel.
    Next, clean boot, install GPU driver from manufacturer, try another browser to monitor computer situation.
    In fact, for Windows 10 1809 version, there are only two updates released in February:
    February 16, 2021—KB4601383 (OS Build 17763.1790) Preview
    February 9, 2021—KB4601345 (OS Build 17763.1757)
    You could uninstall these two updates one by one to check which update lead to BSOD.

    -------------------------------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments
  2. Michael 21 Reputation points
    2021-03-01T21:52:33.587+00:00

    Thank you for your reply.
    It did crash without a browser open and crashed after a reboot using firefox.
    I received several more BSOD and one listed on screen intelppm.sys (the many other BSOD did not list an issue on screen)

    I found online that someone had similar random BSOD and they set the start type to 4 in the registry.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

    After weeks of working with this, I have not had a BSOD in 18 hours since disabling intelppm.

    I suspected a GPU driver issue or the Intel WiFI issue, however both were the latest version and integrity verified.
    Vender supplied GPU driver is somewhat dated.

    After 03 cumulative update is released I will re-enable intelppm.sys and see what happens, I will also keep an eye out for new GPU drivers and new intel drivers.

    0 comments