BSODs while playing games, browsing (ongoing 6 month problem)

Hello spl313 and welcome to the Forums,

I have only analyzed one of your dump files because I am in a hurry, I will analyze the rest in one to three hours, please be patient.

----------

Please don't bump your thread; it's against the forum rules and disadvantageous for you as it makes the thread seem more busy as if you were receiving assistance.

2) No useless posts, e.g., thread bumping, useless one liners, junk posting to increase post count, and identical multi-postings in different forums.

Read here: Forum Rules

----------

Code:

Start Menu\Programs\McAfee Security Scan Plus    Public:Start Menu\Programs\McAfee Security Scan Plus    Public

McAfee is known to cause BSOD's and might be contributing to your problem;
Please Uninstall McAfee;

1. Open the Start Menu by clicking on the .
2. Click on Control Panel and under Programs click on Uninstall a program.
3. Wait for the list to update, and when done, please Right-click on McAfee and select Uninstall/Change.
4. Follow the on screen instructions, and when prompted, please restart your computer.
5. When you are done, please download the McAfee Removal Utility (click to download) and follow the on screen instructions.
6. Restart your computer.

----------

Please download Microsoft Security Essentials from here;

1. Download the file and save it to your desktop.
2. Double click the file and follow the on-screen instructions.
3. Restart your machine after installing MSE and please run a full scan and report back anything found.

----------

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 10E, {1f, fffff8a0138205a0, 0, 82178c}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )

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

Usual cause: Failing GPU driver.
More info Bug check 0x10E_F1.

----------

Please follow this;

Arc said:

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL 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
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

----------

Your dump files point to dxgmms1.sys, which is the Windows DirectX driver;
If you haven't already, please download and install DirextX 11.1 by downloading the KB2670838 update.
Please read before installing; How to download and install DirectX.

----------

After doing this, please stress test the graphics card using Furmark GPU Stress Test.

   Information

During the test please check the screen for artifacts.
The purpose of this test is to make your machine crash and create dump files so that we can pinpoint the cause of your problem.

   Tip

Please run Furmark once when your machine has just started, and once again when your machine has been active for several hours.

Good luck and keep us posted,
Nommy

Hello spl313,

I read your initial post wrong, please discard the downgrading to 314.22 WHQL part.
Instead, have you tried the new 327.23 WHQL and the 331.40 beta yet?
If not, both can be found here.

I still advice you to run Furmark.

----------

I will analyze the dump files in chronological order, from when you last got a BSoD to when you first got one.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80003345cee, 0, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1de )

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

Usual cause: Incompatible hardware, faulty drivers.
More info Bug check 0x1E_5.

Code:

2: kd> dps fffff8800988c000 fffff88009892000
fffff880`09890538  00000000`00000000
fffff880`09890540  fffffa80`03b695f0
fffff880`09890548  00000000`00003384
fffff880`09890550  00000000`000186a0
fffff880`09890558  fffff880`05883a48Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x1daa48

Driver reference table: nvlddmkm.sys.

----------

This dump file also points to your nvidia driver. Let's see if changing to either the 327.23 or 331.40 changes anything.

----------

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa8016bfe690, 0, fffff880063cb750, 2}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+6dc )

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

Usual cause: Incompatible hardware, faulty hardware, wrongly installed hardware, faulty RAM.
More info Bug check 0x50.

Code:

