Får Bluescreen HJÄLP!!!

Hej!
Jag har fått bluescreen flera gånger sedan jag byggt min egna dator och undrade om någon här kunde hjälpa mig förstå vad felet är.

Datorspecifikationer:

Windows 7 Home Premium (64-bit)
Intel Core i5-4670K CPU 3.40 GHz
RAM 8,00 GB
NVIDIA GeForce GTX 760

Bluescreen:

IRQL_NOT_LESS_OR_EQUAL

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select advanced sartup options, and then select safe mode.

Technical information:

*** STOP: 0x0000000A (0x000015B00294A360, 0x0000000000000002, 0x0000000000000002, xFFFFF80002EA6150)

Tack på förhand!

Jag har gjort det och dom verkar sitta bra.

Jag har kollat efter uppdateringar på dom från device manager, dom verkade vara up to date. Jag har inte testat Memtest86+ men ska göra det.

Detta hittade jag:

On Mon 2014-03-10 20:27:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031014-22838-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x293003B4E770, 0x2, 0x1, 0xFFFFF80002EEE150)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 2014-03-10 20:27:10 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x293003B4E770, 0x2, 0x1, 0xFFFFF80002EEE150)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Mon 2014-03-10 19:36:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031014-15896-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x19 (0x22, 0x7700000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

Jag har laddat ner drivrutinerna igen från deras respektive hemsidor, jag ska vänta och kolla om det händer igen. Om det gör så kommer jag testa du skrev.

Jag laddade ner alla drivrutinerna igen från deras hemsidor och nu verkar det ha slutat med bluescreen. På två dagar har jag inte fått någon bluescreen, tror det är fixat.

Tack så mycket för era snabba och hjälpsamma svar.

Det hade fixat sig för typ 5 dagar, men nu fick jag bluescreen igen igår, jag han inte se vad koden var, men verkade samma. Kunde dock varit 0x0000000a0 istället för 0x00000000a. (nollorna är ungefära)