IRQL_NOT_LESS_OR_EQUAL Errors when playing games


  1. Posts : 1
    Windows 10
       #1

    IRQL_NOT_LESS_OR_EQUAL Errors when playing games


    Hello,

    I keep encountering the same error IRQL_NOT_LESS_OR_EQUAL. However, it only shows up when I play games on my laptop. When I am not gaming the system works fine, no error, no BSOD. I'm not sure what the cause is of this error. Can someone please help me out with this issue? It would be greatly appreciated.

    System information:
    Windows version: Windows 10 , 10.0, build: 14393
    Windows dir: C:\WINDOWS
    Hardware: HP Pavilion dv6 Notebook PC, Hewlett-Packard, 1819
    CPU: GenuineIntel Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 12775120896 bytes total

    Crash dump files:

    On Tue 11/22/2016 10:15:33 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\112216-37968-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
    Bugcheck code: 0xA (0x110, 0xD, 0x0, 0xFFFFF802120D340E)
    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.



    On Tue 11/22/2016 10:15:33 PM your computer crashed
    crash dump file: C:\WINDOWS\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0xA (0x110, 0xD, 0x0, 0xFFFFF802120D340E)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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.



    On Mon 11/21/2016 12:34:25 AM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\112116-39265-01.dmp
    This was probably caused by the following module: hidusb.sys (0xFFFFF804DCF83A97)
    Bugcheck code: 0xD1 (0x3EAC15C, 0x2, 0x0, 0xFFFFF804DCF83A97)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\WINDOWS\system32\drivers\hidusb.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: USB Miniport Driver for Input Devices
    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 11/20/2016 9:50:51 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\112016-38000-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
    Bugcheck code: 0x7F (0x8, 0xFFFFA1015A7C8A30, 0xFFFFA1015AA6884C, 0xFFFFF80083555518)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\WINDOWS\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    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 Sun 11/20/2016 5:42:53 PM your computer crashed
    crash dump file: C:\WINDOWS\Minidump\112016-34500-01.dmp
    This was probably caused by the following module: vwififlt.sys (vwififlt+0x1821)
    Bugcheck code: 0xBE (0xFFFFF80C51E31821, 0x344135121, 0xFFFFE000E362A2F0, 0xA)
    Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
    file path: C:\WINDOWS\system32\drivers\vwififlt.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Virtual WiFi Filter Driver
    Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
    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.



    Thanks in advance,

    Tim
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #2

    Please read and follow the instructions here: Blue Screen of Death (BSOD) Posting Instructions as posted at the top of the forum and each thread.

    Thanks.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:23.
Find Us




Windows 10 Forums