The computer has rebooted from a bugcheck

Gustavo Bonasso 101 Reputation points
2021-05-06T11:15:56.72+00:00

94400-image.png
DMP and minidump here:
https://we.tl/t-RPZXby14zP

i see:

> *******************************************************************************  
> *                                                                             *  
> *                        Bugcheck Analysis                                    *  
> *                                                                             *  
> *******************************************************************************  
>   
> PFN_LIST_CORRUPT (4e)  
> Typically caused by drivers passing bad memory descriptor lists (ie: calling  
> MmUnlockPages twice with the same list, etc).  If a kernel debugger is  
> available get the stack trace.  
> Arguments:  
> Arg1: 0000000000000002, A list entry was corrupt  
> Arg2: 00000000000025f6, entry in list being removed  
> Arg3: 000000000087ffff, highest physical page number  
> Arg4: 0000000000000001, reference count of entry being removed  
>   
> Debugging Details:  
> ------------------  
>   
>   
> KEY_VALUES_STRING: 1  
>   
>     Key  : Analysis.CPU.Sec  
>     Value: 2  
>   
>     Key  : Analysis.DebugAnalysisProvider.CPP  
>     Value: Create: 8007007e on DLT-PAR-GBONASS  
>   
>     Key  : Analysis.DebugData  
>     Value: CreateObject  
>   
>     Key  : Analysis.DebugModel  
>     Value: CreateObject  
>   
>     Key  : Analysis.Elapsed.Sec  
>     Value: 6  
>   
>     Key  : Analysis.Memory.CommitPeak.Mb  
>     Value: 67  
>   
>     Key  : Analysis.System  
>     Value: CreateObject  
>   
>   
> BUGCHECK_CODE:  4e  
>   
> BUGCHECK_P1: 2  
>   
> BUGCHECK_P2: 25f6  
>   
> BUGCHECK_P3: 87ffff  
>   
> BUGCHECK_P4: 1  
>   
> PROCESS_NAME:  System  
>   
> STACK_TEXT:    
> ffffd001`a926e958 fffff802`e73710f4 : 00000000`0000004e 00000000`00000002 00000000`000025f6 00000000`0087ffff : nt!KeBugCheckEx  
> ffffd001`a926e960 fffff802`e738e708 : ffffe000`3e38af20 ffffe000`00000000 ffffd001`00000001 00000000`00000000 : nt!MiUnlinkPageFromLockedList+0x5a4  
> ffffd001`a926e9f0 fffff802`e738e5f9 : fffffa80`00071e20 ffffe000`3e3827c8 ffffe000`3fcd3040 ffffe000`42c67500 : nt!MiReferencePageForCluster+0x14  
> ffffd001`a926ea20 fffff802`e738e1e9 : 00000000`00000004 ffffd001`a926eb09 00000000`00000100 ffffd001`ffffffff : nt!MiFillNoReservationCluster+0xa9  
> ffffd001`a926ea70 fffff802`e73ac1ec : ffffe000`3e38b280 ffffd001`00000100 ffffe000`3eee8040 00000000`0005e7e4 : nt!MiGatherPagefilePages+0x57d  
> ffffd001`a926eb70 fffff802`e734893e : fffff802`e7566180 10101111`11111111 00000000`00000080 ffffe000`3e3b0900 : nt!MiModifiedPageWriter+0x1e0  
> ffffd001`a926ec00 fffff802`e73ccf66 : fffff802`e7566180 ffffe000`3eee8040 fffff802`e75cda00 00000000`00000000 : nt!PspSystemThreadStartup+0x18a  
> ffffd001`a926ec60 00000000`00000000 : ffffd001`a926f000 ffffd001`a9269000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16  
>   
>   
> SYMBOL_NAME:  nt!MiUnlinkPageFromLockedList+5a4  
>   
> MODULE_NAME: nt  
>   
> STACK_COMMAND:  .thread ; .cxr ; kb  
>   
> IMAGE_NAME:  memory_corruption  
>   
> BUCKET_ID_FUNC_OFFSET:  5a4  
>   
> FAILURE_BUCKET_ID:  0x4E_2_VRF_nt!MiUnlinkPageFromLockedList  
>   
> OS_VERSION:  8.1.9600.19939  
>   
> BUILDLAB_STR:  winblue_ltsb  
>   
> OSPLATFORM_TYPE:  x64  
>   
> OSNAME:  Windows 8.1  
>   
> FAILURE_ID_HASH:  {8e246d1e-cb84-7efc-c482-693eeac68d17}  
>   
> Followup:     MachineOwner  
> ---------  

thanks in advance,

Windows for business Windows Server User experience Other
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Docs 15,761 Reputation points
    2021-05-06T17:42:04.59+00:00

    1) Run V2:

    https://www.windowsq.com/resources/v2-log-collector.8/
    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    2) Uninstall and reinstall: (make sure V2 results are posted first)
    MxG2hDO64.sys
    Matrox Graphics

    3) Restart Windows Driver Verifier with these settings:
    https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    4) Open administrative command prompt (ACP) and type or copy and paste:
    5) dism /online /cleanup-image /restorehealth
    6) sfc /scannow
    7) chkdsk /scan
    8) wmic recoveros set DebugInfoType = 7
    9) wmic recoveros get autoreboot
    10) wmic recoveros get DebugInfoType
    11) wmic Computersystem where name="%computername%" set AutomaticManagedPagefile=True
    12) wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
    13) bcdedit /enum {badmemory}
    14) verifier /querysettings

    15) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


  2. Carl Fan 6,881 Reputation points
    2021-05-07T09:06:24.03+00:00

    Hi,
    In addition, please check what update you have installed. The latest update was released on April 13, 2021—KB5001382 (Monthly Rollup).
    You could check for update to install the security update.
    This error is typically caused by a driver passing a bad memory descriptor list. For example, the driver might have called MmUnlockPages twice with the same list.
    For this dump, it only displays kernel error. It doesn't provide some related driver or files.
    So after checking for update, you could use Driver verifier tool to check a miss heaving driver.

    Hope this helps and please help to accept as Answer if the response is useful.
    Best Regards,
    Carl

    0 comments No comments

  3. Gustavo Bonasso 101 Reputation points
    2021-05-13T06:54:27.24+00:00

    hi,
    after reading about what PFN_LIST_CORRUPT means, i saw it is a disk related error. checked server firmware and the disk controller was not up to date.
    i did that and so far this was not reproduced.

    0 comments No comments

  4. Docs 15,761 Reputation points
    2021-05-28T14:35:19.807+00:00

    How come only one non-Microsoft driver was tested?

    i40ea64.sys

    Why not follow the instructions in the Microsoft link in the earlier post?

    When using WDV:
    a) select all non-Microsoft drivers
    b) select no Microsoft drivers

    The bugcheck for the latest BSOD was E3.
    Thu May 27 11:53:27.127 2021 (UTC - 5:00)
    There were no misbehaving drivers identified causing this crash.

    Restart WDV with the driver and customized tests in this link:
    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

    If there are performance problems the customized tests can be modified.

    Run: verifier /querysettings > post results

    For share links please use one drive, drop box, or google drive.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.
    .
    .
    .
    .
    .

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.