BSOD playing Borderlands 2, multiple BSOD's

[bsodSUX]

Whenever I play BL2... I get random BSOD's at random times. Sometimes I will get 1-2 for a 2-3 hour session, other times I will get them every 10 minutes or so. I have skype running in the background as well. I can play other games with no issues. I played a dozen plus hours of Homefront with zero crashes. Both Homefront and BL2 were played through steam. Any ideas?

 

[Arc]

Hello bsodSUX.

The two latest crashes pointing it out towards the graphics memory, somehow.

[COLOR=Red]BugCheck 1000007E[/COLOR], {ffffffffc0000005, fffff88003d696fa, fffff88011fd5788, fffff88011fd4fe0}

[COLOR=Red]Probably caused by : dxgmms1.sys[/COLOR] ( dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a )

Followup: MachineOwner
---------
SYMBOL_STACK_INDEX:  0

[COLOR=Red]SYMBOL_NAME:  dxgmms1!VIDMM_MEMORY_SEGMENT[/COLOR]::EvictResource+f3a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

[COLOR=Red]IMAGE_NAME:  dxgmms1.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff88011fd4fe0 ; kb

[COLOR=Red]FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT[/COLOR]::EvictResource+f3a

BUCKET_ID:  X64_0x7E_dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+f3a

Followup: MachineOwner
*************************************************************************
[COLOR=Red]BugCheck 3B[/COLOR], {c0000005, fffff88004502f08, fffff8800b245e60, 0}

[COLOR=Red]Probably caused by : dxgmms1.sys[/COLOR] ( dxgmms1!VidMmQueryAllocationSizeInSystemMemory+0 )

Followup: MachineOwner
---------
SYMBOL_STACK_INDEX:  0

[COLOR=Red]SYMBOL_NAME:  dxgmms1!VidMmQueryAllocationSizeInSystemMemory[/COLOR]+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1
[COLOR=Red]
IMAGE_NAME:  dxgmms1.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

STACK_COMMAND:  .cxr 0xfffff8800b245e60 ; kb

[COLOR=Red]FAILURE_BUCKET_ID:  X64_0x3B_dxgmms1!VidMmQueryAllocationSizeInSystemMemory[/COLOR]+0

BUCKET_ID:  X64_0x3B_dxgmms1!VidMmQueryAllocationSizeInSystemMemory+0

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

Look at the similarity, despite of having two totally different bugcheck codes.

First of all, update your ATI/AMD display driver.
You can get it from the link in our forum, http://www.sevenforums.com/graphic-...alyst-video-driver-windows-7-a.html#post17671, or you may go to AMD Graphics Driver and Software and opt for Automatically Detect and Install the appropriate driver for your card.

During installation, you may opt for advanced installation, and install the display driver only, not the Catalyst Control Center.

Then, tress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

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.

And, stress test the video memory, too.
|MG| Video Memory Stress Test 1.7.116 Download

If you are overclocking, restore everything back to default.

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Let us know the results. And, what antivirus do you use?

 

[bsodSUX]

Thanks. I have begun to try your steps. I have only been noticing this problem with BL2 and haven't had similar issues with other similarly graphic intensive games. I have uninstalled the catalyst center like you have suggested. I will run diagnostics, try BL2 again and will see if things work.

