Win7 Pro-BSOD - DRIVER_IRQL_NOT_LESS_OR_EQUAL -tcpipsys - 0x000000D1  

G'day!

Guys, I am facing a problem with my new laptop, I've done my research for solution of the problem below on the internet, so far it didn't do me any good but to confuse myself. :surrender:

I hope u guys can help me fix it. Thanks in advance, cheers!

Brand New (Less than 2 month :wacko:) Toshiba Satellite Pro L850
OS: Win7 Pro (Constantly Updated)
Antivirus: ESET SmartSecurity 5 (Constantly Updated)

Below is report generated by BlueScreenView.exe of Nirsoft
Download here: My link


NETIO.SYS , ntoskrnl , tcpip.sys, the first top three below has pink marker on the report generated.

==================================================
Dump File : 112712-34554-01.dmp
Crash Time : 27/11/2012 7:35:57 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`0000001c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff880`01ce565e
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+6365e
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7efc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\112712-34554-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 7601
Dump File Size : 292,842
==================================================

==================================================
Filename : NETIO.SYS
Address In Stack : NETIO.SYS+7c74
From Address : fffff880`01b27000
To Address : fffff880`01b87000
Size : 0x00060000
Time Stamp : 0x5034f6a0
Time String : 23/08/2012 2:11:28 AM
Product Name :
File Description :
File Version :
Company :
Full Path :
==================================================

==================================================
Filename : ntoskrnl.exe
Address In Stack : ntoskrnl.exe+7e569
From Address : fffff800`03002000
To Address : fffff800`035ea000
Size : 0x005e8000
Time Stamp : 0x503f82be
Time String : 31/08/2012 2:11:58 AM
Product Name : Microsoft® Windows® Operating System
File Description : NT Kernel & System
File Version : 6.1.7601.17944 (win7sp1_gdr.120830-0333)
Company : Microsoft Corporation
Full Path : C:\windows\system32\ntoskrnl.exe
==================================================

==================================================
Filename : tcpip.sys
Address In Stack : tcpip.sys+6365e
From Address : fffff880`01c82000
To Address : fffff880`01e83000
Size : 0x00201000
Time Stamp : 0x506c552e
Time String : 4/10/2012 2:09:34 AM
Product Name :
File Description :
File Version :
Company :
Full Path :
==================================================

Below is report generated by: (Home Edition) WhoCrashed.exe of Resplendence
Download here: My link

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: (USER)-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\windows
CPU: GenuineIntel Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17137721344 total
VM: 2147352576, free: 1955586048

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

Crash dump directory: C:\windows\Minidump

Crash dumps are enabled on your computer.

On Tue 27/11/2012 8:34:41 AM GMT your computer crashed
crash dump file: C:\windows\Minidump\112712-34554-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x6365E)
Bugcheck code: 0xD1 (0x1C, 0x2, 0x1, 0xFFFFF88001CE565E)
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.

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

One crash dump has 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.

--------------------------------------------------------------------------------

No reply..