Initially I would have suspected memory and even though you have run memtest86 this is no guarantee it isn't memory , to quote since windows 95
Microsoft have stated about memory testing programs
Defective memory chips may not be detected by memory checking tools. Some memory checking programs are not adequate tests because they do not test RAM in the same way that Windows uses RAM. Most memory checkers use read/write cycles when scanning memory. Since Windows is executing code from memory, it uses execute cycles. Execute cycles are different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.
however your crash BAD_POOL_CALLER (c2)
is often caused by drivers which have an invalid memory reference in them somewhere ?
named as the faulting module in your crash is
NETw5s64.sys NETw5s64.sys+e805 fffff880`05870000 fffff880`05f1d000 0x006ad000 0x4aafedb7 15/09/2009 20:40:39
which is your intel network driver and needs updating ?
also these drivers mostly pre-dating windows 7 release
are out of date and need updating ? ssport.sys
SSPORT.sys fffff880`084e2000 fffff880`084ea000 0x00008000 0x42fbda34 12/08/2005 00:07:32
mdmxsdk.sys fffff880`04871000 fffff880`04875280 0x00004280 0x449716be 19/06/2006 22:27:26
Tppwr64v.sys fffff880`03cb2000 fffff880`03cb8000 0x00006000 0x4535e875 18/10/2006 09:40:21
rimspx64.sys fffff880`05f9d000 fffff880`05fb4000 0x00017000 0x46a886a0 26/07/2007 12:33:52
rixdpx64.sys fffff880`05800000 fffff880`05857000 0x00057000 0x46a9ccde 27/07/2007 11:45:50
rimmpx64.sys fffff880`05f88000 fffff880`05f9d000 0x00015000 0x47bcd2c3 21/02/2008 02:24:19
smiifx64.sys fffff880`03f15000 fffff880`03f1c000 0x00007000 0x48280759 12/05/2008 10:01:13
psadd.sys fffff880`0512c000 fffff880`05139000 0x0000d000 0x48a3f2fa 14/08/2008 09:55:22
e1y60x64.sys fffff880`04a00000 fffff880`04a50000 0x00050000 0x48af392e 22/08/2008 23:09:50
000.fcl fffff880`08504000 fffff880`0852f000 0x0002b000 0x48dcdf7a 26/09/2008 14:11:22
is a Port Contention Driver from Samsung Electronics mdmxsdk.sys
- Conexant Modem Diagnostic Interface DRIVER which if not in use should be unninstalled and disabled in your bios ? Tppwr64v.sys
- Lenovo TrackPoint driver rimspx64.sys
ricoh card dreader rixdpx64.sys
ricoh card dreader rimmpx64.sys
ricoh card dreader smiifx64.sys
- SMI Driver for Lenovo system psadd.sys
- lenovo SMI driver e1y60x64.sys
- Intel Gigabit Network Connection NDIS 6 deserialized driver 000.fcl
is possibly a CyberLink FCL Driver or My Book Device Driver by Cyberlink Corp
most of those drivers can be found by going to lenovo support
and downloading the most current versions ?
also can you tell us what antivirus and or third party firewall you are using ?
let us know how it goes