BSOD Memory_Management usually during games (dumps/info included)

I've started having a massive number of BSODs, many back-to-back. It usually happens when i play guild wars 2 and league of legends, though it may also occur during other games, i just don't play other games atm. This also happens when watching videos or twitch. I have been having a lot of issues with Shockwave Flash crashing, as well. I've recently had all my applications close with an error saying "out of memory". I have researched that and done the windows "fix me" for it. Unsure if that fixed it or not. I'm hoping these are all related.

I have opened my laptop (clevo x7200 from 3 years ago made by origin) and cleaned it out and reapplied thermal paste. I have checked all hardware components and removed and put back in the cmos battery. I have tested each ram stick in each slot (3 sticks, 3 slots) and started the laptop with each to verify if they work.

I have also recently seen an error that almost made me believe my computer was dead. It said something like "NFS.sys" or "NTS.sys" or something was the error and upon restarting, claimed windows could not restart. After it running a windows error application and failing, i restarted the computer and it began working again.

The included files are all my BSODs and also my computer specs. Any help would be absolutely amazing! I have tried a recommended route of Driver Verifier (found at this link: Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community). I originally posted this on the official windows forum and received some help, but nothing to correct the issue. Upon trying the above link route, i could not get the dump file that was expected. There was no new dump to point out the driver which may be causing the issue. I wish i could do this and find the issue, but i can't seem to get the program to run correctly. I am at a loss.

Hello and welcome Andro sorry for the wait - mate can't open those RAR files mate it is much easier to use these tutorials to send dump files follow them and send back then we can get going on them.
Dump Files - Configure Windows to Create on BSOD
&
Blue Screen of Death (BSOD) Posting Instructions

Ok that's fine for those mate who can open those types of zip file but I don't have the capacity on mine because it means downloading not to mention paying for software to undo them.

Anyway give it a little time and someone who is better off than I am will take a look.:)

Sorry Andro mate I must have you mixed up with someone else but I am sure the first lot of files was a RAR zip which like I said I cannot access.

However the logs are now being loaded from your first post and as soon as I can I shall take a look - I shouldn't be long - have to go out for a just a while.
John

Ok mate sorry late reply - have not been well most of the day now the dumps

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa800d967df0
Arg3: 000000000000ffff
Arg4: 0000000000000000
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_41790
CUSTOMER_CRASH_COUNT:  2
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  opera_autoupda
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff80003942810 to fffff800038d28c0
STACK_TEXT:  
fffff880`15bbb828 fffff800`03942810 : 00000000`0000001a 00000000`00041790 fffffa80`0d967df0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`15bbb830 fffff800`039061b9 : fffff880`00000000 00000000`028bffff 00000000`00000000 fffff880`00961000 : nt! ?? ::FNODOBFM::`string'+0x338a4
fffff880`15bbb9f0 fffff800`03beab71 : fffffa80`135ea8a0 00000000`00000000 fffffa80`18142950 fffffa80`18142950 : nt!MiRemoveMappedView+0xd9
fffff880`15bbbb10 fffff800`03beaf7f : 0000007f`00000000 00000000`027b0000 fffffa80`00000001 00000000`0009e601 : nt!MiUnmapViewOfSection+0x1b1
fffff880`15bbbbd0 fffff800`038d1b53 : 00000000`00000000 00000000`02870018 fffffa80`13749b10 00000000`0064f2bc : nt!NtUnmapViewOfSection+0x5f
fffff880`15bbbc20 00000000`7724de5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0009dd28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7724de5a
 
STACK_COMMAND:  kb
FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+338a4
fffff800`03942810 cc              int     3
SYMBOL_STACK_INDEX:  1
SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+338a4
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  556356e8
IMAGE_VERSION:  6.1.7601.18869
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+338a4
BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+338a4
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_nt!_??_::fnodobfm::_string_+338a4
FAILURE_ID_HASH:  {b7b6e799-20a2-a8ed-3529-d30731685de0}
Followup: MachineOwner

Two things stick out here one is an issue with some Windows updates and the top one smacks of the RAM not being right. Your problem devices (see pic) I am not sure of what that top one is all about but the Centrino result may be a faulty processor. see pic

Bit to start with I think it best to go with this for starters being an obvious one to me

MEMTEST

The memtest you will needto make a bootable disk / stick and set the BIOS to boot from the optical orUSBand it will take a fair time to run- some leave it overnight.

This is the currentversion http://www.memtest.org/ pleaseuse this as any other test is useless - the Windows one sadly is not worth evena thought about.

But one thing is veryimportant you must let the test run for at least 8 passes any less and the findings are no good. Now if errors come upstraight away then you can stop it - see my pics. Now if there are errors andyou have more than one stick of RAM in then you will need to test each stick ieremove the sticks and replace stick 1 in slot 1 and test no errors do thesame in slot 2 with stick 1 no errors then repeat the process with stick 2 -that will show up the faulty stick - the other thing is it could be a faultyslot but most unusual. With more than two sticks the process is even longer asone may realize.

It is a very lengthy andtedious process but worth it if you have errors.
I have added pics to show what is what and one that will describe the errors for the sequences of passes which must run for at least 8 passes - any less and you may as well not do the test. Having said that if errors come up straight away then you can stop the scan and it is just a matter of tracking down the stick or slot - more commonly the stick though.
Before you start that do this

SLOTCLEANING

Now as for the slots to clean them use a strip of old credit card(or any card thin enough some are better than others ) about 1/2 inch wide nipthe corners off one end - preferably round them offhold apiece of thin lint free cloth over the end dab on some form of alcohol -isopropyl alcohol (what we swab the skin with before an injection) is good and GENTLY swipe along the slots.

This can also be done for the GPU slot/s and also the contacts of thesticks or cards - not the stick but some lint free cloth of course. See my picfor the sick but please be very gentle doing it if you are in any doubt -please ask before doing it but I use this all the time and have yet to damageanything

Ok sorry late reply mate just got up the Opera I would not worry too much about it is the Memory corruption and those references to updates that are more of an issue.
Now regarding the memtest I don't know how those people tested the memory so I cannot say for definite if the memory is ok or not. There are several RAM tests and to be honest the one I linked is the only one we ever use - the Windows feature and others you can find are just really not worth the effort - in fact the effort in some is minimal to say the least.

So if it were me I would go memtest first tedious as it is and then if no errors are found then try some system restores to figure out which updates are causing any problems - again can be tedious but not as much so as the memtest.
Now I see you have a lot of RAM on board so my suggestion would be to test the machine with whole four sticks in.
If you get errors then to find the bad stick/s / slots (and mark them as such) stick #1 in slot #1 for those 8 passes - then stick #1 in slot #2 then slot#3 and so forth until all sticks have been tested through all slots .
Very time consuming but you might just get lucky if you have a memory issue get errors come up quite quickly - then you can stop the testing for that particular stick and / or slot.
Lets get that out of the way first - if there are no errors with that first run with all sticks is then there is no problem.

Don't forget too the graphics card also has memory but lets do the obvious first.