[SOLVED]Random BSODs while playing MapleStory D:

This is an archive of the mabination.com forums which were active from 2010 to 2018. You can not register, post or otherwise interact with the site other than browsing the content for historical purposes. The content is provided as-is, from the moment of the last backup taken of the database in 2019. Image and video embeds are disabled on purpose and represented textually since most of those links are dead.

To view other archive projects go to https://archives.mabination.com

Sapphireoath wrote on 2012-07-12 01:28

By random, I mean I can never predict when its going to happen. It is no specific area, no specific action I'm doing in-game. No damn clue what is causing it.
Is there a crash log (for the BlueScreen) that would help?
I don't really have much more information I can give :( Also, it has only been happening with Maple, nothing else.
Piero wrote on 2012-07-12 01:40

BlueScreenView

It's the program I used when my computer kept crashing a few weeks ago. If you run it, next time your computer crashes, turn it back on and open it up and there should be a new entry for the most reason crash ;o. It tells you where it's coming from.
Yoorah wrote on 2012-07-12 01:41

I'm gonna guess its HackShield is causing a conflict with some driver on your system.

You can analyze the crash minidump created by the BSOD yourself for a possible cause. Instructions here, or just upload the latest minidump and let someone look at it.

I suspect you installed something recently, and HS doesn't like it.

You should also run a diagnostic test on your RAM, since buggy RAM modules will lead to system crashes. Windows Vista and 7 contain a built in diagnostic that you can run, although the industry standard testing tool would be Memtest86+.
Sapphireoath wrote on 2012-07-12 02:35

Quote from Yoorah;906810:
I'm gonna guess its HackShield is causing a conflict with some driver on your system.

You can analyze the crash minidump created by the BSOD yourself for a possible cause. Instructions here, or just upload the latest minidump and let someone look at it.

I suspect you installed something recently, and HS doesn't like it.

You should also run a diagnostic test on your RAM, since buggy RAM modules will lead to system crashes. Windows Vista and 7 contain a built in diagnostic that you can run, although the industry standard testing tool would be Memtest86+.

Couldn't be HS, wouldn't it cause problems if I'm on Mabi too?

My most recent Minidump is on the 8th, which is odd seeing as Maple crashed again a few hours ago. It was probably related though, I think that was another day when it crashed a few times.

Also, about the RAM. Would a buggy module cause a crash if its only happening with 1 program? I'll leave this as a last resort type thing.

My most recent crash log: http://www.mediafire.com/?ybtldh8doie46ey

Edit: Analyzed the minidump, I guess this is the important info?
[SPOILER="Spoiler"][CODE]Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

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

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03005000 PsLoadedModuleList = 0xfffff800`03249670
Debug session time: Sun Jul 8 13:34:34.894 2012 (UTC + 10:00)
System Uptime: 0 days 0:00:18.846
Loading Kernel Symbols
.......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800aed18f8, 0, 0}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800aed18f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`033bd6f0 fffff800`032c6ca9 : fffffa80`0aed18d0 fffffa80`09d80170 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033bdc10 fffff800`031a7547 : fffffa80`0aed18d0 fffff800`032212d8 fffffa80`09d80170 00000000`00000206 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033bdc40 fffff800`0310e945 : fffff800`03282ae0 00000000`00000001 00000000`00000000 fffffa80`09d80170 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033bdc80 fffff800`0308d841 : fffff880`01244f00 fffff800`0310e920 fffff800`03221200 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033bdcb0 fffff800`0331ae6a : 00000000`00000000 fffffa80`09d80170 00000000`00000080 fffffa80`09d63740 : nt!ExpWorkerThread+0x111
fffff880`033bdd40 fffff800`03074ec6 : fffff880`03164180 fffffa80`09d80170 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033bdd80 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bd6a0 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

Followup: MachineOwner
---------[/CODE][/SPOILER]

From what I understood from that, hardware error, GenuineIntel referring to my CPU (i7 950@stock settings) and a "WHEA_UNCORRECTABLE_ERROR (124)" which I assume is the error code.

Honestly not sure if this is the same issue, but I have a feeling it could be.

