BSOD during playing games

brezel · 19 Mar 2013

Hi Guys!

The BSOD-s started with Battlefield 3. Then I tried every kind of solution which i found online, but nothing worked. Then I recently did a full system refresh, Battlefield crashed again. So I got used to it, and played other games like Trine 2 or Counter Strike Global Offensive. Those games worked just fine, but now they're also crashing. Anything else works fine, older games also work. After 10 or 15 minutes of play. Usually I find the root of the problem but now this tricks me well.

Now the PSU is suspicious for me. My card needs minimum 500w, i have this exact amount. But maybe it's not enough for fully powering the videocard.

Thank you in advance!

A fellow gamer.

Saurabh A · 19 Mar 2013

Hi brezel,

The crash dump analysis:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Errors\SF_19-03-2013\031913-11700-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`030a4670
Debug session time: Wed Mar 20 04:03:26.825 2013 (UTC + 5:30)
System Uptime: 0 days 0:22:10.699
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {22fad0, 0, 6b4f40fa, 8}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45955 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
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: 000000000022fad0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: 000000006b4f40fa, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000008, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310e100
 000000000022fad0 

FAULTING_IP: 
+62b2faf03b7dd94
00000000`6b4f40fa ??              ???

MM_INTERNAL_CODE:  8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csgo.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002e6f12b to fffff80002ed5c40

STACK_TEXT:  
fffff880`0ae4c978 fffff800`02e6f12b : 00000000`00000050 00000000`0022fad0 00000000`00000000 fffff880`0ae4cae0 : nt!KeBugCheckEx
fffff880`0ae4c980 fffff800`02ed3d6e : 00000000`00000000 00000000`0022fad0 00000000`218c0201 00000000`21baff34 : nt! ?? ::FNODOBFM::`string'+0x45955
fffff880`0ae4cae0 00000000`6b4f40fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`21bafed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6b4f40fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+45955
fffff800`02e6f12b cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+45955

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  50e79935

FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+45955

BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+45955

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

Probably caused by : ntkrnlmp.exe
Related to 'NT Kernel & System'

It appears that the 'Blue Screen' appeared while playing 'Counter Strike Global Offensive'. You may want to try working with 'video settings' in the game: Open the 'Game' > Go to 'Video Settings' > 'Advanced' > Disable 'Multi core rendering'.

Please clean up (remove) ESET NOD32 anti-virus from the system (For troubleshooting purpose) Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase:

Code:

Start Menu\Programs\ESET	Public
Start Menu\Programs\ESET\ESET NOD32 Antivirus

Please try downloading & installing Microsoft Security Essentials - Microsoft Windows to see if that helps.

PAGE_FAULT_IN_NONPAGED_AREA (50):
Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
Another common cause is the installation of a faulty system service. An antivirus software can also trigger this error, as can a corrupted NTFS volume.

Please share if you recently made any hardware change to the unit (Especially RAM related). In either case, please test the system 'Memory' and share results: RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

If the issue persists, you may try the following steps also:

1. Perform 'Windows Updates' Install Windows updates and check if the issue re-occurs.

2. If you still experience issues, it could be a corrupted 'NTFS volume'. You may try to run Chkdsk /f /r to detect and repair disk errors. Please refer to the steps in this tutorial (Option 2) to attempt the diagnosis/repair through 'Command Prompt': Disk Check

Hope this helps. Do reply with the findings; would be glad to assist.

brezel · 20 Mar 2013

Thank you for the quick response. I did test te ram with memtest and windows memory diagnostics and ther wasn't any problem, but i will do this method asap. As well as the others. I'll reply as soon as I've tried these.

brezel · 20 Mar 2013

So i did the less tricky stuff. All windows update (recommended also), chkdsk/r, turned off multicore rendering... And one of it worked. Neither Trine 2 nor Csgo got BSOD. Is it possible that it wont happen again, or should i continue with the other methods? Can it still be a faulty hardware?

Saurabh A · 21 Mar 2013

Hi brezel,

Thank you for the response.

Glad that the system looks stable now. The 'crash dump' may not produce 'absolute results'. Good that the system is responding well to the initial troubleshooting steps already; would recommend you to observe the performance for a few days to see if the issue re-occurs.

If you experience any further issues, you may continue with the remaining steps (Remove the 'Anti-Virus' and install 'Microsoft Security Essentials') and check results. Do reply with the findings; would be glad to assist.