Random BSODs while playing/browsing/watching

[carltoN1s]

The past few weeks I've been noticing my BSODs have been happening more frequently, it ranges from playing a game and alt-tabbing, to watching Youtube videos and changing tabs. It's never happened while I've done anything non-intensive such as Microsoft Word, or things similar. I've updated my drivers within the past month, but can't remember if I blue-screened before that. I also changed my SSD to AHCI from IDE last week and transferred my desktop to my secondary drive(ran out of SSD space); I also can't remember if it happened more frequently before/after that. I've watched my temps with Realtemp, and nothing is overheating.

Specs:
OS - Windows 7 Ultimate 64-bit
CPU - i5-2500k
Mobo - Gigabyte Z77-D3M
GPU - Gigabyte HD6850
Ram - G. Skill Ripjaw 2x4gb
SSD - Samsung 830
HDD - WD 200GB Sata
(Sorry, don't have the Info on the BSOD, other than it's a LocaleID:1033, forgot to copy it before closing, and didn't want to wait for another BSOD since I don't know when it's going to happen.

 

[Arc]

Hi carltoN1s.

All your recent BSODs are stop 0x3B. Most common for a not-up-to-date system; and equally frequently caused by a malfunctioning display driver.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Uninstall your installed 13.12 WHQL version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

Accept all the offered restarts during the entire process.

Let us know the results.
________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff9600026c9ed, fffff8800c8c8100, 0}

Probably caused by : win32k.sys ( win32k!MulAssociateSharedSurface+15 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff9600026c9ed, Address of the instruction which caused the bugcheck
Arg3: fffff8800c8c8100, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


OVERLAPPED_MODULE: Address regions for 'ksaud' and 'ksaud.sys' overlap

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
win32k!MulAssociateSharedSurface+15
fffff960`0026c9ed 4c8b98300d0000  mov     r11,qword ptr [rax+0D30h]

CONTEXT:  fffff8800c8c8100 -- (.cxr 0xfffff8800c8c8100;r)
rax=0000000000000000 rbx=fffff900c38c2350 rcx=fffffa8008213b00
rdx=00000000c0003840 rsi=fffff900c51e2028 rdi=fffff900c38c23e8
rip=fffff9600026c9ed rsp=fffff8800c8c8ae0 rbp=ffffffffb1122195
 r8=ffffffffb1122195  r9=0000001b000000a0 r10=0000000000000000
r11=fffff8800c8c8b08 r12=fffff900c0134010 r13=00000000c0003840
r14=0000000006cbd2e0 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!MulAssociateSharedSurface+0x15:
fffff960`0026c9ed 4c8b98300d0000  mov     r11,qword ptr [rax+0D30h] ds:002b:00000000`00000d30=????????????????
Last set context:
rax=0000000000000000 rbx=fffff900c38c2350 rcx=fffffa8008213b00
rdx=00000000c0003840 rsi=fffff900c51e2028 rdi=fffff900c38c23e8
rip=fffff9600026c9ed rsp=fffff8800c8c8ae0 rbp=ffffffffb1122195
 r8=ffffffffb1122195  r9=0000001b000000a0 r10=0000000000000000
r11=fffff8800c8c8b08 r12=fffff900c0134010 r13=00000000c0003840
r14=0000000006cbd2e0 r15=0000000000000001
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
win32k!MulAssociateSharedSurface+0x15:
fffff960`0026c9ed 4c8b98300d0000  mov     r11,qword ptr [rax+0D30h] ds:002b:00000000`00000d30=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff960002177bd to fffff9600026c9ed

STACK_TEXT:  
fffff880`0c8c8ae0 fffff960`002177bd : 00000000`00000000 ffffffff`b1122195 00000000`021ff730 fffff8a0`0076d000 : win32k!MulAssociateSharedSurface+0x15
fffff880`0c8c8b10 fffff960`0023a969 : 00000000`00000001 fffff880`0c8c8c60 00000000`021ff730 00000000`0000a18b : win32k!GreSetRedirectionSurfaceSignaling+0x125
fffff880`0c8c8b60 fffff800`02287153 : fffffa80`09f22060 fffffa80`09492060 00000000`0031100b fffffa80`09492060 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880`0c8c8be0 000007fe`fe1a4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`021ff668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe1a4efa


FOLLOWUP_IP: 
win32k!MulAssociateSharedSurface+15
fffff960`0026c9ed 4c8b98300d0000  mov     r11,qword ptr [rax+0D30h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!MulAssociateSharedSurface+15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

IMAGE_VERSION:  6.1.7600.16385

STACK_COMMAND:  .cxr 0xfffff8800c8c8100 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!MulAssociateSharedSurface+15

BUCKET_ID:  X64_0x3B_win32k!MulAssociateSharedSurface+15

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_win32k!mulassociatesharedsurface+15

FAILURE_ID_HASH:  {08b97eea-ad52-6762-8e6c-277f3c48177d}

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