fffff880`0a29cf38 fffff800`031115d4 : 00000000`00000050 fffffa80`16bfe690 00000000`00000000 fffff880`0a29d0a0 : nt!KeBugCheckEx
fffff880`0a29cf40 fffff800`03092cae : 00000000`00000000 fffffa80`16bfe690 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43836
fffff880`0a29d0a0 fffff880`063cb750 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0a29d230 fffff880`063b13e7 : fffffa80`043d2601 fffffa80`03cbb010 00000000`03910248 fffff880`00000061 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x6dc
fffff880`0a29d320 fffff880`0632a072 : fffff880`060be465 00000000`00000200 fffff880`0a29da40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`0a29d370 fffff880`06329837 : fffff8a0`00000001 fffff8a0`09ea31c0 fffff880`0a29d9f0 fffff880`063cae50 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`0a29d980 fffff960`002514ce : 00000000`0807e380 fffffa80`086f2fe0 00000000`00002711 00000000`06f2d78c : dxgkrnl!DxgkRender+0x3e7
fffff880`0a29dbf0 fffff800`03093e13 : 00000000`03b5c210 fffff880`0a29dca0 00000000`00000000 00000000`1258bf70 : win32k!NtGdiDdDDIRender+0x12
fffff880`0a29dc20 000007fe`fdcb13fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0807e358 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fdcb13fa

The stacks point to both dxgmms1.sys and dxgkrnl.sys, which are Windows' DirectX drivers.

----------

Please first follow my suggestion from my previous post to update to DirectX 11.1 to see if anything changes.

----------

Code:

2: kd> dps fffff8800a297000 fffff8800a29e000
fffff880`0a29d350  fffff880`0a29d998
fffff880`0a29d358  fffff880`0a29d410
fffff880`0a29d360  fffff8a0`09ea31c0
fffff880`0a29d368  fffff880`0632a072 dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`0a29d370  fffff880`060be465*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0x8af465

As we can see this dump file also points to nvlddmkm.sys, which is the nvidia GPU driver.

----------

Until now all dump files point to faulty hardware, graphic related drivers and faulty GPU drivers, which makes me suspect the GPU. Let's see what Furmark comes up with.

----------

I see that you have already tested your RAM with Memtest. Question; for how many passes did you let each test run? It is recommended to let each pass run for at least 10 passes.
If you let it run for less passes, please test the RAM again by following this;
Please run Memtest86+ to test your RAM for issues.

   Tip

Let Memtest run for at least 10 passes and preferably overnight as it may take very long to complete.
Especially read part three of the tutorial, which explains you to test each RAM stick in all DIMM slots to filter out failing slots.

Arc said:

Suppose you have got the result like that:
No code has to be inserted here. It is a RAM, a bad RAM.

But if you have got a result like that:
No code has to be inserted here. It is a motherboard issue. The particular slot is bad.

----------

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff960001cf6ff, 0, 39}

Probably caused by : win32k.sys ( win32k!PDEVOBJ::bAllowShareAccess+3 )

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

Another stop 0x1E_5 bug check. But this time it points to a Windows driver; one that shouldn't fail on it's own.

----------

To my debugging knowledge this dump file shows no finite cause of the BSoD.

----------

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005f63060, fffffa8005f63340, fffff800033900d0}

----- ETW minidump data unavailable-----
Probably caused by : csrss.exe

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

Usual cause: Terminated system process.
More info Bug check 0xF4.

----------

This dump file points to csrss.exe, which stands for Client/Server Run time SubSystem and it is, as expected, needed by Windows in order to operate. Termination of this process will result in the BSoD you received.
This should be a one-of-a-time BSoD.

----------

Until now I have analyzed all dump files until the 23rd. And with the exception of one or two, they all point to graphics related drivers/hardware.
A big part of the older dump files from before the 23rd are stop 0x3B bug checks, which all point to faulty GPU drivers.
More info Bug check 0x3B.

I am fairly certain that your Nvidia GeForce GTX 460 is the issue here, but just to be sure I will ask someone else to double check. Please be patient until they arrive here.

----------

Just for good order, let's scan Windows with SFC to see if it comes up with any integrity violations;
Please use the SFC /SCANNOW command as displayed in option two of this tutorial.

1. Click on the .
2. Open an elevated command prompt.
3. Type "SFC /SCANNOW" without the quotations.
4. Let SFC do it's thing, and then prompted to, restart.
   
   If SFC found and repaired anything, please do the following:
5. When restarted, open an elevated command prompt.
6. Type (or copy) the following, this will create a .txt file on your desktop;
   findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
