Multiple BSOD Messages

[Danut_95_13]

I've been getting BSOD messages since the day I bought this computer.
I am using Windows 10, I also tried Windows 8 but I had the same problem.I realy don't know if this is a hardware or a software problem. The error messages I receive the most are:
KERNEL_SECURITY_CHECK_FAILURE
SYSTEM_SERVICE_EXCEPTION
DRIVER IRQL NOT LESS OR EQUAL
KMODE EXCEPTION NOT HANDLED

After reinstalling windows this is all i got(minidumps):
https://www.dropbox.com/sh/gd5xa6dq113zy61/AAB7e1tWKf50CbSLMsaP-5GLa?dl=0

 

[Colif]

i can't read minidumps but this will give us a look at errors and maybe help while I wait for someone to decode the dumps

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

they are likely to be drivers. We shall see

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pastebin.com/JYy9xbur

Spoiler

File: 073117-4906-01.dmp (Mon Jul 31 06:24:08.660 2017)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)] {c0000005, fffff8020f4c7e18, ffffc300119b41f0, 0}
Probably caused by: memory_corruption (Process: Wow-64.exe)

File: 080117-4328-01.dmp (Tue Aug 1 09:33:16.399 2017)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)] {3, ffff8680b21fa500, ffff8680b21fa458, 0}
Probably caused by: ntkrnlmp.exe (Process: RazerIngameEngine.exe)

File: 080117-4500-01.dmp (Tue Aug 1 09:20:28.891 2017)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)] {3, ffffe7815c75c930, ffffe7815c75c888, 0}
Probably caused by: ntkrnlmp.exe (Process: RazerIngameEngine.exe)

File: 072817-4187-01.dmp (Fri Jul 28 10:43:41.592 2017)
BugCheck: [UNEXPECTED_STORE_EXCEPTION (154)] {ffffb80e2c788000, ffff918085b62780, 1, 0}
Probably caused by: memory_corruption (Process: MemCompression)

File: 073117-4296-01.dmp (Mon Jul 31 14:31:26.823 2017)
BugCheck: [REFERENCE_BY_POINTER (18)] {0, ffffbd82eef20a70, 2, ffffffffffffffff}
Probably caused by: memory_corruption (Process: WmiPrvSE.exe)

I can't help you with this. Wait for someone else to reply. Good luck.

 

[Colif]

try updating razer synapse, rest of the drivers seem fairly new. Synapse is from 2015.

 

[Danut_95_13]

i can't read minidumps but this will give us a look at errors and maybe help while I wait for someone to decode the dumps

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

they are likely to be drivers. We shall see

