BSOD with error DRIVER_IRQL_NOT_LESS_OR_EQUAL

[Sunitsa]

Hello everyone, I've recently changed cpu and vga and added an SSD to my computer, since then I've been hit by lots of bsod.


My system specification are:

mobo: ASUS PQ5L PRO
cpu: Intel Q3800
vga: Palit NVIDIA GeForce gtx750
ssd: Toshiba Q series 128gb
hd: WDC 320 gb
os: Windows 7 Ultimate 64bit sp 1
ram: 2x2gb Kingston DDR2 400Mhz, memory timing 1,8 v


I have already tried to use all kind of drivers, old, newest, beta, whatsever. I've also tried to format and install windows again with no success.

I would really need some help to understand what cause it since I'm not really an expert and I'm completly lost and I'm starting to fear that it might be an hardware problem despite whocrashed claiming otherwise

dmp files here: http://www.filedropper.com/minidump_2

These are the whocrashed reports of the lasts bsod (I had many others, but didn't think about copying older report befor formatting so they are gone)

Spoiler

On Tue 28/10/2014 18:37:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102814-19484-01.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880014C18C1)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF880014C18C1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
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 Tue 28/10/2014 18:37:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ndis.sys (0xFFFFF880014C18C1)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF880014C18C1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\ndis.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver NDIS 6.20
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 Tue 28/10/2014 10:31:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102814-16770-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800430D34E)
Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFF7, 0x2, 0x0, 0xFFFFF8800430D34E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 Mon 27/10/2014 21:24:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102714-19032-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x133F)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88003EB533F, 0xFFFFF88009FFD990, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog 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 that cannot be identified at this time.

Any help would be much appreciated, thanks in advance

 

[kapitalistas]

you didnt met minimum watch dogs pc requirements.

 

[Eximo]

Didn't list memory. But DRIVER_IRQL_NOT_LESS_OR_EQUAL errors are usually memory related. You are probably maxing out the memory of the system, forcing it to do more work from the page file.

You might try increasing your memory voltage a little bit (like .05 -.1 volts)

 

[huilun02]

This error is usually caused by network driver issues.

Go here to download the LAN driver for your board
http://www.asus.com/Motherboards/P5QL_PRO/HelpDesk_Download/

Select your Windows version and under the LAN category, get the 2009/09/18 driver.

Now go into device manager and uninstall the driver for your Atheros LAN Driver.

Do a reboot and install the driver you downloaded. Restart again if required.

 

[Sunitsa]

you didnt met minimum watch dogs pc requirements.

This has nothing to do with the game watch dog...

Didn't list memory. But DRIVER_IRQL_NOT_LESS_OR_EQUAL errors are usually memory related. You are probably maxing out the memory of the system, forcing it to do more work from the page file.

You might try increasing your memory voltage a little bit (like .05 -.1 volts)

Damn, I knew I was missing something in the op.

I have 2x2gb of Kingston DDR2, 400 Mhz, set at a memory timing of 1,8 volt.

Are they ok? How can I change their memory voltage if I need to?

This error is usually caused by network driver issues.

Go here to download the LAN driver for your board
http://www.asus.com/Motherboards/P5QL_PRO/HelpDesk_Download/

Select your Windows version and under the LAN category, get the 2009/09/18 driver.

Now go into device manager and uninstall the driver for your Atheros LAN Driver.

Do a reboot and install the driver you downloaded. Restart again if required.

I have already tried both this driver and the one windows automatically install, neither seems to remove the issue.

To be sure I did another clean installation of the Atheros drivers in the case I messed something up earlier

 

[Eximo]

Yes, watchdog.sys is just a part of Windows

Everytime I have seen DRIVER_IRQL_NOT_LESS_OR_EQUAL it was usually related to power or memory issues. System drivers and other Windows functions just start having errors like these. Even had a bad GPU cause it in a co-workers computer. The VRAM was unstable and the video driver would crash at the slightest load with that error.

4GB of DDR2, depending on what you are doing, might not be enough. When the ram is working a full load it can sometimes become unstable. Your BIOS might have voltage adjustments for the memory, but maybe not, ASUS website seems to missing the details for that one.

 

[Paul NZ]

Upload the dmp files somewhere then post the link

 

[Sunitsa]

Upload the dmp files somewhere then post the link

dmp files here: http://www.filedropper.com/minidump_2

 

[kapitalistas]

the guy which know exact fix(Yes, watchdog.sys is just a part of Windows)no offence,but some people like troll.

 

[Paul NZ]

