每次打开trae work cn,必蓝屏,昨晚更新后开始的

正文是使用WhoCrashed获取到的最近5次dump文件内容:Crash Dump Analysis


Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Thu 2026/7/16 12:04:54 your computer crashed or a problem was reported

Crash dump file: C:\Windows\Minidump\071626-24250-01.dmp (Minidump)
Bugcheck code: 0x139(0xA, 0x0, 0x0, 0xFFFFF10A16B967F0)
Bugcheck name: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

On Thu 2026/7/16 12:01:32 your computer crashed or a problem was reported

Crash dump file: C:\Windows\Minidump\071626-24421-01.dmp (Minidump)
Bugcheck code: 0x139(0xA, 0x0, 0x0, 0xFFFFD2090A8CE7F0)
Bugcheck name: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

On Thu 2026/7/16 11:57:04 your computer crashed or a problem was reported

Crash dump file: C:\Windows\Minidump\071626-23406-01.dmp (Minidump)
Bugcheck code: 0x50(0xFFFFF803FC635070, 0x10, 0xFFFFF80374635070, 0x2)
Bugcheck name: PAGE_FAULT_IN_NONPAGED_AREA
Driver or module in which error occurred: Ntfs.sys (Ntfs+115070)
File path: Ntfs.sys
Description: NT 文件系统驱动程序
Product: Microsoft? Windows? Operating System
Company: Microsoft Corporation
Bug check description: This indicates that invalid system memory has been referenced. This can be caused by a faulty driver. Antivirus software can also trigger this error, as can a corrupted NTFS volume. It can also be caused by faulty hardware, (in particular faulty or overheated RAM or video RAM) or an overheated system component.
Analysis: This is likely a software problem which means that it was probably caused by a bug in a driver.
There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It’s suggested that you run CHKDSK to check your drive(s) for errors.

On Thu 2026/7/16 9:56:21 your computer crashed or a problem was reported

Crash dump file: C:\Windows\Minidump\071626-22109-01.dmp (Minidump)
Bugcheck code: 0x139(0xA, 0x0, 0x0, 0xFFFFBA024F4E67F0)
Bugcheck name: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

On Thu 2026/7/16 9:50:50 your computer crashed or a problem was reported

Crash dump file: C:\Windows\Minidump\071626-23656-01.dmp (Minidump)
Bugcheck code: 0x139(0xA, 0x0, 0x0, 0xFFFFC08D239867F0)
Bugcheck name: KERNEL_SECURITY_CHECK_FAILURE
Bug check description: The kernel has detected the corruption of a critical data structure.
Analysis: This particular bugcheck may be caused by malware or a security product that does not follow programming guidelines. This can also be caused by memory corruption. This is possibly a software problem. There is a possibility that this is caused by memory corruption. Memory corruption can be caused by a faulty driver, faulty RAM, overheating and more. Read this article on memory corruption. Read this article on thermal issues

看到你发来的 dump 分析了~针对 Windows 上的 TRAE Work(原 TRAE SOLO)桌面版,普通的软件更新一般是不会直接导致系统蓝屏的。

从你提供的 0x139 KERNEL_SECURITY_CHECK_FAILURE 报错来看,这通常是应用在启动时,与电脑上的安全防护软件(杀毒软件)或者底层驱动发生了冲突。

我们可以先试着从这两个方向排查一下:

  1. 安全软件冲突:如果你电脑上装着火绒、360、迈克菲等第三方杀毒软件,它们的某些内核拦截机制可能会在 TRAE Work 启动时触发蓝屏。建议你暂时完全退出这些安全软件,再尝试打开看看。
  2. 显卡驱动问题:应用启动时调用 GPU 渲染,有时也会触发底层的显卡驱动 Bug。建议去设备官网把显卡驱动更新到最新版试试。

如果退出安全软件后还是必现蓝屏,这个底层冲突可能就需要研发同学深入排查了。建议你把这份 dump 分析文件以及你的 Windows 系统具体版本,发邮件到 feedback@mail.trae.cn,会有专门的同学跟进处理。

你电脑上平时有常驻什么特定的安全软件吗?可以先关掉试试看有没有恢复正常~

目前没有打开,昨晚是更新了openclaw到最新版,不知道是否会有什么冲突?电脑里只有联想电脑管家,但是也已经关闭了

先别直接开 TRAE Work 啦~ 既然只有联想电脑管家,而且你提到昨晚更新了 openclaw,我们可以先从这两个方向缩小范围,确认是安全软件还是 openclaw 引起的,再找彻底的解决方案:

  1. 安全模式启动验证(彻底排除安全软件拦截)

    • 完全关机后,按住 Shift 点击「重启」→ 进入疑难解答 → 高级选项 → 启动设置 → 重启 → 按 4 选择「启用安全模式」。
    • 在安全模式下,联想电脑管家和 openclaw 都不会自动启动,试试能不能正常打开 TRAE Work。如果能,说明是它们中的某一个(或两个一起)引起的冲突。
  2. 回退/卸载 openclaw(怀疑是驱动级冲突)

    • 你昨天刚更新的 openclaw,有可能是驱动版本兼容性问题。可以去设备管理器里找对应的设备,右键属性 → 驱动程序 → 回退驱动程序;或者在「应用和功能」里找到 openclaw 相关程序卸载掉,然后再重新试试 TRAE Work。
  3. 临时禁用联想电脑管家的深层防护

    • 联想电脑管家关闭前台窗口后,后台的内核拦截(HIPS)往往还在跑。如果不放心,可以打开联想电脑管家,找到「实时防护」或「核心防护」,把内核级拦截的几个选项先临时关闭,再打开 TRAE Work 试试。

你现在能先试一下「安全模式下启动电脑,再开 TRAE Work」吗?如果安全模式下没问题,那大概率就是 openclaw 驱动和联想内核防护双重拦截的锅了~

还有个比较严重的问题:是trae work cn,执行久了就直接把整个电脑都卡住了,一动不动,只能强制重启,太伤电脑了

完全理解,直接把整个电脑卡死到必须强启,确实太伤机器了,这体验很糟糕!:sad_but_relieved_face:

结合你之前提到的蓝屏报错(KERNEL_SECURITY_CHECK_FAILURE)和现在的「彻底冻结」现象,这通常说明软件在运行过程中出现了严重的底层资源冲突(比如极端的内存泄漏耗尽了系统资源,或者驱动级死锁)。这也进一步印证了可能是昨晚的更新在你的系统环境下触发了严重的兼容性 Bug。

因为这个现象涉及到了系统底层的死锁,我在知识库里暂时没翻到针对这个具体版本的准确修复步骤,不太敢给你拍脑袋的清理或配置方案。为了保护你的电脑硬件,建议你先暂时不要强行长时间运行它

如果你试了之前建议的「安全模式」下依然会卡死或蓝屏,那这绝对是一个需要研发同学紧急介入的 Bug。还是强烈建议把那几份 dump 文件,连同这个「长时间运行后彻底死机」的现象,一起发邮件给 feedback@mail.trae.cn,让官方技术团队提取日志来定位修复~

在此期间,如果你有紧急任务,可以先试试用浏览器访问 work.trae.cn 使用网页版(网页版的任务在云端运行,不会占用和卡死你的本地电脑)。有其他情况随时跟我聊!

能不能来个真人

主要是确实没遇到这种问题,重新装试试?我笔记本2020年买的,也没出现你说的这些问题,你也可以看看官方昨天发布的一个知识库,里面我看有提到openclaw,你可以去看看。

昨天的更新,自动下载之后,就被我的360杀毒给杀掉了,逼得我关闭杀毒软件,才成功安装上

杀毒软件是会杀..尽量别用,都是流氓软件

还有一种可能性,我昨天操作的项目在C盘,我挪走了,在观察观察

有一些更新功能需要系统权限,写入注册表,被拦截了吧

这个怎么观察?晚上吃完饭,打开trae,又是连续三次蓝屏。。。心累啊,其他都没打开了,openclaw自启动也关了

一打开就要写文件,我压根还没点任何一个东西就蓝屏,这也有点离谱了吧 :rofl:

这个信息复制下

我目前先用workbuddy替代着,它从来没蓝屏过呢,虽然不如trae好用

TRAE Work CN
版本: 0.1.36
提交: ce5758dc0e2ac57402cf51668d6aa665ef545b7f
日期: 2026-07-14T18:13:54.414Z
Electron: 39.2.7-release.1.43.1 (aha)
Node.js: 22.21.1
V8: 14.2.231.27-electron.0
OS: Windows_NT x64 10.0.26200
构建版本: 2.3.55112
设备ID: 95157c09553dffc756034ec1599479809fdd7893fde87c1b37fe67e98af4ea98
Web SDK Version: 1.6.0
Device Id: 142314608539867

收到,我们先看下

蓝屏可能是驱动冲突,试试更新显卡驱动或者回退到之前的版本看看是否稳定

你好,看得如何?有什么进展吗