bsod IRQL NOT LESS OR EQUAL (included whocrashed report)

morgon

Honorable
Jan 5, 2014
82
0
10,630
can someone please explain to me the problem with my newly set up pc thanks. below is included report from whocrashed.

1 month old pc
amd fx9590
nvidia gtx660 (worked perfect in old pc no issues and drivers installed)
asus 990fx 2.0
windows 7 home premium (all updates installed)
corsair h100i cooler
16gb ram (novatech brand)
750 psu
nothing overclocked
microsoft security essentials only (deleted avast)

i have also un installed deamon tools lite as read this can cause a issue and have took ram out and put back in and run a ram test with no faults found.




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 2/23/2014 12:19:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022314-14539-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3F1FAB)
Bugcheck code: 0xD1 (0xFFFFE48046F0F889, 0x2, 0x1, 0xFFFFF880059F8FAB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 334.89
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 334.89
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 334.89 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 2/23/2014 12:19:54 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x3F1FAB)
Bugcheck code: 0xD1 (0xFFFFE48046F0F889, 0x2, 0x1, 0xFFFFF880059F8FAB)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 334.89
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 334.89
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 334.89 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sat 2/22/2014 8:56:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022214-15802-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x40, 0x2, 0x1, 0xFFFFF800030E10D8)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
I will quickly explain why you get a message of IRQL NOT LESS OR EQUAL

It is down to a driver or the hardware not being able to communicate with the device plugged into the board or interface it is using.

The causes are the device is overheating, causing it not to respond to driver requests.
Insufficient steady power supply.
Or that two or more devices are using the same interrupt request.
The cpu gives each device an Irq so it can send or signal information to and from it via the software driver. But if two or three devices use the same Irq number.
The cpu has to wait till a device is finished using it to allow the next device to be talked to.

From the driver through the cpu to the device.
Drivers have a timeout, and cause the BSOD.

You should free up Irq`s of the board by going into the bios and turning off devices you don`t use. Printer ports com ports ect.
 

morgon

Honorable
Jan 5, 2014
82
0
10,630




thanks shaun. the gpu doesnt overheat as never goes above 61c when gaming due to using precision X and having a custom fan setting where if the temp is 30c the fan will be at 40% and at 40c fan will be at 50% and so on so i guess i can rule out over heating.

"Or that two or more devices are using the same interrupt request." sorry what does this mean? two programs talking and configuring the gpu? i only ask as i use precision X to control gpu but the fan is also linked to the corsair link2 software.

i will search as to how to trun off ports i dont use in bios as i am not too savvy on pc insides.

one thing i have seen alot of on the net about "nvlddmkm.sys" is that when you install a fresh windows 7 there is a NT KERNEL update in the 150 odd windows updates when on a fresh install, could this be my issue also as i dont recall having BSOD when i first set up pc and before installing the 150 odd windows updates.

also not sure if this bit of info helps but when i was playing assassin creed 4 after 30 mins the graphics went all choppy before i got a crash yet gpu would have been controlled by precision X and been maxed at 61C as that is the max temp i ever get on games but mostly 54-61C with custom fan setting.

thanks
 

morgon

Honorable
Jan 5, 2014
82
0
10,630
more bsod crashes while gaming. seems to be almost 30 mins of gaming results in a bsod. included new whocrashed report for today



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 2/24/2014 2:12:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022414-12885-01.dmp
This was probably caused by the following module: msfs.sys (Msfs+0x49F4)
Bugcheck code: 0xFC (0xFFFFF880010E19F4, 0x800000040047D121, 0xFFFFF8800AC92530, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\msfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Mailslot driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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 2/24/2014 2:12:24 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm!nvDumpConfig+0x2DD7F5)
Bugcheck code: 0xFC (0xFFFFF880010E19F4, 0x800000040047D121, 0xFFFFF8800AC92530, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 334.89
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 334.89
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 334.89 , NVIDIA Corporation).
Google query: NVIDIA Corporation ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY



On Mon 2/24/2014 12:23:00 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\022414-12901-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800031FC147, 0xFFFFF88003832C50, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




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

3 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 334.89 , NVIDIA Corporation)

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.
 

morgon

Honorable
Jan 5, 2014
82
0
10,630
after loads more bsod and freezing i have used driver sweeper to remove all nvidia items and re installed it all but this time the 331.82 driver and for 2 hrs had no issues on bf4 which beforehand would bsod every 30-40 mins. Will continue testing tomorrow and see if can go for 4-5hrs. This driver was also the only one that whenrunning bf4 wouldnt push you to upgrade to the new current obviously bugged driver. Just hope that was issue.