New
#1
Constant BSOD Whilst gaming
Hi there,
Hopefully you can help me, I'm currently getting alot of BSODs whilst gaming or watching Youtube. I've updated all the drivers that i know off and have memtested the ram and it seems OK. I've recently upgraded the PSU aswell to a EVGA 650W G2 as i thought my old PSU may have been the problem. I'm at my ends wits with it and hopefully you guys can find out why.
Thanks alot.
Code:Microsoft (R) Windows Debugger Version 10.0.15063.468 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Joe\Desktop\081317-4984-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 15063 MP (4 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSMachine Name:Kernel base = 0xfffff803`52491000 PsLoadedModuleList = 0xfffff803`527dd5c0Debug session time: Sun Aug 13 18:24:17.610 2017 (UTC + 1:00)System Uptime: 0 days 0:09:08.264Loading 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 SymbolsLoading unloaded module list........******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 9C, {0, fffff8035464cba0, 0, 0}Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+7b )Followup: MachineOwner---------0: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************MACHINE_CHECK_EXCEPTION (9c)A fatal Machine Check Exception has occurred.KeBugCheckEx parameters; x86 Processors If the processor has ONLY MCE feature available (For example Intel Pentium), the parameters are: 1 - Low 32 bits of P5_MC_TYPE MSR 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of P5_MC_ADDR MSR 4 - Low 32 bits of P5_MC_ADDR MSR If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are: 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error IA64 Processors 1 - Bugcheck Type 1 - MCA_ASSERT 2 - MCA_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing MCA. 3 - MCA_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 4 - MCA_FATAL FW reported a fatal MCA. 5 - MCA_NONFATAL SAL reported a recoverable MCA and we don't support currently support recovery or SAL generated an MCA and then couldn't produce an error record. 0xB - INIT_ASSERT 0xC - INIT_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 0xD - INIT_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 0xE - INIT_FATAL Not used. 2 - Address of log 3 - Size of log 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO AMD64 Processors 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the errorArguments:Arg1: 0000000000000000Arg2: fffff8035464cba0Arg3: 0000000000000000Arg4: 0000000000000000Debugging Details:------------------DUMP_CLASS: 1DUMP_QUALIFIER: 400BUILD_VERSION_STRING: 10.0.15063.540 (WinBuild.160101.0800)SYSTEM_MANUFACTURER: ASUSSYSTEM_PRODUCT_NAME: All SeriesSYSTEM_SKU: AllSYSTEM_VERSION: System VersionBIOS_VENDOR: American Megatrends Inc.BIOS_VERSION: 3003BIOS_DATE: 10/28/2015BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.BASEBOARD_PRODUCT: MAXIMUS VII RANGERBASEBOARD_VERSION: Rev 1.xxDUMP_TYPE: 2DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage DumpBUGCHECK_P1: 0BUGCHECK_P2: fffff8035464cba0BUGCHECK_P3: 0BUGCHECK_P4: 0BUGCHECK_STR: 0x9C_GenuineIntelCPU_COUNT: 4CPU_MHZ: dacCPU_VENDOR: GenuineIntelCPU_FAMILY: 6CPU_MODEL: 3cCPU_STEPPING: 3CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTPROCESS_NAME: Cities.exeCURRENT_IRQL: fANALYSIS_SESSION_HOST: DESKTOP-N7GKGQIANALYSIS_SESSION_TIME: 08-13-2017 18:40:49.0824ANALYSIS_VERSION: 10.0.15063.468 x86freBAD_STACK_POINTER: fffff8035464cb68LAST_CONTROL_TRANSFER: from fffff8035244eb9d to fffff803525fd560STACK_TEXT: fffff803`5464cb68 fffff803`5244eb9d : 00000000`0000009c 00000000`00000000 fffff803`5464cba0 00000000`00000000 : nt!KeBugCheckExfffff803`5464cb70 fffff803`5244efe7 : 00000000`00000004 fffff803`5464ce70 00000000`00000000 00000000`00000004 : hal!HalpMcaReportError+0xf5fffff803`5464ccc0 fffff803`5244f120 : ffff9486`3a6c7690 fffff803`5464cef0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x12bfffff803`5464ccf0 fffff803`526076bb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40fffff803`5464cd20 fffff803`5260742c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7bfffff803`5464ce60 00007ff7`0a5445b1 : 00000001`85352cd0 00000000`3100f840 00000000`18592660 00000000`c0b96040 : nt!KiMcheckAbort+0x1ac00000000`00b1d790 00000001`85352cd0 : 00000000`3100f840 00000000`18592660 00000000`c0b96040 00007ff7`00000000 : 0x00007ff7`0a5445b100000000`00b1d798 00000000`3100f840 : 00000000`18592660 00000000`c0b96040 00007ff7`00000000 00007ff7`0b161420 : 0x00000001`85352cd000000000`00b1d7a0 00000000`18592660 : 00000000`c0b96040 00007ff7`00000000 00007ff7`0b161420 00000001`000001d0 : 0x3100f84000000000`00b1d7a8 00000000`c0b96040 : 00007ff7`00000000 00007ff7`0b161420 00000001`000001d0 00007ff7`0a17cc91 : 0x1859266000000000`00b1d7b0 00007ff7`00000000 : 00007ff7`0b161420 00000001`000001d0 00007ff7`0a17cc91 00000000`04ddfe90 : 0xc0b9604000000000`00b1d7b8 00007ff7`0b161420 : 00000001`000001d0 00007ff7`0a17cc91 00000000`04ddfe90 00007ff7`0a385507 : 0x00007ff7`0000000000000000`00b1d7c0 00000001`000001d0 : 00007ff7`0a17cc91 00000000`04ddfe90 00007ff7`0a385507 00000000`00006ec0 : 0x00007ff7`0b16142000000000`00b1d7c8 00007ff7`0a17cc91 : 00000000`04ddfe90 00007ff7`0a385507 00000000`00006ec0 00000000`9966a100 : 0x00000001`000001d000000000`00b1d7d0 00000000`04ddfe90 : 00007ff7`0a385507 00000000`00006ec0 00000000`9966a100 00000000`00000064 : 0x00007ff7`0a17cc9100000000`00b1d7d8 00007ff7`0a385507 : 00000000`00006ec0 00000000`9966a100 00000000`00000064 00000000`08085c01 : 0x4ddfe9000000000`00b1d7e0 00000000`00006ec0 : 00000000`9966a100 00000000`00000064 00000000`08085c01 00000000`00000000 : 0x00007ff7`0a38550700000000`00b1d7e8 00000000`9966a100 : 00000000`00000064 00000000`08085c01 00000000`00000000 00007ff7`0a17d00a : 0x6ec000000000`00b1d7f0 00000000`00000064 : 00000000`08085c01 00000000`00000000 00007ff7`0a17d00a 00000001`85352cd0 : 0x9966a10000000000`00b1d7f8 00000000`08085c01 : 00000000`00000000 00007ff7`0a17d00a 00000001`85352cd0 00000000`3100f840 : 0x6400000000`00b1d800 00000000`00000000 : 00007ff7`0a17d00a 00000001`85352cd0 00000000`3100f840 00000000`18592660 : 0x8085c01STACK_COMMAND: kbTHREAD_SHA1_HASH_MOD_FUNC: 949731cb0325a4c8281ea8e4ed83d7acfe4453f9THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7f42f7a975d49bf53079f7dd79a26d8cc8ef117dTHREAD_SHA1_HASH_MOD: b4ea994a2f688dc4d96ebf4ff0b4e470ebff6563FOLLOWUP_IP: nt!KxMcheckAbort+7bfffff803`526076bb 488d8c2400010000 lea rcx,[rsp+100h]FAULT_INSTR_CODE: 248c8d48SYMBOL_STACK_INDEX: 4SYMBOL_NAME: nt!KxMcheckAbort+7bFOLLOWUP_NAME: MachineOwnerMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP: 597fd80dIMAGE_VERSION: 10.0.15063.540BUCKET_ID_FUNC_OFFSET: 7bFAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KxMcheckAbortBUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KxMcheckAbortPRIMARY_PROBLEM_CLASS: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KxMcheckAbortTARGET_TIME: 2017-08-13T17:24:17.000ZOSBUILD: 15063OSSERVICEPACK: 540SERVICEPACK_NUMBER: 0OS_REVISION: 0SUITE_MASK: 272PRODUCT_TYPE: 1OSPLATFORM_TYPE: x64OSNAME: Windows 10OSEDITION: Windows 10 WinNt TerminalServer SingleUserTSOS_LOCALE: USER_LCID: 0OSBUILD_TIMESTAMP: 2017-08-01 02:23:25BUILDDATESTAMP_STR: 160101.0800BUILDLAB_STR: WinBuildBUILDOSVER_STR: 10.0.15063.540ANALYSIS_SESSION_ELAPSED_TIME: 55fANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:0x9c_genuineintel_stackptr_error_nt!kxmcheckabortFAILURE_ID_HASH: {f8ecfd5d-d4d1-a55d-22c5-ec2f281b8b0b}Followup: MachineOwner---------
Last edited by Brink; 13 Aug 2017 at 12:55. Reason: code box