Windows 7 Randomly got a few Blue screens of death

[feebas200]

Hey there,
Well a few weeks ago I recieved a blue screen of death, my computer restarted so I ignored this problem. But it happened a few more times. It happened once today. After I restarted, the pc was stuck loading at the desktop so I had to restart again. Can someone help me resolve this problem please? Thanks in advance. I hope someone helps.

Here are my mini dump files-

 

[Trouble]

A couple votes for memory corruption and one memory management indicating ready boost as a problem.

BugCheck 1000007E, {ffffffffc0000005, fffff800036f738d, fffff88002df6518, fffff88002df5d80}
[U][B]Probably caused by : memory_corruption[/B][/U] ( nt!MiGetNextNode+31 )
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800036f738d, The address that the exception occurred at
Arg3: fffff88002df6518, Exception Record Address
Arg4: fffff88002df5d80, Context Record Address

BugCheck 1000007E, {ffffffffc0000005, fffff800036ba38d, fffff88002de15c8, fffff88002de0e30}
[U][B]Probably caused by : memory_corruption[/B][/U] ( nt!MiGetNextNode+31 )
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800036ba38d, The address that the exception occurred at
Arg3: fffff88002de15c8, Exception Record Address
Arg4: fffff88002de0e30, Context Record Address

BugCheck 1A, {1236, fffffa8006cd3a70, fffffa8006cd3ab0, 1d3bc9}
[U][B]Probably caused by : rdyboost.sys[/B][/U] ( rdyboost!ST_STORE<SMD_TRAITS>::StReleaseRegion+4e )
[U][B]MEMORY_MANAGEMENT (1a)[/B][/U]
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000001236, The subtype of the bugcheck.
Arg2: fffffa8006cd3a70
Arg3: fffffa8006cd3ab0
Arg4: 00000000001d3bc9

You need to either update / upgrade, or uninstall or rename the following two drivers
usbVM31b.sys 9/19/2005 Vimicro Products but everything there looks pretty old
and
wanatw64.sys 4/11/2005 very old AOL (America On Line) driver. Seriously....
Update your video card driver from here Drivers - GeForce
Update your audio card driver from here Link Removed
Update your network adapter driver from here Link Removed
Uninstall McAfee completely using the programs own uninstaller or else the programs and features applet in the control panel and follow that up with the vendor specific proprietary removal tool from here Link Removed and replace it with MSE from here Link Removed due to 404 Error
Consider updating to Service Pack 1 for Windows 7

UPDATE READINESS TOOL.
Download and install the correct system readiness tool prior to installing SP1.
Link Removed
Link Removed

If Blue Screens persist then:
First make sure your machine is configured properly to facilitate the collection of .dmp files.

Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.

Then:
Please read the first post in this sticky thread here Link Removed
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Additionally, if you haven’t already, please take some time and fill out your system specs in your forum profile area Link Removed .
Good luck
Randy