BSOD playing games, especially Dota 2 and Call of Duty Ghosts.

steamboat · 29 Nov 2013

Hey guys, I've been getting numerous BSOD when I play games such as Dota 2, Call of Duty Ghosts and Counter Strike Source/Global Offensive.
I'm not sure how to retrieve the error codes, so can someone please help me.

I have run the Windows Memory Diagnostic Tool (2 passes) and there were no problems.

These are 3 critical errors I got today (30/11/13).

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 30/11/2013 11:59:54 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer:
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2013-11-30T00:59:54.841602400Z" />
<EventRecordID>91090</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">10</Data>
<Data Name="BugcheckParameter1">0xfffffa80099b0d70</Data>
<Data Name="BugcheckParameter2">0x2</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0xfffff8000309403f</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 30/11/2013 10:53:46 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer:
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2013-11-29T23:53:46.826002400Z" />
<EventRecordID>90963</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">10</Data>
<Data Name="BugcheckParameter1">0xfffffb80073c6148</Data>
<Data Name="BugcheckParameter2">0x2</Data>
<Data Name="BugcheckParameter3">0x1</Data>
<Data Name="BugcheckParameter4">0xfffff8000308c512</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 30/11/2013 12:55:50 AM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer:
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>2</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000002</Keywords>
<TimeCreated SystemTime="2013-11-29T13:55:50.872802400Z" />
<EventRecordID>90648</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">59</Data>
<Data Name="BugcheckParameter1">0xc0000005</Data>
<Data Name="BugcheckParameter2">0xfffff80003079e94</Data>
<Data Name="BugcheckParameter3">0xfffff880024c6e50</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">false</Data>
<Data Name="PowerButtonTimestamp">0</Data>
</EventData>
</Event>

Arc · 01 Dec 2013

The latest BSOD as per the zip is of 09/11/2013. That was a BSOD caused by the display driver.

In the mean time, there must be some system changes, and analyzing those dumps may not represent the continuing present.

Is the newer BSODs does not generate crash dumps? Then follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

steamboat · 02 Dec 2013

Arc said:

The latest BSOD as per the zip is of 09/11/2013. That was a BSOD caused by the display driver.

In the mean time, there must be some system changes, and analyzing those dumps may not represent the continuing present.

Is the newer BSODs does not generate crash dumps? Then follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

I got a few more BSODs today. Please help

Arc · 02 Dec 2013

First of all, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Next Install the NVIDIA DRIVERS 314.22WHQL only.

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.
________________________________________________________________________________________

Code:

BugCheck 18, {0, fffffa80080c1a10, 2, fffffa8007fca260}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+48de1 )

Followup: MachineOwner
------------------------------------------------------------------------
BugCheck D1, {fffff880090ca608, 2, 1, fffff8800fdb8b3d}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::UnreferenceDmaBuffer+7d )

Followup: MachineOwner
-----------------------------------------------------------------------
BugCheck 1000007E, {ffffffffc0000005, fffff8800f1d3f9c, fffff880022f4f28, fffff880022f4780}

Probably caused by : nvlddmkm.sys ( nvlddmkm+f4f9c )

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

DV Next?

steamboat · 03 Dec 2013

I've followed all the steps, but I'm noticing a decrease in performance in games such as Counter Strike: Global Offensive, Call of Duty Ghosts and Dota 2.

Arc · 03 Dec 2013

Let us know if there is any further BSOD.

steamboat · 03 Dec 2013

Arc said:

Let us know if there is any further BSOD.

I got two BSODs today while playing World of Warcraft. It's the first time I have got a BSOD with WoW.

Also while stress testing using Furmark. I notice there are white horizontal lines that are appearing. The temperature at load levels at around 69 degrees @ 10 fps.

Arc · 04 Dec 2013

There is no solid reason to believe these BSODs are game related.

Code:

BugCheck 50, {fffffb00c0898690, 0, fffff96000145663, 7}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!NtUserQueryWindow+83 )

Followup: MachineOwner
-----------------------------------------------------------------------
BugCheck 1, {772d15fa, 0, 200, fffff88007be7b60}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

If you get any display anomaly during furmark, post a scerrnshot here, let us see it.

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to 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.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions, not the crash dumps only.

Be sure that you upload your MSINFO32.nfo file.

Click on the start button
Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
Give the time for processing, it will save a .nfo file on your desktop.
Zip it, and upload it following the instruction.

steamboat · 04 Dec 2013

Arc said:

####

It's very difficult to obtain a screenshot of the anomaly using the screenshot button, but I am hoping this description is enough. If you look in the top left corner, you'll see two very small white lines. Imagine those lines are longer and span the entire width of the screen, especially at the bottom. They constantly pop up then disappear. Sometimes at different thicknesses. 68°C @ 9 fps.

Attachment 296199

----------------------------------

I ran Driver Verifier and could not run my computer normally after reaching the desktop. It took about 10 seconds after the desktop screen appeared for the computer to bluescreen. I restarted my computer and the same bluescreen error code came up the second time. I went into safe mode then disabled it from there then restarted my computer.

Arc · 05 Dec 2013

It is display artifact, and you need to see the situation with a replacement GPU. Your GPU is failing to take the load.

The driver verifier enabled BSODs caught HIDCLASS.sys, which is common for DeathAdder keyboard/mouse. Cannot say it a issue right now.

We need to see the situation with with a replacement GPU first.