Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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

30 Sep 2013   #1
spl313

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
BSODs while playing games, browsing (ongoing 6 month problem)

I've been having problems with random BSOD's, mostly while playing games. They started around march, this year (as far as I remember). Thing I have done so far:

-formated hard drives twice and reinstalled Windows (zeroed once)
-ran memtest (couple of times with every stick tested solo, around 25 hours of testing altogether with no errors)
-ran chdsk, scannow, hdtune, mhdd boot test, crystaldiskinfo, all with no problems detected
-cleaned whole box with vacuum cleaner and compressed air
-put both GPU and memory sticks out and in
-updated bios, drivers

Computer is 3 years old now, and same problem persisted with next 3 windows instalation ( I did complete hdd format every instalation). There were a lot of errors, most of them related to drivers, but some were just stop errors with some random error codes.

I have a lot of errors in games, I think exceptionally lot since I never had so many errors before. I tried to downgrade my nvidia drivers to 314 but it didn't really help (there is a known problem with nvidia drivers).

I'd be really grateful if you could help me with that problems. It's been bugging me for over half year, with couple of BSODS almost everyday, and I can't afford to buy a new PC.


My System SpecsSystem Spec
.
01 Oct 2013   #2
spl313

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Hello, did you have any insight into my logs?
My System SpecsSystem Spec
02 Oct 2013   #3
nommy the first

Microsoft Windows 8.1 64-bit Professional
 
 

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.
Quote:
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;
Quote   Quote: Originally Posted by Arc View Post
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   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   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
My System SpecsSystem Spec
.

02 Oct 2013   #4
nommy the first

Microsoft Windows 8.1 64-bit Professional
 
 

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   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.
Quote   Quote: Originally Posted by Arc View Post
Suppose you have got the result like that:
testSlot1Slot2
RAM1ErrorError
RAM2GoodGood
It is a RAM, a bad RAM.

