BSOD Clicking "Play" Borderlands 2 & Borderlands the Pre-Sequel

[mdna]

BSOD Clicking "Play" Borderlands 2 & Borderlands the Pre-Sequel

Hello,

I run these games via Steam and when I click "Play" the program goes to the next step, sometimes a splash image pops up then the computer crashes/shuts down and restarts. Sometimes I see the blues creen, other times I get the black screen with the option of running safe mode.

I have:
Uninstalled/Reinstalled Steam and the games. (Also manually deleted all Borderlands folders)
Verified game files integrity on both games
Tried playing offline - wouldn't let me.
Updated graphics drivers. Installing old Physx drivers
Running in windowed mode.
Tried compatibility mode Service Pack 3
Contacted Gearbox (no reply yet)

I have attempted to solve this issue on my own when the problem was happening with Borderlands 2. Now that BL the Pre-Sequel is out, I'm having the same issue and am running out of solutions.

I play other games online and these two are the only programs that are having issues.

I hope I am following the correct steps for assistance.

Thank you!

 

[Arc]

Hi mdna.

A stop 0x124 is usually assumed to be a hardware related issue, but actually it may be anything and everything. Even it is noticed that the gigabyte bloatwares also can cause it.

Are you overclocking?
As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator - The most trusted PSU Wattage Calculator
Also let us know the wattage of the PSU.

You have gigabyte bloatware installed which is known as stop 0x124 causers.

• Start Menu\Programs\GIGABYTE
• Start Menu\Programs\GIGABYTE\AutoGreen
• Start Menu\Programs\GIGABYTE\EasySaver
• Start Menu\Programs\GIGABYTE\ET6

I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest for at least 8 passes, preferably overnight.
If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Stress test the CPU.

Hardware - Stress Test With Prime95
​

Let us know the results.
_____________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80081c6038, 0, 0}

Probably caused by : AuthenticAMD

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

3: 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: fffffa80081c6038, 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_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`031af5b0 fffff800`036dbcb9 : fffffa80`081c6010 fffffa80`06a1c040 fffffa80`00000006 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031afad0 fffff800`035bcea7 : fffffa80`081c6010 fffff800`036362d8 fffffa80`06a1c040 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031afb00 fffff800`03524275 : fffff800`03697d00 00000000`00000001 fffffa80`081b4b60 fffffa80`06a1c040 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031afb40 fffff800`0349a261 : fffff880`010d0e00 fffff800`03524250 fffffa80`06a1c000 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031afb70 fffff800`0372c73a : 00000000`00000000 fffffa80`06a1c040 00000000`00000080 fffffa80`06a00040 : nt!ExpWorkerThread+0x111
fffff880`031afc00 fffff800`034818e6 : fffff880`02fd7180 fffffa80`06a1c040 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031afc40 00000000`00000000 : fffff880`031b0000 fffff880`031aa000 fffff880`03d1b740 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH:  {78c2f422-5335-4ef3-5cef-a28518da5023}

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

 

[Tillysaint]

BSOD 1033 BCCode:1033 can not boot

How can I comply with the Blue Screen of Death (BSOD) Posting Instructions when I can't boot to access anything on my system? I'm "dead in the water!"

 

[mdna]

Hi Arc, Thank you for taking the time to analyze and suggest possible solutions. Due to work, I should be able to post results by Monday at the latest!

 

[mdna]

I would like to update this situation! I have been really busy with work and other responsibilities, and I received a reply (finally) from Gearbox with their solution. I will copy/paste what they sent me here in case anyone else with my problem stumbles upon this. ---- Thank you for contacting 2K Support! First off, I'd like to apologize for the longer than normal response time you had to wait through before hearing back from anyone! We've had a couple game launches this month and as a result, the number of tickets we're receiving from players is a bit overwhelming at the moment, so I'd like to thank you for your patience with us during this crazy time. Our development team is currently looking into an issue that Borderlands 2 seems to be having with very specific processors/motherboards. Specifically, it seems to be related to AMD FX series processors, and their accompanying motherboard/processor/BIOS setups. Basically, the way these setups handle multi-threading is conflicting with the Steam launcher, which can in some cases cause anything from blue screening to full on system resets. Here is an support page on the AMD website describing the issue: STEAM enabled games on AMD FX platforms Below is a known user fix which seems to resolve most cases of AMD FX cards' compatibility issues with Steamworks titles. **This involves a BIOS update, which if done incorrectly, can cause serious permanent damage to the motherboard, so if you are not comfortable doing this yourself, please consult your system manufacturer.** Go to your motherboard manufacturers website and go to their support page. Find or search for your motherboard model. Download the LATEST BIOS for your motherboard. This will differ depending on how the BIOS is on every motherboard. Some BIOSs can update through the UEFI (Graphical BIOS) or through the use of a flash program such as AWDFLASH. Read in your manual about how to update your BIOS. This part is VERY IMPORTANT. DO NOT EVER SHUT DOWN THE PC WHILE THE BIOS IS BEING UPDATED. If you do, it will brick the board and render is useless and inoperable. Once the update is complete, you computer may or may not restart on it's own. Again, read up on it in your manual or on the manufacturers website. You will need to set your BIOS back to default, and any overclock settings or boot order as well. Now you should be ready to game again. Alternatively, players who use gigabyte motherboards can follow this post: Steam Users' Forums - View Single Post - [READ FIRST] AMD Bulldozer CPU Crashes CS:GO If in the event that this DOES NOT fix the issue, contact your motherboard manufacturer about the issue and they might give you an updated BIOS or patch one and put it back on the support site. Furthermore, you can also try checking for a CPU driver update. Most AMD CPUs do have a driver, so you may want to consult AMD about installing/updating one. If you continue to have issues, please provide us with a DXDIAG and MSinfo file. To get these files: 1) Press the Windows key +'R' on your keyboard > Type dxdiag > Click OK > Click Save all information 2) Press the Windows key +'R' on your keyboard > Type msinfo32 > Click OK > Select File and then EXPORT and save the file as a text file(*.txt) Log in to your support ticket and then select the attach file option under the comments box to attach the files to your case. Alternatively respond to this email with the files attached. Once I receive this information, I'll be able to pass it off to the development team and they'll research your issue and get back to you. Personally, a lot of this stuff is over my head (most of this answer was written by someone who has a deep understanding of computers. Much deeper than my understanding. Honestly, I pretty much just spiffed it up and made sure all the provided links were still working), so I'm hoping that this makes sense to you- not to mention that it works for you! I totally get how frustrating it would be to have this crazy crash happen every time you go to boot up BL2. ----- So I followed the directions to update my BIOS and I tried running BL-The PreSequel and so far no crash or restart! I only played for literally 5 minutes as I have no time right now. I hope this puts an end to that problem Thanks again, ARC for taking the time to look into my problem! I really appreciate it!!

 

[Arc]

OK, let us know for any further issue.