Windows 10 BSOD SYSTEM_SERVICE_EXCEPTION and IRQL_NOT_LESS_OR_EQUAL

[Harib0x]

Hi, since a few weeks, I keep having some BSOD with either Error: SYSTEM_SERVICE_EXCEPTION or Error: IRQL_NOT_LESS_OR_EQUAL.

Here are the descriptions from "Who Crashed":

On Thu 29/10/2015 12:37:17 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102915-35031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8013152BB45, 0xFFFFD001CCA277E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Thu 29/10/2015 12:37:17 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: 0x3B (0xC000001D, 0xFFFFF8013152BB45, 0xFFFFD001CCA277E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sun 25/10/2015 13:31:01 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102515-62015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF801F6AFBBA8, 0xFFFFD00020621590, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Sun 25/10/2015 11:39:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\102515-40437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2E0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF8009B65A9C3)
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.


I'm also attaching the dump files of the BSOD.

Thank you for any help you could provide.

 

[kemical]

Oh you wrote 'Seatools' Henk... I misread and took it as chkdsk. Yes it is perhaps a good idea at some point but as you can see we kinda got the culprit. (hopefully)

 

[HenkB]

One by one, easy does it!

 

[Harib0x]

I am running 4 ram stick.

 

[kemical]

Did you buy them as a kit? What i mean is RAM is usually sold in packs of 2 or 4 and are matched in the factory so don't be tempted to buy individual sticks.

 

[Harib0x]

There were already 2 in the PC when I bought it and i bought another pack of 2 afterwards.

 

[kemical]

Ok understood. You could always test the matched pairs individually meaning test the original pair together and then the newly bought pair or are you just gonna buy 4 new sticks?

 

[Harib0x]

Well, I bought the new pair a few months ago, and the BSOD started not so long after (I never had any BSOD before) so I'm pretty sure that it is coming from these 2 sticks, so I'm just going to buy a new pair.

 

[kemical]

Well best of luck with it all. If you get any other issues pop back..

 

[Harib0x]

Thanks for all your help !
I don't think that I'll have the time to change the pair any soon, but I'll let you know how it went and if the BSOD stopped.

 

[kemical]

Your welcome and hope all goes well with the new hardware. I wouldn't leave the faulty RAM installed tho as you don't really want to be blue screening.