Borderlands 2

Borderlands 2

View Stats:
Erised Nov 5, 2013 @ 5:48pm
Please Help. Borderlands 2 Keeps Crashing my Computer.
The game will run for a few minutes, sometimes less, after which the computer will shutdown, or the screen will turn some random color at which point i can't do anything other than restart to get my computer to respond. I've looked through dozens of discussions about how to fix the problem and I've tried so many of the solutions that my brain hurts just thinking about it. it's only this game that makes it crash, the rest work perfectly. Anyways, here are my specs, can someone please help me.


Windows 8.1 Pro 64-bit ( I've tried it on Windows 7 Pro - same problem)
Intel Core i5 3570k @ 3.40GHz
16.0GB Dual-Channel DDR3 @ 933MHz - G.SKILL Ares Series 1866
ASRock Z77 Extreme4 (Updated to the latest BIOS version 2.90)
2047MB NVIDIA GeForce GTX 660 (EVGA)
1TB Western Digital HDD - (game installed here)
120GB Samsung SSD 840 Pro - (OS intalled here, game initially installed here - same problem)
Rosewill Green Series RG630-S12 630W - 80PLUS Broze Certified

I've updated the BIOS, uninstalled drivers using 3rd party softwares (Driver Fusion, IOBIT Uninstaller.. etc) as well as built in methods, clean installed the drivers, install just the basic graphics driver (no physx drivers), re-installed the game, moved the game to different HDD, used Driver Verifier (driver_verifier_detected_violation nvlddmkm.sys), checked if the system is overheating (no it isn't), and so many other solutions that i can't even remember them...

by now i'm tired, and have no clue what to do. any help will be much appreciated.
Last edited by Erised; Nov 5, 2013 @ 8:15pm
< >
Showing 1-15 of 21 comments
Erised Nov 6, 2013 @ 10:30am 
Originally posted by Fred:
Share a DirectX Diagnostics[windows.microsoft.com] log with us.

1. Open the Start menu, type "dxdiag" and press Enter.
2. Select Yes if you are questioned about confirming digitally signed drivers.
3. If available, click "Run 64-bit DxDiag" right from the button "Help".
4. Click "Save All Information...", save the file, and then open the file.
5. Copy the document content to Pastebin[pastebin.com] with a one week paste expiration and an unlisted paste exposure and share it with us.



Thank you for helping, sorry it took long time to reply, but i was at school.
Anyways, here is the report.

http://pastebin.com/byRzXXw6
Erised Nov 6, 2013 @ 10:33am 
Originally posted by Fred:
Try to revert to the previous NVIDIA driver. During install pick Custom and be sure to the tick the clean install option.

I have already done clean install multiple times, and just yesterday, i tried to install the previous version of the driver (331.58)
Erised Nov 6, 2013 @ 10:45am 
Originally posted by Fred:
Press Windows Flag + R and type eventvwr and submit. In there look up the crash. Can you share the details with us? What file or module did the error occur in? Any error code?

At this moment, i can't share the events (ccleaner decided to clear them), so i'll reply back in about 2 hours, when borderlands 2 finishes re-installing and i open it up a few more times and watch it crash my computer and infuriate me. However from what i remember, the critical errors were about Kernel-Power (unexpected shutdown).
Erised Nov 6, 2013 @ 5:15pm 
Originally posted by Fred:
Press Windows Flag + R and type eventvwr and submit. In there look up the crash. Can you share the details with us? What file or module did the error occur in? Any error code?

Here's the latest crash -
Level - Critical
Source - Kernel - Power
Event ID - 41
User - System
Logged - 11/6/2013 6:11:29 PM
There are 3 Other crashes that say the same thing, the only difference is the time.

Here's another one that specifically mentions Borderlands. (Application Error)

Faulting application name: Borderlands2.exe, version: 1.0.92.30171, time stamp: 0x5212ac16
Faulting module name: Borderlands2.exe, version: 1.0.92.30171, time stamp: 0x5212ac16
Exception code: 0xc0000005
Fault offset: 0x00d8fee9
Faulting process id: 0x10b4
Faulting application start time: 0x01cedb4f0d4ad641
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\Borderlands 2\Binaries\Win32\Borderlands2.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\Borderlands 2\Binaries\Win32\Borderlands2.exe
Report Id: 53e2cbc3-4742-11e3-8282-bc5ff47b0665
Faulting package full name:
Faulting package-relative application ID:

There are also a few warning that say the following:
Display driver nvlddmkm stopped responding and has successfully recovered


Erised Nov 7, 2013 @ 9:13am 
Originally posted by Fred:
Originally posted by Erised:

