BSOD at random times

Overclocking
If you are overclocking any hardware, STOP. Reset any changed values back to default.

Virus check

Scan your system with the following:

Kaspersky TDSSKiller - How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)

ESET online scanner - One-time virus scanner free with ESET online scanner

Hard Drive/Storage

Post disk summary using CrystalDiskInfo software: CrystalDiskInfo Standard Edition

• For how to upload a screenshot or file, read here

Make a hard drive test from the hard drive manufacturers website: Hard Drive Diagnostic Procedure

For errors on your Hard drive(s): How to Run Disk Check in Windows 7

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.

System Temperature

Ensure that there are no heat issues, For monitoring heat of the system use Speccy or HWMonitor

BSOD BUGCHECK SUMMARY

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000033d88, a7e00000de5b5867, fffff6fc4002b3c0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

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

1: kd> !analyze -v; !sysinfo cpuspeed; !sysinfo SMBIOS; lmtsmn; q
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000033d88
Arg3: a7e00000de5b5867
Arg4: fffff6fc4002b3c0

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000322dbf6 to fffff80003281c00

STACK_TEXT:  
fffff880`03ed1318 fffff800`0322dbf6 : 00000000`0000001a 00000000`00000403 fffff680`00033d88 a7e00000`de5b5867 : nt!KeBugCheckEx
fffff880`03ed1320 fffff800`032b2e27 : 00000000`00000000 fffff680`00033ff8 fffffa80`086e9060 fffff800`033b5d0e : nt! ?? ::FNODOBFM::`string'+0x3211c
fffff880`03ed14d0 fffff800`0326e3ff : fffffa80`00000000 00000000`06e7bfff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`03ed1690 fffff800`03280e93 : ffffffff`ffffffff fffff880`03ed1960 fffff880`03ed19c8 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`03ed1790 fffff800`0327d450 : fffff960`001574b4 00000000`00000001 00000000`00000000 fffff900`c26102e0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`03ed1928 fffff960`001574b4 : 00000000`00000001 00000000`00000000 fffff900`c26102e0 00000000`00000000 : nt!KiServiceLinkage
fffff880`03ed1930 fffff960`0015780c : 00000000`00000000 fffff880`00000000 fffff900`c26102e0 00000000`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`03ed1a80 fffff960`001181ed : 00000000`4f0514f9 fffff900`c26102e0 00000000`000014f9 00000000`00000002 : win32k!bDeleteSurface+0x34
fffff880`03ed1ab0 fffff800`03280e93 : fffffa80`093ac730 00000000`000001a8 fffff880`03ed1ab8 fffffa80`08e11860 : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`03ed1ae0 00000000`75692e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0012e888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75692e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+3c8
fffff960`001574b4 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`00157669)

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dccb

FAILURE_BUCKET_ID:  X64_0x1a_403_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1a_403_win32k!SURFACE::bDeleteSurface+3c8

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

CPUID:        "Intel(R) Core(TM) i5-2550K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3502

If all RAM fails in the same DIMM slot you can't fix it. You would need to replace the motherboard.

Any new dump files generated?