Computer Crashing Help

Mrsyankster · 06 Jan 2014

Computer Crashing
I removed the GFI folder and is still crashing any help would be great !!

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: GATEWA, Intel Corporation, D915GAG
CPU: GenuineIntel Intel(R) Pentium(R) 4 CPU 3.80GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 2942193664 total
VM: 2147352576, free: 1949016064

Crash Dump Analysis
</B>
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 1/7/2014 1:19:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010614-28468-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F)
Bugcheck code: 0xA (0x2000010, 0x2, 0x0, 0xFFFFFFFF832FF0B5)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.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 Tue 1/7/2014 1:19:01 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7)
Bugcheck code: 0xA (0x2000010, 0x2, 0x0, 0xFFFFFFFF832FF0B5)
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.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL

On Sun 1/5/2014 4:26:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010514-31500-01.dmp
This was probably caused by the following module: sbfw.sys (SbFw+0x7CB1)
Bugcheck code: 0xC5 (0x6CCC, 0x2, 0x0, 0xFFFFFFFF8333B7FF)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\drivers\sbfw.sys
product: GFI Firewall SDK
company: GFI Software
description: GFI Firewall SDK TDI Firewall Driver
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.
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: sbfw.sys (GFI Firewall SDK TDI Firewall Driver, GFI Software).
Google query: GFI Software DRIVER_CORRUPTED_EXPOOL

On Wed 12/11/2013 9:23:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121113-48265-01.dmp
This was probably caused by the following module: tunnel.sys (tunnel+0xA251)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF807FFBFC, 0xFFFFFFFF807FF7E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\tunnel.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Tunnel Interface Driver
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 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 Wed 12/11/2013 9:23:49 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0x0, 0xFFFFFFFF807FFBFC, 0xFFFFFFFF807FF7E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

On Mon 12/9/2013 8:37:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120913-54171-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x1483)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF9115B483, 0xFFFFFFFF8078AE88, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
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 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 Thu 12/5/2013 11:44:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120513-31609-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDEBFC)
Bugcheck code: 0xC2 (0x99, 0xFFFFFFFFE0EE0008, 0x0, 0x0)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
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 Mon 12/2/2013 5:15:40 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120213-29750-01.dmp
This was probably caused by the following module: srv.sys (srv+0x15BD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFB7A515BD, 0xFFFFFFFF8CD1FB88, 0xFFFFFFFF8CD1F760)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\srv.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Server driver
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 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 Mon 12/2/2013 3:46:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120113-28921-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x110A)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 Fri 11/29/2013 3:50:37 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112913-66953-01.dmp
This was probably caused by the following module: rdyboost.sys (rdyboost+0xBC0C)
Bugcheck code: 0xD1 (0x69646D55, 0x2, 0x0, 0xFFFFFFFF8AF40C0C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rdyboost.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ReadyBoost 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.

matts6887 · 06 Jan 2014

check out this link: it might help to resolve the issue

What is ntkrnlpa.exe?

also this:

http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

Did you add any new hardware or ram recently? Because if so; your dump files seem to be pointing towards faulty hardware and or ram. Try taking all of your ram out with the system off; then one by one put them back in and see if you get to a point where you start to get these errors again. If you do get to that point; then it could very well be the ram module itself and or the ram slot that is faulty. Also; one of the errors appears to point towards a program that may not have installed correctly. So you might want to try re installing any programs you may have installed recently as well.

frequent BSOD mostly ntkrpamp.exe

Mrsyankster · 06 Jan 2014

yes I did put in more memory but it was a few months ago . How do you fix and find faulty hardware Iam adding another file.

Mrsyankster · 07 Jan 2014

I took out the memory sticks and the two new ones I bought were different so I left them out and left the two I had before in I will try that for a while Thanks .