[Wosmack]

Hello all,

I am a first time poster here. I have been having extreme BSOD problems with my PC. Sometimes I can play a game (currently Assassin's Creed Brotherhood) for hours, sometimes for half an hour, but I will always get kicked out and get the BSOD with the BCCode 1E. I have zipped up my last minidump files for your enjoyment. Bluescreenviewer says tcpisys and ntoskrnl.exe may be the problems but who knows. I would really appreciate and help I could get to stop the problem. Not very enjoyable to get cut off right in the middle of something great! I am running Win 7 x64. I have also attached the text from bluescreenviewer:

==================================================
Dump File : 113011-25849-01.dmp
Crash Time : 11/30/2011 7:04:52 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+1719a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\113011-25849-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,040
==================================================

==================================================
Dump File : 112911-23571-01.dmp
Crash Time : 11/29/2011 7:54:01 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112911-23571-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,040
==================================================

==================================================
Dump File : 111911-26972-01.dmp
Crash Time : 11/19/2011 10:39:13 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111911-26972-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,024
==================================================

==================================================
Dump File : 111811-25677-01.dmp
Crash Time : 11/18/2011 11:28:50 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+1719a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111811-25677-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,016
==================================================

==================================================
Dump File : 111811-25038-01.dmp
Crash Time : 11/18/2011 9:32:43 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+1719a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111811-25038-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,000
==================================================

==================================================
Dump File : 111811-25287-01.dmp
Crash Time : 11/18/2011 8:34:32 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111811-25287-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,032
==================================================

==================================================
Dump File : 111111-23852-01.dmp
Crash Time : 11/11/2011 9:38:29 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111111-23852-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,032
==================================================

==================================================
Dump File : 111111-18439-01.dmp
Crash Time : 11/11/2011 11:28:13 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17640 (win7sp1_gdr.110622-1506)
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111111-18439-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,032
==================================================

==================================================
Dump File : 102111-22183-01.dmp
Crash Time : 10/21/2011 9:40:23 PM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+1719a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102111-22183-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 335,032
==================================================

Attached Files

•  Minidump.zip   288.9KB   226 downloads

[Advertisements]

Scroll down to Crash Analysis Tool here and download WhoCrashed.
http://www.resplendence.com/downloads

Now run WhoCrashed. Click the Analyze button and follow the instructions in the report view and upload the results here.

[Akabilk]

Scroll down to Crash Analysis Tool here and download WhoCrashed.
http://www.resplendence.com/downloads

Now run WhoCrashed. Click the Analyze button and follow the instructions in the report view and upload the results here.

[Wosmack]

Scroll down to Crash Analysis Tool here and download WhoCrashed.
http://www.resplendence.com/downloads

Now run WhoCrashed. Click the Analyze button and follow the instructions in the report view and upload the results here.

Thank you for your help! Here are the results:

windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom™ 9950 Quad-Core Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 8588353536 total
VM: 2147352576, free: 1945686016



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Thu 12/1/2011 2:02:59 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\113011-25849-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Thu 12/1/2011 2:02:59 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: cm2793.sys (CM2793+0x783)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\cm2793.sys
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.
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: cm2793.sys .
Google query: cm2793.sys KMODE_EXCEPTION_NOT_HANDLED




On Wed 11/30/2011 2:52:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112911-23571-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Sun 11/20/2011 5:37:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111911-26972-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Sat 11/19/2011 6:26:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-25677-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Sat 11/19/2011 4:30:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-25038-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Fri 11/18/2011 9:05:25 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111811-25287-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Sat 11/12/2011 4:36:34 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111111-23852-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Fri 11/11/2011 5:50:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111111-18439-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.


On Sat 10/22/2011 4:38:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102111-22183-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC10)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 which cannot be identified at this time.



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

10 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:

cm2793.sys

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.

[Akabilk]

cm279.sys. is a USB controller driver and is corrupting ntoskrnl.exe. (part of Windows kernal).
Uninstall this driver and reboot. Find another Driver or if unavailable for this USB device (a game controller pad?). Try a clean install of the software and don't forget to reboot after installation.

another more complete method is in the second post from this thread. http://www.sevenforu...l-annoying.html Just substitute into the advice whatever you are using.

[Wosmack]

I just uninstalled the driver and my gamepad still works. Apparently it was a special driver on Snakebyte's site that FFXIV players use so they can map function buttons? The gamepad controller was the Snakebyte FFXIV Controller that I bought cheap off Amazon so I could play the action style games on PC. I guess I paid the price in other ways! Anyway, if anyone else has this problem, DON'T use the drivers on Snakebyte's site. Just plug in the controller and let it install itself. I just played the game 4 hours with no BSOD! Hopefully this works permanently, if not, I will post again. I will test out the solution more over the coming days.

