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

98 answers

Sort by: Newest
  1. Anonymous
    2021-02-16T19:35:09+00:00

    Hi All,

    The issue is still in place. I haven't experienced BSOD since the last FW and Windows updates but I still have this annoying problem with camera hangs when trying to recognize me with Windows Hello.

    The issue appears as follows:

    First Face recognition after reboot or normal boot happens just fine. But once another user logs in using Windows secondary login function camera goes crazy. Visually it looks like it hangs because it turns on and ofа the infrared instrument and small white LED light several times and then it dies with infrared turned off and the white light stays on no matter what is happening next. Then, obviously, the camera becomes completely not functional in any applications and it is impossible recover it even turning the device on and off in Devices MMC.

    I think this is somehow related to the secondary login functionality of Windows and the Camera driver unable to handle it.

    Any thoughts?

    Does this happen every time someone else was logged in before or just occasionally? Every once in a while, I have a similar issue, but it doesn't happen often enough to be a major annoyance.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-02-16T08:03:57+00:00

    Hi All,

    The issue is still in place. I haven't experienced BSOD since the last FW and Windows updates but I still have this annoying problem with camera hangs when trying to recognize me with Windows Hello.

    The issue appears as follows:

    First Face recognition after reboot or normal boot happens just fine. But once another user logs in using Windows secondary login function camera goes crazy. Visually it looks like it hangs because it turns on and off the infrared instrument and small white LED light several times and then it dies with infrared turned off and the white light stays on no matter what is happening next. Then, obviously, the camera becomes completely not functional in any applications and it is impossible to recover it even turning the device on and off in Devices MMC.

    I think this is somehow related to the secondary login functionality of Windows and the Camera driver unable to handle it.

    Any thoughts?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-02-15T22:50:11+00:00

    Update: Still no BSOD since the clean install.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-02-15T13:30:19+00:00

    pretty much the same thing here, it happened when I used Onenote to directly inmport a picture from the camera. I was able to select the picture taken, crop it and insert it into the notebook, a few seconds later BSOD. Rebooted, ran all the tests, all negative. I have been doing this Onenote and camera routine for months, never an issue before today. Win 10 Home 20h2 Nov 20th 2020).

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-02-03T22:44:07+00:00

    This is the exact same thing that happened to me. I bought a surface at the beginning of January, returned it and bought another new one now. 

    I have the issue with both 2004 and 20h2.

    I did a clean install using Windows 10 Media Creation Tool (20H2) last Friday and I haven't experienced any blue screens since. I can't guarantee that it has worked though, as I will have to wait a little longer to make sure.

    If you want to do this, make sure you have the type cover or a USB keyboard because the touchscreen drivers aren't shipping with Windows 10 itself. You then have to install the drivers package from the Microsoft website. I also followed the advice of someone who replied to another post here to copy some device specific files to the clean install so that features like "Enhanced" color mode and the Surface app work properly (Though I don't know if it would've worked without it as well).

    Was this answer helpful?

    0 comments No comments