Fun fact: I found the Pro 8 cheaper with $100! But, I'm thinking of buying an apple device, since I've had exelent reliablity from them.
constant PFN_LIST_CORRUPT BSOD on surface pro 7
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.
98 answers
Sort by: Most helpful
-
Anonymous
2022-04-12T19:18:27+00:00 -
Anonymous
2022-04-12T18:56:12+00:00 Since you probably have a free return window, I'd first try it and return it if you have the same problem. It seems that there are also people whose Pro 7 works just fine, I just don't know why it has this bug for some.
However, keeping it if it works might still pose a risk as this particular bug can't really be forced, it happens sometimes but not every time you use the rear camera, so you just have to assess your risk taking individually.
(Also maybe consider the Pro 7+ or Pro 8 as those are better in some aspects, but of course they cost more, too)
-
Anonymous
2022-04-12T18:15:03+00:00 Hi. I just ordered a surface pro 7 today, and I stumbled upon these articles. Should I cancel my order?
-
Anonymous
2022-04-11T14:39:54+00:00 Nope, but I've found that it happens more often with Windows 11, maybe it occurs more often when more of the RAM/CPU is used.
-
Anonymous
2022-04-10T23:27:34+00:00 Thx for the reply. I am just trying everything and anything I can think of. Disabled encryption and have been testing it. It's so damn random it takes a long time to test things. Have you found any sure fire ways to get the BSOD to occure?