v3-772G BSOD Driver IRQL Not Less Or Equal and other errors

Recently I've had many issues with getting a BSOD and different error messages. One of the most common is Driver IRQL Not Less or Equal, and other errors with Kernel in the subject. I had this error with Windows 8, Windows 8.1, and now Windows 10.

Specs:

OS: Windows 10

Graphics: Intel HD Graphics 4600 and NVIDIA GTX 760M

Processor: Intel i7 2.2 ghz

RAM: 12 GB

What I've tried:

I have uninstalled and reinstalled drivers for all the graphics cards and the processor. I have updated the BIOS and updated all drivers on the Acer support site. I have not tried to do a fresh install because I do not have a backup OS disc. I have run disc cleaners, done registry fixes, and multiple malware scans.

When it occurs:

The occurences are seemingly random. It will happen during normal use, when I'm just leaving the computer idle, or when playing games. Each time I get a different error message, but it's usually one of 5 relating to either driver or kernel errors. Sometimes it goes for a week without errors, and other times I will get back to back BSODs when trying to do troubleshooting. One instance in which I can consistently replicate the error is when updating the intel graphics driver. Usually, the first time I try the install I get a BSOD, but after restarting and doing the install again it finishes the install fine, however it has not prevented the errors from occuring.

Any help is greatly appreciated. Let me know what further information you need to help me with this issue.

Accepted answers

All comments

IronFly

Download Who Crashed

browse to C:\windows\minidump

delete all the dmp files apart the last 2-3

run Who crashed (it will take some minutes), then check the report and post here the report.

FMGarriga1

Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Sat 2/6/2016 4:27:54 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\020616-34984-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1C89BA) Bugcheck code: 0xD1 (0x87, 0x7, 0x0, 0xFFFFF800BABD89BA) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 361.75 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 361.75 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 361.75 , NVIDIA Corporation). Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL On Sat 2/6/2016 4:27:54 AM GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1C89BA) Bugcheck code: 0xD1 (0x87, 0x7, 0x0, 0xFFFFF800BABD89BA) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\WINDOWS\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 361.75 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 361.75 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 361.75 , NVIDIA Corporation). Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL On Thu 2/4/2016 5:07:37 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\020416-27343-01.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802131E2BE8, 0xFFFFD001AD861E40, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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. On Thu 2/4/2016 3:00:15 AM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\020416-50937-01.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x7F (0x8, 0xFFFFF802842FCE70, 0xFFFFF802842E1FB0, 0xFFFFF802825C529F) Error: UNEXPECTED_KERNEL_MODE_TRAP Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 2/2/2016 10:32:33 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\020316-36890-01.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0xD1 (0xFFFFF802B2EE662F, 0xFF, 0xDC, 0xFFFFF802B2EE662F) 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 2/2/2016 7:07:56 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\020316-30968-01.dmp This was probably caused by the following module: ntfs.sys (NTFS!NtfsRaiseStatusInternal+0x6C) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF802A9D32138, 0x0, 0x10) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\WINDOWS\system32\drivers\ntfs.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT File System Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 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 -------------------------------------------------------------------------------- 6 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 361.75 , NVIDIA Corporation)

IronFly

ok, the problem is nvidia driver; you have installed the latest available on nvidia website, please try an older version doing a clean install.

try to set maximum performance on windows Power option.

FMGarriga1

I will try this. I also saw some other solutions onlie about not installing the 3D options and physx controls when installing the NVidia drivers, which might help solve the problem. I'm just not sure which older driver to install because I've been having this trouble for quite a while, regardless I'll just pick one at random.

And when you say clean install, I assume you mean to delete the old driver first, restart, and then install the new one?

IronFly

yes, i meant that.

as you wrote, i would try to install without 3D drivers and physx too.

FMGarriga1

I've done the update. It's New Years where I am right now so I won't have much chance to use the computer to see if I can replicate the issue. Thanks for the help thus far though, I'll be sure to give you Kudos, and if I go through a week without issues I can mark it solved.