Solved BSOD , System_Service_Exception, 0x0000003b

[Ninebreaker]

Hi

Recently my pc has been BSOD quit frequently for the past week all with the same bug check code i have a feeling that it is a hardware fault either RAM or Motherboard slot related and will begin a mem test check once i can burn a cd to boot , i was wondering if someone could take a look at the minidump's and confirm this or if it is however unlikely a software issue.

System

Windows 7 64 bit home home premium

AMD Phenom II x6 Processor 3.2ghz

12GB RAM DDR3 1600Mhz 9-9-9-24

Geforce 580 GTX

 

[Arc]

Hi Ninebreaker.

fffff880`0ac24fe8  fffff880`06717c3bUnable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS[/COLOR]
 aswSnx+0x27c3b

Uninstall Avast using Avast Uninstall Utility. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Download, install and update those, and then run full system scans with both of them, one by one.

Also

fffff880`0ac24228  fffff880`140b7d5f*** WARNING: Unable to verify timestamp for nvlddmkm.sys
[COLOR=Red]*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys[/COLOR]
 nvlddmkm+0x269d5f

Install the latest NVIDIA DRIVERS 314.22WHQL.

• 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 Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960002b1a2d, fffff8800ac25150, 0}

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

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

4: 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: fffff960002b1a2d, Address of the instruction which caused the bugcheck
Arg3: fffff8800ac25150, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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`002b1a2d 4c8b98300d0000  mov     r11,qword ptr [rax+0D30h]

CONTEXT:  fffff8800ac25150 -- (.cxr 0xfffff8800ac25150;r)
rax=0000000000000000 rbx=fffff900c0b63100 rcx=fffffa800ce35d70
rdx=00000000c0000080 rsi=fffff900c40c2ce8 rdi=fffff900c0b63198
rip=fffff960002b1a2d rsp=fffff8800ac25b20 rbp=0000000007122f0b
 r8=0000000007122f0b  r9=0000001400000025 r10=0000000000000000
r11=fffff8800ac25b48 r12=fffff900c0127010 r13=00000000c0000080
r14=0000000003d37d50 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`002b1a2d 4c8b98300d0000  mov     r11,qword ptr [rax+0D30h] ds:002b:00000000`00000d30=????????????????
Last set context:
rax=0000000000000000 rbx=fffff900c0b63100 rcx=fffffa800ce35d70
rdx=00000000c0000080 rsi=fffff900c40c2ce8 rdi=fffff900c0b63198
rip=fffff960002b1a2d rsp=fffff8800ac25b20 rbp=0000000007122f0b
 r8=0000000007122f0b  r9=0000001400000025 r10=0000000000000000
r11=fffff8800ac25b48 r12=fffff900c0127010 r13=00000000c0000080
r14=0000000003d37d50 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`002b1a2d 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 fffff9600025c46d to fffff960002b1a2d

STACK_TEXT:  
fffff880`0ac25b20 fffff960`0025c46d : 00000000`00000000 00000000`07122f0b 00000000`0220f930 fffff8a0`04453000 : win32k!MulAssociateSharedSurface+0x15
fffff880`0ac25b50 fffff960`0027f83d : 00000000`00000001 fffff880`0ac25ca0 00000000`0220f930 00000000`0000ac35 : win32k!GreSetRedirectionSurfaceSignaling+0x125
fffff880`0ac25ba0 fffff800`032cf293 : fffffa80`0e6919d0 fffffa80`0e68def0 00000000`00000000 fffffa80`0e68def0 : win32k!NtGdiHLSurfSetInformation+0x209
fffff880`0ac25c20 000007fe`fda94efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0220f868 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fda94efa


FOLLOWUP_IP: 
win32k!MulAssociateSharedSurface+15
fffff960`002b1a2d 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:  5006f2b7

IMAGE_VERSION:  6.1.7600.17073

STACK_COMMAND:  .cxr 0xfffff8800ac25150 ; 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
---------

 

[Ninebreaker]

Hi arc

Thanks for the reply sorry it has taken so long to get back to you but after following your advice for the graphics drivers the problem apeers to have been solved i will keep an eye on my system for a few more days incase it surfaces again.

 

[Arc]

Good news mate

Let us know for any further issue.