windows 10 insider rs5

Please post your problem description here

Moderator: Barb@Invincea

Post Reply
Boscon71
Posts: 5
Joined: Sat Apr 14, 2018 1:13 am

windows 10 insider rs5

Post by Boscon71 » Sat Apr 14, 2018 1:16 am

windows 10 insider 17639 and 17643
Sandboxie hangs on computer :(

tormento
Posts: 1
Joined: Sat Apr 14, 2018 6:01 am

Green screen of death on Windows 10 RS5

Post by tormento » Sat Apr 14, 2018 6:09 am

It's already a couple of Insider releases that launching a program inside Sandboxie gives instant green screen of death.

Any solution available?

Barb@Invincea
Sandboxie Support
Sandboxie Support
Posts: 2316
Joined: Mon Nov 07, 2016 3:10 pm

Re: windows 10 insider rs5

Post by Barb@Invincea » Mon Apr 16, 2018 9:57 am

All,

The latest version of Windows 10 -Insider- Fast Ring that is fully supported can be found here:
https://www.sandboxie.com/VersionChanges#v_5.24

Regarding your issue, I have not received that update yet, so I can't test it. Let's have you provide the required information and the crash dmp files so that the devs can review them:
viewtopic.php?f=11&t=19746

The dump files can be typically found under C:\Windows ---> MEMORY.dmp
You will need to upload it to a file hosting site as it will be a big file. (Please do not upload the minidump, we need the full thing).

Regards,
Barb.-

Boscon71
Posts: 5
Joined: Sat Apr 14, 2018 1:13 am

Re: windows 10 insider rs5

Post by Boscon71 » Mon Apr 16, 2018 12:14 pm

windows 10 home insider build 17643 [rs5]
Sandboxie 5.24.0.0

no antivirus software.
Microsoft Defender turned out.

Auslo˜gics Boos˜tSpeed 10.0.8.0 started in sandbox
and gave me instant green screen of death.


Memory dump here: https://mega.nz/#!0yQRmAxJ!Ysb2RYzY9iHS ... OmJi_5f1Mk

Gretings ppl

Barb@Invincea
Sandboxie Support
Sandboxie Support
Posts: 2316
Joined: Mon Nov 07, 2016 3:10 pm

Re: windows 10 insider rs5

Post by Barb@Invincea » Mon Apr 16, 2018 12:27 pm

Hello Boscon71,

Thanks, I have made the devs aware and will update this thread with any new information.
At this time, we do not have a way to test this as the Insider updates are not providing the latest build yet.

Regarding the app that is crashing, can you please confirm if any other apps cause the same problem?
Also does the app work fine outside Sandboxie?
Are you using any specific settings?
Does the issue follow you to a new Sandbox with default settings?

Regards,
Barb.-

Boscon71
Posts: 5
Joined: Sat Apr 14, 2018 1:13 am

Re: windows 10 insider rs5

Post by Boscon71 » Mon Apr 16, 2018 2:43 pm

Well, any other application makes green screen of death too.

Barb@Invincea
Sandboxie Support
Sandboxie Support
Posts: 2316
Joined: Mon Nov 07, 2016 3:10 pm

Re: windows 10 insider rs5

Post by Barb@Invincea » Mon Apr 16, 2018 3:06 pm

Hello Boscon71,

Also does the app work fine outside Sandboxie?
Are you using any specific Sandboxie settings?
Does the issue follow you to a new Sandbox with default settings?

Please post your Sandboxie configuration file
Configure --> Edit Configuration
Copy-paste the contents here
Highlight the contents and click on the "</>" button here in the forum to format it.

Regards,
Barb.-

Boscon71
Posts: 5
Joined: Sat Apr 14, 2018 1:13 am

Re: windows 10 insider rs5

Post by Boscon71 » Sat Apr 21, 2018 8:50 am

windows 10 home insider build 17650 [rs5]
Microsoft Defender on
naked windows, runned in VirtualBox

no specific Sandboxie configuration

just another memory dump here:

https://mega.nz/#!9joX0IrR!cY57IUp14hzR ... Kjhi-ygyHE

xa0082249956
Posts: 1
Joined: Sat Apr 21, 2018 10:07 pm

Re: windows 10 insider rs5

Post by xa0082249956 » Sat Apr 21, 2018 11:16 pm

Same issue here.

Environment Info
Windows 10 Pro Insider Preview
10.0.17650 N/A Build 17650
AV: Windows Defender

Dump File

https://mega.nz/#!7PpVHTwK!zA85XYdvhGiG ... dKl8rNvUN4

Dump Preview with WinDbg

Code: Select all

DUMP_TYPE:  1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff802062b194b

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff 

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 
nt!MmManagePartitionMemoryInformation+87
fffff802`062b194b 498b87c01b0000  mov     rax,qword ptr [r15+1BC0h]

EXCEPTION_PARAMETER2:  ffffffffffffffff

BUGCHECK_STR:  0x1E_c0000005_R

CPU_COUNT: 4

CPU_MHZ: 9be

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R)  SIG: 24'00000000 (cache) 24'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  SandboxieRpcSs

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  DESKTOP-HC8QJUO

ANALYSIS_SESSION_TIME:  04-22-2018 11:01:48.0652

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER:  from fffff80205fc25c1 to fffff80205f95e30

STACK_TEXT:  
fffffd0c`13259688 fffff802`05fc25c1 : 00000000`0000001e ffffffff`c0000005 fffff802`062b194b 00000000`00000000 : nt!KeBugCheckEx
fffffd0c`13259690 fffff802`05fa6902 : 00000000`00000000 00000000`00000000 ffffd38d`7e216940 ffffd38d`7e216a68 : nt!KiDispatchException+0x18b4e1
fffffd0c`13259d40 fffff802`05fa300d : 00000000`00000000 00000000`00000000 00000000`00000000 ffffd38d`887d29e0 : nt!KiExceptionDispatch+0xc2
fffffd0c`13259f20 fffff802`062b194b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x2cd
fffffd0c`1325a0b0 fffff802`062b1729 : ffffd38d`896a8060 00000000`00000000 00000000`00000000 fffff802`063218ad : nt!MmManagePartitionMemoryInformation+0x87
fffffd0c`1325a280 fffff802`05fa62f3 : 00000000`00000030 00000000`00000000 fffffd0c`1325a3e0 00000000`00000240 : nt!NtManagePartition+0x15d
fffffd0c`1325a410 fffff802`05f99850 : fffff802`04db40e5 00000000`00000080 ffffbed0`80003000 fffffd0c`1325a680 : nt!KiSystemServiceCopyEnd+0x13
fffffd0c`1325a618 fffff802`04db40e5 : 00000000`00000080 ffffbed0`80003000 fffffd0c`1325a680 00000000`00001001 : nt!KiServiceLinkage
fffffd0c`1325a620 fffff802`04e08d4e : 00000000`00000000 ffffd38d`854a3010 00000000`00000020 00007ffc`ecdd4e20 : dxgmms2!VidMmiOpenCurrentPartition+0x61
fffffd0c`1325a790 fffff802`04db3d73 : ffffd38d`88496f00 00000000`00000000 00000000`00000001 00007ffc`00000000 : dxgmms2!VIDMM_PROCESS::Init+0x142
fffffd0c`1325a7c0 fffff802`06ddcbb2 : 00000000`00000000 00000000`00000000 00000000`00000001 ffffc28e`00000000 : dxgmms2!VidMmCreateProcess+0x43
fffffd0c`1325a7f0 fffff802`06ddc4c3 : ffffd38d`854a3010 00000000`00000000 fffff802`06d83d50 00000000`00000001 : dxgkrnl!DXGPROCESS::DeferredInitialize+0xaa
fffffd0c`1325a820 fffff802`06e00d17 : ffffd38d`854a3010 00000000`00000000 ffffc28e`6ff91280 ffffd38d`854a3010 : dxgkrnl!DXGPROCESS::Initialize+0x2c7
fffffd0c`1325a860 fffff802`06e00c3c : 00000000`00000000 00000000`00000007 ffffbed1`46a85cd8 ffffbead`c515e0d0 : dxgkrnl!DXGPROCESS::CreateDxgProcess+0xc3
fffffd0c`1325a8b0 ffffbead`c4fb34b7 : ffffbed1`46a85be0 ffffc28e`6ff91280 ffffbed1`46a85be0 ffffbead`c5166b68 : dxgkrnl!DxgkProcessCallout+0xac
fffffd0c`1325a900 ffffbead`c4cdbefd : fffffd0c`1325aaa0 fffffd0c`00000000 00000000`00000000 00000000`00000000 : win32kbase!GdiProcessCallout+0x1c7
fffffd0c`1325a980 ffffbead`c4fe5698 : fffffd0c`1325aaa0 00000000`00000000 fffff802`061b4fb8 00000000`00000014 : win32kfull!W32pProcessCallout+0xfd
fffffd0c`1325a9b0 ffffbead`c597103a : fffffd0c`1325aaa0 00000000`00000000 00000000`00000000 00000000`00000000 : win32kbase!W32CalloutDispatch+0x68
fffffd0c`1325aa20 fffff802`062ea4bd : 0000007c`07efe848 fffffd0c`1325aaa0 00000000`00000000 000001d2`00000000 : win32k!W32CalloutDispatchThunk+0xa
fffffd0c`1325aa50 fffff802`062a71ae : ffffc28e`72870080 ffffc28e`6ff91280 00000000`00000020 0000007c`07efe218 : nt!ExCallCallBack+0x3d
fffffd0c`1325aa80 fffff802`05f996a9 : 000001d2`12802500 ffffc28e`72870080 fffffd0c`1325ab80 00007ff4`69ab9888 : nt!PsConvertToGuiThread+0xae
fffffd0c`1325aad0 fffff802`05fa66b3 : 00007ffc`000000a4 00000000`00000080 00000000`00000000 0000007c`07efe7d8 : nt!KiConvertToGuiThread+0x9
fffffd0c`1325ab00 00007ffc`ec2524a7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x164
0000007c`07efe898 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`ec2524a7


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  1e03b088300c832a18dd1605076c354d1b7870eb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  abcb1c0e42e0c59964a33713a9039c9184319cc2

THREAD_SHA1_HASH_MOD:  4b4abbcbe48e020641fbae2333f81aa9d28862b7

FOLLOWUP_IP: 
nt!MmManagePartitionMemoryInformation+87
fffff802`062b194b 498b87c01b0000  mov     rax,qword ptr [r15+1BC0h]

FAULT_INSTR_CODE:  c0878b49

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MmManagePartitionMemoryInformation+87

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  61876b30

IMAGE_VERSION:  10.0.17650.1001

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  87

FAILURE_BUCKET_ID:  0x1E_c0000005_R_nt!MmManagePartitionMemoryInformation

BUCKET_ID:  0x1E_c0000005_R_nt!MmManagePartitionMemoryInformation

PRIMARY_PROBLEM_CLASS:  0x1E_c0000005_R_nt!MmManagePartitionMemoryInformation

TARGET_TIME:  2018-04-22T02:03:37.000Z

OSBUILD:  17650

OSSERVICEPACK:  0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2021-11-07 13:59:12

BUILDDATESTAMP_STR:  180414-2140

BUILDLAB_STR:  rs_prerelease

BUILDOSVER_STR:  10.0.17650.1001.amd64fre.rs_prerelease.180414-2140

ANALYSIS_SESSION_ELAPSED_TIME: 66b

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1e_c0000005_r_nt!mmmanagepartitionmemoryinformation

FAILURE_ID_HASH:  {58836dbf-4144-af73-1786-8226846bd2b0}

Boscon71
Posts: 5
Joined: Sat Apr 14, 2018 1:13 am

Re: windows 10 insider rs5

Post by Boscon71 » Thu Apr 26, 2018 9:28 am

windows 10 home insider build 17655 [rs5]

Same problem :(

Reported to Windows Insider but no answer yet.

Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests