all of a sudden bluescreen- let me tell you what i've tried so far to no avail

Thanks for the info .I did what you said & here is the results.So what now ?

System Information (local)
--------------------------------------------------------------------------------

computer name: STEVE-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 965 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4293058560 total
VM: 2147352576, free: 1962283008




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 5/31/2014 3:58:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-27658-01.dmp
uptime: 00:06:41
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800032E5972, 0xFFFFF88009339F50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 5/31/2014 3:58:05 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 00:06:41
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF800032E5972, 0xFFFFF88009339F50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 5/31/2014 3:50:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-27799-02.dmp
uptime: 00:35:14
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 5/31/2014 3:14:03 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-27783-01.dmp
uptime: 00:48:39
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF800035AE90D)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 5/31/2014 2:24:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-29125-01.dmp
uptime: 01:02:25
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x5, 0x2, 0x1, 0xFFFFF80003281291)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 5/31/2014 1:20:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-28423-01.dmp
uptime: 00:27:56
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003406E83)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 5/31/2014 12:51:51 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\053114-29749-01.dmp
uptime: 00:15:29
This was probably caused by the following module: afd.sys (afd!AfdQueueWorkItem+0x74)
Bugcheck code: 0xE4 (0x1, 0xFFFFFA8004E3FD00, 0xFFFFF80003571220, 0x0)
Error: WORKER_INVALID
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

7 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

I don't understand? The link says to install all updates and do a system restore ? What is it you would have me do.By the way , i am new to this kinda stuff so please have a little patience
I also got a new screen:

Conclusion
________________________________________

5 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

dxgmms1.sys (DirectX Graphics MMS, Microsoft Corporation)
luafv.sys (LUA File Virtualization Filter Driver, Microsoft Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.