BSOD while playing games Locale ID 2057.

Joweey · 25 May 2012

Hi can anyone help me?

During gameplay (any game) I often have the screen go blank (or sometimes striped grey lines) for a few seconds then the computer restarts and when I boot back into windows I get the unexpected shut-down error BSOD (even though I don't actually get a blue screen) Locale ID 2057.

I have tried everything on these forums including a memtest (got 10 passes and no errors) checking for malware and updating graphics drivers etc and nothing seems to sort it. I have a feeling my GFX card needs replacing but I don't want to buy a new one and find out that wasn't what was causing it.

I am running Windows 7 pro 64 bit (full retail) and my computer specs are:

AMD Phenom II X4 965 Processor 3.40ghz
4.00 GB ram
ATI Radeon HD 5670
500gb Samsung HD502HJ ATA

I have attached all the relevant information to help with the error and just before I zipped it all up I completed a Driver verifier process which is the latest error dump file in the zip folder (filename: 052612-45833-01.dmp)

Any help would be much appreciated.

usasma · 26 May 2012

Try the free video tests that I've listed at this link: Additional Hardware Diagnostics
You may also want to try the Prime95 test.

The memory dumps point to hardware. The first one mentions your video drivers, while your last one mentions USB. The last one is a Driver Verifier memory dump, but due to the hardware errors it may not be revealing the true cause.

In addition to the hardware tests above, please run the free tests at this link: Initial Hardware Diagnostics

AsIO.sys dates from 2007. It's likely to be associated with your Asus PCProbe utility (although it can be a part of other Asus utilites). I'm unable to find it in your MSINFO32 report, but it does show up in your 26 May memory dump. Please either update it or remove it from your system.

These 3 drivers belong to your Saitek SD6 device:
SaiBus.sys Fri Jan 18 13:28:24 2008 (4790EFC8)
SaiMini.sys Fri Jan 18 13:28:16 2008 (4790EFC0)
SaiK0728.sys Fri Jan 18 13:28:04 2008 (4790EFB4)
They date from 2008 and need to be updated or removed from your system. Worst case, remove them from the system while we're troubleshooting - then reinstall them once the system is stable again.

Your Razer Lachesis driver dates from 2009 (Lachesis.sys Fri Oct 16 09:09:12 2009 (4AD87078)) These devices are known to cause BSOD's with outdated drivers. Please visit the Razer download site and get the latest, Win7 compatible drivers for it.

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 and install a fresh copy of the ATI drivers from http://www.ati.com (in the upper right corner of the page)
- Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center (if present)
Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC). This is a separate issue and isn't required for the AMD OverDrive removal.

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.

Note below that there are numerous drivers dated from 2009. I'd suggest updating them as you have the time. The links to more info about those drivers are listed below that table in this post.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
MpFilter.sys    Fri Mar 09 06:05:26 2012 (4F59E3F6)
AtiPcie.sys     Tue May 05 11:00:22 2009 (4A005486)
athrx.sys       Mon Oct 05 12:33:57 2009 (4ACA1FF5)
AtihdW76.sys    Thu Feb 23 07:30:12 2012 (4F463154)
AsIO.sys        Mon Dec 17 04:11:49 2007 (47663D55)
atikmpag.sys    Thu Apr 05 21:10:44 2012 (4F7E4294)
amdiox64.sys    Thu Feb 18 10:17:53 2010 (4B7D5A21)
Rt64win7.sys    Fri Jun 10 02:33:15 2011 (4DF1BAAB)
ASACPI.sys      Wed May 13 21:25:17 2009 (4A0B72FD)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
appdrv01.sys    Wed Aug 25 08:03:46 2010 (4C7506A2)
atikmdag.sys    Thu Apr 05 21:48:25 2012 (4F7E4B69)
SaiBus.sys      Fri Jan 18 13:28:24 2008 (4790EFC8)
viahduaa.sys    Thu Jul 09 23:07:01 2009 (4A56B055)
SaiMini.sys     Fri Jan 18 13:28:16 2008 (4790EFC0)
MpFilter.sys    Wed Apr 06 16:07:29 2011 (4D9CC801)
AtihdW76.sys    Tue Dec 06 04:14:25 2011 (4EDDDCF1)
atikmpag.sys    Tue Feb 14 21:13:12 2012 (4F3B14B8)
atikmdag.sys    Tue Feb 14 21:51:52 2012 (4F3B1DC8)
SaiK0728.sys    Fri Jan 18 13:28:04 2008 (4790EFB4)
Lachesis.sys    Fri Oct 16 09:09:12 2009 (4AD87078)
MpNWMon.sys     Wed Apr 06 16:07:23 2011 (4D9CC7FB)
AODDriver2.sys  Mon Dec 19 02:30:03 2011 (4EEEE7FB)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-45833-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 25 19:40:01.535 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:18.064
Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )
BUGCHECK_STR:  0xc9_23b
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc9_23b_VRF_HIDCLASS!HidpMajorHandler+0
Bugcheck code 000000C9
Arguments 00000000`0000023b fffff880`073d4710 fffffa80`068eecf0 00000000`00000000
BiosVersion = 0904   
BiosReleaseDate = 12/22/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051612-28298-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 16 06:32:05.139 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:11.668
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04f148f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\051312-19219-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 13 07:02:33.892 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:09.422
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04f06038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\050712-17768-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon May  7 10:24:43.644 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:08.174
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04fe54f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042612-20451-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Thu Apr 26 14:44:52.676 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:08.815
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04f128f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042312-18891-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon Apr 23 05:16:06.126 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:09.656
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04ec68f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042212-18096-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sun Apr 22 05:51:34.534 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:09.673
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04ff28f8 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\042112-18610-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Sat Apr 21 14:05:59.111 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:09.640
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04f8f038 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\041612-19078-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon Apr 16 12:03:05.014 2012 (UTC - 4:00)
System Uptime: 0 days 0:12:43.441
*** 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+79e0 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`04a5b4e0 fffff880`043009e0 00000000`00000000 00000000`0000000d
BiosVersion = 0904   
BiosReleaseDate = 12/22/2009
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Joweey · 27 May 2012

