It is custom built.

BSOD caused by tcpip.sys
Started by
VescanRazvan
, Mar 28 2013 02:18 PM
#16
Posted 05 April 2013 - 10:28 AM

It is custom built.
#17
Posted 05 April 2013 - 06:52 PM

I'd try this one:
Win7 and WinServer 2008 R2 Driver 7.069 2013/3/26 839k US1 US2 CN HK1 UK1 US3
Click on any of the US links, US1 - US3. The download file is: Driver_Win7_7069_03212013.zip
I don't see any 32 or 64 bit designation so I believe it handles both.
Win7 and WinServer 2008 R2 Driver 7.069 2013/3/26 839k US1 US2 CN HK1 UK1 US3
Click on any of the US links, US1 - US3. The download file is: Driver_Win7_7069_03212013.zip
I don't see any 32 or 64 bit designation so I believe it handles both.
#18
Posted 06 April 2013 - 01:22 AM

Ok,i've installed it and I will come back with news if necessary.
#19
Posted 06 April 2013 - 12:42 PM

[bleep]!Another crash.For some reason I have 2 reports on the same crash.They are not different from the others.
On Sat 06.04.2013 18:36:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rt86win7.sys (Rt86win7+0x14B80)
Bugcheck code: 0xD1 (0x3955E73D, 0x2, 0x1, 0xFFFFFFFF8B26738D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rt86win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8101E/8168/8169 NDIS 6.20 32-bit 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.
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: rt86win7.sys (Realtek 8101E/8168/8169 NDIS 6.20 32-bit Driver , Realtek ).
Google query: Realtek DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 01.04.2013 14:21:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040113-36519-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x86307)
Bugcheck code: 0xD1 (0xFFFFFFFFAFDD9059, 0x2, 0x1, 0xFFFFFFFF8B29D307)
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 06.04.2013 18:36:07 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: rt86win7.sys (Rt86win7+0x14B80)
Bugcheck code: 0xD1 (0x3955E73D, 0x2, 0x1, 0xFFFFFFFF8B26738D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\rt86win7.sys
product: Realtek 8136/8168/8169 PCI/PCIe Adapters
company: Realtek
description: Realtek 8101E/8168/8169 NDIS 6.20 32-bit 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.
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: rt86win7.sys (Realtek 8101E/8168/8169 NDIS 6.20 32-bit Driver , Realtek ).
Google query: Realtek DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Mon 01.04.2013 14:21:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040113-36519-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x86307)
Bugcheck code: 0xD1 (0xFFFFFFFFAFDD9059, 0x2, 0x1, 0xFFFFFFFF8B29D307)
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.
#20
Posted 07 April 2013 - 03:16 PM

Please download MINITOOLBOX and run it.
http://download.blee...MiniToolBox.exe
Checkmark following boxes:
Flush DNS
Reset FF proxy Settings
Reset Ie Proxy Settings
Report IE Proxy Settings
Report FF Proxy Settings
List content of Hosts
List IP configuration
List Winsock Entries
List last 10 Event Viewer log
List Installed Programs
List Users, Partitions and Memory size
List Devices (problems only)
Click Go and post the result.
Please upload your minidump files as well.
http://h30434.www3.h...iles/m-p/253475
Download Autoruns and Autorunsc
http://download.sysi...es/Autoruns.zip
Unzip it to your desktop and then double click autoruns.exe After the scan is finished then click on File>>>>>>>>>>>Save The default name will be autoruns.arn make sure to save it as Autoruns.txt under the file type option. in other words make sure it is a .txt file instead of .arn Attach the text in your next reply.
http://download.blee...MiniToolBox.exe
Checkmark following boxes:
Flush DNS
Reset FF proxy Settings
Reset Ie Proxy Settings
Report IE Proxy Settings
Report FF Proxy Settings
List content of Hosts
List IP configuration
List Winsock Entries
List last 10 Event Viewer log
List Installed Programs
List Users, Partitions and Memory size
List Devices (problems only)
Click Go and post the result.
Please upload your minidump files as well.
http://h30434.www3.h...iles/m-p/253475
Download Autoruns and Autorunsc
http://download.sysi...es/Autoruns.zip
Unzip it to your desktop and then double click autoruns.exe After the scan is finished then click on File>>>>>>>>>>>Save The default name will be autoruns.arn make sure to save it as Autoruns.txt under the file type option. in other words make sure it is a .txt file instead of .arn Attach the text in your next reply.
#21
Posted 08 April 2013 - 01:18 AM

Here you got the result file,the autoruns file and the minidumps.
files.rar 409.71KB
148 downloads
EDIT.
Another mini dump from 3 hours ago.
040813-15022-01.rar 23.01KB
138 downloads

EDIT.
Another mini dump from 3 hours ago.

Edited by VescanRazvan, 08 April 2013 - 04:05 PM.
#22
Posted 17 April 2013 - 12:31 PM

Is somebody here?
#23
Posted 17 April 2013 - 07:05 PM

Same failure as before, Rt86win7.sys.
I PMd Rockmilk so hopefully he will drop by soon as I'm out of ideas at the moment.
Is the LAN connection on-board (buuilt into the mother board? If so, one thing I would try is to add a PCI or PCI-E (what ever your board will take) network card and see if that resolves the problem.
I PMd Rockmilk so hopefully he will drop by soon as I'm out of ideas at the moment.
Is the LAN connection on-board (buuilt into the mother board? If so, one thing I would try is to add a PCI or PCI-E (what ever your board will take) network card and see if that resolves the problem.
#24
Posted 18 April 2013 - 06:18 AM

I think i have an onboard lan.Also,i had no issues when i used windows xp.I want to avoid buying a new lan card.
#25
Posted 18 April 2013 - 08:07 PM

Well, we've already tried installing the latest available RealTek driver and that didn't help so the easiest thing to do is install a PCI/PCI-E lan card. They are very cheap, but perhaps you could even borrow one from a friend just to test with?
Also, looking at Startup.txt, I see
DAEMON Tools Lite
Steam
Might want to try disabling them for a while as a test. Both have been know to cause problems at times.
Also, looking at Startup.txt, I see
DAEMON Tools Lite
Steam
Might want to try disabling them for a while as a test. Both have been know to cause problems at times.
#26
Posted 19 April 2013 - 01:01 PM

I will not buy a lan card until it is absolutely necessary.
About the startup programs,I didn't even know daemon tools is on the startup list.More weird is that it doesn't show up as an opened software,it doesn't even show up in the processes list,same as Nero.Anyway,I will disable them and see what happens.I haven't had a crash since 07.04.
When this problem will annoy me very much,I will install a new Windows 7 or even a Xp version.
Too bad we couldn't find a solution that would not require hardware changes.Anyway,if there is no suggestion you can give to me,you can unsubscribe from this post.If I get the same problem after I reinstall a different version of windows,I will come back with another topic.
Thank you very much.
About the startup programs,I didn't even know daemon tools is on the startup list.More weird is that it doesn't show up as an opened software,it doesn't even show up in the processes list,same as Nero.Anyway,I will disable them and see what happens.I haven't had a crash since 07.04.
When this problem will annoy me very much,I will install a new Windows 7 or even a Xp version.
Too bad we couldn't find a solution that would not require hardware changes.Anyway,if there is no suggestion you can give to me,you can unsubscribe from this post.If I get the same problem after I reinstall a different version of windows,I will come back with another topic.
Thank you very much.
#27
Posted 19 April 2013 - 08:25 PM

I'm sorry we didn't find a fix. Hope not to hear from you again

Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:






