constant PFN_LIST_CORRUPT BSOD on surface pro 7

Question

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?

Answer 1

Update: Still no BSOD since the clean install.

Answer 2

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?

Answer 3

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.

Answer 4

According to statistics I managed to collect It happens everytime when: user1 logs in for the first time after the device rebooted. Camera is ok and Hello works fine. Then user1 locks the screen by any means either automaticaly or by pressing the button. Now user2 takes the device and logs in with Hello and it is OK again. User2 also locks the screen. Now user1 wants to login again and... camera fails after several retries. From this moment it is impossible to recover the camera. Only reboot will help.

Answer 5

Reformatting to FAT32 is not an option. I can only reformat to exFAT or NTFS. Will either of these work?

Which install of Windows do you suggest creating the recovery media for, 1909 or 2004?

Should I update to 20h2 immediately after rei-installing from the USB?