Hello,
Not long ago, I buy Notebook Lenovo R500 NP75URT. In additional I add 2Gb RAM (DDR3, 1066).
After some time, I power on my notebook and I see BSOD with 7F stop code. After research with my colleague we achive to conclusion, that network dirvers works incorrectly 
(( I check update center lenovo and windows update and it's not have new versions of drivers. Therefore, I think that's bug (( Can you help me?
Following I write windbg result:
Opened log file 'C:\Temp\debuglog.txt'
0: kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
Expanded Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/downloads/symbols
0: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..................................................
..................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
**************************************************
*
* Bugcheck Analysis *
*
**************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffffa60012de904
Debugging Details:
------------------
