win10下登陆qq然后蓝屏笑脸

马台街48

删了qq装上tim也一样会触发，异常log如下

问题签名
问题事件名称:        BlueScreen
代码:        1e
参数 1:        ffffffffc000001d
参数 2:        ffffc0013307e246
参数 3:        ffff9b835a7e5080
参数 4:        f9c
操作系统版本:        10_0_16299
Service Pack:        0_0
产品:        256_1
OS 版本:        10.0.16299.2.0.0.256.48
区域设置 ID:        2052

关于该问题的额外信息
存储段 ID:        0x1E_c000001d_BAD_IP_nt!KiInvalidOpcodeFault

-

EventData

BugcheckCode

30

BugcheckParameter1

0xffffffffc000001d

BugcheckParameter2

0xffffac00e4b17246

BugcheckParameter3

0xffffd90955f0b700

BugcheckParameter4

0x1258

SleepInProgress

0

PowerButtonTimestamp

0

BootAppStatus

0

Checkpoint

0

ConnectedStandbyInProgress

false

SystemSleepTransitionsToOn

0

CsEntryScenarioInstanceId

0

BugcheckInfoFromEFI

true

CheckpointStatus

0

有人遇到过吗

V5Style

https://docs.microsoft.com/en-us ... ception-not-handled
内核或驱动触发了非法指令。

建议楼主自己用 WinDbg 查一下是哪个驱动导致的，另外建议驱动能更新的就更新。
https://www.microsoft.com/zh-cn/p/windbg/9pgjgd53tn86
说不定是 QPCore 导致的。

Atail

不会有windbg的话可以发一下dmp文件，自行百度位置在哪儿

营业收入

我也建议用 WinDbg 来检查蓝屏后生成的转储文件
WinDbg 使用方法可以参考 https://www.forece.net/post/3794.htm

马台街48

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


Loading Dump File [C:\Windows\Minidump\082221-8062-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 16299 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff801`5441e000 PsLoadedModuleList = 0xfffff801`54784fd0
Debug session time: Sun Aug 22 15:14:38.333 2021 (UTC + 8:00)
System Uptime: 0 days 0:01:52.154
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`545936e0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffd004`e3a1b0e0=000000000000001e
9: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: ffff9780045a6246, The address that the exception occurred at
Arg3: ffff840250d01080, Parameter 0 of the exception
Arg4: 000000000000095c, Parameter 1 of the exception

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1749

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 1844

    Key  : Analysis.Init.CPU.mSec
    Value: 1561

    Key  : Analysis.Init.Elapsed.mSec
    Value: 1262030

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc000001d

BUGCHECK_P2: ffff9780045a6246

BUGCHECK_P3: ffff840250d01080

BUGCHECK_P4: 95c

EXCEPTION_PARAMETER1:  ffff840250d01080

EXCEPTION_PARAMETER2:  000000000000095c

BLACKBOXBSD: 1 (!blackboxbsd)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  QQ.exe

TRAP_FRAME:  ffff840200000000 -- (.trap 0xffff840200000000)
Unable to read trap frame at ffff8402`00000000

FAILED_INSTRUCTION_ADDRESS:
+0
ffff9780`045a6246 ff              ???

STACK_TEXT:  
ffffd004`e3a1b0d8 fffff801`545c6d3d     : 00000000`0000001e ffffffff`c000001d ffff9780`045a6246 ffff8402`50d01080 : nt!KeBugCheckEx
ffffd004`e3a1b0e0 fffff801`545a680e     : 00000000`00000000 fffff801`544c6749 ffff8402`00000000 ffff8402`50d4c080 : nt!KiDispatchException+0x11ec9d
ffffd004`e3a1b790 fffff801`545a0659     : 00000000`00000001 00000000`00000001 00000000`00000000 ffff8402`50d311f0 : nt!KiExceptionDispatch+0xce
ffffd004`e3a1b970 ffff9780`045a6246     : ffff8402`50d01080 00000000`12633200 00000000`00000000 ffff8402`4c851670 : nt!KiInvalidOpcodeFault+0x3d9
ffffd004`e3a1bb00 ffff8402`50d01080     : 00000000`12633200 00000000`00000000 ffff8402`4c851670 00000000`00000000 : 0xffff9780`045a6246
ffffd004`e3a1bb08 00000000`12633200     : 00000000`00000000 ffff8402`4c851670 00000000`00000000 00001f80`02010000 : 0xffff8402`50d01080
ffffd004`e3a1bb10 00000000`00000000     : ffff8402`4c851670 00000000`00000000 00001f80`02010000 00000000`0003000f : 0x12633200


SYMBOL_NAME:  nt!KiDispatchException+11ec9d

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.16299.192

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  11ec9d

FAILURE_BUCKET_ID:  0x1E_c000001d_BAD_IP_nt!KiDispatchException

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {32d53838-e3d6-fa50-5106-1dd1cbc4aba1}

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



所以是ntkrnlmp.exe导致的吗  我更新下驱动试试

calmer

感觉像腾讯的人瞎几把写驱动

—— 来自 HUAWEI NOP-AN00, Android 10上的 S1Next-鹅版 v2.4.4.1

上班族

qq就应该扔虚拟机里
虽然我自己也懒

系统杀手

我把qq扔进了sandboxie就不怕了。但前提是扔沙盘前电脑里不能已经安装腾讯的安全驱动，比如qqprotect啥的。已经装了安全驱动的依旧会透传搞崩系统。

马台街48

折腾了好久还是没搞定  这台电脑装了一堆开发环境实在不想重装  拜拜了您内 fuck Tencent Inc