BSOD while playing online game Elsword

[West05]

Hello postee's of SevenForums. I've been playing this game Elsword for quite some time, and recently, been experiencing the BSOD while playing in dungeons. This doesn't occur anywhere else in-game, nor while playing any other games. When the BSOD occurs, it says something about unistalling hardware/software, disabling BIOS memory, reboots back to desktop, and then a window pops relating files to the problem. I have tried reinstalling my GPU drivers, reverted back to stock clocks on my GPU and CPU and even closing applications running in the background.

My specs are as follows

CPU - FX-6300
GPU - Radeon HD 7870 OC Edtion (Gigabyte)
SSD - Samsung 840 series 256GB
RAM - 8GB
MB - ASRock 970 Xtreme4


Here are the files that are apparently associated with the problem.

 

[West05]

I apologize. I just read the BSOD instructions concerning the dump files.

 

[koolkat77]

Welcome to the forum West05,

Reduce items at start-up:

• http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot:

• http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

The BSOD's were caused by:
MijXfilt.sys Sat May 12 10:27:12 2012 (4FADE6A0)
MotioninJoy simulate Xbox 360 controller (virtual Xinput device)
Driver Reference Table - MijXfilt.sys

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10D, {5, 0, 1202, fffffa800be9b930}

*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

Use Revo Uninstaller to uninstall stubborn software. Opt for Advance Mode while uninstalling which allows you to remove leftover registry:-

• Download Revo Uninstaller Freeware - Free and Full Download - Uninstall software, remove programs, solve uninstall problems

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Scan with Kaspersky TDSSKiller:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable!:-

AsrAppCharger.sys Tue May 10 14:28:46 2011 (4DC8F73E)
ASRock App Charger Likely BSOD cause.
Driver Reference Table - AsrAppCharger.sys

AODDriver2.sys Tue Feb 11 17:06:52 2014 (52FA044C)
AMD Overdrive; also in EasyTune6 for Gigabyte motherboard
Known BSOD issues in Win7 - Part of AMD Fuel
Location: C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys

   Information

AMD OverDrive Removal - Step 1:
AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems.

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download (but DO NOT install) a fresh copy of the ATI drivers from http://ati.amd.com (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure - Sysnative Forums

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

xusb21.sys Wed Apr 8 20:28:44 2009 (49DCB49C)
XBox USB wireless controller [br] BSOD issues in Win7 with 2009 driver (found in mid-2012)
Driver Reference Table - xusb21.sys

ALSysIO64.sys Mon Apr 20 01:41:04 2009 (49EB7E50)
Core Temp - CPU temperature monitor
Driver Reference Table - ALSysIO64.sys

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue May 20 13:17:44.553 2014 (UTC + 6:00)
System Uptime: 0 days 1:29:59.550
BugCheck 10D, {5, 0, 1202, fffffa800be9b930}
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )
BUGCHECK_STR:  0x10D_5
PROCESS_NAME:  Better DS3.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue May 20 11:47:18.898 2014 (UTC + 6:00)
System Uptime: 0 days 2:06:35.895
BugCheck 10D, {5, 0, 1202, fffffa800835ab70}
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )
BUGCHECK_STR:  0x10D_5
PROCESS_NAME:  Better DS3.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Tue May 20 02:40:30.238 2014 (UTC + 6:00)
System Uptime: 0 days 11:36:38.235
BugCheck 1000007E, {ffffffffc0000005, fffff88000f1df0f, fffff88009fd4258, fffff88009fd3ab0}
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+2033 )
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon May 19 15:03:22.673 2014 (UTC + 6:00)
System Uptime: 0 days 0:08:12.671
BugCheck 10D, {5, 0, 1202, fffffa80093ebaf0}
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )
BUGCHECK_STR:  0x10D_5
PROCESS_NAME:  Better DS3.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Debug session time: Mon May 19 11:49:28.142 2014 (UTC + 6:00)
System Uptime: 0 days 1:42:19.030
BugCheck 10D, {5, 0, 1202, fffffa800bc7d9c0}
*** WARNING: Unable to verify timestamp for MijXfilt.sys
*** ERROR: Module load completed but symbols could not be loaded for MijXfilt.sys
Probably caused by : MijXfilt.sys ( MijXfilt+363a )
BUGCHECK_STR:  0x10D_5
PROCESS_NAME:  Better DS3.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Recommended antivirus program for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials Download | Free Spyware Protection
• Malwarebytes - The Free version
• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

:warn: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Check for heating issues using Speccy or HWmonitor

Upload a screen shot: http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Keep us posted.

 

[West05]

Played for about 40 minutes to an hour until the BSOD happened. Did everything you posted up here, too. I too believe it is the controller causing the issue

 

[koolkat77]

Thanks for the update.