7. In your next reply, please attach this file using the method displayed in this tutorial.

Good luck and keep us posted,
Nommy

spl313 said:

(there is a known problem with nvidia drivers).

What is that? Explain please?

If you have problems with 314.22 WHQL and 327.23 WHQL ... and that is a known problem, if you let us know about it, it will be helpful.

Also, please take the furmark test as nommy the first suggested.

Hello spl313,

You have done a lot of testing by yourself I must say:)

----------

Code:

Ashampoo Anti-Virus Guard    "c:\program files (x86)\ashampoo\ashampoo anti-virus\aav_guard.exe" -autorun    Public    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

For testing purposes, please uninstall Ashampoo Anti-Virus Guard as it might be contributing to your problems.

I searched the web and couldn't find a specialized removal tool, so please remove it using Revo Uninstaller;

• Download and install Revo Uninstaller. I see that you have the pro version, please use it.
• Right click the program that needs to be removed, and click on Uninstall.
• Select "Advanced" as uninstall mode.
• Let Revo remove the program, and afterwards please follow the displayed steps to remove all entries of the program as well.
• When all programs have been uninstalled, please restart your machine.

----------

Please download Microsoft Security Essentials from here;

1. Download the file and save it to your desktop.
2. Double click the file and follow the on-screen instructions.
3. Restart your machine after installing MSE and please run a full scan and report back anything found.

----------

I see two things when I look at your most recent dump file; a 0x3B stop code, and a 0xC0000005 NTSTATUS code. The 0c3B is easily debugged, but the NTSTATUS code is beyond my debugging knowledge and I will request someone else to take a look at it;

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000f2ad4, fffff88008500e50, 0}

Probably caused by : memory_corruption

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

More info Bug Check 0x3B
Usual causes: Faulty RAM, faulty GPU driver.

----------

Code:

dps fffff880084f9000 fffff88008502000
fffff880`08500d90  fffff880`085015f8
fffff880`08500d98  fffff880`0f21a600Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0x12b600
fffff880`08500da0  00000009`00000000
fffff880`08500da8  fffff880`085014a0
fffff880`08500db0  fffff960`000f2ad4 win32k!xxxHkCallHook
fffff880`08500db8  fffff960`000f2ad5 win32k!xxxHkCallHook+0x1

Failing driver atikmdag.sys.
This is the GPU driver of your AMD Radeon R9 270x

----------

Code:

lmvm atikmdag
start             end                 module name
fffff880`0f0ef000 fffff880`0fddd000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Nov 22 16:51:33 2013 (528F7D85)
    CheckSum:         00C9BED4
    ImageSize:        00CEE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please downgrade the GPU driver to the 13.10 version. You can download it here.
Attachment 296119
----------

Code:

BugCheck 3B, {c0000005, fffff960000f2ad4, fffff88008500e50, 0}

Code:

!error 0xc0000005
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

This is a STATUS_ACCESS_VIOLATION error.

I have requested someone else to take a look at this and give further advice, please be patient until they arrive:)


Good luck and keep us posted,
Nommy

x BlueRobot said:

Please update your AMD graphics card driver to the latest WHQL version.

WHQL
Release Date: November 18th 2013
Version: 13.11

mov qword ptr [rsp+10h],rbx is used to move data from the rbx register into the offset of the GDT and the rsp register which contains the stack pointer.

Harry, something I need to tell you. Dont take it otherwise. I think the quote above is your only suggestion in that post? Coz, there is nothing else that is meaningful and necessary for the OP in that.

If that is your only suggestion, make it clear that the OP cannot update the display driver. Updating is not technically possible with a previous version, as the installed Driver is AMD Catalyst 13.11 BETA 9.2 (13.250.18.0 of November 7) which is a later version than the suggested (and required) version.

Though Nommy suggested almost the same thing just above.

Dont mind my friend, but you are a good debugger. Please concentrate on the main part of the job. You are supposed to suggest the OP some good thing.