constant PFN_LIST_CORRUPT BSOD on surface pro 7

Anonymous
2020-11-19T08:47:16+00:00

I have a surface pro 7 that I use 90% of the time for taking notes. I've noticed that about once every week, immediately after using the camera in Onenote for Windows 10 I get a PFN_LIST_CORRUPT blue screen. This happens when onenote is syncing with onedrive, after the camera app has shut down. This doesn't occur every time I use the camera, and so far I have only seen this BSOD while using onenote. My four most recent minidump files can be found here: https://1drv.ms/u/s!AmXBsokKEXVkwBl\_KnsTW9XEo91w

Any solutions?

Surface | Surface Pro | Install and update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

98 answers

Sort by: Most helpful
  1. Anonymous
    2020-11-20T00:37:28+00:00

    Hello DanielYu3,

    We're really sorry for the inconvenience this has caused you. 

    Please give these troubleshooting steps a try to isolate the issue.

    1. Disable Antivirus and Security Software. If you have more than one antivirus or any firewall installed, that may cause the error. We highly recommend to just use Windows Security, which is free security and anti-virus tool comes in Windows 10.

    2. Run System File Checker in Windows 10.

    3. **Run Surface Diagnostic Toolkit and check for Windows Update.**Restart the Surface after installing updates. Updates have fixes to common problems, or issues. 4. Update drivers and firmware

    Check what is the current OS Build of your Windows version by typing winveron the search barnear the Windows logo.

    Go to **Download driver and firmware for Surface,**choose (your Surface model) then click Download.

    Choose the .msi file that matches your current OS Build and click Next.

    After downloading, run and install the .msi then Restart. 

    5. Perform a Memory diagnostic. From Search, type Memory Diagnostic and run the Windows Memory Diagnostic program.

    Also, check Windows stops responding on Surface for more info.

    In any event, if the issue persists after performing the above mentioned, I would highly recommend that you reset the Surface using a USB Recovery Image. You must have at least 16GB/32GB of USB Flash drive and it must be formatted to FAT32 prior to downloading the Recovery Image. 

    Note: This removes all the files and apps on your device. You will need to back up your data and reinstall the desktop apps or run updates after the completion.

    To download the Recovery Image:

    1. Visit the page at http://www.surface.com/support/warranty-service-and-recovery/downloadablerecoveryimage
    2. Sign in with your Microsoft Account (this is the email address we asked you for at the start of the call)
    3. From the list of Surface devices available, select the device that you need a recovery image for

    Please note that while you will only be presented with devices that are currently registered on your account, you will also be presented with the option to get an image for a different type of device. If you try to use this option, you will be prompted to enter the serial number for that device 4. Download the recovery image using the button on the page 5. When the download bar pops up at the bottom of your screen, save the file in a location you will be able to find it.

     Format USB Drive:

    1. Insert your USB drive into the USB port of your PC.
    2. From the desktop, open File Explorer
    3. Tap and hold or right-click on the USB drive and choose Format
    4. Select FAT32 as the file system and enter a Volume label to name the USB drive, such as RECOVERY, and then tap or click Start
    5. Tap or click OK to erase the contents of the USB drive
    6. Tap or click OK when the format is complete

    Create a recovery drive:

    1. On your Surface or PC, open recovery image that you downloaded by double-clicking it
    2. At the top of the window tap on Extract and then Extract all. Select the USB drive you formatted earlier for the location and click Extract.

    Perform USB recovery image:

    1. Turn the Surface off by pressing the power button
    2. Insert the USB recovery drive into the USB port
    3. Press and hold the volume-down (-) rocker
    4. Press and release the power button
    5. When the Surface logo appears, release the volume-down (-) rocker
    6. When prompted, choose your language options and keyboard layout
    7. Select Troubleshoot
    8. Select System Image Recovery. Recovering this PC. If prompted for BitLocker Key, tap Skip this Drive.
    9. If prompted, select Repartition the drives

    Hope this helps.

    Kind regards,

    StevenK

    0 comments No comments
  2. Anonymous
    2020-11-20T00:52:33+00:00

    I've tried all the above methods (except memory test) and I have seen nothing out of the ordinary. Would it be possible that the minidump files could provide some clues?

    0 comments No comments
  3. Anonymous
    2020-11-20T01:48:40+00:00

    I just ran memory diagnostic. Windows reports that no problems were found.

    0 comments No comments
  4. Anonymous
    2020-12-07T11:21:32+00:00

    Hi Daniel did you manage to receive some comments from MS on this issue? I have the same issue with my SP7. Camera periodically hangs on login screen or produces a BSOD PFN_LIST_CORRUPT when using Webex/Zoom etc

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-12-07T12:14:08+00:00

    Unfortunately, no. I had to reinstall windows 10 with a surface recovery image because everything else I tried didn't work, and I haven't had any problems since. I assume this is caused by a camera related driver/microcode not integrating correctly with the fresh install, either that or one of the miscellaneous problems windows 10 has become so infamous for.

    MS forums have been of little help, in fact windows 10 is so inconsistent that the guys from MS basically tell you to reinstall the OS in the hopes that things will work correctly and windows won't screw itself up again.

    4 people found this answer helpful.
    0 comments No comments