Windows 10: BSOD when using Teamviewer to Online game (machine check exception)

Hi all,

I just buy a new computer, and found that there are BSOD when i am using teamviewer to my game, only this will cause BSOD, actually there are no Blue screen, just the screen hang there and i must reboot the computer manually. Below is my minidump file, someone please help, thanks a lot.

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR – Windows System Software — Unique Expertise, Guaranteed Results)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 8 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.0.amd64fre.rs1_release.160715-1616
Machine Name:
Kernel base = 0xfffff802`d2880000 PsLoadedModuleList = 0xfffff802`d2b85060
Debug session time: Fri Mar 3 11:24:18.643 2017 (UTC - 5:00)
System Uptime: 0 days 0:15:48.364
*******************************************************************************
* *
* 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 error
Arguments:
Arg1: 0000000000000000
Arg2: ffff9380e1d38860
Arg3: 0000000000000000
Arg4: 0000000000000000

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

BUGCHECK_STR: 0x9C_GenuineIntel

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: BlackDesert64.

CURRENT_IRQL: f

LAST_CONTROL_TRANSFER: from fffff802d28417a1 to fffff802d29c9f90

STACK_TEXT:
ffff9380`e1d38828 fffff802`d28417a1 : 00000000`0000009c 00000000`00000000 ffff9380`e1d38860 00000000`00000000 : nt!KeBugCheckEx
ffff9380`e1d38830 fffff802`d2841bdb : 00000000`00000008 ffff9380`e1d38b30 00000000`00000000 00000000`00000008 : hal!HalpMcaReportError+0xf5
ffff9380`e1d38980 fffff802`d2841d00 : ffffd40e`442d1c50 ffff9380`e1d38bb0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x12b
ffff9380`e1d389b0 fffff802`d29d3efb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
ffff9380`e1d389e0 fffff802`d29d3c84 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
ffff9380`e1d38b20 00000001`411c1b50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x184
00000000`40b6ec60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x1`411c1b50


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KxMcheckAbort+7b
fffff802`d29d3efb 488d8c2400010000 lea rcx,[rsp+100h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!KxMcheckAbort+7b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 578998f1

FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+7b

BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+7b

Followup: MachineOwner


The attached file is my computer information using CPU-z


I have tested some cases:
1. BSOD only occur in being remote by other, i can remote to other computer.
2. when i am remote to my computer, if i do not open the game, it will not crash.
3. the game consume about 50% CPU && 50% Memory of my computer.
4. CPU temperature is okay
5. drivers are all updated ( use driver booster Pro to check)

:)

 

BSOD Machine Check Exception

Hi Melvin,

Thank you for letting us know that you are no longer facing the issue. We appreciate your effort.

If you have any Windows related queries in the future, let us know, We will be glad to help.

Thank you for contacting Microsoft Community.

 

BSOD Machine Check Exception

Hey everyone,

This BSOD has become a daily thing now and it always happens while I am playing a particular game (Skyforge). The crash is fairly random from as quick as 5 minutes to as long as couple of hours while playing the game. I noticed that 'Windowed Mode' of the
game helps delay the BSOD but it is still disappointing as this is a relatively new system and to have BSODs at the start is just :/ I run a MSI GE62 2QD Apache Pro and have not altered anything since I purchased it ~6 months ago (aside from clearing bloatwares).
It was pre-installed with Windows 8.1 and I have tried the following in sequence:

1. Updating drivers via Windows Update and via MSI Support page

2. Updating to the latest Nvidia Graphic Driver

-The following changed the BSOD from Machine Check Exception to Driver_IRQL_Not_Less_Than_Or_Equal bwcW8x64.sys which relates to a variety of .sys files including but not limited to (acpiex.sys, rdyboost.sys, bwcW8x64.sys, etc.)

3. Uninstalled the latest Nvidia Graphic Driver and allowed Windows to automatically reinstall Nvidia Graphics Driver

-Back to Machine Check Exception

4. Cleaned all my fans, reseated RAM, fans are working

5. Monitored my temps, usually in the range of 40-60 (can reach 70~80 sometimes but this only lasts couple of seconds?)

6. Stressed test with Prime95 for 6 hours, no errors

7. Reinstalled Skyforge

8. Ran Driver Verifier

-Windows BSOD constantly, driver localised to hal.dll +37745 and ntoskrnl.exe (sadly I have lost the driver file because of 9)

9. Upgrade AND clean install to Windows 10

-BSOD again Machine Check Exception within minutes of game (hal.dll +364b1)

10. Please help

BlueScreenView dump file:

032816-47828-01.dmp

MSInfo:

TEST.TXT

I hope I have not missed out anything so that the team can help me with this issue. If there's anything else you need just let me know. You will have my eternal gratitude x

 

Please use the BSOD posting instruction to provide the Dumpfile BSOD - Posting Instructions - Windows 10 Forums