UNSOLVED

ms_moore

updated

19 years ago

M

ms_moore

1 Rookie

85 Posts

0

13964

September 18th, 2007 01:00

KERNEL_STACK_INPAGE_ERROR

I've been getting a BSOD about twice a week with the following
stop error: 0x00000077 (0xC000000E, 0X00000000, 0x00805000)

Been researching it all day and finding nothing.
The application event viewer has hanging errors for msaccess and iexplorer
The system event viewer last error said it was a disk error.

Trying to narrow it down to hardware or software.

My system stats are
System Type:Dimension 4400
Ship Date: 3/18/2002
Dell IBU: Americas Quantity
Parts #
Part Description 1 1K529 ASSEMBLY, CARD (CIRCUIT), PLANAR (MOTHERBOARD), DIM4400, AUDIO 1 1K670 PROCESSOR, 80531, 1.7G, 0, 400FSB, SOCKET N, D0 1 9C487
KEYBOARD, 104, 6P, UNITED STATES, SILITEK, MIDNIGHT GRAY 1 735HE
MOUSE, PERSONAL SYSTEM 2, 6P, 2BTN, WHEEL, 1.3A, MICROSOFT, MIDNIGHT GRAY 1 3K113
DUAL IN-LINE MEMORY MODULE, 256, 266M, 32X64, 8K, 184 1 1K636
MODEM, V.92, DATA FAX, INTERNAL, PATRON, ASIA, LATIN AMERICA, NORTH AMERICA 1 611WY COMPACT DISK DRIVE, 128K, I, 5.25"
FORM FACTOR, 20/48X, LTN-486,
CHASSIS 2001 1 3K595 CARD (CIRCUIT),
GRAPHICS, 64MB, NV11, TELEVISION OUTPUT, SECOND 1 8G157 DISPLAY, CATHODE-RAY TUBE, 17, DUAL, M782, MIDNIGHT GRAY, DELL AMERICAS ORGANIZATION 1 8F371
FLOPPY DRIVE, 1.44M, 3.5" FORM FACTOR, 3MD, NO BEZEL, NEC CORPORATION, 419, CHASSIS 2001 1 2K223
HARD DRIVE, 40G, I, 3.5" FORM FACTOR, 1N, 7.2K, WD-XL40 1 0E784 KIT,
SOFTWARE, OFCXPSB, ENGLAND/ENGLISH, ORIGINAL EQUIPMENT MFGR. 1 9K255 KIT, SOFTWARE, OVERPACK, WINDOWS XP PROFESSIONAL, COMPACT DISKETTE W/DOCUMENTATION, ENGLAND/ENGLISH, A01 1 7C712 CARD (CIRCUIT),
NETWORK, ETHERNET, 10/100, CNET TECHNOLOGY INC, REVISION

Thanks

