Home Edition Notice
--------------------------------------------------------------------------------
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: JUST-A-LAPTOP
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 4294172672 total
VM: 2147352576, free: 1935020032
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 31.08.2011 16:41:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\083111-14196-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003A0B1C4, 0xFFFFF8800CB61680, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 31.08.2011 16:41:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: sbiedrv.sys (SbieDrv+0x1034)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003A0B1C4, 0xFFFFF8800CB61680, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Program Files\Sandboxie\SbieDrv.sys
product: Sandboxie
company: SANDBOXIE L.T.D
description: Sandboxie Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sbiedrv.sys (Sandboxie Kernel Mode Driver, SANDBOXIE L.T.D).
Google query: sbiedrv.sys SANDBOXIE L.T.D SYSTEM_SERVICE_EXCEPTION
On Mon 29.08.2011 16:21:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082911-15834-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003A6D1C4, 0x0, 0x7FFFFFF0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 28.08.2011 10:06:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082811-14196-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x2046EB)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002E46EB, 0xFFFFF8800B1E2850, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
sbiedrv.sys (Sandboxie Kernel Mode Driver, SANDBOXIE L.T.D)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Click to expand...
Problems? See this thread at archive.org.
thanks you alot