But if you have got a result like that:
testSlot1Slot2
RAM1ErrorGood
RAM2ErrorGood
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
My System SpecsSystem Spec
02 Oct 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by spl313 View Post
(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.
My System SpecsSystem Spec
03 Dec 2013   #6
spl313

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Hello
Iím writing this in word, saving it every minute because last 2 posts were lost in BSOD.
First of all, sorry for bumping post last time, I had couple of BSODS in a row and was upset.

Problem with BSODS is persistent, it still crashed for last two months.

Things Iíve done since I last posted:

-changed my GPU from GTX 460 to r9 270x (Gigabyte)

-changed my CPU and thermal paste (Enermax TS40)

-scanned with sfc /scannow (just recently), no problems there

-scanned for viruses (with spybot, malwarebytes and ashampoo, aswell as some specific programs for rootkits and Microsoft Essentials). Except some cookies and maybe one spyware thing it found nothing else.

-checked RAM again with guidelines mentioned in RAM memtesting guide (each slot tested with each ram stick)

-reseated all cables (had to take out my mobo while I replaced cpu cooling anyway)

-updated my drivers (from here Prezentacja - GA-P55A-UD3 (Rev. 1.0) - P55 - Chipset Socket 1156 - P?yty g?ůwne - GIGABYTE, removed nvidia driver too, updated BIOS)

-I also tested my GPU (both of them) with furmark, no artifacts, temperature seems to be ok.

-tested system with prime95, mostly no problems (had no crashes for 8 hours and 11 hours, had one crash after 3 hours), temperatures seems fine especially after I changed CPU cooling

-My HDD tempretaures right now are 34 C and 38 C, SMARTs are fine I guess, Iíve tested both disks with WD testing tool and some other things couple of months ago, with no problems

-BSODS started around april, since then I have reinstalled my system (Windows 7) 3 times, zeroed both HDD once

-no overclocking (except Gigabyte overclock on GPU, tried lowering that on both cards anyway Ė didnít help)

-reseted CMOS

And it still crashes. Usually while I play games (mostly World of Warcraft and BF4 recently), but I just had 2 BSODS while I tried to write this post (without doing anything special, nothing tough in background).

I have my onboard audio disabled right now (it was mentioned as solution to some BF4 crashing problems). Even before I disabled it, sometimes I was losing sound in Windows7 and I had to restart Windows Aduio service manually to regain it (Iím using Logitech G930 headset, itís USB plugged and wireless), mostly happened when I was using Teampeak3.

Iím suspecting motherboard, though I donít have any reasons to suspect it (Iíve got no other ideas and no real tools to test it). I have be quiet! Silent PSU & Cooling for your PC, but I donít have an amperometer and knowledge to test it thouroughly. I donít have money to change mobo anyway since Iíve spent savings on GPU and cooling.

Iím providing a winrared folder from SFtool, I hope its fine.

I hope guys you can help me, since Iíve got no clue whats wrong.
My System SpecsSystem Spec
04 Dec 2013   #7
nommy the first

Microsoft Windows 8.1 64-bit Professional
 
 

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
My System SpecsSystem Spec
04 Dec 2013   #8
x BlueRobot

 

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

Probably caused by : memory_corruption
Code:
3: kd> !chkimg -f !win32k
Warning: Any detected errors will be fixed to what we expect!
3664 errors (fixed): !win32k (fffff960000f2001-fffff960000f2fff)
Now, I can disassemble the function better with the uf command, since before it would give me this:

Code:
3: kd> uf win32k!xxxHkCallHook
Flow analysis was incomplete, some code may be missing
Code:
3: kd> .cxr 0xfffff88008500e50
rax=0000000000000000 rbx=fffff900c0813480 rcx=fffff900c0813480
rdx=0000000000000000 rsi=0000000000000000 rdi=fffff900c1ffd400
rip=fffff960000f2ad4 rsp=fffff88008501838 rbp=fffff88008501ca0
 r8=0000000000000001  r9=fffff88008501b68 r10=fffff88008501b68
r11=0000000000000003 r12=0000000000000001 r13=fffff88008501b68
r14=0000000000000308 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
win32k!xxxHkCallHook:
fffff960`000f2ad4 48895c2410      mov     qword ptr [rsp+10h],rbx ss:0018:fffff880`08501848=????????????????
The hook is most likely used here for debugging purposes.

Code:
3: kd> 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 15:51:33 2013 (528F7D85)
    CheckSum:         00C9BED4
    ImageSize:        00CEE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please update your AMD graphics card driver to the latest WHQL version.

Quote:
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.

There a couple reasons it could have caused a access violation here, wrong privilege levels, invalid memory address (NULL or non-canonical) or alignment faults.

Code:
3: kd> uf win32k!xxxHkCallHook
win32k!xxxHkCallHook:
fffff960`000f2ad4 48895c2410      mov     qword ptr [rsp+10h],rbx
fffff960`000f2ad9 4889742418      mov     qword ptr [rsp+18h],rsi 
fffff960`000f2ade 57              push    rdi
fffff960`000f2adf 4154            push    r12
fffff960`000f2ae1 4155            push    r13
fffff960`000f2ae3 4156            push    r14
fffff960`000f2ae5 4157            push    r15
fffff960`000f2ae7 4883ec60        sub     rsp,60h
fffff960`000f2aeb 498bf1          mov     rsi,r9
fffff960`000f2aee 4d8bf0          mov     r14,r8
fffff960`000f2af1 448bca          mov     r9d,edx
fffff960`000f2af4 488bf9          mov     rdi,rcx
fffff960`000f2af7 4c8b6938        mov     r13,qword ptr [rcx+38h]
fffff960`000f2afb 33db            xor     ebx,ebx
fffff960`000f2afd 4c3beb          cmp     r13,rbx
fffff960`000f2b00 0f841c060000    je      win32k!xxxHkCallHook+0x64e (fffff960`000f3122)
Code:
win32k!xxxHkCallHook+0x64e:
fffff960`000f3122 33c0            xor     eax,eax
My System SpecsSystem Spec
04 Dec 2013   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by x BlueRobot View Post

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

Quote:
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.
My System SpecsSystem Spec
04 Dec 2013   #10
spl313

Microsoft Windows 7 Ultimate 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

So far I followed everything Nommy said

-uninstalled Ashampoo
-installed and ran Microsoft Essential scan, no viruses
-downgraded to 13.10

So far I've been playing BF4 for last 4-5 hours with no BSOD, only around 10-15 game crashes but I believe it's because game is just terribly bugged and not optimised. I'm not yet sure BSODs stopped because of things you suggested, I used to have no BSODS for even 2-3 days.

I'm going to stick with these drivers for a while, unless I'll get BSOD. I'd be suprised if this is matter of this driver - I had those BSODS before I updated to 13.11.

I'm going to play WoW this evening (that caused most of crashes) and will update if any BSOD happens.
My System SpecsSystem Spec
Reply

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




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Getting BSODs from playing games, browsing the web, etc.
Hi, I have been getting BSODs the last 2 days from doing random things such as just browsing the internet (I was trying to google some of the stop codes, and I blue screened one time, go figure) to playing games on my computer. I custom built my PC 3 months ago, and I recently installed a new...
BSOD Help and Support
Random BSODs while playing games, videos, browsing etc
Hi, I seem to have random BSODs happen rather frequently and pointing to different issues. Any help on this issue would be much appreciated. Attached are the dump files. (Wasn't able to use the grab all in SF Diagnostic Tool, had to manually select all to get it to work. Mgadiag and CPUZ...
BSOD Help and Support
Random BSODs while playing games and browsing
Just recently started getting BSOD every time I try to do pretty much anything. I've had them while playing Civ 5, browsing on Chrome, while trying to install various programs. They are slightly random, but they will not happen if the computer is inactive. Thanks in advance for help.
BSOD Help and Support
Frequent BSODs while web browsing and playing video games.
Hello SevenForums, wondering if you could help narrow down an extremely frustrating problem I have been having for quite some time with blue screens. The minidump files are included in the attachment of this post in a zip folder. Please let me know if I need to give you any other information or...
BSOD Help and Support
Multiple BSODS in the last month while playing games, watching movies
In the last month i got 6-7 random BSODS. My system specifications: - x64. - the original installed OS on the system? - YES. - FULL RETAIL - 3 years. - Install date: 11.12.2010 .rar files have been atached. Thank you for what you're doing here!
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 13:51.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App