This is what I got from WinDebug running it from the Sandbox folder

snipped. --tzuk

Thanks for your help!

Sorry, I have not been able to get around the BSOD. As soon as I click on "Capture Kernel", I get the BSOD. At least, I have the info for the BSOD, though googling does not seem to yield anything useful.
Stop:0x000000BE (0x5045837C, 0x00458121, 0xBBB97A68, 0x0000000A) An attempt was made to write to read only memory. This driver may be at fault: Dbgv.sys *** Address 8045837C base at 80400000 datestamp 4b7a1beb ntoskrnl.exe

Is there any way any of these problems could be processor dependent? I am using an Atom N270.

mtl: What processor are you using?

Thanks.

I'm using an Intel Pentium M on a Toshiba Portege M205-S810 Tablet PC.

Thanks mtl. I assume that the abrupt end of the log following "SbieDll INIT START (1) " indicates that your debugger is indicating *BUSY* at the lower left corner, and the SandboxieRpcSs program seems to go on running. Is that right?

You have a file C:\WINDOWS\system32\guard32.dll loading into the process. This isn't a standard Windows file, and it seems to be related to a COMODO product. I did try to reproduce your problem the other day by installing "cisfree_installer_x86.exe" but that didn't really cause any problems for me. Would you mind removing your COMODO product, just temporarily of course, just long enough to get guard32 to not load into SandboxieRpcSs and see if it makes any difference? Thanks.



In rare cases it is possible for hard disk and/or errors in RAM to cause driver crashes and general system craziness. Considering what the SbieDll logs have so far indicated about your system, there is a degree of craziness there. Can you please run some disk checks and memory checks? Thanks.

You were correct. The debugger said *BUSY* at the lower left. I uninstalled Comodo and rebooted. Sandboxie worked after that, so the problem is something to do with Comodo. This is the result of the debugger after uninstalling Comodo:

snipped. --tzuk

After reinstalling Comodo, Sandboxie gives me the same problem. This is what the debugger said after reinstalling Comodo (cisfree_installer_x86.exe).

snipped. --tzuk

Nice progress, mtl, we finally have an idea about what's causing this. I installed COMODO Internet Security Free again, and again no problem. Any ideas which setting I can try to turn on for this? Also I would point out it says version 4.0.141842.828, database version 1. Same as you?

tzuk, I only installed the "COMODO firewall" option (unchecked the other options) and then later on in the install wizard selected "Firewall with Maximum Proactive Defense". I'll play around installing and uninstalling it and playing around with the other settings and see if I get it to work with Sandboxie.

Thank you for your time.

chkdsk reports no errors.
memory test reports no errors.
Further, all of the errors are deterministic. My experience has been that a failing drive or a memory problem will cause more or less random errors. Further, only Sandboxie broke when MS did their update. No other software has started misbehaving. Put another way, everything that used to work - still works, except Sandboxie. debugview was a new thing on this machine.

I do not dispute the strong possibility that something is "different" on my machine. But there is no evidence that it is hardware.

Thanks.

Sorry, I wasn't complete in my answer. I'm going to install the firewall and let you know the options as I go:
* Install in C:\Program Files\COMODO\COMODO Internet Security\
* Check Firewall with Maximum Proactive Defense
* Check "I do NOT want to join the Threatcast community"
* Check "I do not want to use COMODO Secure DNS Servers"
* Uncheck both check boxes (Make Hosurf.com my homepage, and Make Ask.com my default search provider)
* Before restarting the laptop, I uninstalled the COMODO LivePCsupport (it's in Start/Programs/Comodo)

The version I just installed is the same as yours 4.0.141842.828. It doesn't show a database version.

I've played around with some options, I'm not even sure which, but I did start seeing the problem "Stack overflow - code c00000fd (first chance)" at some point. On IE, though, not on SandboxieRpcSS. I'm trying to see what I can do about this, I'll let you know more once I have a better idea.

I disabled all the startup stuff I could. There was no change in behavior. See earlier post re: negative mem or disk errors.

Thanks.

exfetus, if version 3.44 was working well for you, then try version 3.442.

http://www.sandboxie.com/index.php?DownloadSandboxie

mtl, you can do the same of course. As I said before, I also have a handle on the problem now and can reproduce it, it is a little complicated so might take me another day or so to release a proper fix.

tzuk, 3.442 didn't work for me because of Comodo. I'll wait for the next version of Sandboxie.
Thank you for your help with this issue.

tzuk and exfetus, have a great weekend!

tzuk:

Thank you for your efforts. All is well now. Ticket closed.

mtl, try version 3.45.08 please.

http://www.sandboxie.com/phpbb/viewtopic.php?t=7511

exfetus,

I'm glad to hear version 3.442 works, but as you probably realize, it is possible that you might not be able to upgrade beyond this version, due to the problems we identified here, which we could not resolve.