BSOD Windows 7 Home Premium 64bit_ ntoskrnl.exe ( nt+6f880 )

[sWin7]

Hello, I have just joined the forums and looking for a solution to BSOD issue on my laptop (MSI GT 70).
The laptop came equipped with HDD where initial OS (Windows 7 Home Premium 64 bit OEM) have been installed on the first boot. Then I put in an SSD (crucial m4, latest firmware), moved the system (clean, just msi drivers and utilities supplied with the laptop) to the SSD, computer worked fine for about 7 months, then suddenly or as I suspect right after installation and first run of Malwarebytes started Blue screening, forcing the drive checks on restart and finally stopped booting.
After some unsuccessful system restore attempts I have resorted to a complete OS reinstall.
Now the set up is as follows:
C: SSD OS (windows 7 x64 Home Premium, no Service packs installed)
D: HDD Data, storage drive + Users OS folder (has been moved on fresh OS install using following guide: Move the User Folder To A Separate Drive/Partition (The Right Way) - Idealistically Caspan )
E: SSD most software

However computer still periodically Blue screens though runs fine in Safe mode
Short memory diagnostics showed no errors, extended session froze; I have terminated it and have not run since.

I have tried to run windows update but it would either freeze during update or blue screen, so can not update the OS at present.

I have searched the web for a while now, have also tried installing Windows Debugging Tools on the laptop that has BSOD issues - error on install, so have installed it on a different (stable) computer to check the dump files, however could not pin point the cause of the BSOD.
So far I have not found any solution that worked for me, hence the post.

My course of action as of now:
1. Run memory test (Memtest86+ - Advanced Memory Diagnostic Tool)
2. Install windows 7 SP1 and try windows update, however Microsoft does advice to get the drivers sorted out before SP1 install so I am not sure whether to go for it or use Driver Verifier
3. If SP1 + update does not resolve the problem will use Driver Verifier to try and determine driver issue
Should anyone have other suggestion, please let me know.

Any help would be much appreciated
Thanks in advance

Minidump files are uploaded below

 

[Arc]

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP [/COLOR](8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack Center - Microsoft Windows

Your crash dumps are not showing any finite probable cause.

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 memtest comes to be free from errors, 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.
_____________________________________________________________________________
BSOD ANALYSIS:

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

Use !analyze -v to get detailed debugging information.

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

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+32f36 )

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

0: 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: fffffa80039c3690
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002f4274e to fffff80002ecf880

STACK_TEXT:  
fffff880`0a5a17e8 fffff800`02f4274e : 00000000`0000001a 00000000`00041790 fffffa80`039c3690 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0a5a17f0 fffff800`02f029c9 : 00000000`00000000 000007fe`f7ce1fff fffffa80`00000000 fffffa80`06f40000 : nt! ?? ::FNODOBFM::`string'+0x32f36
fffff880`0a5a19b0 fffff800`031e3e90 : fffffa80`076011c0 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0a5a1ad0 fffff800`031e429b : 00000980`00000000 000007fe`f7c00000 fffffa80`00000001 fffffa80`0d32fc10 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0a5a1b90 fffff800`02ecead3 : 00000000`00000000 000007fe`f7c00000 fffffa80`06f43710 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f
fffff880`0a5a1be0 00000000`76f3f95a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0010aa98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f3f95a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+32f36
fffff800`02f4274e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+32f36

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5147dc36

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+32f36

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+32f36

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

 

[sWin7]

thanks for quick response, I will go through the steps mentioned and post the results as appropriate