first crash was really corrupted and could not be used.
the second crash looks like a bug in a device driver. this is only a guess but you have a very large number of bluetooth drivers on your system, I would disable them (or the ones you can) and see if your system starts working.
btath_a2dp.sys Mon Jan 21 01:42:31 2013
btath_avdt.sys Mon Jan 21 01:19:11 2013
btath_bus.sys Mon Jan 21 01:18:42 2013
btath_flt.sys Mon Jan 21 01:42:22 2013
btath_hcrp.sys Tue Dec 18 01:54:54 2012
btath_lwflt.sys Thu Nov 01 22:35:44 2012
btath_rcp.sys Tue Dec 18 01:54:50 2012
btfilter.sys Mon Jan 21 01:19:45 2013
BthEnum.sys Tue Jan 08 19:58:34 2013
BthLEEnum.sys Wed Jul 25 19:25:02 2012
bthpan.sys Wed Jul 25 19:23:42 2012
bthport.sys Thu Feb 28 20:55:37 2013
BTHUSB.sys Tue Jan 08 19:59:16 2013
you might also want to look for a updated file for
LhdX64.sys Mon Jan 11 07:06:58 2010
- just based on the date it is pretty old. it is a lenovo developed disk driver and a bug in it would explain why the last
crash dump could not be read by the windows debugger. it is very old, look for a update from lenovo.
- you have a few other files to look at but that is a start.
-you may also be able to find proper updates for the drivers.
basically, there is a bug in a driver that is corrupting low level areas of windows memory reserved memory area.
you might also want to confirm that your actual physical memory is good by running memtest86.
- you have had many bugchecks, you will want to confirm that your files have not become corrupted because of them.
run cmd.exe as a admin (windows key +x+ type A)
run the system file checker
sfc.exe /scannow <- this will check the microsoft core files for corruption and fix them if it can.
if the tool finds corruption that it can not fix, then you run the dism.exe command
dism.exe /online /cleanup-image /restorehealth
this command will check for corruption of core windows files and get new ones from a trusted online source to fix any corrupted versions. (useful if a virus corrupts the hidden backup copy of the file)