Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD playing League of Legends, Locale ID 1033

03 Nov 2013   #1

windows 7 pro x64
 
 
BSOD playing League of Legends, Locale ID 1033

BBCode: 116
BCP1: FFFFFA8008079010
BCP2: FFFFF88003F78DB8
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

I am running a dual monitor setup with my new (1 month) ASUS HD 7970 HD DCII 3GB.
I was playing League of Legends and messing around with my water-cooling loop. (Already completed but I was cable tying some fan cables together). Then suddenly the screen turned a peach color and froze. I restarted my system and there are now green and red horizontal blocks of lines.. around 10 in a block.. arranged in a checker pattern on my screen. After the BIOS screen the BSOD came up. I restarted in safe mode and the lines are still there.



Attached Files
File Type: zip SF_03-11-2013.zip (2.02 MB, 2 views)
My System SpecsSystem Spec
.

03 Nov 2013   #2

Windows 7 Home Premium x64
 
 

Welcome to SF!

Were you handling the PC while it was running?
If you did you might have shorted something out.

The SystemInfo.txt file is missing, please follow the instructions below.
Download and save Info.bat to the desktop.

Open an elevated command prompt and then type the following command:

Code:
cd C:\Users\<Username>\Desktop
Then type:

Code:
Info.bat
The batch file will begin to run, the SystemInfo.txt file will be saved to your C:\ partition,
the MSINFO32 file will simply open, therefore click File and then Save.
Chose the save location as your Desktop, and then copy the two files into a zipped folder.

Upload the zipped folder in your next post.
Info.bat

I would first shutdown the PC and disconnect it from the Mains (wall outlet) and re-seat all of the connectors / expansion cards and see if the coloured artifacts still appear after the fact.

Good practice, open up the case and re-seat all types of connection.
  • SATA Cables (HDD/SSD/ODD).
  • SATA-Power.
  • Motherboard 24-pin.
  • Motherboard 4/8-pin (CPU).
  • Re-seat the RAM.
  • Re-seat the GPU.
Make sure that every slot / cable head is free of dust or other obstruction.
Make sure that every connection is seating properly and firmly in-place.

Most of the bug checks were a TDR (Timeout Detection & Recovery) and its not a real crash
in the sense that something wrong occurred in the Kernel.
Quote   Quote: Originally Posted by TVeblen View Post
"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in Windows 7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected.
.
.
.
.
There are numerous reports of hardware solutions to TDR's. The most common are:
  • Poor Cooling
  • Problems with the power supply
  • Overclocking Issues
  • Bad System memory or incorrect memory timings
  • Defective PC Components
Code:
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008049010
Arg2: fffff88003e08db8
Arg3: 0000000000000000
Arg4: 0000000000000002
Code:
lmvm atikmpag
start             end                 module name
fffff880`03e00000 fffff880`03e76000   atikmpag T (no symbols)           
    Loaded symbol image file: atikmpag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmpag.sys
    Image name: atikmpag.sys
    Timestamp:        Fri Sep 28 04:12:52 2012
Please update the driver.
Name File Size Revision Number Release Date Download Link
Catalyst Software Suite 197 MB 13.9 9/18/2013 Download
The more worrying thing is that the latest of the dumps is a 0x124.

Code:
BugCheck 124, {0, fffffa8007ac4028, be200000, 5110a}
Code:
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8007ac4138
Section       @ fffffa8007ac42c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : GCACHEL2_ERR_ERR (Proc 3 Bank 6)
  Status      : 0xbe2000000005110a
  Address     : 0x000000016a0bbc40
  Misc.       : 0x000000d02401c086
You were stressing the PC using Prime95.
Code:
PROCESS_NAME:  prime95.exe
This was a generic L2 CACHE error, this could be a thermal issue.
Code:
Error Type    : Cache error
Operation     : Generic
Quote:
A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. - H2SO4
The generic nature of the 0x124 (Arg1=0) stop code means we would have to take
the trail & error approach.


What is the make, model and age of you PSU?
Fill out this form and post back the result:

Reset the BIOS back to default:
Note   Note
Write down the current value of the SATA Mode!
Its either AHCI or IDE.
After resetting the CMOS go back and verify the value for SATA Mode is what it was
when the OS was installed.

Note   Note
If any component is overclocked reset it back to stock speeds!



Test for thermals and stability (well you already tried this but we need this information):
  • Download Speccy and post a Screenshot of the summary window, one at idle and another while putting load on the PC using Prime95 for the CPU side and Furmark for the GPU.
    • Before running Prime95 make sure to enable Round-off checking (see 1st post under the tutorial).



Good places to read more:

Post back with the results.


My System SpecsSystem Spec
Reply

 BSOD playing League of Legends, Locale ID 1033




Thread Tools



Similar help and support threads for2: BSOD playing League of Legends, Locale ID 1033
Thread Forum
BSOD playing league of legends error id 1033 BSOD Help and Support
Solved BSOD while playing League of Legends. BSOD Help and Support
BSOD playing League of Legends. BSOD Help and Support
BSOD playing League of Legends BSOD Help and Support
BSOD Playing League of Legends BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:43 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33