Associate
- Joined
- 23 Mar 2012
- Posts
- 473
- Location
- SY4
I'll get straight to the point:
I've just the other day upgraded to an 8gb ram kit and a Plextor 128Gb SSD (full spec in sig) and i'm getting random reboots and the odd BSOD just to add insult to injury.
I ran memtest for just over three hours on the memory - both sticks were tested at the same time - and it didn't find any errors.
I'll post the WhoCrashed stuff below, however, it says that a likely culprit is Kaspersky, which I find hard to believe to be honest. I've been running the latest KIS for the past year nearly and i've had no issue with it at all.
Motherboard is using the latest BIOS and the Plextor has the latest firmware on it. All drivers are up to date, as is Windows itself.
On Wed 14/08/2013 11:07:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-7675-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFC03, 0x1, 0xFFFFF80002C905B0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 14/08/2013 11:07:45 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: klif.sys (klif+0x1BC2E)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFC03, 0x1, 0xFFFFF80002C905B0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\klif.sys
product: Kaspersky™ Anti-Virus ®
company: Kaspersky Lab ZAO
description: Klif Mini-Filter [fre_wlh_x64]
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klif.sys (Klif Mini-Filter [fre_wlh_x64], Kaspersky Lab ZAO).
Google query: Kaspersky Lab ZAO PAGE_FAULT_IN_NONPAGED_AREA
On Mon 12/08/2013 12:14:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081213-10686-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A50F3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002BA80F3, 0xFFFFF88002FA18B8, 0xFFFFF88002FA1110)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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.
I'm gonna leave the memory testing all afternoon just to be sure, but i'd appreciate your thoughts.
I've just the other day upgraded to an 8gb ram kit and a Plextor 128Gb SSD (full spec in sig) and i'm getting random reboots and the odd BSOD just to add insult to injury.
I ran memtest for just over three hours on the memory - both sticks were tested at the same time - and it didn't find any errors.
I'll post the WhoCrashed stuff below, however, it says that a likely culprit is Kaspersky, which I find hard to believe to be honest. I've been running the latest KIS for the past year nearly and i've had no issue with it at all.
Motherboard is using the latest BIOS and the Plextor has the latest firmware on it. All drivers are up to date, as is Windows itself.
On Wed 14/08/2013 11:07:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081413-7675-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFC03, 0x1, 0xFFFFF80002C905B0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 14/08/2013 11:07:45 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: klif.sys (klif+0x1BC2E)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFC03, 0x1, 0xFFFFF80002C905B0, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\klif.sys
product: Kaspersky™ Anti-Virus ®
company: Kaspersky Lab ZAO
description: Klif Mini-Filter [fre_wlh_x64]
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: klif.sys (Klif Mini-Filter [fre_wlh_x64], Kaspersky Lab ZAO).
Google query: Kaspersky Lab ZAO PAGE_FAULT_IN_NONPAGED_AREA
On Mon 12/08/2013 12:14:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081213-10686-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A50F3)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002BA80F3, 0xFFFFF88002FA18B8, 0xFFFFF88002FA1110)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread 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.
I'm gonna leave the memory testing all afternoon just to be sure, but i'd appreciate your thoughts.