Third BSOD today, otherwise at least weekly if not daily

craigpc said:

I've attempted to fix this ongoing problem to no avail.

I am running Windows 7 Enterprise x64

The BSODs are relatively random from a user perspective, but have been happening for a while now (past 30 days). They had become pretty infrequent, but now are again a daily occurrance.

I've attached the info as described in your BSOD How-To and have filled in the System Specs as best as I am able.

Any technical insights would be much appreciated.

- Craig

Hi craigpc welcome to SF :)
This crash was caused by cng.sys (Kernel Cryptograph).
Since it is an OS file,for first step you should run a SFC /SCANNOW Command - System File Checker to verify and repair OS files.

From your Most Recent BSOD

   Information

SYSTEM_SERVICE_EXCEPTION - STOP 0x3B

Usual causes: System service, Device driver, graphics driver, ?memory

Probably caused by : win32k.sys

   Note

The memory check may take up to 24 Hours to complete

First of all Please run a Full Scan of your Memory and if you are Overclocking any Devices then please reset to factory Clock speed

See - Guide to using Memtest86+ - Geeks to Go Forums

Memtest86+ - Advanced Memory Diagnostic Tool

After that please make sure you Run a System File Checker Scan as panais suggested

Then run a Full Anti-Virus Scan and then post back

For Reference:

Code:

*******************************************************************************
*                                                                             *
*                        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: fffff960001d565f, Address of the instruction which caused the bugcheck
Arg3: fffff8800a40db00, 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!xxxDCEWindowHitTest+6b
fffff960`001d565f ff4308          inc     dword ptr [rbx+8]

CONTEXT:  fffff8800a40db00 -- (.cxr 0xfffff8800a40db00)
rax=fffff900c06443d0 rbx=f7fff900c0644240 rcx=fffff900c06443d0
rdx=0000000000000200 rsi=0000000000000001 rdi=0000000000000000
rip=fffff960001d565f rsp=fffff8800a40e4e0 rbp=fffff8800a40e730
 r8=0000000000000000  r9=0000000002220416 r10=0000022200000416
r11=fffff8800a40e4d8 r12=0000000002220416 r13=0000000000000000
r14=0000000000000200 r15=0000000002220416
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
win32k!xxxDCEWindowHitTest+0x6b:
fffff960`001d565f ff4308          inc     dword ptr [rbx+8] ds:002b:f7fff900`c0644248=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  iexplore.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff960001d565f

STACK_TEXT:  


FOLLOWUP_IP: 
win32k!xxxDCEWindowHitTest+6b
fffff960`001d565f ff4308          inc     dword ptr [rbx+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!xxxDCEWindowHitTest+6b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4de066b3

STACK_COMMAND:  .cxr 0xfffff8800a40db00 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxDCEWindowHitTest+6b

BUCKET_ID:  X64_0x3B_win32k!xxxDCEWindowHitTest+6b

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