BSOD IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe While under heavy load

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 Ultimate x64
       #1

    BSOD IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe While under heavy load


    I've been getting these crashes since day one of putting the pc together and over the years and picked at it trying to figure the issue. I use to get the IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe bsod a lot and traced it back to a driver issue over a year ago but continued getting other crashes, I cannot for the life of me remember what or how I figured it out the last time.

    Recently my drive had be getting a bit full so I got a new 2t drive to use as game storage, put everything I wanted to keep on the new drive and reformatted my old 750 gig drive to use for windows and miscellaneous files. Right after the install I immediately began getting the old bsod error again and have been unable to track it down. So far I have attempted updating all drivers I could think of but I'm out of ideas and I apparently dont know how to track down these issues as well as I had hoped. Hopefully someone who knows what they're doing better then I do can lead me in the right direction.

    So far all of the crashes have happened when the system was under heavy usage. Examples, playing a graphic intensive game for over an hour, downloading multiple large files, transferring several gigs of data from one drive to the next.

    Any help at all would be very much appreciated, Thank you in advance.
      My Computer

  2.    #2

    Sounds like bad RAM to me, you have Driver Verifier enabled and it still hasn't picked anything up.

    Memtest86 will test your RAM

       Information

    Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing
      My Computer


  3. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Just finished a 38 hour 10 pass memtest run, no errors.
    I ran memtest back when I first started trying to figure this our over a year ago, didn't have any issues then either.
    I have also recently run Western Digital's Data Lifeguard and as well as an asus pc stress test utility for an hour and found/had no issues.
      My Computer

  4.    #4

    Have you had any new crashes?
    If so upload the dump files, lets see if anything different pops up.
      My Computer


  5. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #5

    I haven't had any new crashes, they suddenly decided to stop as soon as I actually want them to happen. I'm going to be out of town for a few days and wont be using my pc. But when I'm back and it crashes again I'll upload a new report.
      My Computer


  6. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #6

    I've been back for a while now but my pc seems to have suddenly decided to stop crashing despite the lack of any changes. Whenever it dose again I'll return and upload a new report.
      My Computer

  7.    #7

    Okay keep us posted.
      My Computer


  8. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #8

    After all this time the pc finally crashed again, this time just playing a video via web browser. Though this time the string reported SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. I've never gotten that string before today. Regardless of if its related or not I've uploaded a report.
      My Computer


  9. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Ran Memtest again thinking maybe something got damaged but again it didn't turn up with anything. I've been repeatedly having crashes with the SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION string report.
      My Computer


  10. Posts : 15,026
    Windows 10 Home 64Bit
       #10

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck C1, {fffff98028200fc0, fffff98028200717, 6b4040, 32}
    
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by : atikmdag.sys ( atikmdag+3eadb )
    
    Followup: MachineOwner
    ---------
    
    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
    Special pool has detected memory corruption.  Typically the current thread's
    stack backtrace will reveal the guilty party.
    Arguments:
    Arg1: fffff98028200fc0, address trying to free
    Arg2: fffff98028200717, address where one bit is corrupted
    Arg3: 00000000006b4040, (reserved)
    Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0xC1_32
    
    SPECIAL_POOL_CORRUPTION_TYPE:  32
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    PROCESS_NAME:  FlashPlayerPlu
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff8000311ecb3 to fffff8000308fbc0
    
    STACK_TEXT:  
    fffff880`08342288 fffff800`0311ecb3 : 00000000`000000c1 fffff980`28200fc0 fffff980`28200717 00000000`006b4040 : nt!KeBugCheckEx
    fffff880`08342290 fffff800`03197903 : fffff6fc`c0133d30 fffff980`267a6f60 fffff980`01452408 00000000`00000000 : nt!MiCheckSpecialPoolSlop+0x83
    fffff880`083422d0 fffff800`031c293b : fffff800`0301a000 00000000`494e494d 00000000`00290638 00000000`4e4b4e55 : nt!MmFreeSpecialPool+0x1d3
    fffff880`08342410 fffff880`110c3adb : fffff980`28200fc0 00000000`00000001 fffff800`03247480 fffff800`03152743 : nt!ExDeferredFreePool+0xf33
    fffff880`083424c0 fffff980`28200fc0 : 00000000`00000001 fffff800`03247480 fffff800`03152743 fffff880`08342540 : atikmdag+0x3eadb
    fffff880`083424c8 00000000`00000001 : fffff800`03247480 fffff800`03152743 fffff880`08342540 fffff880`110c067a : 0xfffff980`28200fc0
    fffff880`083424d0 fffff800`03247480 : fffff800`03152743 fffff880`08342540 fffff880`110c067a 00000000`4e4b4e55 : 0x1
    fffff880`083424d8 fffff800`03152743 : fffff880`08342540 fffff880`110c067a 00000000`4e4b4e55 00000000`00000000 : nt!MiSpecialPool
    fffff880`083424e0 fffff800`031535cb : fffff980`23d8a740 fffff880`110945a2 fffff980`28200fc0 fffff880`083426c0 : nt!RtlWalkFrameChain+0x63
    fffff880`08342510 00000000`00000000 : 00000002`00000048 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x4b
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    atikmdag+3eadb
    fffff880`110c3adb ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  atikmdag+3eadb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: atikmdag
    
    IMAGE_NAME:  atikmdag.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53508a3c
    
    FAILURE_BUCKET_ID:  X64_0xC1_32_VRF_atikmdag+3eadb
    
    BUCKET_ID:  X64_0xC1_32_VRF_atikmdag+3eadb
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm atikmdag
    start             end                 module name
    fffff880`11085000 fffff880`11f95000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Timestamp:        Fri Apr 18 08:13:16 2014 (53508A3C)
        CheckSum:         00EAEEE6
        ImageSize:        00F10000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Caused by ATI Card drivers with verifier enabled. Have you disabled verifier already?
      My Computer


 
Page 1 of 2 12 LastLast

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

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