WinXP SP2 Stop error 0x0A

By Bal2001bc ยท 4 replies
Mar 15, 2007
  1. Hi

    Can someone make sense of this Mini Dump as WinXP keeps crashing and I am not sure what is causing it.

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

    Debugging Details:

    READ_ADDRESS: 00000028


    80515621 8b4e28 mov ecx,dword ptr [esi+28h]





    LAST_CONTROL_TRANSFER: from 804dbb37 to 80515621

    805501d0 804dbb37 00000000 0000000e 00000000 nt!PopProcessorIdle+0xa7
    805501d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


    80515621 8b4e28 mov ecx,dword ptr [esi+28h]


    SYMBOL_NAME: nt!PopProcessorIdle+a7

    FOLLOWUP_NAME: MachineOwner


    IMAGE_NAME: ntoskrnl.exe


    FAILURE_BUCKET_ID: 0xA_nt!PopProcessorIdle+a7

    BUCKET_ID: 0xA_nt!PopProcessorIdle+a7

    Followup: MachineOwner

    eax=00000000 ebx=ffdffc70 ecx=ffdffc70 edx=0000000d esi=00000000 edi=823b6498
    eip=80515621 esp=805501bc ebp=805501d0 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    80515621 8b4e28 mov ecx,dword ptr [esi+28h] ds:0023:00000028=????????
    ChildEBP RetAddr Args to Child
    805501d0 804dbb37 00000000 0000000e 00000000 nt!PopProcessorIdle+0xa7 (FPO: [Non-Fpo])
    805501d4 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10 (FPO: [0,0,0])

    As far as I can see ecx,dword ptr [esi+28h] seems to be Firewire?? but I don't know for sure.

    Am I reading the dump wrong?

  2. riekmaharg2

    riekmaharg2 TS Rookie Posts: 137

    I dont no much about minidumps, however I have noticed it has the word IMAGE_NAME: ntoskrnl.exe. Maybe that file is corrupt or something. Try this:

    Missing or corrupt ntoskrnl.exe file

    If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.

    Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
    Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
    In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
    Select the operating system you wish to fix, and then enter the administrator password.
    Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
    You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
    Type exit to reboot the computer.
  3. kwspony

    kwspony TS Booster Posts: 121

    Download and run Memtest86 v1.70. There is a link in the sticky. Let it run for at least 7 passes. It will test your memory. The error with the letter "a" reference may be bad RAM.
  4. Bal2001bc

    Bal2001bc TS Rookie Topic Starter

    I started running this but after an 30 mins to an hour, so I gave up.

    How long are you suppose to leave it running for?

  5. kwspony

    kwspony TS Booster Posts: 121

    I would let it run for 7 to 10 passes. On the screen you will see the number of passes. It does I think 8 tests per pass.
Topic Status:
Not open for further replies.

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...