Forum Discussion
BSOD with Message (Resource not owned) when using Pen
Question: Can anyone else maybe with Surface Hardware reproduce this?
Edge Build: 96.0.1035.0
Reproduction: Use Surface Pen, happens instantly
Does not happen on:
Stable Build (I don't know if it was already a case in earlier builds as I didn't use the pen for a while.) Touch inputs.
It's maybe worth noting if it happens to more people here.
I did send a bug report just in case that this isn't known yet
- Last update here!
https://twitter.com/MSEdgeDev/status/1445839848665796610
Canary & Beta channels already have the fix, but we are still rolling it out to Dev & Stable. Relaunching Edge 2-3 times should resolve any issues.
24 Replies
- I'm having this issue on a clean install of win 10 build 19044.1288 experience pack 120.2212.3920.0 getting BSOD using pen with whiteboard after a minute or so. Is on a surface pro 5 and basically rendered it useless. This is a year after the issue seems to have been first raised, is there any help?
Thanks - Last update here!
https://twitter.com/MSEdgeDev/status/1445839848665796610
Canary & Beta channels already have the fix, but we are still rolling it out to Dev & Stable. Relaunching Edge 2-3 times should resolve any issues.Watching at dump files one can only wonder... How is it possible for Edge, being an application, to be able to create BSOD?
The issue is not limited to a specific PC model or specific pen, so other drivers can't be at fault. Then what is? Is the issue really in Bluetooth drivers or Windows kernel? Maybe fixing Edge was a temporary workaround? How is it possible to fix BSOD in win32kbase.sys by updating Edge.
Not trying to start any flame wars or smth, just genuinely curious- I am also really curious about this
Hi, We are having issues with this and wanted to find out when this would be made public.
Some of our users have reported that edge now works with the pens but some have mentioned it still does not working.
Thanks,
Sangeet
Hey again everyone!
As some of you have already noticed, the fix for this was available in yesterday's Canary build! We're speeding it along to the other channels as well, thanks for your patience.
YasinAkimura We're having the same issue on our site on the latest build, but have found that the issue is not present in the 96.0.1037.0 canary build - Hopefully this update gets pushed through soon!
We are an organization of all Surface Pros 250+ and exclusively use Edge and we are having this issue with multiple users.
Hey folks!
The team is aware of this and investigating, I'll circle back here with any updates or if we need additional information to dig in. Thank you so much for your reports of this, both here and in the browser itself!
Alex Rowell (she/her)
Community Manager - Microsoft Edge
Join us on Twitter, or over on Reddit in r/MicrosoftEdge or r/edge- Hi Alexandra,
Thought it might help to note that this issue does not seem to be present in the 96.0.1037.0 canary build! - I can only guess but maybe because the problem does not occur on windows 11 the cause could be some of the new haptic capability if that is tied to software feedback and maybe its good to note that there are two different causes for the BSOD at least if we trust the error message
On Stable Edge I get a BSOD when selecting text with win32key.sys as the failing part. Alexandra-R if it helps in troubleshooting, this isn't isolated to Surface hardware. We use Lenovo gear (X1 Tablet Gen 3 with stylus) and we're getting reports that this BSOD has started happening over the last few days.
- I have the same problem with my Surface Pro 4 (m3) using Edge and trying to use the pen to draw PDF documents: Windows crashes with blue screen and this message.
This behavior started this week, as last week editing PDFs with the pen worked perfectly. Same issue here on Surface Go 2.
I have updated to 21H1 just before BSOD started. But that might be a coincidence.
Thanks for pointing out that it is a pen which is causing the issue. I have disabled Bluetooth and didn't have BSOD ever since. Still able to use the pen for input- same problem here. hope we get a response as surface is unusable now
- I have the same problem with my surface pro X. Also Word is not running smoothly. Please fix all the issues with the surface Pro X Microsoft!!
