☰

Windows 10 + Google Drive File Stream + 可执行文件 = BSOD SYSTEM_SERVICE_EXCEPTION (3B)

tag-icon • tag-icon windows bsod google-drive
Windows 10 + Google Drive File Stream + 可执行文件 = BSOD SYSTEM_SERVICE_EXCEPTION (3B)

还没有真正找到这个问题的令人满意的解决方案。

我有 Windows 10 Home x64。
我安装了 Google Drive 和 Drive File Stream，并正在同步我的驱动器。大多数文件都在线，直到我与它们交互，然后它会将它们下载到本地（相当标准）。

当我双击.exe文件, 视窗蓝屏死机马上。 

SYSTEM_SERVICE_EXCEPTION (0x0000003B)

当我右键单击该文件并选择：Drive File Stream>“可离线使用”，
然后双击，它也会蓝屏死机。

我尝试过从 Windows 中完全删除 DFS 并重新安装。
我现在已经将它用在了两个 Windows 安装上，结果是一样的。

尝试向 Google 提出此问题，他们说不支持从 DFS 运行可执行文件，并建议改用备份和同步。

我还没有尝试过，但我觉得这是倒退。他们说这不是 Drive File Stream 的 bug，而是 Windows 的 bug。

如果我向微软提出这个问题，他们只会责怪谷歌。

有人有什么想法吗？

提前致谢！

答案1

好的，在运行并分析 WinDbg 后，我发现安装了一个与崩溃相关的程序。卸载此程序已解决问题。

以下是已删除信息的 WinDbg 输出。您可以看到我已写入 SuspectProgram 的区域。

Microsoft (R) Windows Debugger Version 10.0.19041.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\User\Desktop\052220-6984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff806`15200000 PsLoadedModuleList = 0xfffff806`15648170
Debug session time: Fri May 22 15:45:40.875 2020 (UTC + 10:00)
System Uptime: 0 days 21:04:23.193
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff806153a0cb6, Address of the instruction which caused the bugcheck
Arg3: ffff9e8f9d6bde60, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for SuspectProgram.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on COMPUTERNAME

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 10

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 79

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff806153a0cb6

BUGCHECK_P3: ffff9e8f9d6bde60

BUGCHECK_P4: 0

CONTEXT:  ffff9e8f9d6bde60 -- (.cxr 0xffff9e8f9d6bde60)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=ffff9e8f9d6b005c rsi=ffffa20fcd3f9990 rdi=00000000000031e0
rip=fffff806153a0cb6 rsp=ffff9e8f9d6be858 rbp=ffff9e8f9d6beb89
 r8=0000000000000000  r9=0000000000000000 r10=ffff9e8f9d6be8f0
r11=ffffa20fe0c5e080 r12=0000000000000001 r13=0000000000000000
r14=000000000000000a r15=fffff80615705ef0
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050246
nt!wcsrchr+0x6:
fffff806`153a0cb6 0fb701          movzx   eax,word ptr [rcx] ds:002b:00000000`00000000=????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  explorer.exe

BAD_PAGES_DETECTED: 1

STACK_TEXT:  
ffff9e8f`9d6be858 fffff806`2f322201 : ffffa20f`dc94a080 ffffd80d`4ea09b80 ffffa20f`c72b9040 fffff806`158d35c1 : nt!wcsrchr+0x6
ffff9e8f`9d6be860 ffffa20f`dc94a080 : ffffd80d`4ea09b80 ffffa20f`c72b9040 fffff806`158d35c1 00000000`00000000 : SuspectProgram+0x2201
ffff9e8f`9d6be868 ffffd80d`4ea09b80 : ffffa20f`c72b9040 fffff806`158d35c1 00000000`00000000 00000000`00000000 : 0xffffa20f`dc94a080
ffff9e8f`9d6be870 ffffa20f`c72b9040 : fffff806`158d35c1 00000000`00000000 00000000`00000000 ffffffff`80003f0c : 0xffffd80d`4ea09b80
ffff9e8f`9d6be878 fffff806`158d35c1 : 00000000`00000000 00000000`00000000 ffffffff`80003f0c 00000000`000031e0 : 0xffffa20f`c72b9040
ffff9e8f`9d6be880 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpCloseHandle+0x85


SYMBOL_NAME:  PAGE_NOT_ZERO

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .cxr 0xffff9e8f9d6bde60 ; kb

FAILURE_BUCKET_ID:  PAGE_NOT_ZERO_0x3B_c0000005

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e53488a4-f53d-5828-4e8b-03e3e9cba4c2}

Followup:     MachineOwner
---------

 *** Memory manager detected 1 instance(s) of page corruption, target is likely to have memory corruption.

相关内容