BSOD happens randomly on laptop toshiba

Hi all sorry to trouble you i am having a problem has happened a few times but manage to catch this 1
any help would be great please
im running a toshiba satellite pro L450D
specs are
2gig amd sempron SI-42
4 GB ( NEW RAM)
500gig hd
ati 3200 HD graphics
windows 7 ultimate 64 bit


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC000001D
BCP2: FFFFF80002A7C449
BCP3: FFFFF880009BB888
BCP4: FFFFF880009BB0E0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\042013-20108-01.dmp
C:\Users\Chris\AppData\Local\Temp\WER-41511-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt



edited due to i needed 2 upload a file sorry
sorry didnt read rules proper

Blue Screen of Death (BSOD) Posting Instructions

Please follow what's asked in this quote:

Dave76 said:

Can you download CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Go to your BIOS and tell us what the CPU, RAM and the CPU integrated memory controller voltages (QPI/DRAM core voltage) are set at.

• 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. RAM - Test 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, before going to bed.

• Use the System File Checker tool (SFC.exe) to determine which file is causing the issue, and then replace the file. Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 . The sfc /scannow command scans all protected system files and replaces incorrect versions with correct Microsoft versions. SFC /SCANNOW Command - System File Checker

• Post a screen shot using Crystal Disk Info: CrystalDiskInfo Standard Edition
  How to Upload and Post a Screenshot and File in Seven Forums

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

• Run disk check for errors on your Hard Drive(s) Disk Check

• For monitoring heat of the system, use Speccy or HWMonitor:

Speccy System Information
HWMonitor

System Optimisers

Please remove the following software:

Code:

Start Menu\Programs\TuneUp Utilities 2011	Public:Start Menu\Programs\TuneUp Utilities 2011	Public
Start Menu\Programs\TuneUp Utilities 2011\All functions	Public:Start Menu\Programs\TuneUp Utilities 2011\All functions	Public

This software is a known cause of BSOD's. The windows 7 operating system does not require these registry cleaning software. They often tune-down rather than tune-up and can wreck the OS beyond repair. Microsoft have improved Windows 7 significantly and it is much better at organising and optimising itself than its predecessors. Check this, this and this thread for evidence.

If you feel the need to use a registry cleaning or optimisation software, most of us recommend the use of CCleaner - PC Optimization and Cleaning - Free Download but make sure you back up the registry before making letting ccleaner delete anything.

• 10 Tips on How to Properly Maintain Your Computer

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

Code:

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat Apr 20 19:19:39.221 2013 (UTC + 6:00)
System Uptime: 0 days 0:03:33.453
BugCheck 1000007E, {ffffffffc000001d, fffff80002a7c449, fffff880009bb888, fffff880009bb0e0}
*** WARNING: Unable to verify checksum for win32k.sys
empty
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sat Apr 20 04:47:07.776 2013 (UTC + 6:00)
System Uptime: 0 days 1:06:13.008
BugCheck 19, {3, fffff88000800440, fffff88000800440, a8f201}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Fri Apr 19 13:48:36.781 2013 (UTC + 6:00)
System Uptime: 0 days 0:07:42.012
BugCheck 1000007E, {ffffffffc000001d, fffff80002a7c449, fffff880009bb888, fffff880009bb0e0}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x7E
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Thu Apr 18 07:19:40.780 2013 (UTC + 6:00)
System Uptime: 0 days 0:02:00.012
BugCheck 109, {a3a039d89584575a, b3b7465ee80126b0, fffff80002ab638c, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Apr 16 03:44:57.158 2013 (UTC + 6:00)
System Uptime: 0 days 1:39:50.390
BugCheck 109, {a3a039d8997eb524, b3b7465eebfb847a, fffff80002a7c330, 1}
*** WARNING: Unable to verify checksum for win32k.sys
empty
Probably caused by : memory_corruption
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Tue Apr 16 02:04:34.635 2013 (UTC + 6:00)
System Uptime: 0 days 4:54:31.867
BugCheck 1A, {8886, fffffa80005b9ef0, fffffa80005ba430, 200}
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+19c )
BUGCHECK_STR:  0x1a_8886
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

mcfc

Have you updated your Ethernet and wireless drivers ?

Did you download the drivers from the Toshiba website or from the NIC and wireless manufacture's website Realtek ?

toshiba i just got the wireless driver now from realtek tryin 2 find the other driver from them

Both drivers updated