BSOD When I play Maple story with Game booster 3

Hi, I have been getting alot of BSOD error messages when ever I play games such as Maple Story or when I use Game Booster 3. It mostly happens after I'm on the game for about 5mins.
After the BSOD shows up I restart my computer then the BSOD shows up again, and again.
Then I'm force to System restore it. If anyone could please help me as soon as possible I would appreciate it.


My System Specs:
MS Windows 7 Home Premium: 64-bit SP1.
Manufacturer: Hewlett-Packard.
Model#: 1444 (Socket S1G4).
CPU Type: AMD K10, AMD Phenom(tm) II P650 Dual-Core Processor.
Speed:Bus Speed 199.5 MHz, Rated Bus Speed 1795.5 MHz, Stock Core Speed2600 MHz, Stock Bus Speed 200 MHz, Average Temperature 55 °C.
BIOS: Version F.29 Date 04/07/2011.
RAM Type: DDR3 DDR3, 3.00 GB (2.74 GB usable) Module name
PC3-10600
PC3-10600
Video: Device Kind Camera/scanner, Device Name USB Video Device, AMD M880G with ATI Mobility Radeon HD 4250. Speed: 5400
Power Supply Unit: power scheme Home/Office Desk Power On Count 1698 timesPower On Time 64.4 days.


On Mon 6/25/2012 9:32:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-26754-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x4A44D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004C7444D, 0xFFFFF880064A4000, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION




On Mon 6/25/2012 9:32:36 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x4A44D)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004C7444D, 0xFFFFF880064A4000, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, ATI Technologies Inc.).
Google query: atikmdag.sys ATI Technologies Inc. SYSTEM_SERVICE_EXCEPTION




On Mon 6/25/2012 4:30:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062512-32588-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F190)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Can anyone please help?

You did not properly follow the posting instructions, so no, we cannot help you at this time. Please follow the https://www.sevenforums.com/crashes-d...tructions.html.

Oh sorry, I see what you mean.

1. 64 Bit
2. Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service
Pack 1
3. OEM it came preinstalled
4. 4/7/2011 age of hard ware

Problematic Software:

Code:

Start Menu\Programs\Advanced SystemCare 5	Public:Start Menu\Programs\Advanced SystemCare 5	Public

• Many of us on the forums actually do not recommend automated optimization tools for Windows 7. Windows 7 does a much better job of handling its own optimization than its predecessors did. We especially do not recommend registry cleaning as an "optimization" step because automated registry cleaning causes more harm to the registry than it actually repairs.
  
  In the future, if you need help optimizing Windows 7, please post a thread in Performance & Maintenance - Windows 7 Forums or follow the tutorial enclosed in that forum to Optimize Windows 7.

Your most recent crash was caused by your Atheros AR9285 802.11b/g/n WiFi Adapter driver. You should download an update from your HP Support site for your model and update it.

After downloading the driver update, use the following steps to install it:

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Expand Network adapters
6. Right click the Atheros network device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device and hit OK
9. Do not restart your computer
10. Install the downloaded driver for the Atheros network device.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Expand Network adapters
7. Right click the Atheros network device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device and hit OK
10. Do not restart your computer
11. Install the downloaded driver for the Atheros network device.

BugCheck 0x124

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.


BugCheck 0x101

STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg


Also, please refrain from using CCleaner for the duration of your troubleshooting. It deletes the .dmp files and makes it difficult to find patterns.