Tags: 0xa, computer, continually, crashes, drive, erased, error, havechecked, message, microsoft, msdn, oxa, programs, ram, repaired, software, thexp, troubleshooting

OXA error troubleshooting

On Microsoft » Microsoft XP

7,212 words with 4 Comments; publish: Sun, 01 Jun 2008 11:41:00 GMT; (331155.76, « »)

My computer continually crashes and I get a 0XA error message. I have

checked the RAM, the hard drive, erased recently added programs, repaired the

XP installation and nothing has solved the problem. Any suggestions?

Would a clean install of XP be likely to help?

All Comments

Leave a comment...

  • 4 Comments
    • STOP 0x0A:IRQL_NOT_LESS_OR_EQUAL

      http://www.aumha.org/a/stop.php#0x0a

      Leonard Grey

      Errare humanum est

      BitesBack wrote:

      > My computer continually crashes and I get a 0XA error message. I have

      > checked the RAM, the hard drive, erased recently added programs, repaired the

      > XP installation and nothing has solved the problem. Any suggestions?

      > Would a clean install of XP be likely to help?

      #1; Sun, 01 Jun 2008 11:42:00 GMT
    • "Ed Metcalfe" wrote:

      > "BitesBack" <BitesBack.windows-xp.questionfor.info.discussions.microsoft.com> wrote in message

      > news:966D2D76-8762-47AC-98D8-D5AB2989A7AF.windows-xp.questionfor.info.microsoft.com...

      > Do you mean you are getting a Blue Screen?

      > We'd need more details of the error message you are receiving before we can

      > give a proper answer.

      > If it's a software problem then a clean install of XP may solve the problem

      > until you reinstall the offending software (and as you will not know what it

      > is this is likely). If it's a hardware problem then reinstalling XP will

      > almost certainly achieve nothing at all. My advice is (as it almost always

      > is when somebody is talking about formatting/reinstalling Windows to fix a

      > problem) don't bother.

      > Ed Metcalfe.

      >

      > Yes, I get a blue screen.

      The entire error code is:

      STOP: 0X0000000A (0X00000000, 0X00000002, 0X00000000, 0X80519F24)

      If a clean install is not the answer are you suggesting that the situation

      is essentailly hopeless?

      Thanks

      #2; Sun, 01 Jun 2008 11:43:00 GMT
    • BitesBack <BitesBack.windows-xp.questionfor.info.discussions.microsoft.com> wrote:

      >The entire error code is:

      >STOP: 0X0000000A (0X00000000, 0X00000002, 0X00000000, 0X80519F24)

      >If a clean install is not the answer are you suggesting that the situation

      >is essentailly hopeless?

      >Thanks

      Your error condition is being triggered by whichever device driver,

      application program or Windows component (most likely a device driver)

      is using memory address 0X80519F24.

      The following procedure should help you to identify the culprit, if it

      is a device driver:

      *******

      Identifying the cause of STOP errors using PSTAT & Excel

      Many times when a STOP error occurs the information provided does not

      specifically identify the application, device driver, or other

      component file where the error occurred. However the 4 parameters

      associated with the STOP (bugcheck) code will very often include one

      that is the address where the error occurred. You first need to look

      up the detailed information about the specific STOP code in order to

      determine if the address is included and if so which of the 4

      parameters has the address.

      You can identify the meaning of each of the parameters for your

      specific STOP code at:

      http://msdn2.microsoft.com/en-us/library/ms789516.aspx

      The second step in the procedure is to identify the addresses that

      each active process is being loaded at. The PSTAT utility will

      provide this information. On some systems the PSTAT utility may

      already be present. Check this by opening a Command Prompt window

      (Start - Run - CMD) and entering the following command:

      PSTAT /?

      If PSTAT is not on your computer you can download it free from

      Microsoft. The download is called "Windows XP Service Pack 2 Support

      Tools" and it is available from

      http://www.microsoft.com/downloads/details.aspx?FamilyId=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en

      With PSTAT installed on your computer the next step is to open a

      Command Prompt window again (Start - Run - CMD) and generate a report

      with PSTAT. Because you need to copy part of the information from

      this report (and only part) it is best to create the report as a text

      file. In the Command Prompt window enter the following command:

      PSTAT > C:\JUNK\PSTAT.TXT

      You may change C:\JUNK\ to whatever drive and folder that you want to

      save the report into.

      Now open the saved file in Notepad. Start - Run - NOTEPAD

      C:\JUNK\PSTAT.TXT

      Scroll down the file, about 80% of the way to the end of the file and

      you will find a head line:

      ModuleName Load Addr Code Data Paged LinkDate

      It is the information from this line to the end of the file that we

      want to copy from this file and save as a separate file. Select the

      block of text and copy it to the clipboard. Open a new notepad window

      and paste the clipboard contents into it. Save this file under a

      different name. I use PSTAT2.TXT and put it into the same C:\JUNK

      folder.

      Now launch Microsoft Excel and use File - Open to bring the PSTAT2.TXT

      file into Excel. Excel will automatically parse the file into

      columns. Once this is done use DATA - SORT to sort the entire

      spreadsheet based on the value in Column B (Load Addr).

      It is now a simple task to read down the addresses until you find the

      highest value that is less than the address where the error occurred.

      That module (name in column A) is the prime suspect for the cause of

      your error.

      ********

      Good luck

      Ron Martell Duncan B.C. Canada

      Microsoft MVP (1997 - 2008)

      On-Line Help Computer Service

      http://onlinehelp.bc.ca

      Syberfix Remote Computer Repair

      "Anyone who thinks that they are too small to make a difference

      has never been in bed with a mosquito."

      #3; Sun, 01 Jun 2008 11:44:00 GMT
    • I'm getting the blue screen error. It's because of oxe errors. Can't find

      the drivers to delete them..help.

      "Ed Metcalfe" wrote:

      > "BitesBack" <BitesBack.windows-xp.questionfor.info.discussions.microsoft.com> wrote in message

      > news:966D2D76-8762-47AC-98D8-D5AB2989A7AF.windows-xp.questionfor.info.microsoft.com...

      > Do you mean you are getting a Blue Screen?

      > We'd need more details of the error message you are receiving before we can

      > give a proper answer.

      > If it's a software problem then a clean install of XP may solve the problem

      > until you reinstall the offending software (and as you will not know what it

      > is this is likely). If it's a hardware problem then reinstalling XP will

      > almost certainly achieve nothing at all. My advice is (as it almost always

      > is when somebody is talking about formatting/reinstalling Windows to fix a

      > problem) don't bother.

      > Ed Metcalfe.

      >

      >

      #4; Sun, 01 Jun 2008 11:45:00 GMT