• Happy holidays, folks! Thanks to each and every one of you for being part of the Tom's Hardware community!

Blue screen error: tcpip.sys w/ System Service Exception Error

Toggle sidebar Toggle sidebar
T

Technovice_krf

Distinguished
Dec 21, 2011
12
0
18,510
I am having difficulty with drivers on my Acer Aspire 5253 system using Win 7. It is a couple months old. Within the last month, I have been getting random blue screen of death error messages in which the computer shuts down to prevent damage. The computer boots up fine without any problems. The blue screen that I see contains the same information each time:

System_service_exception

Disable the driver or check for updates. Try changing video adapters.

Tech Info:
Stop: 0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF88001996AF2, 0xFFFFF880031E7888, 0xFFFFF880031E70E0)

Tcpip.sys – Address FFFFF88001996AF2 base at FFFFF880118BF000, datestamp 4e83e948


I have sought advice from my computer’s manufacturer, who says that the problem can be resolved with complete system reinstallation. I am trying to avoid this. I have reinstalled the computer drivers (including video and sound), but still I get the blue screen. I have more information on the blue screen error if that would help - it is contained in an attachment.

kf
 
Sort by date Sort by votes

You might try setting up a new network connection.
If that fails, bite the bullet & reinstall as mfgr suggests.
 
Upvote 0 Downvote
No no no
Get a crash analyzer like "Whocrashed" from resplendence software and run it.
It will tell you what the offending piece of software really is and how to fix it.

You are having a system service exception that is causing tcpip.sys to crash. Think of tcpip.sys being the guy that gets caught in "friendly fire"...
 
Upvote 0 Downvote
That's what I thought. That the error is not really with tcpip.sys, but something else that is manifesting as a tcpip.sys error. Problem has been identifying that "something else." I will try the software you mention and report back.
 
Upvote 0 Downvote
I have done that but will do it again. I have Norton AV, so does running a full system scan include the anti-malware scan also? What about blue screen view as alternative to Whocrashed? download.cnet.com/BlueScreenView/3000-2094_4-10965136.html

I had done that before, but that just seemed to isolate the tcpip.sys. I'm running whocrashed now; hopefully that will be much more specific.
 
Upvote 0 Downvote
Ok, pardon the long post, but here are the results from the whocrashed analyzer. I see one or two drivers that I could update, I guess. But nothing more specific regarding the tcpip.sys driver, unless I'm missing something.

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 12/20/2011 5:35:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122011-36161-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD7AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001965AF2, 0xFFFFF8800B1B31B0, 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 12/14/2011 9:40:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121411-34835-01.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x23980)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001929AF2, 0xFFFFF880031F5888, 0xFFFFF880031F50E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall 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.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Fri 12/9/2011 2:01:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-57377-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD7AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880018E9AF2, 0xFFFFF8800A4F91B0, 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 Thu 12/8/2011 9:05:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120811-34585-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD7AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880019D4AF2, 0xFFFFF8800A3031B0, 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 Mon 12/5/2011 11:33:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120511-26052-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD7AF2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001996AF2, 0xFFFFF880031E7888, 0xFFFFF880031E70E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 which cannot be identified at this time.


On Tue 11/29/2011 1:46:38 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112811-32229-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD7AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880019D6AF2, 0xFFFFF880098461B0, 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 Tue 11/29/2011 1:46:38 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD7AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880019D6AF2, 0xFFFFF880098461B0, 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 Tue 11/29/2011 12:03:56 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112811-30966-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD7AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF880019A5AF2, 0xFFFFF8800AEBD1B0, 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 Sun 11/27/2011 5:36:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112711-33134-01.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x23980)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF880018DCAF2, 0xFFFFF880031E0888, 0xFFFFF880031E00E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall 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.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Thu 10/20/2011 5:58:43 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102011-54881-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0xD7AF2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88001936AF2, 0xFFFFF88007F811B0, 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 10/19/2011 12:28:06 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101911-50419-01.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0x23980)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88001980AF2, 0xFFFFF880031F5888, 0xFFFFF880031F50E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall 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.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: mfewfpk.sys McAfee, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Thu 9/22/2011 9:33:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092211-52525-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x18E160)
Bugcheck code: 0xC2 (0x7, 0x109B, 0x4140010, 0xFFFFFA8008BDF500)
Error: BAD_POOL_CALLER
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 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 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 Tue 8/30/2011 12:54:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082911-40154-01.dmp
This was probably caused by the following module: mfehidk01.sys (mfehidk01+0xF809)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88007ACB809, 0xFFFFF880095E2650, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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.
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: mfehidk01.sys .
Google query: mfehidk01.sys SYSTEM_SERVICE_EXCEPTION




