积分 520 最后登录 2024-4-19 精华 0 阅读权限 40 主题 32 UID 338055 帖子 1151 PB币 1500 威望 10 贡献 0 技术 0 活跃 665
UID 338055 帖子 1151 PB币 1500 贡献 0 技术 0 活跃 665
1600X+ AB350 华qing妖板+8X2 2400杂牌金T克内存+1060显卡(显卡驱动随便一个版本安装也会蓝屏,蓝屏几次之后又稳定用)
已经买了新的硬盘,CPU默认频率自动电压,内存默认频率,显卡从来没有超频或者做任何调节,还有两年质保。主板BIOS也更新过任何一个版本一样蓝屏。
内存用MEMTEST,12开,跑过差不多4小时没有任何问题,机械硬盘没坏道,固态MLC也正常,另外新购入了NVME的盘也没有改善任何问题,依然蓝屏。
LTSB 1803 LTSC,精简原版一样蓝屏。。
这个电脑快迫死我了。。
下面是前几分钟的蓝屏报告
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff803`06ca9000 PsLoadedModuleList = 0xfffff803`070c89b0
Debug session time: Sat Dec 22 19:37:45.812 2018 (UTC + 8:00)
System Uptime: 0 days 0:00:45.643
Loading Kernel Symbols
...............................................................
................................................................
..............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 119, {2, ffffffffc000000d, fffffb85e592c960, ffffca075d10c9d0}
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiSendToExecutionQueue+15578 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: fffffb85e592c960
Arg4: ffffca075d10c9d0
Debugging Details:
------------------
KEY_VALUES_STRING: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: To Be Filled By O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P5.00
BIOS_DATE: 07/05/2018
BASEBOARD_MANUFACTURER: ASRock
BASEBOARD_PRODUCT: AB350 Gaming K4
BASEBOARD_VERSION:
DUMP_TYPE: 1
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: fffffb85e592c960
BUGCHECK_P4: ffffca075d10c9d0
CPU_COUNT: c
CPU_MHZ: eb8
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 1
CPU_STEPPING: 1
BLACKBOXBSD: 1 (!blackboxbsd)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-R72HK57
ANALYSIS_SESSION_TIME: 12-22-2018 20:06:48.0917
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff803108040db to fffff80306e5a040
STACK_TEXT:
fffffb85`e592c878 fffff803`108040db : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffb85`e592c960 : nt!KeBugCheckEx
fffffb85`e592c880 fffff803`12c6b3e8 : 00000000`00000000 ffffca07`5d109000 fffffb85`e592c9c0 ffffca07`5d109000 : watchdog!WdLogEvent5_WdCriticalError+0xdb
fffffb85`e592c8c0 fffff803`12cc594d : ffffca07`00000000 ffffca07`5d10c9d0 ffffca07`5d04a000 ffffca07`5f8ce800 : dxgmms2!VidSchiSendToExecutionQueue+0x15578
fffffb85`e592ca00 fffff803`12cd5285 : ffffca07`5f8ce800 ffffca07`5d110620 00000000`00000000 ffffca07`5d110620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffffb85`e592cb80 fffff803`12cd50fa : ffffca07`5d04a400 fffff803`12cd5030 ffffca07`5d04a000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
fffffb85`e592cbd0 fffff803`06dca6c5 : ffffca07`5d0da680 fffff803`00000001 ffffca07`5d04a000 00000065`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffb85`e592cc10 fffff803`06e6149c : ffff8b01`591b9180 ffffca07`5d0da680 fffff803`06dca670 00000028`282444c7 : nt!PspSystemThreadStartup+0x55
fffffb85`e592cc60 00000000`00000000 : fffffb85`e592d000 fffffb85`e5927000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c
THREAD_SHA1_HASH_MOD_FUNC: 3c3aefa711a40e43478598e53abd6873e0c9ed57
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: cff5d5a2ea8e231b3d58354fd6878114077ad8e0
THREAD_SHA1_HASH_MOD: 8bc3a1490ebecb3d757d5cd2041e6cd7da5819c4
FOLLOWUP_IP:
dxgmms2!VidSchiSendToExecutionQueue+15578
fffff803`12c6b3e8 0f1f440000 nop dword ptr [rax+rax]
FAULT_INSTR_CODE: 441f0f
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+15578
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.17763.55
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 15578
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
PRIMARY_PROBLEM_CLASS: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
TARGET_TIME: 2018-12-22T11:37:45.000Z
OSBUILD: 17763
OSSERVICEPACK: 107
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: unknown_date
BUILDDATESTAMP_STR: 180914-1434
BUILDLAB_STR: rs5_release
BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
ANALYSIS_SESSION_ELAPSED_TIME: 45d
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x119_2_driver_failed_submit_command_dxgmms2!vidschisendtoexecutionqueue
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
展开阅读全文​