Edit: Also did a quick Google Search of WHEA_UNCORRECTABLE_ERROR (124), and its apparently due to a low VCore on my CPU? Common cause of BSOD when overclocking according to 1 thread I read (http://forums.guru3d.com/showthread.php?t=360152)...which couldn't apply to me, when I have never touched any settings on my CPU D:
Yoorah wrote on 2012-07-12 02:59

They could be using differnt HS versions of different security settings, so it's hard to say.

The minidump doesn't point at any specific driver, though...

[CODE]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800aed18f8, 0, 0}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800aed18f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`033bd6f0 fffff800`032c6ca9 : fffffa80`0aed18d0 fffffa80`09d80170 00000000`00000001 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`033bdc10 fffff800`031a7547 : fffffa80`0aed18d0 fffff800`032212d8 fffffa80`09d80170 00000000`00000206 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`033bdc40 fffff800`0310e945 : fffff800`03282ae0 00000000`00000001 00000000`00000000 fffffa80`09d80170 : nt!WheapProcessWorkQueueItem+0x57
fffff880`033bdc80 fffff800`0308d841 : fffff880`01244f00 fffff800`0310e920 fffff800`03221200 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`033bdcb0 fffff800`0331ae6a : 00000000`00000000 fffffa80`09d80170 00000000`00000080 fffffa80`09d63740 : nt!ExpWorkerThread+0x111
fffff880`033bdd40 fffff800`03074ec6 : fffff880`03164180 fffffa80`09d80170 fffff880`0316efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033bdd80 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bd6a0 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME: GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE_PRV

Followup: MachineOwner[/CODE]

Pretty weird, it's suggesting that.. the CPU itself crashed? I'm really not sure, lol. I suggest you stress test the hardware to make sure it's 100% stable and not buggy. prime95 is a good tool for this. You should probably run the Blend type Torture Test. Just be sure you have some program (like HWMonitor) to monitor CPU temps, as p95 will make the CPU heat up quite a lot if you don't have a powerful heatsink. Maybe open the case side panel and point a fan into it while you test. :P The test should be run for a few hours, to see if the CPU/RAM will crash or produce bad calculations.
Sapphireoath wrote on 2012-07-12 04:28

Quote from Yoorah;906897:
They could be using differnt HS versions of different security settings, so it's hard to say.

The minidump doesn't point at any specific driver, though...

Pretty weird, it's suggesting that.. the CPU itself crashed? I'm really not sure, lol. I suggest you stress test the hardware to make sure it's 100% stable and not buggy. prime95 is a good tool for this. You should probably run the Blend type Torture Test. Just be sure you have some program (like HWMonitor) to monitor CPU temps, as p95 will make the CPU heat up quite a lot if you don't have a powerful heatsink. Maybe open the case side panel and point a fan into it while you test. :P The test should be run for a few hours, to see if the CPU/RAM will crash or produce bad calculations.

Analyzed a different crash log, from LiveKernelReports this time. I actually found logs that correspond to when the BSOD's actually occur. I'm not actually getting the BlueScreen report from Windows upon restarting though, any reason why?
[SPOILER="Spoiler"][CODE]
Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WD-20120712-1410.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`03067000 PsLoadedModuleList = 0xfffff800`032ab670
Debug session time: Thu Jul 12 14:10:18.273 2012 (UTC + 10:00)
System Uptime: 0 days 2:39:04.226
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa80122bc390, fffff88004043768, 0, 0}

*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+8768 )

Followup: MachineOwner
---------

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

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa80122bc390, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004043768, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

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

FAULTING_IP:
atikmpag+8768
fffff880`04043768 ?? ???

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

BUGCHECK_STR: 0x117

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`069da400 fffff880`040f05f7 : fffffa80`122bc390 00000000`00000024 fffffa80`0eff18f0 fffff880`040f0298 : watchdog!WdDbgReportRecreate+0xa3
fffff880`069da920 fffff880`040f0a2e : 00000000`00001000 fffff8a0`2b8fc380 00000000`00000008 00000000`00004000 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`069da970 fffff880`040f1ce2 : fffffa80`122bc390 fffffa80`122bc390 fffffa80`0eff18f0 fffffa80`0c7c7010 : dxgkrnl!TdrCollectDbgInfoStage1+0x2e6
fffff880`069daa10 fffff880`05571f07 : fffffa80`122bc390 00000000`00000000 fffffa80`0eff18f0 fffffa80`0c7c7010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`069daa40 fffff880`0559bb75 : 00000000`ffffffff 00000000`000952d0 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`069dab20 fffff880`0559a2bb : 00000000`00000102 00000000`00000000 00000000`000952d0 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`069dab50 fffff880`0556d2c6 : ffffffff`ff676980 fffffa80`0c7c7010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`069dabf0 fffff880`05599e7a : 00000000`00000000 fffffa80`0eff18f0 00000000`00000080 fffffa80`0c7c7010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`069dad00 fffff800`0337ce6a : 00000000`0b97d031 fffffa80`0c130060 fffffa80`09d4a5f0 fffffa80`0c130060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`069dad40 fffff800`030d6ec6 : fffff880`03164180 fffffa80`0c130060 fffff880`0316efc0 2c307830`2c307830 : nt!PspSystemThreadStartup+0x5a
fffff880`069dad80 00000000`00000000 : fffff880`069db000 fffff880`069d5000 fffff880`09161d70 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atikmpag+8768
fffff880`04043768 ?? ???

SYMBOL_NAME: atikmpag+8768

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmpag

IMAGE_NAME: atikmpag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f7e4294

FAILURE_BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

BUCKET_ID: X64_0x117_IMAGE_atikmpag.sys

Followup: MachineOwner
---------

2: kd> lmvm atikmpag
start end module name
fffff880`0403b000 fffff880`04095000 atikmpag T (no symbols)
Loaded symbol image file: atikmpag.sys
Image path: atikmpag.sys
Image name: atikmpag.sys
Timestamp: Fri Apr 06 11:10:44 2012 (4F7E4294)
CheckSum: 0005A52D
ImageSize: 0005A000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Mini Kernel Dump does not contain unloaded driver list
[/CODE][/SPOILER]
This time its related to a graphics card thing, driver conflict with MapleStory? This actually makes for more sense than a CPU issue.

[CODE]VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.[/CODE]

Card: HD6970
Catalyst Version: 12.3

I'll update to 12.4, see if it solves the issue.

Edit: Make that 12.6, didn't realise I missed a few LOL

Edit2: Crash again, same log "VIDEO_TDR_TIMEOUT_DETECTED (117)" Has to be something within Maple, never happens with anything else.
Sapphireoath wrote on 2012-07-19 04:00

Fixed it a few days ago, VIDEO_TDR_TIMEOUT_DETECTED was related to "Display Driver Stopped Responding" (which I never got, it just skipped that and went straight to freezing) which after a bit of Googling turned up the TDR timeout settings, where if the graphics card doesn't respond to Windows after 2 second, Windows tells it to restart...so I found out you can increase that 2 seconds, which I did.
Voila, no more Maple crashes :D
So I guess it must be a graphics issue within Maple, could be one of the W7 Maple issues I've heard about and never experienced till now :)
Case Closed.