BSOD twice in 24 hr period could be several things

Hi hunttom.

The crash dump is not saying anything precisely. Though a stop 0x3B is usually either a failing device driver (mostly graphics driver) or failing memory. So ......

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.
_______________________________________________________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960000eec6c, fffff8800913e070, 0}

Probably caused by : win32k.sys ( win32k!GetClassInfoEx+114 )

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: fffff960000eec6c, Address of the instruction which caused the bugcheck
Arg3: fffff8800913e070, 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!GetClassInfoEx+114
fffff960`000eec6c 488b00          mov     rax,qword ptr [rax]

CONTEXT:  fffff8800913e070 -- (.cxr 0xfffff8800913e070)
rax=7ffff900c00bef40 rbx=fffff900c06d59c0 rcx=0000000000000400
rdx=fffff900c06ccc60 rsi=000000006f8c0000 rdi=fffff8800913eb30
rip=fffff960000eec6c rsp=fffff8800913ea50 rbp=0000000077920000
 r8=000000006f8c0000  r9=000000000000c30c r10=0000000000000000
r11=000000000000c30c r12=fffff900c21cfc20 r13=fffff8800913eb08
r14=0000000000000000 r15=0000000003e1e670
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
win32k!GetClassInfoEx+0x114:
fffff960`000eec6c 488b00          mov     rax,qword ptr [rax] ds:002b:7ffff900`c00bef40=????????????????
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 fffff960000eef74 to fffff960000eec6c

STACK_TEXT:  
fffff880`0913ea50 fffff960`000eef74 : 00000000`00000000 fffff880`0913eca0 00000000`03e1e660 fffff900`c1c36360 : win32k!GetClassInfoEx+0x114
fffff880`0913ea90 fffff800`03079e53 : 00000000`6f8c0000 fffffa80`131cea00 00000000`03e1e628 00000000`00007f00 : win32k!NtUserGetClassInfoEx+0x230
fffff880`0913ebb0 00000000`7418096a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`03e1e608 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7418096a


FOLLOWUP_IP: 
win32k!GetClassInfoEx+114
fffff960`000eec6c 488b00          mov     rax,qword ptr [rax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!GetClassInfoEx+114

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52705fba

STACK_COMMAND:  .cxr 0xfffff8800913e070 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!GetClassInfoEx+114

BUCKET_ID:  X64_0x3B_win32k!GetClassInfoEx+114

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

Good news :)

Let us know for any further issue.

The CCC (Catalyst Control Center) does cause many issues. It's best if you can live without it and use only the display driver.