BSOD - Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

[Garlotch]

I am getting random blue screens of death, that give me this message.

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

I ran a WhoCrashed analysis, and here is the report.

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

computer name: ELLIOT-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P5GC-MX
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2146033664 total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 24/01/2015 10:51:09 p.m. GMT your computer crashed
crash dump file: C:\Windows\Minidump\012515-67220-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x63042)
Bugcheck code: 0xD1 (0x10, 0x2, 0x1, 0xFFFFFFFF89C7D042)
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 24/01/2015 10:51:09 p.m. GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.sys (hal!KeRaiseIrqlToSynchLevel+0x8F)
Bugcheck code: 0xD1 (0x10, 0x2, 0x1, 0xFFFFFFFF89C7D042)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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: hal.sys .
Google query: hal.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL





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

2 crash dumps have been found and analyzed. A third party driver has 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:

hal.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 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.

I have updated all the drivers with IOBit's Driver Booster 2, and I have gone into safe mode and scanned/removed all malware and viruses. I have also ran and cleaned with CCleaner.

Does anyone know how I can fix this problem?

I have uploaded a zip file, from the DM Log Collector.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 1, 89c8d042}

Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )

Followup: MachineOwner
---------

The problem appears to be related to your ethernet/wifi adapter driver. However, the .dmp files are corrupted, probably because of the poor choice of software you are using....more on that later.

For now, see if an update is available for your Atheros ethernet driver.

I have updated all the drivers with IOBit's Driver Booster 2

Do NOT use this software to update your drivers - get your drivers directly from the manufacturer's site. You have no idea whether the drivers updated using this tool have been tampered with, or are indeed the correct versions for your software.

Start Menu\Programs\Advanced SystemCare 8	Public:Start Menu\Programs\Advanced SystemCare 8	Public
Start Menu\Programs\Driver Booster 2	Public:Start Menu\Programs\Driver Booster 2	Public
Start Menu\Programs\Free Window Registry Repair	Public:Start Menu\Programs\Free Window Registry Repair	Public

Uninstall all of the above - they are worthless, and possibly have already caused damage to the file system.

Do NOT use CCleaner until the BSOD has been solved - it deletes the .dmp files neccessary to analyse and solve the BSOD's.

Start Menu\Programs\AVAST Software	Public:Start Menu\Programs\AVAST Software	Public
Start Menu\Programs\IObit Malware Fighter	Public:Start Menu\Programs\IObit Malware Fighter	Public

Do NOT use multiple instances of AV software - they conflict wih one another causing system instability. Remove the IOBit stuff - its crap.

 

[Garlotch]

Thank you Golden,

I will try everything you have suggested, including uninstalling the IOBit software, although I will keep the IOBit Uninstaller, since it has a nice function that powercleans the registry after uninstalling software.

I'll get back to you soon.

 

[Garlotch]

I do not know where to find the latest Atheros L2 driver, I went to atheros.cz (the official site), but there was no download for windows 7, only for xp and vista

 

[Garlotch]

Ok so I downloaded a vista driver, which should work, I tried to install it and then it said, that the driver was up to date? I don't know if it installed or not. I am going to upload another DMLogCollector report, please tell me if the driver has been updated?

 

[Garlotch]

I looked at it myself, and it doesn't seem that the driver was updated to something different? Should I try find a different version? Or is it fine the way it is? :/

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 1, 89c76042}

Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )

Followup: MachineOwner
---------

0: kd> lmvm l260x86
start    end        module name
9319c000 931a8000   l260x86    (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\l260x86.sys
    Image name: l260x86.sys
    Timestamp:        Tue Mar 17 20:30:43 2009 (49BF74CB)
    CheckSum:         00015036
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table
Just did some further research, it looks like there isn't a version for Windows 7, so the only way to solve this will be to replace the adapter.

 

[Garlotch]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 1, 89c76042}

Probably caused by : tcpip.sys ( tcpip!TcpBeginTcbSend+9f6 )

Followup: MachineOwner
---------

0: kd> lmvm l260x86
start    end        module name
9319c000 931a8000   l260x86    (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\l260x86.sys
    Image name: l260x86.sys
    Timestamp:        Tue Mar 17 20:30:43 2009 (49BF74CB)
    CheckSum:         00015036
    ImageSize:        0000C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Driver Reference Table
Just did some further research, it looks like there isn't a version for Windows 7, so the only way to solve this will be to replace the adapter.

There must be SOME other soluation Golden! It was working perfectly fine, for years until now. I haven't changed the O.S at all recently!

 

[Golden]

True, but you have been doing regular Windows Updates, so over time it has indeed changed. Perhaps that change is subtle enough to have caused this very old driver to now clash with the newer system files to the point that it causes the BSOD.

 

[Garlotch]

I understand. Is there anything you suggest I could attempt to solve this, without replacing the adapter? Maybe rollback a windows update perhaps?

 

[Golden]

Maybe rollback a windows update perhaps?

No chance.....how far to roll back? Impossible to tell. Unfortunately, I can think of no other alternative. A properly functioning driver is an absolute must for every device