BSODs while playing games, Error IRQL_NOT_LESS_OR_EQUAL Solved

Page 7 of 7 FirstFirst ... 567
  1. ICIT2LOL's Avatar
    Posts : 1,101
    7 and 10 on various machines
       09 Sep 2017 #61

    Well my two cents worth for what it is worth there is still memory corruption according to this and well could be down to the slots on the board being bad - I ma havng difficulties highihing the parts I want so just read thought is
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8049b327595, The address that the exception occurred at
    Arg3: 0000000000000001, Parameter 0 of the exception
    Arg4: 000000003af54974, Parameter 1 of the exception
    Debugging Details:
    BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834
    SYSTEM_MANUFACTURER:  Gigabyte Technology Co., Ltd.
    SYSTEM_PRODUCT_NAME:  Z170X-Gaming 7
    SYSTEM_SKU:  Default string
    SYSTEM_VERSION:  Default string
    BIOS_VENDOR:  American Megatrends Inc.
    BIOS_DATE:  06/28/2017
    BASEBOARD_MANUFACTURER:  Gigabyte Technology Co., Ltd.
    BASEBOARD_PRODUCT:  Z170X-Gaming 7
    DUMP_TYPE:  2
    BUGCHECK_P1: ffffffffc0000005
    BUGCHECK_P2: fffff8049b327595
    BUGCHECK_P3: 1
    BUGCHECK_P4: 3af54974
    WRITE_ADDRESS: fffff800f6feb358: Unable to get MiVisibleState
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
    fffff804`9b327595 f00fc14344      lock xadd dword ptr [rbx+44h],eax
    EXCEPTION_PARAMETER1:  0000000000000001
    EXCEPTION_PARAMETER2:  000000003af54974
    BUGCHECK_STR:  0x1E_c0000005_W
    CPU_COUNT: 8
    CPU_MHZ: fa8
    CPU_VENDOR:  GenuineIntel
    CPU_MODEL: 5e
    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: BA'00000000 (cache) BA'00000000 (init)
    PROCESS_NAME:  dwm.exe
    ANALYSIS_SESSION_TIME:  09-10-2017 13:56:47.0128
    ANALYSIS_VERSION: 10.0.10586.567 amd64fre
    EXCEPTION_RECORD:  ffff908184b4b1e0 -- (.exr 0xffff908184b4b1e0)
    ExceptionAddress: 000000003af54974
       ExceptionCode: 00000002
      ExceptionFlags: 00000000
    NumberParameters: 985446336
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000000
       Parameter[2]: 0000000000000000
       Parameter[3]: 0000000000000000
       Parameter[4]: 0000000000000000
       Parameter[5]: 0000000000000000
       Parameter[6]: 0000000000000000
       Parameter[7]: 0000000000000000
       Parameter[8]: 0000000000000000
       Parameter[9]: 0000000000000000
       Parameter[10]: 0000000000000000
       Parameter[11]: 0000000000000000
       Parameter[12]: 0000000000000000
       Parameter[13]: fffff800f6d7fe57
       Parameter[14]: 0000000000000000
    LAST_CONTROL_TRANSFER:  from fffff800f6c34b7c to fffff800f6d76560
    ffff9081`84b4a9d8 fffff800`f6c34b7c : 00000000`0000001e ffffffff`c0000005 fffff804`9b327595 00000000`00000001 : nt!KeBugCheckEx
    ffff9081`84b4a9e0 fffff800`f6d8198e : ffff9081`84b4b1e0 fffff804`00000000 00000000`00000000 ffffd888`3b016000 : nt!KiDispatchException+0x23c
    ffff9081`84b4b090 fffff800`f6d7fe57 : 00000000`00000000 ffff9081`00000002 00000000`00000000 ffffc680`12b93be0 : nt!KiExceptionDispatch+0xce
    ffff9081`84b4b270 fffff804`9b327595 : ffffd888`3af54930 ffffd888`00000003 00000000`3af54930 ffff9081`84b4b590 : nt!KiPageFault+0x217
    ffff9081`84b4b400 fffff804`9c082264 : ffffd888`3af54930 ffffd888`3af61d40 ffff9081`84b4b570 fffff800`00000000 : FLTMGR!FltGetStreamContext+0x65
    ffff9081`84b4b440 fffff804`9b324b4c : ffffd888`3af61d40 ffff9081`84b4b590 ffff9081`00000001 ffffd888`3afc9c00 : Wof!WofPreReadCallback+0x54
    ffff9081`84b4b500 fffff804`9b3246ec : ffff9081`84b4b6f0 00000000`00000000 00000000`00000000 ffffd888`3b016003 : FLTMGR!FltpPerformPreCallbacks+0x2ec
    ffff9081`84b4b620 fffff804`9b3236d8 : 00000000`00000000 ffff9081`84b4b6f0 ffffd888`3b016010 ffff9081`84b4b700 : FLTMGR!FltpPassThroughInternal+0x8c
    ffff9081`84b4b650 fffff804`9b3234be : 00000000`00000001 ffff8c3f`fcd94c98 00000000`0000000d 7fffffff`ffffffff : FLTMGR!FltpPassThrough+0x168
    ffff9081`84b4b6d0 fffff800`f6c464a5 : ffffd888`3b016030 ffffd888`3b016010 ffffd888`3af61d40 fffff400`03956c01 : FLTMGR!FltpDispatch+0x9e
    ffff9081`84b4b730 fffff800`f6cabf42 : ffffd888`37b799b0 fffff800`f6cabdbb ffffd888`37b79a10 ffffd888`37b799d0 : nt!IoPageReadEx+0x265
    ffff9081`84b4b7a0 fffff800`f6cab970 : 00000000`00000003 ffff9081`84b4b830 00000000`00000000 ffffd888`37b799b0 : nt!MiIssueHardFaultIo+0xb6
    ffff9081`84b4b7f0 fffff800`f6c97486 : 00000000`c0033333 ffff9081`84b4ba80 00000000`00000000 ffff9081`84b4b990 : nt!MiIssueHardFault+0x190
    ffff9081`84b4b890 fffff800`f6d7fd72 : ffffd888`3ae4d740 00000000`00000000 00000000`00000000 ffffd888`3abf5a50 : nt!MmAccessFault+0xc96
    ffff9081`84b4ba80 00007ff9`bc29440f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x132
    00000092`6167e8f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`bc29440f
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
        fffff800f6c9754c-fffff800f6c9754d  2 bytes - nt!MmAccessFault+d5c
     [ ff f6:7f 8c ]
        fffff800f6c97d27-fffff800f6c97d28  2 bytes - nt!MiResolvePageTablePage+3b7 (+0x7db)
     [ ff f6:7f 8c ]
        fffff800f6c97d48-fffff800f6c97d4c  5 bytes - nt!MiResolvePageTablePage+3d8 (+0x21)
     [ df be 7d fb f6:8f 11 23 46 8c ]
        fffff800f6caba12-fffff800f6caba13  2 bytes - nt!MiIssueHardFault+232 (+0x13cca)
     [ 80 f6:00 8c ]
    11 errors : !nt (fffff800f6c9754c-fffff800f6caba13)
    MODULE_NAME: memory_corruption
    IMAGE_NAME:  memory_corruption
    FOLLOWUP_NAME:  memory_corruption
    TARGET_TIME:  2017-09-09T17:32:05.000Z
    OSBUILD:  15063
    SUITE_MASK:  784
    OSNAME:  Windows 10
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal
    USER_LCID:  0
    OSBUILD_TIMESTAMP:  2017-08-01 11:23:25
    BUILDDATESTAMP_STR:  170317-1834
    BUILDLAB_STR:  rs2_release
    BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834
    FAILURE_ID_HASH_STRING:  km:memory_corruption_large
    FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}
    Followup:     memory_corruption
      My ComputerSystem Spec

  2. Posts : 20
    Windows 10 Home Edition 64 Bit
    Thread Starter
       01 Oct 2017 #62

    Hi all,

    I just wanted to report back after sending back both motherboard and CPU. I received a replacement i7 6700K and my motherboard was reverted to BIOS version F21 and returned to me.

    I'm able to run my PC with Turbo Boost enabled now, and for the last couple of days I have been stable in all of my games. I've decided against overclocking for my own personal reasons. I know that I'm likely walking away from a boost in performance and I'm OK with that.

    One important thing I wanted to mention is that today I also swapped out the fan I had installed on my Hyper 212 Evo. When I built this PC in December, I opted to use a different fan on my CPU cooler than the stock Hyper 212 Evo fan. I installed this Fractal Design fan instead (Fractal Design - FD-FAN-SSR2-120-BK 66.0 CFM 120mm Fan (FD-FAN-SSR2-120-BK) - PCPartPicker). Reviews said this was a quieter fan.

    I'm not sure what the difference in airflow is between the two fans, however I do know that the Fractal Design fan runs at about 1200 RPM at all times, while the Hyper 212 Evo stock fan goes up to about 1600 RPM and as low as 950 RPM when CPU load is down. The Hyper 212 Evo fan has a 4-pin PWM plug, and the Fractal Design fan does not. I wanted to run a quieter PC by using the Fractal Design fan on my cooler, but this backfired in two ways: 1) higher temperatures due to the lower RPM, and 2) a louder system overall because the Fractal Design fan is always running at its highest RPM due to the lack of a PWM pin.

    Thanks to everyone who contributed to solving this issue. I wish this gracious community all the best in its PC building endeavors!
      My ComputerSystem Spec

Page 7 of 7 FirstFirst ... 567

Related Threads
After 10-30mins I'm getting BSOD IRQL_NOT_LESS_OR_EQUAL while Im playing lineage 2. I got new PC ASUS ROG GL553VD. I was playing GTA V and Mass Effect before and didnt have got such a problem. I can normally use my PC. I've checked hardware and...
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...
Hi, I am having some issues with a BSOD when playing games on an overclocked 6600k. The processor itself is be completely stable with a 4.5GHz overlock at 1.296V when stress tested for ~7 hours and through normal use. The BSOD occurs within 30...
I have been seeing intermittent BSOD's for the last couple of months now whilst playing games, always IRQL_NOT_LESS_OR_EQUAL message codes, but never any more information. I've read that this is usually caused by bad drivers accessing invalid...
Hello, So I'm having BSOD issues for a while now. It can be one in 5 days or 5 in 1 hour. I'm kinda getting pissed with this situation therefore requesting for some help here. I ran Memtest 86 before upgrading to W10 months ago without any...
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 13:47.
Find Us