1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Repeated IRQL_NOT_LESS_OR_EQUAL BSOD issue

Discussion in 'Windows XP' started by illiards, 2009/06/18.

  1. 2009/06/18
    illiards

    illiards Inactive Thread Starter

    Joined:
    2009/06/18
    Messages:
    4
    Likes Received:
    0
    Help please.
    Repeated IRQL_NOT_LESS_OR_EQUAL BSOD.

    Have setup to save mini dumps and have used WinDbg to look at dump record.

    A different culprit is identified each time.
    BSOD started a few months back and did not coincide with any new hardware install. No hardware install since either.

    Last two dump analyses posed below.

    Dump 1.

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini061709-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Wed Jun 17 19:41:58.933 2009 (GMT+10)
    System Uptime: 0 days 0:16:02.514
    Loading Kernel Symbols
    ..............................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {82bd025c, 1c, 0, 804e37ff}

    Probably caused by : ntoskrnl.exe ( nt!KiIdleLoop+12 )

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

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    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.
    Arguments:
    Arg1: 82bd025c, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000000, 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: 804e37ff, address which referenced memory

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


    READ_ADDRESS: 82bd025c

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt!KeUpdateSystemTime+c2
    804e37ff 3b72fc cmp esi,dword ptr [edx-4]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

    BUGCHECK_STR: 0xA

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from 804dc0d9 to 804e37ff

    STACK_TEXT:
    80550864 804dc0d9 badb0d00 00000000 00000000 nt!KeUpdateSystemTime+0xc2
    805508d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x12


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiIdleLoop+12
    804dc0d9 90 nop

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KiIdleLoop+12

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntoskrnl.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

    FAILURE_BUCKET_ID: 0xA_nt!KiIdleLoop+12

    BUCKET_ID: 0xA_nt!KiIdleLoop+12

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

    Dump 2.

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini060909-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 2600.xpsp_sp2_rtm.040803-2158
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Tue Jun 9 13:15:31.402 2009 (GMT+10)
    System Uptime: 0 days 0:04:48.855
    Loading Kernel Symbols
    .......................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {0, 2, 1, f5d2c385}

    Probably caused by : rdbss.sys ( rdbss!RxTimerDispatch+0 )

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

    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: 00000000, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: f5d2c385, address which referenced memory

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


    WRITE_ADDRESS: 00000000

    CURRENT_IRQL: 2

    FAULTING_IP:
    rdbss!RxTimerDispatch+0
    f5d2c385 8bff mov edi,edi

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: Idle

    LAST_CONTROL_TRANSFER: from 804dcaad to f5d2c385

    STACK_TEXT:
    80550764 804dcaad f5d36360 00000000 8bcb742a rdbss!RxTimerDispatch
    80550880 804dc928 80559580 80559320 ffdff000 nt!KiTimerListExpire+0x122
    805508ac 804dc179 80559980 00000000 000070ab nt!KiTimerExpiration+0xaf
    805508d0 804dc0ed 00000000 0000000e 00000000 nt!KiRetireDpcList+0x46
    805508d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x26


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    rdbss!RxTimerDispatch+0
    f5d2c385 8bff mov edi,edi

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: rdbss!RxTimerDispatch+0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: rdbss

    IMAGE_NAME: rdbss.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 41108015

    FAILURE_BUCKET_ID: 0xD1_W_rdbss!RxTimerDispatch+0

    BUCKET_ID: 0xD1_W_rdbss!RxTimerDispatch+0

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

    Many thx
     
    illiards,
    #1
  2. 2009/06/18
    surferdude2

    surferdude2 Inactive

    Joined:
    2004/07/04
    Messages:
    4,009
    Likes Received:
    23
    The general rule when getting random errors that specify different items each time would be to check your RAM. Run a RAM diagnostic tool or else switch it with known good. If you have more than one RAM stick, test them individually by pulling one, then the other. Sometime just removing and reinstalling can correct the problem if it's due to a poor card edge connection.
     
    surferdude2,
    #2


  3. to hide this advert.

  4. 2009/06/18
    illiards

    illiards Inactive Thread Starter

    Joined:
    2009/06/18
    Messages:
    4
    Likes Received:
    0
    Many thx.
    I will try out your suggestions in regards to removing and reinstalling RAM.
    In the meantime are you able to suggest a good RAM diagnostic tool?

    Cheers
    illiards
     
    illiards,
    #3
  5. 2009/06/18
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.

    The only satisfactory way of testing RAM is to test the installed RAM in various configurations. If you have a single module swap it around the slots. If you have a pair of modules run each one singly, swapping between slots; then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.
     
    PeteC,
    #4
  6. 2009/06/18
    illiards

    illiards Inactive Thread Starter

    Joined:
    2009/06/18
    Messages:
    4
    Likes Received:
    0
    Regards.

    I have a pair of modules so can test as you suggest.

    Stay tuned.

    illiards
     
    illiards,
    #5
  7. 2009/08/03
    illiards

    illiards Inactive Thread Starter

    Joined:
    2009/06/18
    Messages:
    4
    Likes Received:
    0
    Have moved RAM about and tried in different configurations. Still getting repeated irql_not_less_or_equal BSOD.
     
    illiards,
    #6
  8. 2009/08/03
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Make sure all your drivers are up-to-date.

    Also check your hardware... temperature wise... also check your PSU.

    Please enter your System Details. It helps us in answering your questions!
     
    Arie,
    #7

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...