On Wed 8/17/2011 4:22:09 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081711-38391-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x6FB8)
Bugcheck code: 0x116 (0xFFFFFA8004333010, 0xFFFFF88002CC7FB8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: atikmpag.sys Advanced Micro Devices, Inc. VIDEO_TDR_ERROR




On Fri 6/3/2011 4:00:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\060311-51449-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5B68)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880098861D8, 0xFFFFF88009885A40, 0xFFFFF8000338C1D0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates a problem occurred in the NTFS file system.
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.



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

16 crash dumps have been found and analyzed. Only 15 are included in this report. 3 third party drivers have 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:

atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.)

mfehidk01.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.
 
Upvote 0 Downvote
Hmm, I'm not sure on Norton, I haven't used their software in quite some time, but I believe it does both in the full scan, but either way you should be fine when it does a full scan.
I haven't used BlueScreenView, but I'm givin' it a look right now =D
 
Upvote 0 Downvote
Ok, after looking at your crash dump, it appears that possibly McAffee firewall is possibly screwing up your TCPip.sys. The only thing is, its happening on different days. Maybe on certain crashes the TCPIP.SYS driver gives up before McAfee crashes. Anyways, I would suspect that because it's in the firewall module of McAfee and that would interact with TCPip.sys alot.
Also, you mentioned that you are running Norton too? If thats the case, you can get rid of McAfee or Norton, you only need the one. I would keep the Norton one lol.

But, I would reinstall McAfee if you intend to keep it.
 
Upvote 0 Downvote
Well, the Whocrashed analyzer gave more specific information that the blue screen view: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.), mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.), and
mfehidk01.sys and potential problems. Now I'm trying to find updates to these drivers, but not having much luck. Anyone familiar with any of these and possible how to update or remove (if that's even a viable option)?
 
Upvote 0 Downvote
The atikmpag.sys is for your video card, more than likely its not the cause of your problems(you said you reinstalled your graphics driver too, so that should be ok as well)
mfewfpk.sys and mfehidk01.sys are part of McAfee's firewall module. Now, that part definately interacts with TCPip.sys, and could cause problems with TCPIP.SYS.

That's why I suggested that you reinstall McAfee. You already have Norton, and windows firewall, so if it were me, I would get rid of McAfee and go with Norton with Windows Firewall if your Norton package don't have the firewall with it.
 
Upvote 0 Downvote
Yes, it was a trial version of McAfee that I got with the laptop. I had no intention of keeping it, but also had difficulty getting rid of it. But, after all this research into bad drivers, I've been hesitant to just casually get rid of it since apparently some drivers and things don't get deleted and can cause problems later on, which apparently it has. But this is the first time I've been able to isolate Mcafee as the possible problem. So, now it's on. Getting rid of everything McAfee is the goal. Any thoughts how to do this without causing more problems? Initial thought is to uninstall through control panel, but will that get rid of the problem drivers?
 
Upvote 0 Downvote
Yes, getting rid of it in control panel -> Programs and Features, should toss the drivers as well, they are part of the McAfee software(not windows).
You will be fine as far as Anti-Virus/Malware is concerned. You have Norton, so you are good there. Your system should be a little faster too because you have two antivirus programs running at the same time and that would cause a resource hog on your hard drive, causing a slow down.
When you uninstall McAfee, windows should or automatically restart it's own builtin firewall as well.
 
Upvote 0 Downvote
So I've tried to uninstall McAfee and there's a problem. Since the security program came pre-installed on my laptop, there is an extra hoop(s) to jump through in getting rid of this thing that I didn't realize when I tried to uninstall it several months ago. Bottom line is that it won't uninstall just through control panel. I'll have to contact Mcafee to get the subscription information to be able to uninstall that way. What a hassle..I just hope this fixes the BSOD errors once and for all. Thanks
 
Upvote 0 Downvote
I get the same thing.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000028
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88004FA9D68
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\070514-27781-01.dmp
C:\Users\Mike\AppData\Local\Temp\WER-48703-0.sysdata.xml
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom