Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD and system freezing


  • Please log in to reply

#1
narcist

narcist

    New Member

  • Member
  • Pip
  • 3 posts
Hi, my PC is bsod erratically and its driving me mad as i cannot find the problem. Its a custom build, sometimes it will run fine for days, other times it happens 2 or 3 times per day. I have run memtest, and its fine. Tried running prime and it only seems to like 1 stick of ram, i did manage to get it to run 2 sticks overnight with no errors so really not sure if its ram related.
Here is the report from who crashed. I appreciate any help or suggestions to get this fixed. Thank you

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 10/10/2013 02:50:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101013-8470-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFF789BFFD6708, 0x0, 0xFFFFF80003073061, 0x5)
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 Thu 10/10/2013 02:50:11 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: 0x50 (0xFFFFF789BFFD6708, 0x0, 0xFFFFF80003073061, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 Sun 06/10/2013 12:27:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-9001-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0x18, 0x2, 0x0, 0xFFFFF800030E32FA)
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 Sun 06/10/2013 06:38:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100613-10264-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001E7D296)
Bugcheck code: 0xD1 (0xFFFFF300157F0008, 0x2, 0x0, 0xFFFFF88001E7D296)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 05/10/2013 13:50:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100513-10498-01.dmp
This was probably caused by the following module: kneps.sys (kneps+0x1DE9C)
Bugcheck code: 0xD1 (0xFFFFF88003C5A7AC, 0x2, 0x1, 0xFFFFF88004BE7E9C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\kneps.sys
product: Kaspersky™ Anti-Virus ®
company: Kaspersky Lab ZAO
description: KNEPS Power
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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: kneps.sys (KNEPS Power, Kaspersky Lab ZAO).
Google query: Kaspersky Lab ZAO DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Thu 03/10/2013 08:20:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100313-18439-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF80003324BAE, 0x2, 0x0, 0xFFFFF800030B0242)
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 Wed 02/10/2013 19:48:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100213-29281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x109 (0xA3A039D89F24F550, 0xB3B7465EF1A1C4A6, 0xFFFFF80003073051, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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 Wed 02/10/2013 17:29:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100213-28828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x109 (0xA3A039D89DFE96FB, 0xB3B7465EF07B6651, 0xFFFFF800030272B0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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 Wed 02/10/2013 15:12:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100213-32401-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x109 (0xA3A039D89EBD455C, 0xB3B7465EF13A14B2, 0xFFFFF800030A5C50, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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 30/09/2013 06:58:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\093013-8626-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x109 (0xA3A039D8987B8736, 0xB3B7465EEAF8569C, 0xFFFFF80003073000, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
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 kernel has detected critical kernel code or data corruption.
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 Sun 29/09/2013 16:24:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092913-10233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x50 (0xFFFFF7FFFB853BD8, 0x8, 0xFFFFF7FFFB853BD8, 0x2)
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 Sat 28/09/2013 08:52:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092813-12870-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0xA (0xFFFFF8A0156FD212, 0x0, 0x0, 0xFFFFF80003356A40)
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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

kneps.sys (KNEPS Power, Kaspersky Lab ZAO)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

Advertisements


#2
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

kneps.sys (KNEPS Power, Kaspersky Lab ZAO)


This seems to be at least part of your issue.
Have you tried disabling Kaspersky for a bit and see if the problem still happens?
Are you attached to Kaspersky and\or have the paid version that ties you to it for a extended period of time?
When was the last time you checked drivers to make sure everything was up to date?
Is all your Microsoft updates current?
Just for my curiosity please do the following and attach the requested screenshots please.



Download DriverMax and have it scan your system. It will open their website with all the out of date drivers you can update. With the free version you can update only 2 drivers per day so if you have a lot of them it will take a few days to get everything updated. I have been using it for about 4 months now and like it better then any other utility out there for keeping my drivers up to date.
If you want you can post screenshots of all the drivers in the list that need to be updated and I will suggest in what order to get them.
  • 0

#3
narcist

narcist

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
I installed drivermax, few days back. Since doing so updated my wireless usb driver. had a lor more bsod, so rolled back the driver. I'm uninstalling Kaspersky now will update how that goes. Thanks for the reply
  • 0

#4
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
OK thanks for the update. :thumbsup:
  • 0

#5
narcist

narcist

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
Had another BSOD i will copy the latest from who crashed. Any other info you would like?

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 11/10/2013 02:42:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101113-10514-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xC5 (0x8, 0x2, 0x1, 0xFFFFF800031FC147)
Error: DRIVER_CORRUPTED_EXPOOL
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 system attempted to access invalid memory at a process IRQL that was too high.
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 Fri 11/10/2013 02:42:14 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: 0xC5 (0x8, 0x2, 0x1, 0xFFFFF800031FC147)
Error: DRIVER_CORRUPTED_EXPOOL
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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 Fri 11/10/2013 02:00:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101113-11154-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880016B2BB0)
Bugcheck code: 0x109 (0xA3A039D8A250A85B, 0xB3B7465EF4CE8625, 0xFFFFF880016B2BB0, 0x1)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path: C:\Windows\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 6.20 driver
Bug check description: This indicates that the kernel has detected critical kernel code or data corruption.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts

0x000000C5: DRIVER_CORRUPTED_EXPOOL
An attempt occurred to touch invalid memory at a process IRQL that is too high. This is almost always caused by drivers that have corrupted the system pool. If you’ve recently installed any new software, check to see if it’s properly installed; and check for updated drivers on the manufacturer’s web site.


Any new software installed in the last 2 to 3 weeks?
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP