Ergebnis 1 bis 2 von 2
Thema: Driver_irql_not_less_or_equal Hello hello, i am having unregular BSOD with DRIVER_IRQL_NOT_LESS_OR_EQUAL the last 2 were 25.12 and 16.12 so from my point ...
  1. #1
    Xhaido
    Erster Beitrag

    Driver_irql_not_less_or_equal

    Hello hello,

    i am having unregular BSOD with DRIVER_IRQL_NOT_LESS_OR_EQUAL the last 2 were 25.12 and 16.12 so from my point and experience i cant reliable troubleshoot any changes because its so unregular..

    so i just gonna paste everything that might help u hope u have more clue than i do

    so my guess would be according to other forum posts that some driver causese problems with my sys driver/ writes somewhere in the memrory which causes trouble maybe u can find the faulty driver would be awsome!

    Sidenote: not 100% sure but the bsod only occurs while palying League of Legends (just a random thought)




    Minidumps.zip https://www.dropbox.com/s/n1o86bgff6...idump.zip?dl=0




    verborgener Text:
    Loading User Symbols
    Loading unloaded module list
    ..............................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {1284, ff, 66, 1284}

    Probably caused by : Unknown_Image ( nt!KiPageFault+247 )

    Followup: MachineOwner
    ---------

    2: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000001284, memory referenced
    Arg2: 00000000000000ff, IRQL
    Arg3: 0000000000000066, value 0 = read operation, 1 = write operation
    Arg4: 0000000000001284, address which referenced memory

    Debugging Details:
    ------------------


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 10.0.14393.576 (rs1_release_inmarket.161208-2252)

    SYSTEM_MANUFACTURER: System manufacturer

    SYSTEM_PRODUCT_NAME: System Product Name

    SYSTEM_SKU: SKU

    SYSTEM_VERSION: System Version

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 2202

    BIOS_DATE: 09/19/2016

    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT: MAXIMUS VIII RANGER

    BASEBOARD_VERSION: Rev 1.xx

    DUMP_TYPE: 2

    BUGCHECK_P1: 1284

    BUGCHECK_P2: ff

    BUGCHECK_P3: 66

    BUGCHECK_P4: 1284

    READ_ADDRESS: fffff801cd83a338: Unable to get MiVisibleState
    0000000000001284

    CURRENT_IRQL: d

    FAULTING_IP:
    +0
    00000000`00001284 ?? ???

    PROCESS_NAME: System

    CPU_COUNT: 8

    CPU_MHZ: fa8

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    BUGCHECK_STR: AV

    ANALYSIS_SESSION_HOST: DESKTOP-D4EQKS7

    ANALYSIS_SESSION_TIME: 12-25-2016 18:10:55.0350

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    TRAP_FRAME: ffffab0fb50f77d0 -- (.trap 0xffffab0fb50f77d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000300000000 rbx=0000000000000000 rcx=0000000000140014
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
    r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di pl nz na pe nc
    00000000`00000000 ?? ???
    Resetting default scope

    EXCEPTION_RECORD: fffff80c32521320 -- (.exr 0xfffff80c32521320)
    ExceptionAddress: 33c18b4c08418b48
    ExceptionCode: 8348c033
    ExceptionFlags: ccc328c4
    NumberParameters: 265434057
    Parameter[0]: c9010f008b410448
    Parameter[1]: 83485340ccccccc3
    Parameter[2]: c98548d98b4820ec
    Parameter[3]: 8b0c757e39804074
    Parameter[4]: c48348c28b480451
    Parameter[5]: 00000130e8c35b20
    Parameter[6]: ea74c08548d08b48
    Parameter[7]: 480374c984024b8a
    Parameter[8]: 40f980014b8aead3
    Parameter[9]: 4800000001b8d873
    Parameter[10]: d02348c8ff48e0d3
    Parameter[11]: ccccc7ebc033c8eb
    Parameter[12]: 5c89486a74c98548
    Parameter[13]: 8020ec8348570824
    Parameter[14]: 8b48fa8b48000279

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000`00001284 ?? ???

    LAST_CONTROL_TRANSFER: from fffff801cd5e8829 to fffff801cd5dd6f0

    STACK_TEXT:
    ffffbd01`cf8dc358 fffff801`cd5e8829 : 00000000`0000000a 00000000`00001284 00000000`000000ff 00000000`00000066 : nt!KeBugCheckEx
    ffffbd01`cf8dc360 fffff801`cd5e6e07 : a2b5a8fd`20f90ac6 00000000`00000000 46b3a154`4db017b2 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    ffffbd01`cf8dc4a0 00000000`00001284 : fffff801`cd5df1c4 ffffbd01`cf8dc790 fffff801`cd4a0700 ffffab0f`b5134e18 : nt!KiPageFault+0x247
    ffffbd01`cf8dc638 fffff801`cd5df1c4 : ffffbd01`cf8dc790 fffff801`cd4a0700 ffffab0f`b5134e18 ffffffff`ffffffff : 0x1284
    ffffbd01`cf8dc640 fffff80c`32522832 : fffff80c`32521320 000001f2`bbacf471 ffffab0f`b50f77d0 ffffbd01`cf870180 : nt!KiInterruptDispatchNoLockNoEtw+0x44
    ffffbd01`cf8dc7d8 fffff80c`32521320 : 000001f2`bbacf471 ffffab0f`b50f77d0 ffffbd01`cf870180 00000000`00000000 : intelppm!C1Halt+0x2
    ffffbd01`cf8dc7e0 fffff801`cd55f933 : 00000000`00000000 00000000`003bb94f 00000000`00000000 00000000`00000000 : intelppm!AcpiCStateIdleExecute+0x20
    ffffbd01`cf8dc810 fffff801`cd55f13a : fffff80c`300c4ca0 02166ee4`02166ee4 00000000`00000001 00000000`00000001 : nt!PpmIdleExecuteTransition+0x643
    ffffbd01`cf8dca80 fffff801`cd5e074c : 00000000`00000000 ffffbd01`cf870180 ffffbd01`cf87ccc0 ffffab0f`b3d50080 : nt!PoIdle+0x33a
    ffffbd01`cf8dcbe0 00000000`00000000 : ffffbd01`cf8dd000 ffffbd01`cf8d6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: 279f237cf584af91ffd49f09b7e54c6f8d84dda4

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f6c7a71c5f4ab2940d57cd3db913dd13750705a0

    THREAD_SHA1_HASH_MOD: 49a52e3efe0d80d6ec790ffb40a09425b40d5496

    FOLLOWUP_IP:
    nt!KiPageFault+247
    fffff801`cd5e6e07 33c0 xor eax,eax

    FAULT_INSTR_CODE: ffb0c033

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!KiPageFault+247

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    IMAGE_VERSION: 10.0.14393.576

    MODULE_NAME: Unknown_Module

    BUCKET_ID: RAISED_IRQL_USER_FAULT_AV

    DEFAULT_BUCKET_ID: RAISED_IRQL_USER_FAULT_AV

    PRIMARY_PROBLEM_CLASS: RAISED_IRQL_USER_FAULT

    FAILURE_BUCKET_ID: RAISED_IRQL_USER_FAULT_AV

    TARGET_TIME: 2016-12-25T07:02:17.000Z

    OSBUILD: 14393

    OSSERVICEPACK: 576

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-12-09 10:23:02

    BUILDDATESTAMP_STR: 161208-2252

    BUILDLAB_STR: rs1_release_inmarket

    BUILDOSVER_STR: 10.0.14393.576

    ANALYSIS_SESSION_ELAPSED_TIME: 911

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:raised_irql_user_fault_av

    FAILURE_ID_HASH: {1ae3b702-9567-a461-faae-d89b06459582}

    Followup: MachineOwner
    ---------
    Geändert von Wolko (27.12.2016 um 09:27 Uhr) Grund: Spoiler gesetzt.

  2. #2
    Ari45
    gehört zum Inventar Avatar von Ari45

    AW: Driver_irql_not_less_or_equal

    Willkommen im Forum, @Xhaido!
    In einem deutschen Forum sollte man sich bemühen, wenigstens ansatzweise deutsch zu schreiben, und sei es mittels eines Translaters.
    Die Dumpfile werde ich mir nicht herunter laden. Lade die Dumpfile hier als Anhang ins Forum hoch, dann wird es hier auch Mitglieder geben, die sich diese Datei ansehen.

    Ohne selbst debugged zu haben, kann ich jetzt schon vermuten, dass wahrscheinlich intelppm.sys versucht hat, eine Funktion in einem nicht geladen Treiber auf zu rufen.

Lesezeichen


  • An Google übertragen Google
  • -->

    Berechtigungen

    • Neue Themen erstellen: Nein
    • Themen beantworten: Nein
    • Anhänge hochladen: Nein
    • Beiträge bearbeiten: Nein
    •  

    1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162