IRQL BSOD after installing videocard

[Kokito55]

I bought a second hand gtx 770.

The PC starts fine and runs about 5 minutes then i get IRQL not less or equal, I installed the videocard drivers in safe mode(it works fine in safe mode //i think//) but the same thing happens.

It runs fine without the card.

 

small detail: because my usual monitor doesn't have a hdmi slot(pc was connected via VGA cable pre-gpu), and I don't have a DVI cable at the moment i just connected the videocard to my tv via hdmi. Don't know if that's relevant.

[Arcanekitten]

Did you first uninstall the previous drivers with DDU? also BSOD's can be a one time occurrence.  

[Kokito55]

3 minutes ago, Arcanekitten said:

Did you first uninstall the previous drivers with DDU? also BSOD's can be a one time occurrence.  

Previous drivers were to the integrated gpu, does it matter? It happened about 5 times consistently

[Syncrosys]

Hi @Kokito55

 

If you can get in to windows, can you run this? http://www.resplendence.com/whocrashed

 

Copy and paste the error you might get. If there's more than one, paste it all.

 

Thanks!

 

 

[Kokito55]

4 hours ago, Syncrosys said:

Hi @Kokito55

 

If you can get in to windows, can you run this? http://www.resplendence.com/whocrashed

 

Copy and paste the error you might get. If there's more than one, paste it all.

 

Thanks!

 

 

Sure 

Here it is:
On Sat 6/10/2017 1:38:44 AM your computer crashed
crash dump file: C:\Windows\Minidump\061017-19718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F440)
Bugcheck code: 0xA (0xFFFF80001B036FC0, 0x2, 0x0, 0xFFFFF80002F316DF)
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 Sat 6/10/2017 1:38:44 AM 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 (0xFFFF80001B036FC0, 0x2, 0x0, 0xFFFFF80002F316DF)
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 Sat 6/10/2017 1:25:34 AM your computer crashed
crash dump file: C:\Windows\Minidump\061017-18454-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F440)
Bugcheck code: 0xA (0xFFFFFA801A6DC370, 0x2, 0x1, 0xFFFFF80002F46666)
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 Sat 6/10/2017 1:17:11 AM your computer crashed
crash dump file: C:\Windows\Minidump\061017-18860-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F440)
Bugcheck code: 0xA (0xFFFF80001B037500, 0x2, 0x0, 0xFFFFF80002F716DF)
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 Sat 6/10/2017 1:11:38 AM your computer crashed
crash dump file: C:\Windows\Minidump\061017-22900-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F440)
Bugcheck code: 0xA (0xFFFFFA801A743370, 0x2, 0x1, 0xFFFFF80002F88666)
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.




 

[Syncrosys]

@Kokito55

 

That's what I thought you'd have for an error. Unfortunately, this is one of the more difficult BSOD to diagnose. Basically this is happening because windows is hitting a part of the memory that it cant access. Not the GTX 760's memory, but the RAM. But the error could be related in the sense that the new card is putting a load on the system, so the issue could ALSO not be the memory. So this could be a CPU error, it could also be the motherboard's chip set bogging down when in use. And if that wasn't vague enough, this could all be due to the voltage to the part causing the issue. So it could in fact be your PSU.

 

So... in a perfect world where everyone has access to test parts... here is what I would do:

 

1) Test a known good power supply(note down results)

2) Test with known good RAM stick(s)(note down results)

3) Try your Ram in another known good working computer and see if the issue persists

4) Test video card in another computer that has a similar or more powerfull video card

 

Of course... you might not be able to perform those tests. And it is frustrating. But its a good place to start, short of taking it to your local computer shop and paying them to do it.

 

I wish I could do it for you since I'm sitting on spare parts... I'm sure you can find a friend or an acquaintance that has some of those though.

 

Good luck, and let me know your findings.