Message Edited by ms_moore on 09-18-2007 05:09 PM
  • ManyDimensions

    1318 Posts

    671

    0

    Posted September 18th, 2007 01:00

    ms_moore
     
    This is the Microsoft troubleshooting page for the referenced stop error"
     
     
    This points to hardware, specifically bad sectors. Although this may not be the only problem, that is where I would start using chkdsk.
     
    MD
  • mombodog

    2 Intern

    12735 Posts

    671

    0

    Posted September 18th, 2007 04:00

    Run the Dell diagnostics extended tests if chkdsk fails to give results
     
     
     
     
     
     
    http://kb.wisc.edu/helpdesk/page.php?id=5097  how to run chkdsk from the XP CD
  • ManyDimensions

    1318 Posts

    671

    0

    Posted September 18th, 2007 13:00

    mombodog
     
    That face slap avatar is hysterical..........love it!
     
    MD


    Message Edited by ManyDimensions on 09-18-2007 09:22 AM
  • ms_moore

    1 Rookie

    85 Posts

    671

    0

    Posted September 18th, 2007 20:00

    Thanks for the replies and the funny avatars and signature!

    I have some questions:

    1) I ran chkdsk /r via the cmd prompt, restarted the computer and ran. How is this different then using the chkdsk in the recovery console?

    2) I did go to the link http://support.microsoft.com/kb/315266 but could not understand what the following meant:

    This issue can occur if a requested page of kernel data could not be read from the paging file into memory, or the master boot record is infected with a virus. To further determine the possible cause, you must properly interpret the error message. If both the first and third parameters are zero, then the four parameters are defined as:

    1. 0 (zero)

    2. Page Table Entry (PTE) value at time of error

    3. 0 (zero)

    4. Address of signature on kernel stack

    If either the first or the third parameter is not a zero, then the following definitions apply:

    1. Status code

    2. I/O status code

    3. Page file number

    4. Offset into page file

    Thanks again!

    Message Edited by ms_moore on 09-18-2007 05:02 PM
  • mombodog

    2 Intern

    12735 Posts

    671

    0

    Posted September 18th, 2007 21:00

    " How is this different then using the chkdsk in the recovery console?"
     
    Not sure there is any difference other than you can specify switches to be used with chkdsk in recovery console.
     
    2. takes allot of reading and research to understand that stuff, very technical.
     
    a. " data could not be read from the paging file into memory"  Bad memory.
     
    b. "the master boot record is infected with a virus"   explains itself, you have to do an offline virus scan, either by using a bootable CD with a portable virus scanner on it, or mount the hard drive in another PC and scan the drive
     
    c. "you must properly interpret the error message. If both the first and third parameters are zero, then the four parameters are defined as:"
    BSOD error messages are broken down into sections
     
     0x00000077 ( 0xC000000E, 0X00000000, 0x00805000)
    status code   I/O status code Page file number Offset into page file
     
    red is first parameter and so on. Since yours is not 0 for the first and third, then the second set of definition codes apply to this particular set.
     
    When you get a bsod, it creates a mini dump file in C:\Windows\minidump, if you can get to this file you can analyze it to find out what is the most likely cause, in your case you have to copy the file to another XP PC and analyze it on that PC since yours cannot boot. This is the best way to troubleshoot a bsod error. Not easy.
     
    Most likely causes, from most likely to least likely
    1- File system corruption, chkdsk should repair this.
    2- Bad stick of memory
    4- Failing hard drive
    5- Disk controller error or failure, bad motherboard.
     

     


    Message Edited by mombodog on 09-18-2007 05:40 PM
  • ms_moore

    1 Rookie

    85 Posts

    671

    0

    Posted September 18th, 2007 23:00

    Thank you for a such a thorough explanation. That was most excellent! Currently, I've been running a diagnostic test with the included cd (since there was no hidden diagnostic test at the boot screen). Via an extended test it showed that the hard drive has 69 errors and then it got jammed up and I had to clt-alt-del to stop the test. I did a quick test of everything and it showed no errors, but the extended did. My conclusion is that I need a new hard drive. Thanks for the input! Kasi

    Message Edited by ms_moore on 09-18-2007 07:41 PM
  • mombodog

    2 Intern

    12735 Posts

    671

    0

    Posted September 18th, 2007 23:00

    "showed that the hard drive has 69 errors"
     
    did you run the      chkdsk /r      from the recovery console?
  • ms_moore

    1 Rookie

    85 Posts

    671

    0

    Posted September 19th, 2007 02:00

    I ran the chkdsk via the recovery console and it fixed a disk error. I'm going to run a diagnostics check again just to verify.

    Thanks again!
  • ms_moore

    1 Rookie

    85 Posts

    146

    0

    Posted September 22nd, 2007 20:00

    Thanks for the info.
    That's what I was thinking.
  • shesagordie

    12 Elder

    46017 Posts

    146

    0

    Posted September 22nd, 2007 20:00

    ms_moore

    It would seem that the hard drive is bad, you need to replace it.

    Bev.




    ===================================================
    Please don't send me questions about your system by DCF Messenger.
    Post the issue in the appropriate Board, where they will be answered.