This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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.
My 20H2 reinstallation using Media Creation Tool apparantly didn't really fix it, I just didn't use my rear camera as often because pandemic and stuff. I will try using the 2004 recovery image now, I hope that will fix it, otherwise, I will call the Microsoft Support and ask them to do something like giving me a working device, I don't know how.
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?
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.
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?
Update: Still no BSOD since the clean install.
