driver_irql_not_less_or_equal tcpip.sys windows 8

Status
Not open for further replies.

Dominik Murko

Reputable
Sep 14, 2014
8
0
4,510
Sorry sorry...but i don´t know where i can give minidump...leteckaposta.cz is for file upload...

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

computer name: PC
windows version: Windows 8 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: HP Envy 17 Notebook PC, Hewlett-Packard, 1966
CPU: GenuineIntel Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8518651904 total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 14.9.2014 6:21:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091414-26000-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001DAAE3C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001DAAE3C)
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 Sun 14.9.2014 6:21:27 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x161E3C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001DAAE3C)
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 13.9.2014 20:18:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-25062-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001E36E3C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001E36E3C)
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 13.9.2014 14:40:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-29906-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001E56E3C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001E56E3C)
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 13.9.2014 13:28:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-53968-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001D83E3C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001D83E3C)
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 13.9.2014 1:31:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091314-29953-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001E2EE3C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001E2EE3C)
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 Fri 12.9.2014 6:35:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091214-64296-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001D83E3C)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001D83E3C)
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 Thu 11.9.2014 8:14:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091114-19718-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF8800205AA45)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF8800205AA45)
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 Thu 11.9.2014 8:06:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091114-20140-01.dmp
This was probably caused by the following module: tcpip.sys (0xFFFFF88001DD4A45)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88001DD4A45)
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.

 
first bugcheck was in network code:
It looks like you have a Ralink RT2860 series Wireless LAN Card
\SystemRoot\system32\DRIVERS\netr28x.sys Tue Nov 26 00:32:08 2013

maybe look here: http://www.mediatek.com/en/downloads/
8/14/2014 windows driver might work. (it is for the usb rt2870)

the company was sold to another company last year (media tex) and driver updates are harder to find now. But do update yours if you can find it. Nice that you do have a more recent version. In that case the driver does depend on your USB ports which depend on fixes to your BIOS and updated drivers from intel. You can get the current drivers from intel here:https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=20775

you would have to get any BIOS update from hp.

Note: virus scanners can also trigger bugchecks on USB ethernet devices if there is a bug or the device runs too slow.

note: if you have any extra usb 3.0 controller in your laptop you will also want to update it at the HP website for your hardware. (or your usb device will work on the 2.x usb connectors and might fail on usb 3.0 connectors.



machine info:
Processor Version Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Processor Voltage 88h - 0.8V
Socket Designation U3E1
Manufacturer Hewlett-Packard
Chassis Type Notebook
Manufacturer Hewlett-Packard
Product 1966
Version KBC Version 93.51
Manufacturer Hewlett-Packard
Product Name HP Envy 17 Notebook PC
SKUNumber E2U49EA#UUZ


 
Status
Not open for further replies.