blue screen trouble

[Twitched74]

Hello Ive had trouble with my computer with blue screens so did a clean re-install of windows everything seemed to be running fine till i tryed to play league of legends or Dragon age
The blue screen was 0x0000000C2 and 0x0000004E

First time posting so any help would be appreciated

Edit,
1 hour after i posted this i reseved another blue screen 0x0000001A
at the time i was just reading on google chrome
after the reset i was unable to use any programs with out it saying an error and closing, google chrome and internet explorer would not work with out instanly crashing

here is the second file

if there is anything else i need to post or more info is needed please tell me

 

[koolkat77]

[FONT="Lucida Console"]
Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\TWITCHED74-PC-11_01_2015__05729_37\011115-27892-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e94890
Debug session time: Sun Jan 11 06:52:57.954 2015 (UTC + 6:00)
System Uptime: 0 days 0:14:13.766
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 1c484c, 2, 1}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001c484c, page frame number
Arg3: 0000000000000002, current page state
Arg4: 0000000000000001, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Origin.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre

LAST_CONTROL_TRANSFER:  from fffff80002d55a4c to fffff80002cc6bc0

STACK_TEXT:  
fffff880`0cce5118 fffff800`02d55a4c : 00000000`0000004e 00000000`00000099 00000000`001c484c 00000000`00000002 : nt!KeBugCheckEx
fffff880`0cce5120 fffff800`02d314c8 : 00000000`29d7f000 fffffa80`05850e10 00000000`00000000 fffff880`0cce53e8 : nt!MiBadShareCount+0x4c
fffff880`0cce5160 fffff800`02fd95ed : fffff980`12b80000 fffff8a0`0b0414b0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2ba87
fffff880`0cce5440 fffff800`02ce967b : 00000000`29d40000 fffffa80`066db660 00000000`00000000 00000000`29e00000 : nt!CcUnmapVacb+0x5d
fffff880`0cce5480 fffff800`02cdc039 : fffff980`00000001 00000000`29600000 fffffa80`0a842e00 fffffa80`066e1b70 : nt!CcUnmapVacbArray+0x1bb
fffff880`0cce5510 fffff800`02fb0fb2 : 00000000`00000000 00000000`29e00000 fffff880`0cce55e0 fffff880`0cce5670 : nt!CcGetVirtualAddress+0x38a
fffff880`0cce55a0 fffff880`012cfdbf : fffff880`00000000 00000000`00000005 fffffa80`0a66eb50 fffffa80`00100001 : nt!CcCopyRead+0x132
fffff880`0cce5660 fffff880`01104098 : fffffa80`07ceaf20 fffffa80`0a66eae8 00000000`00000001 fffffa80`07ceaf01 : Ntfs!NtfsCopyReadA+0x18f
fffff880`0cce5840 fffff880`011078ba : fffff880`0cce5910 00000000`15240003 00000000`15240000 fffffa80`07ceaf00 : fltmgr!FltpPerformFastIoCall+0x88
fffff880`0cce58a0 fffff880`01125630 : fffffa80`07ceaf20 00000000`00000000 fffff880`0cce5a00 00000000`00100000 : fltmgr!FltpPassThroughFastIo+0xda
fffff880`0cce58e0 fffff800`02fb0b39 : fffffa80`07ceaf20 fffffa80`00000001 fffffa80`06743640 fffffa80`07ceaf20 : fltmgr!FltpFastIoRead+0x1d0
fffff880`0cce5980 fffff800`02cc5e53 : 00000000`74af2450 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x417
fffff880`0cce5a70 00000000`74af2e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`12a9ef38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74af2e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiBadShareCount+4c
fffff800`02d55a4c cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_VERSION:  6.1.7601.18409

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x4e_99_nt!mibadsharecount+4c

FAILURE_ID_HASH:  {4c83cdad-f603-74ff-b7e1-9eb7f3029c2a}

Followup: MachineOwner
---------
[/FONT]

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.