776      阿裏雲  技術社區[雲棲]

打遊戲的時候會經常藍屏 已用windbg分析，求大神幫助

已用win10內存檢測測試過內存條沒問題。

最新的一次藍屏分析：

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


Loading Dump File [C:\Windows\Minidump\110517-94375-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:symbolsDown*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff803`6808e000 PsLoadedModuleList = 0xfffff803`683da5c0
Debug session time: Sun Nov  5 20:50:35.125 2017 (UTC + 8:00)
System Uptime: 0 days 0:20:19.799
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
..............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffff938e5e568178, 2, 0, fffff8036817ea20}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffff938e5e568178, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8036817ea20, address which referenced memory

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


READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 ffff938e5e568178 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExpScanGeneralLookasideList+40
fffff803`6817ea20 418b48d8        mov     ecx,dword ptr [r8-28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from fffff803682058a9 to fffff803681fa580

STACK_TEXT:  
ffffce81`7122b818 fffff803`682058a9 : 00000000`0000000a ffff938e`5e568178 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffce81`7122b820 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69


STACK_COMMAND:  .bugcheck ; kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
10 errors : !nt (fffff8036817e14d-fffff8036817efe8)
fffff8036817e140  00  00  c0  4c  89  78  c8  48  bb  00  00  00  00 *00 *8c  ff ...L.x.H........
fffff8036817e150  ff  49  ba  00  00  00  00 *00 *e0  ff  ff  0f  1f  44  00  00 .I...........D..
...
fffff8036817e330  ba  00  00  00  00  00  00  00  80  48  bb  00  00  00  00 *00 .........H......
...
fffff8036817e3a0  ba  00  00  00  00 *00 *e0  ff  ff  41  8b  d3  49  b9  ff  ff .........A..I...
...
fffff8036817efe0  c1  48  b9  00  00  00  00 *00 *e0  ff  ff  48  8b  34  08  49 .H.........H.4.I

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------

1: kd> lmvm memory_corruption
start             end                 module name

最後更新：2017-11-06 11:04:12

  上一篇： win10 照片應用無法打開

  下一篇： 1703專業版係統無法更新到1709版本！