BSOD randomly

Hello, s00ther and welcome to the forums. you stated you attached the last minidump, do you have more/ If so, run the BSOD posting instructions again and don't edit the file. Please send everything with it.

Your dump said

Code:

 
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
 
Probably caused by : Netwsw02.sys ( Netwsw02+16087 )

Netwsw02.sys is your Intel® Wireless WiFi Link Adapter If it is part of the Laptop, please try to update it from the Lenovo web site for your laptop. Your current driver is not that old.

Code:

 Netwsw02
start             end                 module name
fffff880`08456000 fffff880`087c9000   Netwsw02 T (no symbols)           
    Loaded symbol image file: Netwsw02.sys
    Image path: \SystemRoot\system32\DRIVERS\Netwsw02.sys
    Image name: Netwsw02.sys
    Timestamp:        Mon Mar 23 04:04:01 2015 (550FD701)
    CheckSum:         00353B66
    ImageSize:        00373000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Also, please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Let us know about the other dump files and the scan as well as how your laptop performs after doing that.