[Akabilk]

[SingingG]

I too am having a lot of BSOD's and would like assistance please...

Computer is a Gateway ZX4951 Desktop Running Windows 7 Home Premium 64-bit 4GB's of RAM

Here are my "Who Crashed" Analysis Results.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 4/30/2013 5:13:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\043013-19905-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 4/30/2013 5:13:05 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Fri 4/26/2013 9:27:15 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042613-20716-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002FD2C20, 0xFFFFF8800569EE70, 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 4/25/2013 3:57:20 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042513-19999-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x50 (0xFFFFF8A00DBB8D38, 0x1, 0xFFFFF80002FAC1F7, 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 4/17/2013 7:09:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041713-17284-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2D27D)
Bugcheck code: 0xFE (0x6, 0xFFFFFA800410A000, 0x43787254, 0x0)
Error: BUGCODE_USB_DRIVER
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 an error has occurred in a Universal Serial Bus (USB) driver.
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 4/11/2013 5:41:35 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041113-17004-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x4E (0x9A, 0x88906, 0x2, 0x0)
Error: PFN_LIST_CORRUPT
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 page frame number (PFN) list is corrupted.
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 Thu 4/11/2013 10:26:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041113-51683-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8003B9C320, 0xFFFFF00400008080, 0xFFFFF8A0042A3680)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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 Thu 4/11/2013 10:22:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041113-52431-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
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 Tue 4/9/2013 5:33:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040913-16380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x1A (0x5003, 0xFFFFF70001080000, 0x7EF, 0x8B800000F14)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 3/22/2013 5:42:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032213-16395-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0xA (0x108A5092CA, 0x2, 0x1, 0xFFFFF80002C9E5FF)
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 Thu 3/21/2013 9:41:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032113-17706-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C40)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFF85, 0x1, 0xFFFFF80002C8CA08, 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 Thu 3/21/2013 10:24:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\032113-20155-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x4932)
Bugcheck code: 0x19 (0x20, 0xFFFFF8A00DB50A40, 0xFFFFF8A00DB51820, 0x5DE80B0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a pool header is corrupt.
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 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.




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

12 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.


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.



This being a Windows 7 64-bit machine, is there any way to re-install the ntoskrnl.exe file without losing anything that is on the computer?
Any help would be GREATLY appreciated.


Sorry for posting in the wrong place if I may have... I just joined.

[phillpower2]

SingingG

For future reference please do not post inside another members topic as it may lead to your request for help being overlooked, staff and members who assist on the forums will always check out a topic that has not received any replies to see if they are able to help the OP, they may not check a topic that is more than two years old either

Have you checked the Device Manager to see if there are any yellow ! or red Xs shown and possibly against the network device.

Please Run the PCPitstop.com OverDrive Full Tests

Here's how:

You must use your Internet Explorer for this procedure. (doesn't work so well in Firefox or others). If your machine is running Vista or Windows 7, you must Select IE to “Run as Administrator”. After completing PCPitstop OverDrive you can close your IE browser and re-open it Normally so that you are no longer running as administrator.

Go to: http://www.pcpitstop...pit/default.asp
Click on "Free Computer Check-up" listed below PC Pitstop OverDrive
In the User Login - Click on "Sign up FREE!"
You'll need to submit a valid email address and create your own password, then click - Create Account(button)

Now enter your email address and password to Log in, Select - Scan this system Now!(button)
You will then be asked to download an ActiveX component and allow it to install.
It is safe and does not compromise your privacy.
Follow the on-screen prompts to install the ActiveX and to allow the Full Tests to be run on your machine.

The Full Tests take about 2 1/2 - 3 minutes on most machines.
When complete, a Results - Summary - Recommended Fixes will be displayed.

Please post the URL internet address, from your Results, back here into this Topic Thread so that we can review the configuration and present performance levels of your machine.

Note: During the graphics 2D and graphics 3D testing, your screen will display some rapidly moving objects.
If you are sensitive to visual flashing, it may cause dizziness. Therefore, look away from the screen during that portion of the testing.

After reviewing the results we will be more informed and may be able to provide better recommendations for you to work towards improving your machine's performance.

While PCPitstop does offer a variety of Paid Products, the PCPitstop OverDrive testing is FREE. Please ignore the references to Paid Products. We prefer to provide manual solution instructions that you can apply directly to your machine.

Thanks to rshaffer61 for the PCPitstop information

NB: An example of the url that we require and the information that it leads to http://www.pcpitstop.com/betapit/sec.asp?conid=25271813

[SingingG]

I greatly apologize for posting in wrong section... If I knew how to delete and make a new post, I would.

Here is the URL to PC Pitstop Results:
http://www.pcpitstop...?conid=25320035

[phillpower2]

No worries we only wish to ensure that you do not get overlooked

I asked;

Have you checked the Device Manager to see if there are any yellow ! or red Xs shown and possibly against the network device.

Have you checked this out?

While I check your test results can you run DriverMax to see if any updated drivers are suggested http://www.innovativ....com/drivermax/ if any upgrades are suggested before installing them let us know what they are so that we can take a look.

Please note that you can only download 2 drivers a day for free and be sure to uncheck the "install AVG Toolbar" box.

[SingingG]

Yes, no conflicts. However, I do get a notice at times stating that a USB driver was not able to be installed. Strange thing about that is that only keyboard and mouse are USB and I've unplugged them both before and still got message. (This desktop is a touchscreen all in one)

[phillpower2]

Hello SingingG

While checking your test results I noticed the following software entry Playtopus Playtopus 5/3/13
There is a possibility that this is malicious software and so until that it is confirmed that your computer is clean by the staff over on the malware forums we must hold off here, please see below;

I suspect that you have some malware on your computer causing issues that we are not able to solve through means we can use here in the Tech Forums. I suggest you read the 'Start Here' topic found here. With these self-help tools you have a high chance of fixing the problems on your own. If you are still having problems after following Step 3 of the guide, continue with Step 4 and 5 and post in the Malware Forum. If you are unable to run any programs, Please create a topic stating what you have tried so far and that you are unable to run any programs. Also, Please do NOT post the logs in this thread.

If you are still having issues after the malware expert gives you a clean bill of health, Please return to THIS thread and we will pursue other options to help you solve your current problem(s).

Additional guidance;

1: Do not create a topic on the malware forum unless you have a malware issue that you cannot resolve yourself.
2: If you do need to start a topic there provide a link to this thread so that steps that have already been taken can be checked.
3: As the Malware Techs are extremely busy you may not receive an instant reply, if you have waited for three days then post in the Waiting Room http://www.geekstogo...e-waiting-room/ be sure to identify the issue as malware related and provide a link to your malware topic.

The Playtopus issue is well documented on the Internet but I strongly suggest that you entrust the GTG experts to make sure that your computer is safe and not some "quick fix" that is offered elsewhere.

[SingingG]

OK, it reports that 27 of my drivers are out of date...

These are all marked with red "X"

Intel® HD Graphics v.12.100.17.0000 Date 2013-03-18

High Definition Audio Controller v9.011.0.0000. Date 2012-11-16

Intel ® 5 Series /3400 Series Chipset Family PCI Express Root Port 8 - 3500
V. 9.1.9.1003. Date 2013-02-25

Intel® 5 Series/3400 Series Chipset Family SMBus Controller - 3B30
V.16.2.19.7. Date 2013-04-17

Intel® 82801 PCI Bridge - 244E
V. 4.1.1.5. Date 2011-10-20

Intel® Processor DRAM Controller - 0040
V. 9.1.9.1003. Date 2013-02-25

Realtek High Definition Audio
V. 6.0.1.6622. Date 2012-04-24

Realtek PCIe GBE Family Controller
V. 8.013.0314.2013. Date 2013-03-14

HID Keyboard Device
V. 13.7.47.508. Date 2013-03-21

HID-Compliant Device
V. 8.0.0.4 Date 2012-07-31

HID-Compliant Mouse
V.6.1.7600.16385. Date 2013-03-21

Intel® 5 Series/3400 Series Chipset Family USB Enhanced Host Controller 3B3C
V. 9.1.9.1003 Date 2013-02-25

Intel® 5 Series/3400 Series SATA AHCI Controller
V. 9.1.9.1003 Date 2013-02-25

USB Input Device
V. 3.3.0.34. Date 2012-11-10

USB MASS STORAGE Device
V. 6.2.9200.30150. Date 2012-12-21

All the rest have green checkmarks.

Sorry, I was unable copy & paste...

[phillpower2]

The chipset drivers for the MB should always be the first drivers installed as they are responsible for so many functions.

First = Intel® 5 Series/3400 Series Chipset Family SMBus Controller - 3B30
V.16.2.19.7. Date 2013-04-17

As the issue is possibly related to the Network that should also be updated.

Second = Realtek PCIe GBE Family Controller
V. 8.013.0314.2013. Date 2013-03-14

That is as much as I can advise for now but rest assured I will be around once you have had the all clear from the malware staff should you still require assistance with this.

[SingingG]

I have already gone to Gateways support page for these drivers and downloaded and installed latest drivers. However, the Chipset driver install hangs, then after a minute or so, acts like everything installed OK.... I don't know how to determine if in fact they did indeed install...

But I truly do thank you for all of your help. I will keep checking for updated word here in forum.