Hi,

Thanks for your quick reply, I'm currently working through all your suggestions and I will report back with my findings.

Btw the only Asus product I actually own is a tablet, could that be what the Asus driver relates to?

usasma · 27 May 2012

Yes, it can relate to another utility on the Asus tablet. It's tough to figure out which since Asus bundles this stuff in a number of their utilities. Good luck!

Joweey · 28 May 2012

Hi,

I have run all the tests you suggested and nothing out of the ordinary came back and they all passed with no problems at all.

I have also updated the Saitek keyboard the Lachesis mouse (firmware and drivers) using the links you gave me. They seemed successful but when I checked them in the device manager the driver dates were still very old?! Am I updating them wrong?

The asus driver I was unable to find (again I may just not know where to look to find it) and the AMD overdrive I was also unable to find but I updated this to the newest version anyway.

I haven't tested the system yet to see if I am still getting the problem but I will and report back.

Again thanks for your help with this.

usasma · 29 May 2012

Let's see what happens. If it gives more BSOD's, please zip them up and upload them with your next post. FYI - they are located in C:\Windows\Minidump

Joweey · 31 May 2012

Right I thought I was in the clear but today I got a signal that it isn't fixed.

While playing a game the screen went blank with grey horizontal lines on it, then it flickered between the game and the grey lines before settling back on the game but the windows toolbar went grey (as if in compatibility mode) and I got an error message saying the display driver stopped working and recovered.

That was a few seconds ago and I'm expected a BSOD to follow anytime now which I will attach when it happens (I know its going to because this is what it's done a few times before).

Edit: Just happened again only this time the lines were brown and now I am getting lots of graphical issues popping up in the right corner of my screen

usasma · 31 May 2012

The error about the display driver is actually a kind of BSOD (it's a STOP 0x117 error).

If you've uninstalled the ATI drivers and installed fresh one's (when removing the AMD OverDrive) - then we have to wonder if there's a physical problem with your video card. Have a look at it to see if the fan is running, and that it's not clogged with dirt/dust/furballs/cats/or small children :0)

Use a temperature monitor to check the temp of the video card. I suggest this free one: CPUID - System & hardware benchmark, monitoring, reporting

Try the free video tests at this link: Additional Hardware Diagnostics

Joweey · 01 Jun 2012

LOL I can't see any small children in the fan but there is a bit of dust (I can't get inside the fan much due to the damn casing), the fan is spinning so I can only assume its not that?

I was unable to locate the AMD Overdrive so I wasn't able to remove it, is it possible for you to provide me with a bit of help on how to do it?

As soon as I can I will check the temperature of the graphics card and undertake the other test you suggested and report back.

Joweey · 01 Jun 2012

Right I've just had the worst one yet, I was playing football manager then the screen went black with lines, then came back on and the right hand screen had really bad graphical glitches and the left not so bad. (picture 1)

Within a few seconds of this the screen went black again and reappeared with both screens showing massive graphical issues and the computer frozen. (picture 2 shows both and 3 and 4 each seperatly)

I checked the fan on the graphics card and that was spinning fine but the computer couldn't be used at all! more annoyingly it didn't crash completely so I had to power it down via the switch and got no dump data from it.

I have attached some images to show you what the screen looked like.