BSOD While browsing internet or playing games.

The crash dumps are indicating to memory malfunctioning.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

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

Let us know the result. If possible, a camera snap of the memtest86+ window before closing teh program would be great.
______________________________________________

Code:

BugCheck 1A, {41790, fffffa8008dcf720, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::Map+175 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8008dcf720
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  GFExperience.e

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff800030e6810 to fffff800030768c0

STACK_TEXT:  
fffff880`08db5238 fffff800`030e6810 : 00000000`0000001a 00000000`00041790 fffffa80`08dcf720 00000000`0000ffff : nt!KeBugCheckEx
fffff880`08db5240 fffff800`030aa1b9 : 00000000`00000000 00000000`19ffefff 00000189`00000000 0000018a`000001c7 : nt! ?? ::FNODOBFM::`string'+0x338a4
fffff880`08db5400 fffff800`0338eb71 : fffffa80`118e0650 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`08db5520 fffff960`000e69e5 : 00000000`00000001 fffffa80`102b8c90 fffff900`00000001 fffff960`00262200 : nt!MiUnmapViewOfSection+0x1b1
fffff880`08db55e0 fffff960`000e7d3f : 00000000`00000000 fffff880`08db56c8 fffffa80`102b8bf0 fffffa80`10272b50 : win32k!SURFACE::Map+0x175
fffff880`08db5630 fffff960`00213c31 : 00000000`00000000 fffffa80`102b8bf0 fffffa80`10272b50 00000000`00000003 : win32k!SURFREFVIEW::bMap+0x1b
fffff880`08db5660 fffff960`0016a782 : fffff900`c012c010 00000000`00040206 fffff900`000001b4 0000024c`000002f5 : win32k!GrePtInSprite+0x1cd
fffff880`08db5740 fffff960`000c8faa : 0000024c`000002f5 0000024c`000002f5 00000000`00000000 fffff900`c06086a0 : win32k!DCESpeedHitTest+0x1a6
fffff880`08db57b0 fffff960`0012fdc4 : 00000000`00000000 ffffffff`00000000 0000024c`000002f5 fffff900`00000002 : win32k!zzzSetFMouseMoved+0x72
fffff880`08db5920 fffff960`000f64f8 : 00000000`00000000 fffff960`00323fd0 00000000`00000004 00000000`00000003 : win32k!ProcessQueuedMouseEvents+0x288
fffff880`08db59b0 fffff960`0008593c : fffffa80`0000007b 00000000`0000000f fffff880`00000003 ffffffff`80000324 : win32k!RawInputThread+0x878
fffff880`08db5a80 fffff960`00106f9a : fffffa80`00000002 fffff880`08d99e00 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`08db5ab0 fffff800`03075b53 : fffffa80`10bfc470 00000000`00000004 000007ff`fffd3000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`08db5ae0 000007fe`fd231eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02b1ff58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd231eea


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::Map+175
fffff960`000e69e5 8b4574          mov     eax,dword ptr [rbp+74h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!SURFACE::Map+175

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  556356ff

IMAGE_VERSION:  6.1.7601.18869

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::Map+175

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::Map+175

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_win32k!surface::map+175

FAILURE_ID_HASH:  {c85ac33e-3c48-6d1f-a616-7578ed6b05b9}

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

Now follow the "Part 3: If You Have Errors:" of How to Test and Diagnose RAM Issues with Memtest86+

Errors/red lines means one or more RAM is faulty. But the fault may occur due to a faulty DIMM slot, too, which is a motherboard component. Using memtest86+, you can discriminate between a faulty RAM and a faulty motherboard.

How? Say you have two RAM sticks and two DIMM slots. You obtained errors at the test with all RAM sticks installed. Now, remove all the sticks but one. Test it in all the available slots, one by one. Continue the same procedure for all the available sticks.
How to make the inference that is it a RAM issue or it is a motherboard issue? Suppose you have got the result like that:

No code has to be inserted here.

It is a RAM, a bad RAM.

But if you have got a result like that:

No code has to be inserted here.

It is a motherboard issue. The particular slot is bad.

If it is a bad RAM, you need to change the RAM. Take the other existing (good) RAM to the shop and get one of the exactly same specification. The best is, get a totally new RAM KIT.

If it is a bad slot, it is a motherboard issue. But changing the motherboard needs a preparation for most of us; so dont populate that slot for the time being.

Welcome. :)