Uninstall Avast for now. Then use their removal tool. http://www.avast.com/en-nz/uninstall-utility

It can cause both of these stop errors (the 0x3b and 0xd1 with ndis.sys)

The other file thats crashing belongs to directx

L1E62x64.sys these drivers are old / from 2009. Your atheros LAN drivers. See if there's an update for them.

Its possible since these are old, theyre crashing ndis.sys. Since both are network related files

 

[Sunitsa]

I'm starting to think that I might have more than just one issue, damn me not saving the older and bigger dump folder.

I will try to remove avast, but before formatting I had avira on and bsod keep happening

There seems to not be any newer driver than the 2009 one for my atheros in the asus website or it's just me who can't find them. Is it worth noting that the same drivers with the same mobo worked fine for years when I had xp and a different cpu/vga?

 

[Paul NZ]

Do you use Ethernet or wireless? You'll have to try the atheros site or search for it. So was Avira installed before Avast (after you formatted).

Or did you format after Avira was installed / you removed it? Then installed Avast?

 

[kapitalistas]

i recommend uninstall any antivirus and network drivers software in safe mode with cccleaner or etc.(network drivers Windows installs automatically) and see if the problem persist.

 

[Sunitsa]

I use Ethernet and I'm using the same one I have always used which never gave trouble before, unless there is a known issue with my Atheros and Windows 7 it sounds pretty strange to me.

As before, to be sure I have uninstalled both Avast and Atheros drivers in safe mode with cccleaner. However, after I exited safe mode windows automatically installed some kind of driver in order to use the Ethernet: was this the result I was looking for?

I'm also pretty sceptical about being an antivirus issue since I used to run avira before formatting and the bsods happen back then too, actually switching to avast was a try to see if avira could have been the cause of my troubles (and ofc I installed it only after formatting).

Just to be sure in this aspect too, I'm currently without any antivirus, let's see if I'm bsod free

 

[Sunitsa]

Got a new bsod without having an antivirus and with atheros drivers updated to the newest version I could fine (the 2009 one).

whocrashed reports:

On Wed 29/10/2014 12:48:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102914-17815-01.dmp
This was probably caused by the following module: mouhid.sys (mouhid+0x2869)
Bugcheck code: 0xD1 (0x110000, 0x2, 0x1, 0xFFFFF880057AE869)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mouhid.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver del filtro del mouse HID
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 Wed 29/10/2014 12:48:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: mouhid.sys (mouhid+0x2869)
Bugcheck code: 0xD1 (0x110000, 0x2, 0x1, 0xFFFFF880057AE869)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\mouhid.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver del filtro del mouse HID
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.


dump file: http://www.filedropper.com/dump

 

[huilun02]

The issue is definitely driver related.

Try going into BIOS and enabling legacy support.

mouhid.sys is Microsoft's mouse driver.

To better pinpoint the culprit, remove one of the newly added components at a time to see if the crashing stops.

Also, does the crashing occur only when you perform a specific action? Does it occur even in safe mode?

 

[Sunitsa]

The crashes happen when "stressing" the computer, usually while gaming but a couple of time also while simply surfing with firefox or watching a video.

I didn't test it much but I don't think it would happen in safe since I would need to run something to recreate the crash. I also have no way to remove one of the newer component since I have nothing to replace them with and to test if something is wrong I would need to run a game.

I could try to enable legacy support, I just need to google and undestand what is it and how to enable it.

Thanks for the help!

 

[Sunitsa]

Okay, I've run memtest86 overnight and it seems the memories are fine.

I have failed to grasp how to run in legacy support, but from what I understood it won't help my issue because I won't be able to replicate the bsod without stressing somehow the computer.

I still have no way to remove the vga or the cpu to pinpoint wich one might cause the issue, but even if would manage to find out that it's caused by the vga for example, how would I be able to resolve it? I have already tried many different kind of drivers and the error keep coming with all of them, I'd assume that if it's a driver issue, it's because there should be some incompatibilities with the vga or the cpu and the motherboard.

Could a new bios installation help?

And is worth something that booting the computer is getting significantly harder with it something shutting down a couple of seconds after I power it on?

 

[huilun02]

You can test just the GPU by running something like Furmark

For the CPU you can use Prime95

If both of them cause the same crash then it might indicate a PSU power draw problem.

 

[Sunitsa]

It is definitly a vga related issue, apart from replacing it are there anything I can do? I have already tried using its boxed driver and the most recent ones

 

[huilun02]

None that I know of. If you have an old/spare graphics card or borrow one from a friend, you could see if changing the card does any good.