BSOD at shutdown PFN Corrupt message

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 34
    Windows 7 home
    Thread Starter

    Yes reran it before I posted the newest V2 - run it again?
      My Computer

  2. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    Yes please. If/when you get a BSOD, run V2 as soon as possible. Also, take a picture of the BSOD screen if there is any information on it that may be useful. Make sure Automatic restart on system failure is disabled:

    You can turn off automatic restart so you can read BSOD information:

    Right click on This PC and select Properties.
    Click Advanced system settings then Startup and Recovery Settings.
    Uncheck box for Automatically restart.
      My Computers

  3. Posts : 34
    Windows 7 home
    Thread Starter
      My Computer

  4. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    Did you take pictures of any of the BSOD screens when Driver Verifier was active?
    Have you disabled Automatic Restart yet?

    None of the dumps in the zip have Driver Verifier enabled.
      My Computers

  5. Posts : 34
    Windows 7 home
    Thread Starter

    Sorry Rich I am not sure I know what I did wrong. Will go back to square one from your original post and repeat it all. I could not take pix of BSOD but the message stated Corrupted PFN - I will write down any following messages and report in. Thanks for your patient assistance.
      My Computer

  6. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    I'm asking for the pic of the BSOD screen in case there is information on the screen indicating what driver cause it. Sometimes it gets overlooked.

    When you use DV this time, start with 5 drivers. After a half hour or hour, if no BSOD, add 5 more and repeat.
      My Computers

  7. Posts : 34
    Windows 7 home
    Thread Starter

    OK will try that. I will try to get a pic for you next crash
      My Computer

  8. Posts : 34
    Windows 7 home
    Thread Starter

    I ran with verifier two days without any BSOD excepting the PFN LIST CORRUPT that occurs at shutdown. I went back through all steps and here are the logfiles. Log Collector stopped when msinfo.exe timed out. I reran this manually and it got hung at OLE Registration step. - Google Drive
    OWNER981841-PC-(2020-07-30_09-53-22).zip - Google Drive

    - - - Updated - - -

    msinfo32.nfo - Google Drive
    Last edited by bam12b; 30 Jul 2020 at 09:55. Reason: typo
      My Computer

  9. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    Run the older DM log collector and upload it's zip file.

    Run Verifier again, following this tutorial: Enable and Disable Driver Verifier in Windows 10
    Especially Part Two Step 4.

    Also make sure these are checked:

    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [X] 0x00200000 NDIS/WIFI verification.
    [X] 0x02000000 Code integrity checks.
      My Computers

  10. Posts : 13,934
    Windows 10 Pro X64 21H1 19043.1503

    Zbook just pointed out to me there was a driver problem in a dump from 7/26 : 062620-25890-01.dmp

    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.
    Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
    Arg2: 00000000000033cb, page frame number
    Arg3: 0000000000000001, current share count
    Arg4: 0000000000000000, 0
    Debugging Details:
    *** WARNING: Unable to verify timestamp for LHidEqd.Sys
    fffff58d`1e3c46b0  fffff803`135a0000Unable to load image LEqdUsb.Sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for LEqdUsb.Sys
    Name LEqdUsb.Sys Date: 6/9/2015 3:25:30 PM
    Info Logitech SetPoint Unifying KMDF USB Filter
    Source SetPoint – Logitech Support + Download

    Driver is pretty old. See if you can find an update for it or uninstall it if it's not needed.
      My Computers


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 17:31.
Find Us

Windows 10 Forums