Question Computer Blue Screens when playing CS:GO only

Feb 1, 2019
1
0
10
0
Hi, I have recently built a computer about a month ago, and it's been running great except when I play CS:GO. Whenever I play this game, my computer ends up bluescreening and giving me a whea_uncorrectable_error code. It just feels odd because Whenever I do other tasks, or play other games my computer runs fine. But whenever I decide to play CS, it bluescreens and it's been really frustrating. Here's the minidump file I found through windows.

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1401

BIOS_DATE: 05/21/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: TUF X299 MARK 2

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffe582e2f54028

BUGCHECK_P3: b2000000

BUGCHECK_P4: 70005

BUGCHECK_STR: 0x124_GenuineIntel

CPU_COUNT: 18

CPU_MHZ: b58

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 55

CPU_STEPPING: 4

CPU_MICROCODE: 6,55,4,0 (F,M,S,R) SIG: 2000049'00000000 (cache) 2000049'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: csgo.exe

CURRENT_IRQL: f

ANALYSIS_SESSION_HOST: BEASTEST

ANALYSIS_SESSION_TIME: 02-15-2019 23:00:05.0979

ANALYSIS_VERSION: 10.0.18317.1001 amd64fre

STACK_TEXT:
ffff8701781c4f88 fffff80313c53667 : 0000000000000124 0000000000000000 ffffe582e2f54028 00000000b2000000 : nt!KeBugCheckEx
ffff8701781c4f90 fffff80d522a146b : ffffe582e2f54028 ffffe582e14d2eb0 ffffe582e14d2eb0 ffffe582e14d2eb0 : hal!HalBugCheckSystem+0xd7
ffff8701781c4fd0 fffff80313fc77de : ffffe582e2f54028 0000000000000000 ffffe582e14d2eb0 ffffe582e14d2eb0 : PSHED!PshedBugCheckSystem+0xb
ffff8701781c5000 fffff80313c54f59 : 0000000000000728 0000000000000016 0000000000000000 0000000000000000 : nt!WheaReportHwError+0x25e
ffff8701781c5060 fffff80313c552de : 0000000000000010 ffffe582e14d2f00 ffff8701781c5208 0000000000000016 : hal!HalpMcaReportError+0x5d
ffff8701781c51b0 fffff80313c551ba : ffffe582e14dff20 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandlerCore+0xf2
ffff8701781c5200 fffff80313c55424 : 0000000000000018 0000000000000001 0000000000000000 0000000000000000 : hal!HalpMceHandler+0xda
ffff8701781c5240 fffff80313c5469c : 0000000000000000 ffff8701781c54d0 0000000000000000 0000000000000000 : hal!HalpMceHandlerWithRendezvous+0xd4
ffff8701781c5270 fffff80313c556c7 : ffffe582e14dff20 0000000000000000 0000000000000000 0000000000000000 : hal!HalpHandleMachineCheck+0x5c
ffff8701781c52a0 fffff80313f353ab : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : hal!HalHandleMcheck+0x37
ffff8701781c52d0 fffff80313e6ae7a : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiHandleMcheck+0xb
ffff8701781c5300 fffff80313e6ab60 : 0000000000000000 0000000000000000 00000000a0a32120 0000000000000000 : nt!KxMcheckAbort+0x7a
ffff8701781c5440 000000005c15aeea : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiMcheckAbort+0x260
0000000034cd8e5c 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x5c15aeea


THREAD_SHA1_HASH_MOD_FUNC: 4de11a045a075685c6206f99f334fdcf81e00201

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 0b8032aa666286f6596270ae3164aba9f3d108a7

THREAD_SHA1_HASH_MOD: e68de900930b6f9798c6a02efd69edc806b33cb0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_UNKNOWN

BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_MAE_UNKNOWN

PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_MAE_UNKNOWN

TARGET_TIME: 2019-02-16T03:49:10.000Z

OSBUILD: 17763

OSSERVICEPACK: 316

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: 134b

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_mae_unknown

FAILURE_ID_HASH: {d1b54118-491d-1f97-b145-f80457d2955b}

Followup: MachineOwner

I've been looking through this for awhile now, and I just can't seem to find an answer. Any help would be greatly appreciated. And if you need anymore information please let me know!

Thanks!
 

ASK THE COMMUNITY

TRENDING THREADS