TechSpot

BSOD unknown hardware error. Possible IRQ conflict.

By CSHIFT
Oct 19, 2007
  1. Hello everyone!

    This my first post so go easy on me.

    The Issue:
    Client's computer crashes almost everyday.
    Steps Taken:
    Reinstalled RAM
    Performed Windows Updates (hardware)
    -Updated Ethernet Driver
    Ran WinDbg on the Minidump Files
    -The error that I found is:

    *******************************************************************************
    * *
    * 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: ffe3d420, 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: 80502e58, address which referenced memory

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


    READ_ADDRESS: ffe3d420

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt!KiSwapThread+8c
    80502e58 8a4f58 mov cl,byte ptr [edi+58h]

    CUSTOMER_CRASH_COUNT: 5

    DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: System

    LAST_CONTROL_TRANSFER: from 804fcc66 to 80502e58

    STACK_TEXT:
    bacffd48 804fcc66 899de118 005637bc 89e3d3c8 nt!KiSwapThread+0x8c
    bacffd74 80537adc 00000001 00000001 00000000 nt!KeRemoveQueue+0x22a
    bacffdac 805cea08 899de118 00000000 00000000 nt!ExpWorkerThread+0xcc
    bacffddc 8054546e 80537a10 00000001 00000000 nt!PspSystemThreadStartup+0x34
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiSwapThread+8c
    80502e58 8a4f58 mov cl,byte ptr [edi+58h]

    SYMBOL_STACK_INDEX: 0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 45e5484a

    SYMBOL_NAME: nt!KiSwapThread+8c

    FAILURE_BUCKET_ID: 0xA_nt!KiSwapThread+8c

    BUCKET_ID: 0xA_nt!KiSwapThread+8c

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

    Please find the attached Minidump files.

    I would like to thank all of you in advance :)

    I believe that this has been an issue ever since we put the computer together 1 month ago. I am not really sure what to do at this point, any input would be greatly appreciated.

    Thank You
     
  2. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,088

    The dump log you've posted has crashed at IRQL 1c, and this is almost always hardware related. RAM tops the list followed by CPU. What's the RAM setup? Try running Memtest.

    BugCheck 1000000A, {ffe3d420, 1c, 0, 80502e58} <-- IRQL 1c.
    Probably caused by : memory_corruption ( nt!MmProbeAndLockPages+2da )
     
  3. CSHIFT

    CSHIFT TS Rookie Topic Starter

    Thank You for the quick reply.

    I will run memtest ASAP. However, I seriously doubt that it's the RAM because I replaced it 1 week ago.
     
  4. CSHIFT

    CSHIFT TS Rookie Topic Starter

    Wow !!!

    What a huge waste of time. The problem turned out to be that the case fan in front of the hard drives crapped out. In frustration I decided to replace the ram, and opened the case. Once I touched one of the hard drives by accident and got a blistering burn, I immediately knew where the problem was.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

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