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

[steamboat]

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]

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: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
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]

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: http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html
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]

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.
________________________________________________________________________________________

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]

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]

Let us know if there is any further BSOD.

 

[steamboat]

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]

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

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.

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

 

[steamboat]

####

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.

View 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]

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.

 

[steamboat]

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.

Hello again, mate.

Thanks for all your help so far, but I'm afraid I got a BSOD today (27/12/2013) after I installed my new GPU. I bought an Asus AMD R9 270x DC2T.

I just wanted to let you know that I am using a Logitech G15 Keyboard and Razer deathadder and I don't have the drivers of those installed. I'm just using the microsoft ones, which gets installed when I plug the USB of these devices in.

Here's the dump file and other files.

 

[Arc]

This time the crash dump is reporting memory issue.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {10000c1a6, 2, 1, fffff800030d390a}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR]

Followup: memory_corruption
---------

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.

Let us know the result.

 

[steamboat]

This time the crash dump is reporting memory issue.

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {10000c1a6, 2, 1, fffff800030d390a}

[COLOR=Red]Probably caused by : memory_corruption[/COLOR]

Followup: memory_corruption
---------

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.

Let us know the result.

I left it overnight and memtest ran 14 passes with ZERO errors.

Over the past 3 days I got a few more BSOD.

View attachment 299500

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

I ran 'verifier' to test the drivers. I didn't get any BSOD, but my screen was all distorted and it froze.

 

[Arc]

BSODs are almost the same, mostly pointing to memory corruption.

Memtest did not detect any memory issue.
GPU is changed.
Driver Verifier does not find any failing driver.

So now the situation is tough.

Three more things I would ask ......

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.

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

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 .
________________________________________________________________________________________

BugCheck A, {fffffa800b2badd4, d, 1, fffff800030d0180}

Probably caused by : memory_corruption

Followup: memory_corruption
-----------------------------------------------------------------------
BugCheck 50, {fffffa000307e8c4, 0, fffff8000307cd1d, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceRepeat+2b )

Followup: MachineOwner
-------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff80003095607, fffff88006094f80, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

 

[steamboat]

BSODs are almost the same, mostly pointing to memory corruption.

Memtest did not detect any memory issue.
GPU is changed.
Driver Verifier does not find any failing driver.

So now the situation is tough.

Three more things I would ask ......

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.

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

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 .
________________________________________________________________________________________

BugCheck A, {fffffa800b2badd4, d, 1, fffff800030d0180}

Probably caused by : memory_corruption

Followup: memory_corruption
-----------------------------------------------------------------------
BugCheck 50, {fffffa000307e8c4, 0, fffff8000307cd1d, 7}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceRepeat+2b )

Followup: MachineOwner
-------------------------------------------------------------------------
BugCheck 3B, {c0000005, fffff80003095607, fffff88006094f80, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

I'm pretty confident in my hardware, especially my PSU.

1. I haven't overclocked any of my hardware.

2. According to eXtreme Power Supply Calculator the recommended PSU wattage is 408W.
I'm running a Corsair HX750W Silver Plus. It's a professional series power supply that cost me quite a bit.

3. I've never had an overheating issue. My computer runs pretty cool.

 

[Arc]

Everything looks fine, except only one thing. The furmark screenshot.

I would suggest you to observe the situation with another GPU.

 

[steamboat]

Everything looks fine, except only one thing. The furmark screenshot.

I would suggest you to observe the situation with another GPU.

That screenshot was taken with my old GPU (Asus GTX 460).
I've replaced that with a new Asus Radeon r9 270x. There's no problem with my new graphics card when I run furmark. I still get a BSOD sometimes, especially when I play Dota 2.

 

[Arc]

Let us see the furmark screenshot using your new GPU.

 

[steamboat]

Let us see the furmark screenshot using your new GPU.

Here you go.
View attachment 299711

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

I got a different BSOD today with this <dxgmms1.sys> in the error code.

 

[steamboat]

Let us see the furmark screenshot using your new GPU.

The BSODs are becoming more frequent. I've gotten so many over the past few weeks.