BOSD irql_not_less_or_equal ntoskrnl.exe

By MaxFfm
Feb 19, 2015
Post New Reply
  1. Hallo,

    every couple of days I get a BSOD, with the error above. For detailed minidumpo see below.
    Furthermore the PC doesn't autmoatically restart (even it is activated in system properties / advances / startup and recovery).

    Does anybody have a solution? I already tried reg-cleaning, crc and memtest86 checking.

    Thank you,

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\Users\Maximilian\Desktop\021715-30843-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\Symbols*
    Symbol search path is: SRV*C:\Symbols*
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
    Machine Name:
    Kernel base = 0xfffff801`84a1b000 PsLoadedModuleList = 0xfffff801`84cf4250
    Debug session time: Mon Feb 16 06:18:19.329 2015 (UTC + 1:00)
    System Uptime: 3 days 16:11:09.816
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck A, {ffffffe2fc, 2, 0, fffff80184ad526f}
    Probably caused by : ntkrnlmp.exe ( nt!KiAbTryIncrementIoWaiterCount+3f )
    Followup: MachineOwner
    5: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arg1: 000000ffffffe2fc, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80184ad526f, address which referenced memory
    Debugging Details:
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80184d7e138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    fffff801`84ad526f f780fc02000000001000 test dword ptr [rax+2FCh],100000h
    PROCESS_NAME:  tv_w32.exe
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    TRAP_FRAME:  ffffd000a3cfa6c0 -- (.trap 0xffffd000a3cfa6c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000024 rbx=0000000000000000 rcx=ffffc001fc4c34e0
    rdx=0000000000000026 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80184a855a0 rsp=ffffd000a3cfa850 rbp=ffffd000a3cfab80
    r8=ffffc001fc4c34e0  r9=7fffc001fd72a5d0 r10=ffffc001fd72a5d0
    r11=7ffffffffffffffc r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    fffff801`84a855a0 f0480fc11f      lock xadd qword ptr [rdi],rbx ds:00000000`00000000=????????????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80184b774e9 to fffff80184b6b9a0
    ffffd000`a3cf9ef8 fffff801`84b774e9 : 00000000`0000000a 000000ff`ffffe2fc 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffffd000`a3cf9f00 fffff801`84b75d3a : 00000000`00000000 80000000`00000000 fffff801`84d20f00 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    ffffd000`a3cfa040 fffff801`84ad526f : fffff801`84ab66de 80000000`00000000 80000000`00000000 ffffd000`a3cfa219 : nt!KiPageFault+0x23a
    ffffd000`a3cfa1d8 fffff801`84ab66de : 80000000`00000000 80000000`00000000 ffffd000`a3cfa219 00000000`00000002 : nt!KiAbTryIncrementIoWaiterCount+0x3f
    ffffd000`a3cfa1e0 fffff801`84ab53f0 : ffffd000`9fec0180 fffff801`00000000 ffffe000`425e5880 fffff801`84ad020f : nt!KiAbProcessContextSwitch+0x1be
    ffffd000`a3cfa280 fffff801`84ab4f79 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwapThread+0x40
    ffffd000`a3cfa320 fffff801`84a81c40 : 00000000`00000001 ffffd000`9fec0180 00000000`00000000 fffff6fc`00c26e10 : nt!KiCommitThreadWait+0x129
    ffffd000`a3cfa3a0 fffff801`84aa2918 : fffff801`84d76dd0 ffffe000`425e5ba0 fffff801`84d76dd0 ffffd000`a3cfa400 : nt!ExfAcquirePushLockExclusiveEx+0x2e0
    ffffd000`a3cfa460 fffff801`84a85d29 : 00000000`00000001 ffffe000`40cff080 ffffd000`a3cfa6c0 ffffd000`a3cfa7f0 : nt!MiSystemFault+0x968
    ffffd000`a3cfa500 fffff801`84b75c2f : 00000000`00000001 00000000`00000001 00000000`00000000 ffffc002`00001000 : nt!MmAccessFault+0x769
    ffffd000`a3cfa6c0 fffff801`84a855a0 : fffff801`84b77198 fffff801`84e97628 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f
    ffffd000`a3cfa850 fffff801`84dc2674 : ffffc001`fd72a060 00000000`00000000 fffff801`84a1b000 ffffc001`fd72a060 : nt!ObfReferenceObject+0x20
    ffffd000`a3cfa890 fffff801`84e9776b : ffffc001`fd72a5f0 00000000`00d7db00 ffffd000`00000210 ffffd000`a3cfa9e8 : nt!ObQueryNameStringMode+0x27c
    ffffd000`a3cfa990 fffff801`84b771b3 : ffffe000`425e5880 00000000`00d7da88 ffffd000`a3cfaaa8 00000000`7ef9d000 : nt!NtQueryObject+0x143
    ffffd000`a3cfaa90 00007ffb`53960eda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`00d7da68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`53960eda
    fffff801`84ad526f f780fc02000000001000 test dword ptr [rax+2FCh],100000h
    SYMBOL_NAME:  nt!KiAbTryIncrementIoWaiterCount+3f
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_NAME:  ntkrnlmp.exe
    IMAGE_VERSION:  6.3.9600.17630
    FAILURE_BUCKET_ID:  AV_VRF_nt!KiAbTryIncrementIoWaiterCount
    BUCKET_ID:  AV_VRF_nt!KiAbTryIncrementIoWaiterCount
    FAILURE_ID_HASH_STRING:  km:av_vrf_nt!kiabtryincrementiowaitercount
    FAILURE_ID_HASH:  {447846c0-3554-8894-8818-c8d0c3d254ab}
    Followup: MachineOwner
    5: kd> lmvm nt
    start             end                 module name
    fffff801`84a1b000 fffff801`851af000   nt         (pdb symbols)          c:\symbols\ntkrnlmp.pdb\2BCBB42C1BC741DF9E1D4E2D28DAC9631\ntkrnlmp.pdb
        Loaded symbol image file: ntkrnlmp.exe
        Mapped memory image file: c:\symbols\ntoskrnl.exe\54B0C2F7794000\ntoskrnl.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Timestamp:        Sat Jan 10 07:13:11 2015 (54B0C2F7)
        CheckSum:         0072D721
        ImageSize:        00794000
        File version:     6.3.9600.17630
        Product version:  6.3.9600.17630
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   6.3.9600.17630
        FileVersion:      6.3.9600.17630 (winblue_r7.150109-2022)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Test the boot drive by going to Computer, and right-click on the C drive. Select Properties, Tools, Check Now. Put a check mark in both boxes to set a disk check on the next start up

Similar Topics

Add your comment to this article

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...