TechSpot

driver_irql_not_less_or_equal BSOD

By schm00))
Sep 28, 2005
  1. I have built a new box and it consistantly gets a BSOD. The event seems to be at random intervals.
    The parts used were:
    Foxconn 648/661 socket 478
    Cel 2.4, 512 RAM, Samsung 52X CDROM
    Seagate 40, XP Pro Sp1

    I have done some debugging but do not know how to decifer the latest results see below:

    > *******************************************************************************
    > *
    > *
    > * 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: 808b537c, memory referenced
    > Arg2: 00000002, IRQL
    > Arg3: 00000000, value 0 = read operation, 1 = write operation
    > Arg4: 804e60a4, address which referenced memory
    >
    > Debugging Details:
    > ------------------
    >
    >
    > READ_ADDRESS: 808b537c
    >
    > CURRENT_IRQL: 2
    >
    > FAULTING_IP:
    > nt!KiDeliverApc+16a
    > 804e60a4 8b4f1c mov ecx,[edi+0x1c]
    >
    > DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
    >
    > BUGCHECK_STR: 0xA
    >
    > LAST_CONTROL_TRANSFER: from 804de855 to 804e60a4
    >
    > TRAP_FRAME: f3519ca4 -- (.trap fffffffff3519ca4)
    > ErrCode = 00000000
    > eax=808b536c ebx=848b5364 ecx=848b536c edx=f3519d24 esi=848b5330
    > edi=808b5360
    > eip=804e60a4 esp=f3519d18 ebp=f3519d4c iopl=0 nv up ei pl nz na pe
    > nc
    > cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
    > efl=00010202
    > nt!KiDeliverApc+0x16a:
    > 804e60a4 8b4f1c mov ecx,[edi+0x1c]
    > ds:0023:808b537c=????????
    > Resetting default scope
    >
    > STACK_TEXT:
    > f3519d4c 804de855 00000001 00000000 f3519d64 nt!KiDeliverApc+0x16a
    > f3519d4c 7c90eb94 00000001 00000000 f3519d64 nt!KiServiceExit+0x58
    > WARNING: Stack unwind information not available. Following frames may be
    > wrong.
    > 01e7fd54 71a6104f 00000328 0000032c 00000002
    > Unknown_Module_7c900000+0xeb94
    > 01e7fdd4 71abf6cf 0000032c 01e7fe44 00000001 mswsock!WSPRecvFrom+0x1f0
    > 01e7fe18 71ad303e 0000032c 01e7fe44 00000001 WS2_32!WSARecvFrom+0x7d
    > 01e7fe4c 00cdaf1f 0000032c 00000000 00000100 WSOCK32!recvfrom+0x39
    > 01e7fe74 00cdac60 01e7fe90 0000274d 0000274d SSNETLIB+0xaf1f
    > 01e7ffb4 7c80b50b 00ce1c60 00000000 00000000 SSNETLIB+0xac60
    > 01e7ffec 00000000 00cdaa70 00ce1c60 00000000 kernel32!BaseThreadStart+0x37
    >
    >
    > FOLLOWUP_IP:
    > nt!KiDeliverApc+16a
    > 804e60a4 8b4f1c mov ecx,[edi+0x1c]
    >
    > SYMBOL_STACK_INDEX: 0
    >
    > FOLLOWUP_NAME: MachineOwner
    >
    > SYMBOL_NAME: nt!KiDeliverApc+16a
    >
    > MODULE_NAME: nt
    >
    > IMAGE_NAME: ntoskrnl.exe
    >
    > DEBUG_FLR_IMAGE_TIMESTAMP: 42250ff9
    >
    > STACK_COMMAND: .trap fffffffff3519ca4 ; kb
    >
    > FAILURE_BUCKET_ID: 0xA_nt!KiDeliverApc+16a
    >
    > BUCKET_ID: 0xA_nt!KiDeliverApc+16a
    >
    > Followup: MachineOwner
    >
    This from a full memory dump which is too large to attach
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.