Here's the latest crash -
Level - Critical
Source - Kernel - Power
Event ID - 41
User - System
Logged - 11/6/2013 6:11:29 PM
There are 3 Other crashes that say the same thing, the only difference is the time.

Here's another one that specifically mentions Borderlands. (Application Error)

Faulting application name: Borderlands2.exe, version: 1.0.92.30171, time stamp: 0x5212ac16
Faulting module name: Borderlands2.exe, version: 1.0.92.30171, time stamp: 0x5212ac16
Exception code: 0xc0000005
Fault offset: 0x00d8fee9
Faulting process id: 0x10b4
Faulting application start time: 0x01cedb4f0d4ad641
Faulting application path: D:\Program Files (x86)\Steam\steamapps\common\Borderlands 2\Binaries\Win32\Borderlands2.exe
Faulting module path: D:\Program Files (x86)\Steam\steamapps\common\Borderlands 2\Binaries\Win32\Borderlands2.exe
Report Id: 53e2cbc3-4742-11e3-8282-bc5ff47b0665
Faulting package full name:
Faulting package-relative application ID:

There are also a few warning that say the following:
Display driver nvlddmkm stopped responding and has successfully recovered

Does your computer shut down or give any sign of issues outside of Borderlands 2 crashing your entire system?

No, Nothing other than borderlands 2. All of the other games i play work perfectly.
Last edited by Erised; Nov 7, 2013 @ 9:14am
probe Nov 7, 2013 @ 1:53pm 
Don't know if this helps but it might be worth a look >>
http://www.instructables.com/id/How-to-Fix-the-Nvlddmkm-Error/

Be sure to read the comments on it as there seems to be other issues that can cause this error.
Last edited by probe; Nov 7, 2013 @ 1:56pm
Erised Nov 7, 2013 @ 3:12pm 
Originally posted by Fred:
There is nothing I really tell from the excellent information you have provided so far.

If you do not mind, feel free to add me and I will try to diagnose the issue via a https://join.me remote desktop session.

I'm currently talking to Nvidia Tech support, if nothing pans out over there, i'll try it your way. Thank you for offering.
Last edited by Erised; Nov 7, 2013 @ 3:26pm
TillDeEnd Nov 7, 2013 @ 5:17pm 
Im no pro at this but i think it may be a driver issue. i say get geforce expirience and have that update your drivers. Again i dont really know exactly whats going on.
Drcane Nov 7, 2013 @ 5:18pm 
You can try Gearbox support as well. http://support.gearboxsoftware.com/anonymous_requests/new
probe Nov 7, 2013 @ 5:27pm 
According to the link from before it could even be your RAM not working properly. Is this the only time (or the only game) that causes this experience?
Erised Nov 7, 2013 @ 7:53pm 
i've talked to the Nvidia people, apparently it's not the driver's fault. I've submitted a request to gearbox to take a look at the problem. Also, since this is the only game that's having the problem, i don't think it is the RAM or the driver, since anything wrong with either of these would affect all of the games.
Escapegoat Aug 31, 2014 @ 10:41pm 
I have had this happen in the past with skyrim as well as just recently. The #1 cause of computer malfunctions is overheating, and second is micro-cracks within the circuitry caused by repeated rapid heating and then cooling, such as from consistent turning on and off. Don't keep turning it on and off many times or you will accelerate the inevitable process of crack damage.

Getting back to the shutting off, I remember that this case was caused by overheating. In the case of skyrim, my computer had slightly below required processing and graphics capabilities which I thought I fixed by lowering all the quality settings, but on top of that, it was extremely dusty which caused massive amounts of resistance within the circuitry which caused large amounts of heat, eventually frying the graphics card beyond repair.

I would take the computer to a professional and have them get rid of all the dust for $10-$20, ask them for an opinion since diagnostics are usually free, a solid state hard drive would help but is expensive, and otherwise you'd just need a better PC that's actually meant for intense gaming. In my case most recently, I was using a laptop, and even though it processed the graphics fine, it required too much processing and forced the computer to shut itself off to avoid heating damage, and when it did, part of it was so hot it would burn my skin if I kept my hand on it.
probe Sep 2, 2014 @ 5:13am 
For heat issues use CPUID HWMonitor for keeping track on your hardwares heatlevel. The program is free.
SALTe Sep 15, 2015 @ 4:25pm 
Originally posted by probe:
According to the link from before it could even be your RAM not working properly. Is this the only time (or the only game) that causes this experience?

This is what happens to me
peoples.ryan1087 Oct 9, 2015 @ 5:06pm 
Was this resolved? I am having the exact same issue. My desktop is only a few months old and this is the only game that does this.
< >
Showing 1-15 of 21 comments
Per page: 1530 50

Date Posted: Nov 5, 2013 @ 5:48pm
Posts: 21