Sign in with
Sign up | Sign in
Your question
Solved

BSOD caused by ntoskrnl.exe / tcpip.sys

Last response: in Windows 7
Share
September 26, 2012 3:47:22 PM

Hi, first of all ive read tons of solutions on the internet and I still have the problem. Following is analysis done by whocrashed. :) 

Quote:
System Information (local)
--------------------------------------------------------------------------------

computer name: ADMIN-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8526381056 total
VM: 2147352576, free: 1928896512



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Wed 9/26/2012 3:10:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-17674-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x2A471)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800168B471, 0xFFFFF880098F7B20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 9/26/2012 3:10:27 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x2A471)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8800168B471, 0xFFFFF880098F7B20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 9/26/2012 3:07:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-17908-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80061F68F0, 0xFFFF, 0x0)
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 which cannot be identified at this time.


On Wed 9/26/2012 7:24:22 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-17316-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xBE (0xFFFFF683FF7EAC00, 0x19B0000082BE1025, 0xFFFFF88009F05080, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
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 Tue 9/25/2012 4:17:04 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-12745-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x31, 0xFFFFFA8008696C50, 0xFFFFF88003B15000, 0xFFFFF8A0080B2C83)
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 which cannot be identified at this time.


On Tue 9/25/2012 4:10:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092612-12854-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800445A1F0, 0xFFFF, 0x0)
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 which cannot be identified at this time.


On Tue 9/25/2012 12:35:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092512-16504-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80061F68F0, 0xFFFF, 0x0)
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 which cannot be identified at this time.


On Tue 9/25/2012 6:27:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092512-16270-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80061F6920, 0xFFFF, 0x0)
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 which cannot be identified at this time.


On Tue 9/25/2012 5:56:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092512-18454-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC5 (0xFFFFFFFFFFFFFFF1, 0x2, 0x0, 0xFFFFF80002E01DD3)
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 which cannot be identified at this time.


On Tue 9/25/2012 4:52:44 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092512-18969-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41284, 0xFFFFF8A01FFE6001, 0x14B70, 0xFFFFF781C0000000)
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 which cannot be identified at this time.


On Mon 9/24/2012 9:19:32 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092412-17737-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80061F68F0, 0xFFFF, 0x0)
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 which cannot be identified at this time.


On Sun 9/23/2012 4:27:06 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092312-19000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF8, 0x0, 0xFFF49E67, 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 which cannot be identified at this time.


On Sat 9/22/2012 4:10:46 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092312-17456-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CC50C5, 0x0, 0xFFFFFFFFFFFFFFFF)
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 9/22/2012 12:46:45 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-20451-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x1DA4A)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600002DA4A, 0xFFFFF88007E5DB60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 9/22/2012 2:48:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092212-21340-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800445A220, 0xFFFF, 0x0)
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 which cannot be identified at this time.



Hoping someone can help me. Thank you! :bounce: 
a b $ Windows 7
September 26, 2012 5:02:21 PM

You can check for bad memory by running memtest86.

Have you reinstalled or uninstalled any drivers? How about reformatting your computer?

Aside from that, what have you tried? When did the problem start? When does the computer crash? What are the specs on your computer?

A crash dump is only so helpful :) 
m
0
l
a b $ Windows 7
September 26, 2012 6:22:33 PM

there is a rootkit going around that infects those files and more, called zeroaccess.rootkit . there is a automated removal tool from symantec. Trojan.Zeroaccess Removal Tool
m
0
l
Related resources
Can't find your answer ? Ask !
September 27, 2012 2:53:36 AM

djscribbles said:
You can check for bad memory by running memtest86.

Have you reinstalled or uninstalled any drivers? How about reformatting your computer?

Aside from that, what have you tried? When did the problem start? When does the computer crash? What are the specs on your computer?

A crash dump is only so helpful :) 


ive read somewhere that wireless adapter always causes BSOD so yeah i tried uninstall and install back(from given CD). i also tried the newer version of the driver but its not working. my wireless adapter is ASUS Wireless USB Adapter N13. i know this adapter is old.. :sweat: 

reformating i havent done it because i dont have the Windows 7 installation CD. the pc is new about a month old but when i bought it, they never give a windows CD.

Not sure when it start crashing..maybe after i messed up the BIOS.. :sweat:  i just set it to "load optimized defaults" and then my pc stuck at "starting windows". Then i tried change the BIOS and finally its working.

ive done memtest86 and there is a lot of red, i mean failing address. but i did not complete the memtest because i needed to use the pc :sweat: 

so what's next? oh almost forgot, the specs.

I5 3470
8gb Value RAM G.Skill 1333
Asus P8B75 M LX
Shinobi White
Gigabyte Powerock 500W
1TB Blue HDD
LG 24x DVDRW
Gigabyte 7850OC
Dell U2312HM
ASUS USB-N13 Adapter Wireless-N

Thx! :) 
m
0
l
September 27, 2012 3:00:08 AM

the great randini said:
there is a rootkit going around that infects those files and more, called zeroaccess.rootkit . there is a automated removal tool from symantec. Trojan.Zeroaccess Removal Tool

i will try that! thnx :D 
m
0
l
September 27, 2012 3:57:16 AM

no infections found..now i will try the memtest again.. :ange: 
m
0
l

Best solution

a b $ Windows 7
September 27, 2012 1:34:01 PM

Looks like RAM: 0x1A: MEMORY_MANAGEMENT, 0x3B: SYSTEM_SERVICE_EXCEPTION, and 0x50: PAGEFAULT_IN_NONPAGED_AREA are three of the BSOD's I'd expect from bad RAM. Run memtest86 for a few passes.
Share
September 28, 2012 3:09:04 PM

ive ran memtest a few times and i get errors..but i dont really understand what to do next. ive contacted the pc seller he asked to change the DRAM timing and RAM speed. i did it but did not run the memtest yet..
m
0
l
October 5, 2012 4:25:44 PM

Best answer selected by croness.
m
0
l
!