Windows 7: BSOD Randomly at idle and using

Ok been getting the dreaded BSOD randomly over past few weeks. started off mostly when comp was idle but increasing even more. Ive tried changing paging size since i was told from friend that could be the problem but didnt solve anything. Ive just recently wiped the comp completely with a fresh install and still getting the BSOD. Ive ran driver checkers and checked all my drivers are up to date to no avail. So now im out of ideas and need some pro tech help from you guys

couple of problem reports i caught:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA80009CAB60
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 2057

Additional information about the problem:
BCCode: 34
BCP1: 0000000000050853
BCP2: FFFFF88003185738
BCP3: FFFFF88003184F90
BCP4: FFFFF8000E6EB1A9
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1



OS Windows 7 Pro x64
CPU intel Core i5-2500k CPU @ 3.30GHz
Motherboard Asus Sabretooth p67
Memory Corsair Vengeance DDR3 (4x4096GB)
Graphics Card Palit NVIDIA GeForce GTX560Ti
Hard Drives Corsair Force Series 3 60GB SSD Samsung Spinpoint 1.0TB

Quick update the iusb3 drivers have just been installed for those looking at the reports.

just ran memory test using Windows 7 tool and came back with:

The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer.

Ive read this tool can give false results? Is this true and where should i go from here?

Pulled each ram stick 1 by 1 and tested. 4/4 one tested returned no problems (always the last 1 you try hey?) anyway going to run it for a while to see then get back in day or to with results. Fingers crossed

PC has been running perfect now. Pushed to extremes yesterday running multiple games at once and left it running throughout the night also so marking this as solved.

Good to know you solved it on your own