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.
Mine is 1866. Mostly have issues with front cam. Just because I do not use rear one. The issue appears in Zoom, Skype and other meeting apps
1866 is the model number, not the LOT number (all Pro 7 i5 8GB 128GB models are model 1866). The LOT number is on the same sticker on the underside of your box, but a bit further down and a little smaller. It says LOT: XXXX with XXXX being the LOT number.
Let’s sue them! People received $500 million from Apple for battery issues with 6 and 7 iPhone.
They sell faulty device and refuse to fix issues it has. I have Pro5 at work which is free of any such issues. I am gonna check the camera device make/model on it to compare. Will keep you posted
Mine is 1866. Mostly have issues with front cam. Just because I do not use rear one. The issue appears in Zoom, Skype and other meeting apps
Yes, the only reason why I don't think it's just driver or software related is that there appear to be people out there who use their rear camera regularly and don't report this issue.
By the way, the technical department did not get back to me, so I got my device replaced. The replacement unit (thankfully advanced exchange) had an even bigger issue (BSOD's all the time while setting it up). Tomorrow I will receive another replacement device, I'll try not to install anything on that one for a while. If it crashes, I'll try to get my favourite support agent to ask his supervisor if I can get a Pro 7+, if not, I will start installing more software one at a time.
I'll keep you posted about it.
Could you please check the LOT number of your original device? You can find it on the underside of your box on the sticker. Somewhere between the barcodes it says LOT: XXXX . Mine is 2037, if yours is the same or at least somewhat similar, that might mean that they used a faulty component in that batch.
Decided to chime in just to see if MS would react in some way. I highly doubt this is a high-level software issue: My Surface BSOD'ed on me again a few days back when I was recording a video using the basic in-built camera app. I also somewhat doubt this is a hardware issue since the problem seems to be very widespread (there are several Reddit threads about it) and appears on replacement units too (often more than once in a row). My guess of the culprit would be a camera-related bug in post-1909 versions of windows 10. I'm out of ideas concerning how we should sway MS into fixing this issue (it's been there for almost a year and their customer service is sh*t), hopefully someone would come up with a petition of sorts.
Also my device's lot number is 2024, if that helps.
