I have been using sandboxie recently in a project of mine and in my project I began making individual Sandboxies having their own name, to explain what happens:
On making the Sandboxies and as you know I can then right click on the Sandboxie Control which is located in system tray and in doing so you’ll agree that I would see all my sandboxies and with a label to the right side of the list.
In any case as I proceed to make my sandboxies I get to making about 6 or 10 and then a BSOD - Nonpaged Area.
I tried to see if there was something else causing this and thus I began updating all drivers and also checked my ram with testing etc. No issues reported.
I proceeded again with Sandboxie and began the same again making sandboxies with their own name. Again the same BSOD - Nonpaged Area. I repeated this several times to see if indeed it was sandboxie and I have whittled it down to Sandboxie being the issue.
My system info:
OS Name Microsoft Windows 10 Pro
Version 10.0.15063 Build 15063
Code: Select all
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name COMP
System Manufacturer ASUS
System Model All Series
System Type x64-based PC
System SKU All
Processor Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz, 3501 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1202, 04/12/2014
SMBIOS Version 2.8
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Binding Not Possible
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume3
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.15063.0"
Username Comp
Time Zone GMT Summer Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 29.1 GB
Total Virtual Memory 36.7 GB
Available Virtual Memory 33.7 GB
Page File Space 4.75 GB
Page File C:\pagefile.sys
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware No
Hyper-V - Data Execution Protection Yes