Whenever i try and use the eject button on Portable apps 26.2.1 it causes a BSOD (page fault in nonpaged area).
This has happened on two different computers now.
Has anyone else seen this recently?
New: streamWriter (Jun 28, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
The PA.c Platform bundles and uses the open source USB Disk Ejector utility. It uses standard Windows API calls to attempt to eject the disk. Please try using that on its own to see if you can determine where the error is occurring.
Sometimes, the impossible can become possible, if you're awesome!
I used the app from the link provided and had it eject the flash drive (San disk extreme 256GB) that portable apps is installed on. The drive ejected as expected.
But, like before, when i eject from portable apps…i get a blue screen with the same error (PAGE FAULT_IN_NONPAGED AREA)
When you close the platform, it works as expected? If so, please open up the X:\PortableApps\PortableApps.com\App\Bin folder and rename eject.exe to eject-unused.exe. Then try ejecting from the platform again.
Sometimes, the impossible can become possible, if you're awesome!
After renaming…when i push the eject button…it closes out of portable apps but does not eject (as expected)…but also there was NO blue screen.
Interesting.
Create a text file called eject.bat within your X:\PortableApps\PortableApps.com\App\Bin directory with the following contents:
Make sure the PA.c Platform, all your apps, and all your local apps are closed. Then run the batch file.
Sometimes, the impossible can become possible, if you're awesome!
I created the batch file (D:\PortableApps\PortableApps.com\App\Bin eject.exe /REMOVETHIS /SHOWEJECT)
The result is a BSOD with the same error message page_fault in nonpaged area
Ok, we know it's not any of our code. But, it should be impossible for Windows to blue screen from a userspace app making standard Windows API calls unless there's a driver issue.
What OS are you using (version , 32v64-bit)? Do the 2 computers you had this happen on share any specific hardware or unique software quirks?
Sometimes, the impossible can become possible, if you're awesome!
I have tried it on two Lenovo P series mobile workstations (P16 gen 1 and P52s)
The P16 uses 64bit windows 11
The P52s uses 64bit Windows 10
Both OS’s are updated.
We do have a zero trust security application called SentinalOne. It will block executables it does not trust. However, it hasn’t been an issue before.
Unfortunately, I'm not sure what specifically would be causing it on your machines. It could be SentinalOne. Or it could be a bad driver from Lenovo that's used on both laptops.
Could you try copying the version that is in the PA.c Platform to your Desktop and then running the following from the command line in that directory with X being the letter of the drive you use?
eject.exe /REMOVELETTER X
Sometimes, the impossible can become possible, if you're awesome!
Yes, i ran it from the desktop and it blue screens again.
Unfortunately, that's about all the help I can offer at the moment. I was thinking that if it was something I could work around by copying eject.exe locally and having it eject from there I could have something to do. There's a driver or that utility mentioned on your PCs that's causing the BSOD, unfortunately, when a standard Windows API call is made. For now, I'd suggest you don't use the platform to eject, just close on the affected machines.
Sometimes, the impossible can become possible, if you're awesome!