Page 2 of 2

Posted: Sat Nov 16, 2013 7:40 am
by Crular
Same problem here running Windows 8.1 and Sandboxie 4.07.3. Crash happened while starting a downloaded program from inside a sandboxed Chrome.

Posted: Mon Nov 18, 2013 4:06 pm
by explanoit
I know it's not much help but I was running into this as well. I haven't had it happen in a few days though and I've made quite a few system changes. Just letting you know.

Posted: Tue Nov 19, 2013 12:23 pm
by DemonAk
launched steam and received Blue screen with error PAGE_FAULT_IN_NONPAGED_AREA, windows 8.1 x64

Minidump

BSoD and a possible temporary workaround

Posted: Sat Nov 23, 2013 3:55 pm
by C. Kuma
I've experienced the BSoD many times while using Windows 8 and 8.1 and with Sandboxie 4.06 and earlier versions. I haven't tried the 4.07 betas yet, though. I have noticed the following behavior, and I hope this information will help while a solution is being sought. Of course, this is just my experience.

1. The BSoD problem doesn't not happen when I'm using an administrator account, only when I'm running a user account.

2. It happens when I start up the first program I try to run in Sandboxie. After I start that first one and it does not cause a BSoD, then I never subsequently experience one (until after the next re-boot, of course).

3. It does not happen (or hasn't yet) if the first program I start while signed into a user account is forced to require administrator privileges to run inside Sandboxie.

So, it seems, for me anyway, that when I use a regular user account and require the first sandboxed program I run to seek administrator privileges, doing so "patches" the problem thus far. I don't experience a BSoD after the first program runs and I haven't experienced any when requiring administrator privileges for that first program.

Re: BSoD and a possible temporary workaround

Posted: Sun Nov 24, 2013 3:22 am
by balloonshark
C. Kuma wrote:I've experienced the BSoD many times while using Windows 8 and 8.1 and with Sandboxie 4.06 and earlier versions. I haven't tried the 4.07 betas yet, though. I have noticed the following behavior, and I hope this information will help while a solution is being sought. Of course, this is just my experience.

1. The BSoD problem doesn't not happen when I'm using an administrator account, only when I'm running a user account.

2. It happens when I start up the first program I try to run in Sandboxie. After I start that first one and it does not cause a BSoD, then I never subsequently experience one (until after the next re-boot, of course).

3. It does not happen (or hasn't yet) if the first program I start while signed into a user account is forced to require administrator privileges to run inside Sandboxie.

So, it seems, for me anyway, that when I use a regular user account and require the first sandboxed program I run to seek administrator privileges, doing so "patches" the problem thus far. I don't experience a BSoD after the first program runs and I haven't experienced any when requiring administrator privileges for that first program.
For a workaround I wonder if we could start notepad.exe as admin in sandboxie as the first program to run sandboxed after boot. After that close notepad and delete the sandbox contents. Would everything work normally until the next boot?

Would it matter which sandbox we would start notepad in? For example could I create a separate sandbox for notepad, close and delete the contents and then have my browser sandbox work normally afterwards?

Edit: Just to be clear about the workaround I was talking about. Does the program only need to be run as admin and/or does Sandboxie's .exe's need to be running as admin? I want to make a shortcut and I'm not sure how to go about it.

Reply

Posted: Sun Nov 24, 2013 6:20 pm
by C. Kuma
It has been my experience than any running program in any sandbox works. I haven't noticed any "preferences" for particular programs. As long as I start the first run sandboxed program as an administrator while using a regular user account, I don't suffer the BSoD. Of course, I would be interested in knowing if others experience the same. Also, it doesn't matter if I just start the program, exit it, and then continue on as I normally would using programs that do not run with administrator privileges. The effect seems to be the same--no BSoD problem.

Posted: Mon Nov 25, 2013 1:27 am
by balloonshark
Thanks C. Kuma. If I can figure out how to make a shortcut to start notepad as admin sandboxed I will give a try for a while.

Posted: Mon Nov 25, 2013 1:59 pm
by tzuk
I have another change in version 4.07.04 that will hopefully fix this problem. Please let me know if it makes a difference.

Same bsod error

Posted: Wed Dec 04, 2013 7:12 am
by Carpz
Hello,

Have same bsod with 4.06 i have crashdump that indicates the same sandboxie driver that other ppl here have said. Il try now 4.07 beta and well see if it works :)

I'l report back.

Posted: Sun Dec 22, 2013 9:03 am
by Carpz
Well it has been 2 weeks and not a single blue screen :)

Guess that change that Tzuk did helped the issue.

Gratz!

Posted: Mon Dec 23, 2013 5:38 am
by tzuk
Thanks Carpz! I am happy to hear this problem is finally fixed.

Posted: Thu Jan 02, 2014 9:53 am
by Throwawayaccount123456
I finally spent yesterday following this guide at as research into the reasons for my frequent bluescreens.

After that, I searched this forum and found two threads with persons having bluescreens.


Maybe the issue has been resolved with the recent beta versions but I figured it wouldn't hurt to submit my minidump analyses. The bluescreens happened using Windows 8.1 (64-bit) and Sandboxie 4.06 (64-bit).
You can download the analyses from here. The password for the archive file is "sandboxie tzuk" without quotation marks.

Tzuk, I can provide you with the *.dmp files as well if you're interested.


I updated Sandboxie to the latest beta version yesterday and will report back in case a bluescreen happens again.

Posted: Fri Jan 03, 2014 3:59 am
by tzuk
Sorry for your trouble, but version 4.07.05 should hopefully fix the problem.

Posted: Fri Jan 03, 2014 7:51 pm
by Mr.X
tzuk wrote:Sorry for your trouble, but version 4.07.05 should hopefully fix the problem.
@tzuk
Hi, I think you should finish this 4.07.05 beta and release the final version before you go to paradise... :) 8)