The reason why I had the Catalyst Center installed originally was because my monitor, LG W2353V-PF would not display (or maybe it's the 6950) the screen properly. There are margins around the screen, approximately 1" on the left and right and .5" on top and bottom. The Catalyst program allowed me to correct that.

 

[bsodSUX]

http://www. justin.my/2011/12/cannot-display-full-screen-using-ati-amd-radeon/

This is the problem that I'm having... everyone says that the 6950 is very intimately tied into the Catalyst program

 

[Arc]

In this situation you need to keep CCC installed. Actually it is a bloatware, usually not needed, and sometimes problematic.

Let us know how things go.

 

[bsodSUX]

Ok so no BSOD on BL2... but an app crash.. this is what came up on the crash.

Problem signature:
Problem Event Name: APPCRASH
Application Name: Borderlands2.exe
Application Version: 1.0.28.42246
Application Timestamp: 50eccfc4
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.18015
Fault Module Timestamp: 50b83c8a
Exception Code: 00000001
Exception Offset: 0000c41f
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 79f0
Additional Information 2: 79f00ca709e9e46a95c902827f16d9ae
Additional Information 3: f7b1
Additional Information 4: f7b11826d7091f719e791db9769a9d7b

 

[bsodSUX]

Tried Metro2033 and about 1-1.5 hrs in, the game crashed but no BSOD.. got this

Problem signature:
Problem Event Name: APPCRASH
Application Name: Metro2033.exe
Application Version: 1.0.0.1
Application Timestamp: 4c7775b7
Fault Module Name: Metro2033.exe
Fault Module Version: 1.0.0.1
Fault Module Timestamp: 4c7775b7
Exception Code: c0000005
Exception Offset: 000a99a6
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

 

[bsodSUX]

I may have solved the issue... Apparently in Steam, you can verify the integrity of each game's files.... and whaddya know... several files needed to be re-acquired. Hopefully that fixes the issue.

 

[bsodSUX]

Well validating the game files have fixed the non BSOD crashes but I'm still getting more BSOD's... had reinstalled drivers after wiping them out... all bios settings are at default... furmark runs fine, prime 95 runs fine... This is starting to become annoying

 

[Arc]

If you get BSODs, you need to post the crash dumps following the Blue Screen of Death (BSOD) Posting Instructions, so that we can see it.

 

[bsodSUX]

Should have some of the latest ones... I'm beginning to think it may be the video card. I didn't unlock it or tinker with it at all, but I'm getting the vast majority of these BSOD's while gaming.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 50[/COLOR], {fffff6fc1004a780, 0, fffff80004c9b7a1, 2}


Could not read faulting driver name
[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MiDispatchFault+d1 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR=Red]PAGE_FAULT_IN_NONPAGED_AREA (50)[/COLOR]
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff6fc1004a780, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80004c9b7a1, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80004eae100
GetUlongFromAddress: unable to read from fffff80004eae1c0
 fffff6fc1004a780 Nonpaged pool

FAULTING_IP: 
nt!MiDispatchFault+d1
fffff800`04c9b7a1 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88007f53820 -- (.trap 0xfffff88007f53820)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=f820094f02b00400 rbx=0000000000000000 rcx=00000000f820094f
rdx=00000000ffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004c9b7a1 rsp=fffff88007f539b0 rbp=fffff683ff7491e8
 r8=fffff820094f02b0  r9=0000000000000000 r10=0000000fffffffff
r11=fffff68000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!MiDispatchFault+0xd1:
fffff800`04c9b7a1 4b8b1c1c        mov     rbx,qword ptr [r12+r11] ds:fffff680`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80004c258e0 to fffff80004c7efc0

STACK_TEXT:  
fffff880`07f536b8 fffff800`04c258e0 : 00000000`00000050 fffff6fc`1004a780 00000000`00000000 fffff880`07f53820 : nt!KeBugCheckEx
fffff880`07f536c0 fffff800`04c7d0ee : 00000000`00000000 fffff6fc`1004a780 fffff880`07f53700 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x437f6
fffff880`07f53820 fffff800`04c9b7a1 : 00000000`0031bcff 000007fe`e92b63d0 fffff683`ff7495b0 fffffa80`0d0e8c48 : nt!KiPageFault+0x16e
fffff880`07f539b0 fffff800`04c8b549 : 00000000`00000000 000007fe`e923dff3 fffff700`01080000 00000000`00000000 : nt!MiDispatchFault+0xd1
fffff880`07f53ac0 fffff800`04c7d0ee : 00000000`00000008 000007fe`e923dff3 00000000`ffffff01 00000000`00000000 : nt!MmAccessFault+0x359
fffff880`07f53c20 000007fe`e923dff3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`01d5c480 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`e923dff3


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDispatchFault+d1
fffff800`04c9b7a1 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDispatchFault+d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

[COLOR=Red]IMAGE_NAME:  memory_corruption[/COLOR]

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

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

According to Carrona.org, STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Let us check them one by one.

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.

Run SFC /SCANNOW Command - System File Checker

Which antivirus Do you use? Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

There is a little Hint of NTFS corruption.

fffff880`07f53748  fffff880`01224020 Ntfs!NtfsInitializeIrpContext+0x60
fffff880`07f53798  fffff880`012affee Ntfs!NtfsCopyReadA+0x20e
fffff880`07f53a18  fffff880`01110541 fltmgr!FltpFastIoRead+0xe

Do some disc checks.

1. Update your SSD's Firmware (Skip it, if it is not a SSD)
2. Re-seat the sata and power.
   
   
3. Run chkdsk /f/r, following the option two of the tutorial Disk Check
4. Seatool for dos: SeaTools | Seagate download
   Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run.

Finally, you may search for any available update for your BIOS.

BIOS Version/Date    American Megatrends Inc. 0402, [COLOR=Red]5/16/2011[/COLOR]

But if you are not sure how to do it, and what to do, ask us.

One more thing .... uninstall it.

Start Menu\Programs\Free Window Registry Repair

Such a program is not only unnecessary but also harmful. It may damage windows 7's file and registry system beyond repair.

Let us know the results.

 

[bsodSUX]

Reg program uninstalled. I'll start memtest right now and let it sit overnight. I do have an SSD installed. I am using malwarebytes as my antivirus. I will get on your advice and will post my results... thanks!

Edit:

The steam games are constantly becoming corrupted... I'm not sure if it's because of BSOD's in mid game play ... you mentioned NTFS corruption... could they be linked?

It should also be noted that I do not recall having a noticeable volume of BSOD's when I had Vista installed... I have a Corsair Force 3 SSD and their site forums state

This update has been validated for use with Windows 7. It has not been validated with Windows Vista and Windows XP however it may work with these OS's. Users are encouraged to update the drives with Windows 7 when possible.

 

[bsodSUX]

2 minutes into memtest, 4 items in red appeared.

 

[Arc]

My best suggestion for you is to use the free version of MBAM only, and for the real time protection use MSE. Ntfs.sys and fltmgr.sys may be failed by this programs filtering mechanism, too.

EDIT. Stop memtest.
Go to the Part 3: If You Have Errors:
Follow it. It will help you to determine which stick is corrupted. Otherwise, you may get an all new kit.

 

[bsodSUX]

Thanks... Yeah, 125 errors at the 25 minute mark. I will test further in the morning. Hopefully I will not have to buy all new ram, but a single stick

 

[bsodSUX]

And so through the testing, I believe I found the culprit stick of ram... I have tested it on it's own and errors... tested the other 3, no errors... tested the slots in the mobo as well with no issues. I have removed it and now have 12gb of ram but my computer is sluggish as hell. I'll continue to investigate and once I can solve the sluggishness, I'll try some games.

 

[bsodSUX]

Computer is now unbearably slow since removing ram from it. It now has 8gb in it as I thought for some odd reason it may not have liked having 3 x 4gb in it... 2 slots are black, 2 are blue.

I feel like driving over this tower with my car and building a new one

Edit: SFC came back fine. I have the full ver of malwarebytes and it's full scan came back neg...

 

[Arc]

Make it sure that all the RAM sticks are of equal FSB. Otherwise, it will use the average RAM only, which will cause the system run slow.

 

[bsodSUX]

All 4 are the same. Running security essentials scans now. 10 hours of memtest and the 2 sticks in the machine are fine. Zero errors. Computer is still sluggish. I have no idea why. 2 crashes as well but they didn't BSOD. The screen went garbly colors like all tiny rectangles if I had to coin shapes to it.