2.94.20 BSOD

MikeH · Post by **MikeH** » Mon Jun 25, 2007 3:03 pm

Tried installing 2.94.20 over 2.94.19: Got BSOD.

A problem has been detected and windows has been shut down to prevent damage to your computer.

The problem seems to be caused by the following file SBIEDRV.SYS.

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

Back to using 2.94.19: could not get 2.94.20 to work.

SnDPhoenix · Post by **SnDPhoenix** » Mon Jun 25, 2007 3:07 pm

....the hell, its back, omg, i thought the BSOD problem was fixed builds ago, granted i havent gotten the bsod since a few builds ago, but still, seems it must be back

did you at least get a mini dump, if so then that would help alot in seeing what might be wrong.

Paul_K · Post by **Paul_K** » Mon Jun 25, 2007 4:52 pm

MikeH wrote:A problem has been detected and windows has been shut down to prevent damage to your computer.

If Windows performed a "memory dump", as happened with me, you may want to check your startup programs for a dumprep o-K entry that Windows puts there. Some research showed me that it can create problems if left there.
Also, on WinNT, a memory dump was created at C:\Winnt\memory.dmp - a very large file that you probably won't be able to use for anything, and will probably want to delete.

street011 · Post by **street011** » Tue Jun 26, 2007 5:58 am

i realy don't know what you do with your computers... but i NEVER had any BSOD with sandboxie...
sorry i can't help here...

tzuk · Post by **tzuk** » Tue Jun 26, 2007 7:51 am

MikeH, I'd appreciate it if you can send me the minidump associated with that crash. Otherwise I can't do anything about it, and you may or may not continue to experience these BSODs in future versions of Sandboxie.

Paul_K · Post by **Paul_K** » Tue Jun 26, 2007 11:58 am

street011 wrote:i realy don't know what you do with your computers... but i NEVER had any BSOD with sandboxie...
sorry i can't help here...

I would have to agree that problems I've had with Sandboxie are probably due to something specific to my computer. Still, I didn't have a BSOD until I got "adventurous" with a couple of the beta versions, one of which is no longer listed in the 'sticky' post (2.94.17). I wish the BSOD was all that was involved. After a re-boot I found that I could not run anything from my Start menu - actually, that's not quite correct: I could start any program, but no window would open. Even Ctrl-Alt-Del would not open the Task Manager window, so another manual shut-down would be needed. Thankfully, V 2.86 is working fine.

My System Event Viewer file has been less than helpful, and I didn't have the minidump option set up correctly, so I will have to wait until I have the time and desire to try again with another version. If I succeed in getting a mini-dump I will make it available.

SnDPhoenix · Post by **SnDPhoenix** » Tue Jun 26, 2007 3:14 pm

wow man that must suck for you, atleast 2.86 is working for you, well hopefully when we get done with the beta versions and the new final rolls around, you wont have those problems, (btw .20 is pretty damn stable)

MikeH · Post by **MikeH** » Tue Jun 26, 2007 6:51 pm

tzuk:

I do not have a minidump file associated with the crash. The last minidump file that I have is dated 2/6/2007. Perhaps the absence of the minidump file is due to the fact that I immediately booted into safe mode (per the installation instructions) to try to uninstall sandboxie. My recollection of events after that is hazy.

Paul_K wrote:

If Windows performed a "memory dump", as happened with me, you may want to check your startup programs for a dumprep o-K entry that Windows puts there. Some research showed me that it can create problems if left there.

I checked my startup items via msconfig and found dumprep 0 -u. The odd thing was that its corresponding box was not checked. My experience has always been that if something shows up in the startup list then its corresponding box is checked.

Paul_K · Post by **Paul_K** » Tue Jun 26, 2007 7:31 pm

MikeH wrote:I checked my startup items via msconfig and found dumprep 0 -u. The odd thing was that its corresponding box was not checked. My experience has always been that if something shows up in the startup list then its corresponding box is checked.

My guess is it's from a different "dump" than the one I had. You can find info about it by searching with Google.
If it's unchecked, you're OK.

For WINNT:
If it bothers you being there, you can find it and the other unchecked items, in the Registry at the MSConfig list located at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig\startupreg

This is where all of the unchecked entries are stored, in case you want to re-check them again.

MikeH · Post by **MikeH** » Wed Jun 27, 2007 9:27 pm

Was able to install 2.94.20. Did so by first uninstalling 2.94.19.

SnDPhoenix · Post by **SnDPhoenix** » Thu Jun 28, 2007 1:59 am

So you were able to install .20 as long as you removed .19 first, but if you tried installing .20 over .19 then it fails? Well try this, try installing .20 over .20 and see what happens.

tzuk · Post by **tzuk** » Thu Jun 28, 2007 6:41 am

I've been thinking about this problem for a bit, I think it should happen fairly infrequently. I am going to increase some small waiting time from 2 seconds to 5 seconds and hope that it further reduces the chances of that.

MikeH · Post by **MikeH** » Thu Jul 05, 2007 11:49 pm

tzuk:

I am almost certain that the BSOD was due to SSM. I believe that I installed SSM the day before I got the BSOD. I started going through the SSM forums and came upon an analgous situation to mine:

http://www.wilderssecurity.com/showthre ... ost1000147

To make a long story short, I uninstalled SSM, then went back and installed version 19. I was then able to install version 20 over version 19 without the BSOD. Continuing on, I installed version 22 over version 20, version 23 over version 22, and finally version 25 over version 23.

This can be moved to Resolved Problems.

As an aside anyone considering SSM might want to check out the included link. Poster FRug solved the BSOD for me, and pointed out a hooking problem with SSM.

Sandboxie Support

2.94.20 BSOD

2.94.20 BSOD

Re: 2.94.20 BSOD

Who is online