On Tue 8/1/2017 4:33:16 PM your computer crashed
crash dump file: C:\Windows\Minidump\080117-4328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x139 (0x3, 0xFFFF8680B21FA500, 0xFFFF8680B21FA458, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 8/1/2017 4:20:28 PM your computer crashed
crash dump file: C:\Windows\Minidump\080117-4500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x139 (0x3, 0xFFFFE7815C75C930, 0xFFFFE7815C75C888, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 7/31/2017 9:31:26 PM your computer crashed
crash dump file: C:\Windows\Minidump\073117-4296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x18 (0x0, 0xFFFFBD82EEF20A70, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
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 the reference count of an object is illegal for the current state of the object.
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.



On Mon 7/31/2017 1:24:08 PM your computer crashed
crash dump file: C:\Windows\Minidump\073117-4906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8020F4C7E18, 0xFFFFC300119B41F0, 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 Fri 7/28/2017 5:43:41 PM your computer crashed
crash dump file: C:\Windows\Minidump\072817-4187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0x154 (0xFFFFB80E2C788000, 0xFFFF918085B62780, 0x1, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[Colif]

Try updating Razer drivers, they are from 2015... every other driver is from 2017 so that doesn't mean they aren't cause but half the drivers mentioned are Avast so if you keep getting bsod after updating razer drivers, take avast off until we figure out the cause (others will suggest that idea anyway)

 

[Danut_95_13]

Try updating Razer drivers, they are from 2015... every other driver is from 2017 so that doesn't mean they aren't cause but half the drivers mentioned are Avast so if you keep getting bsod after updating razer drivers, take avast off until we figure out the cause (others will suggest that idea anyway)

I had this problem long before I installed this driver, I do not think he's the problem. But I'll do it.

 

[Colif]

Unexpected Store exception - okay... i have only ever seen this a few times and 3 times in last month, and it can be caused by bad cables on hdd or using wrong sata port on motherboard. Its something to do with the hdd/ssd

what are specs of PC apart from MSI B150M MORTAR Motherboard?

Bug Check 0x18: REFERENCE_BY_POINTER

This indicates that the reference count of an object is illegal for the current state of the object.

The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object, the driver calls a kernel routine to increase the reference count of the object by one. When the driver is done with the pointer, the driver calls another kernel routine to decrease the reference count by one.

Drivers must match calls to the routines that increase (reference) and decrease (dereference) the reference count. This bug check is caused by an inconsistency in the object's reference count. Typically, the inconsistency is caused by a driver that decreases the reference count of an object too many times, making extra calls that dereference the object. This bug check can occur because an object's reference count goes to zero while there are still open handles to the object. It might also occur when the object's reference count drops below zero, whether or not there are open handles to the object.

Reference by pointer is also a fairly rare error, and it too can be software or bad memory. Try running memtest86 on each ram stick, 1 stick at a time. Any errors are too many. Memtest makes a bootable USB so can run it outside windows

 

[Danut_95_13]

Unexpected Store exception - okay... i have only ever seen this a few times and 3 times in last month, and it can be caused by bad cables on hdd or using wrong sata port on motherboard. Its something to do with the hdd/ssd

what are specs of PC apart from MSI B150M MORTAR Motherboard?

Bug Check 0x18: REFERENCE_BY_POINTER

This indicates that the reference count of an object is illegal for the current state of the object.

The reference count of an object is illegal for the current state of the object. Each time a driver uses a pointer to an object, the driver calls a kernel routine to increase the reference count of the object by one. When the driver is done with the pointer, the driver calls another kernel routine to decrease the reference count by one.

Drivers must match calls to the routines that increase (reference) and decrease (dereference) the reference count. This bug check is caused by an inconsistency in the object's reference count. Typically, the inconsistency is caused by a driver that decreases the reference count of an object too many times, making extra calls that dereference the object. This bug check can occur because an object's reference count goes to zero while there are still open handles to the object. It might also occur when the object's reference count drops below zero, whether or not there are open handles to the object.

Reference by pointer is also a fairly rare error, and it too can be software or bad memory. Try running memtest86 on each ram stick, 1 stick at a time. Any errors are too many. Memtest makes a bootable USB so can run it outside windows

MSI NVIDIA GeForce GTX 970, GTX 970 GAMING 4G LE, 4GB GDDR5, 256bit
Procesor INTEL i5 6400, BX80662I56400, 2.7GHz/3.3GHz, 6MB
Hard Disk Drive WESTERN DIGITAL Caviar Blue WD10EZEX, 1000GB, 64MB, SATA 3
ZALMAN ZM500-GLX, 500W, 12cm fan, PCF activ
KINGSTON ValueRAM 8GB DDR4, 2133MHz, CL15, KVR21N15D8/8
Solid-State Disk INTEL 540 120GB, SATA3, SSDSC2KW120H6X1

I tested my RAM using memTEST and got nothing

 

[Colif]

download and run this on ssd: https://downloadcenter.intel.com/download/26837/Intel-Solid-State-Drive-Toolbox - check out smart scores and see if drive is healthy

You can download Data Life Guard for windows from here: https://support.wdc.com/downloads.aspx?lang=en and run short/long tests on the WD drive

can try different data cables on ssd/hdd if you have them.

I am not 100% sure what the cause is at this time, hence testing hardware that might be cause.

 

[Danut_95_13]

download and run this on ssd: https://downloadcenter.intel.com/download/26837/Intel-Solid-State-Drive-Toolbox - check out smart scores and see if drive is healthy

You can download Data Life Guard for windows from here: https://support.wdc.com/downloads.aspx?lang=en and run short/long tests on the WD drive

can try different data cables on ssd/hdd if you have them.

I am not 100% sure what the cause is at this time, hence testing hardware that might be cause.

i tryed a new cable for the SSD, i tested the SSD and HardDisk ( no errors ) multiple stress test , sometimes i got bsod sometimes i didn't , i can't find a pattern for the errors they are completly random.
Got any other suggestions or test to do to find the problem ?

 

[Colif]

can you share the dump files and we see what we can find in them

 

[Danut_95_13]

i can't read minidumps but this will give us a look at errors and maybe help while I wait for someone to decode the dumps

Can you download and run who crashed - it will give us a glimpse of the errors you getting and might help us solve them

Copy/paste summary in here and I see what I can do

they are likely to be drivers. We shall see

can you share the dump files and we see what we can find in them

https://www.dropbox.com/sh/gd5xa6dq113zy61/AAB7e1tWKf50CbSLMsaP-5GLa?dl=0

I don't know if i'm doing this right so i'll also give you this

On Thu 8/17/2017 2:10:38 AM your computer crashed
crash dump file: C:\Windows\Minidump\081717-4578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802184C409D, 0x0, 0x2C)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
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 Wed 8/16/2017 10:49:08 PM your computer crashed
crash dump file: C:\Windows\Minidump\081617-4343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x154 (0xFFFF8D08C05B0000, 0xFFFFE10040457780, 0x1, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 8/16/2017 10:25:32 PM your computer crashed
crash dump file: C:\Windows\Minidump\081617-4390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x154 (0xFFFFC101043E1000, 0xFFFFAD01A9D1E780, 0x1, 0x0)
Error: CUSTOM_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 8/15/2017 5:18:37 PM your computer crashed
crash dump file: C:\Windows\Minidump\081517-4593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x139 (0x3, 0xFFFFB500CED7C7B0, 0xFFFFB500CED7C708, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I changed the Memory with a HyperX Savage 8Gb

 

[Colif]

good old custom error... they should fix that as its not right.
Bug Check 0x154: UNEXPECTED_STORE_EXCEPTION still. Guess we never did work out why you were getting that.

if I were you, I would post a question on the next link as well, new eyes might see what I can't in the dump files. Follow the instructions at top of page here: https://www.tenforums.com/bsod-crashes-debugging/

I will look at the dump files once gardenman does his magic.

 

[gardenman]

Hi, I ran the dump file(s) through the debugger and got the following information: https://pastebin.com/Mr11dMjw

File: 081717-4578-01.dmp (Wed Aug 16 19:10:38 2017)
BugCheck: [KMODE_EXCEPTION_NOT_HANDLED (1E)] {ffffffffc0000005, fffff802184c409d, 0, 2c}
Warning: Unable to verify timestamp for: rzpnk.sys
Probably caused by: rzpnk.sys (Process: RazerIngameEng)

File: 081617-4390-01.dmp (Wed Aug 16 15:25:32 2017)
BugCheck: [UNEXPECTED_STORE_EXCEPTION (154)] {ffffc101043e1000, ffffad01a9d1e780, 1, 0}
Probably caused by: ntkrnlmp.exe (Process: MemCompression)

File: 081517-4593-01.dmp (Tue Aug 15 10:18:37 2017)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)] {3, ffffb500ced7c7b0, ffffb500ced7c708, 0}
Probably caused by: ntkrnlmp.exe (Process: GRW.exe)

File: 081617-4343-01.dmp (Wed Aug 16 15:49:08 2017)
BugCheck: [UNEXPECTED_STORE_EXCEPTION (154)] {ffff8d08c05b0000, ffffe10040457780, 1, 0}
Probably caused by: ntkrnlmp.exe (Process: MemCompression)

I can't help you with this. Wait for someone else to reply. Good luck.

 

[Colif]

top error crashed razer synapse which is different

old driver list -
ndisrfl.sys (Dated Thu Jul 9 2015) -Intel(R) Technology Access Filter Driver - Intel NDIS 6.30. This is related to LAN drivers, I have seen it a lot recently. thing is, you appear to have latest LAN drivers now. And searching for Intel Technology access filter leads you in the wrong direction as it implies its a driver for the sensors in laptops. I figured out that isn't right a few days ago. I have yet to figure out the right answer for this question.

 

[Danut_95_13]

top error crashed razer synapse which is different

old driver list -
ndisrfl.sys (Dated Thu Jul 9 2015) -Intel(R) Technology Access Filter Driver - Intel NDIS 6.30. This is related to LAN drivers, I have seen it a lot recently. thing is, you appear to have latest LAN drivers now. And searching for Intel Technology access filter leads you in the wrong direction as it implies its a driver for the sensors in laptops. I figured out that isn't right a few days ago. I have yet to figure out the right answer for this question.

Thx for trying ,i really appreciate it , i also posted on that forum and waiting for an answer