[CuteSmartNBlonde]

Okay, I have researched this topic for days and days and I am still clueless on what's going on or what to even do. Whenever I run a virus scan (ANY) towards the end I get a BSOD with the error:

Stop: Kernel_stack_inpage_error 0x00000077 (0xC000000E, 0xC000000E, 0x0000000, 0x0D4E2000)

I tried to do that disc scan thing that automatically began when I restarted my computer. When I did that it completed almost 4 of the 5 steps and then I got another BSOD with an error that I can't recall but it stopped and froze also wouldn't let me log in to windows kept trying to run the check disk thing. It kept doing that until I went into the BIOS and reset the settings to default. It then allowed me to system restore and now I am able to log on the computer again. Just recently the computer has also started acting slow. If you have any idea on what is going on please let me know. :up:

 

[schusterjo]

Troubleshooting "Stop 0x00000077" or "KERNEL_STACK_INPAGE_ERROR"

 

[CuteSmartNBlonde]

I appreciate you posting that. I have looked at that many times, but I am not completely computer literate yet. I need it broken down into blonde terms.

 

[schusterjo]

Press F8 repeatedly while XP is Rebooting in order to enter safemode, or start/run/type msconfig/boot.ini tab/check safemode... and run Scandisk and Defrag your Computer
to chkdsk start/mycomputer/right click on your hard drive/properties/tools/ there you will see error checking and defrag. run both.
Run your antivirus program in safemode.
post back, if you have already followed those direction (in safemode you must be in to run) then let me know.

 

[CuteSmartNBlonde]

did that tonight, while in safe mode doing the defrag I got a stop error 0x000000f4. I have no idea what's going on

 

[Frank4d]

I did some Googling and found 0x00000077 and 0x000000F4 errors are both hard drive related. Some sites suggested the errors could be caused by a bad IDE cable, or if the hard drive is connected to an IDE cable as a slave and there is no master device connected to the same cable.

If you aren't sure whether "hard drive is connected to an IDE cable as a slave and there is no master device connected to the same cable" applies, you can check it when you boot the computer. At POST (before Windows starts) the screen should show Primary Master and Slave, and Secondary Master and Slave drives.

 

[schusterjo]

I did some Googling and found 0x00000077 and 0x000000F4 errors are both hard drive related.

not "always" hard drive related, more like "hardware" related, not always "hardware" related either could be other things as well such as simply disabling caching shadowing in the bios. Could be faulty ram, just can't narrow it down to one thing without running a few more test.

Okay lets run a few more test before we go pointing fingers at what it may be.
Have you added anything new to your computer lately? hardware or software? remove any software lately?

1.open the case and (unplug from the wall for a few minutes before opening, touch the inside of the case somewhere while touching pats)
Verify that all the adapter cards in your computer are properly seated. (simply push down on cards to make sure they are all the way down in the slots and any end of the cable make sure it is all the way into the connector) make sure your hard drives are jumped correctly (only have one make it master, two the one at the end of the cable is master the one in the middle is slave,)

2. Download memtest86 and run it.

3.
A very good resource page on BSODs
http://aumha.org/win5/kbestop.htm
(left side column look for kernel paging error+ read all the other info on determining your problem)

General Troubleshooting of STOP Messages
If you can't find a specific reference to your problem, running through the following checklist stands a good chance of resolving the problem for you. This checklist is also usually the best approach to troubleshooting some specific Stop messages, such as 0x0A and 0x50.

1. Examine the "System" and "Application" logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open "Administrative Tools" in the Control Panel then launch Event Viewer.
2. If you've recently added new hardware, remove it and retest.
3. Run hardware diagnostics supplied by the manufacturer.
4. Make sure device drivers and system BIOS are up-to-date.
5. However, if you've installed new drivers just before the problem appeared, try rolling them back to the older ones.
6. Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.
7. Confirm that all of your hardware is on the Hardware Compatibility List. If some of it isn't, then pay particular attention to the non-HCL hardware in your troubleshooting.
8. Check for viruses.
9. Investigate recently added software.
10. Examine (and try disabling) BIOS memory options such as or caching shadowing.

4.

1) Install microsoft debugging tools from http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
2) Create folder c:\symbols
3) Download and install the http://www.microsoft.com/whdc/devtoo...nstallx86.mspx
4) Locate your latest memory.dmp file- C:\windows\Minidump\Mini011005-01.dmp or whatever
4) Open a CMD prompt and cd\program files\debugging tools for windows\
5) Type the following stuff:

Code:
c:\program files\debugging tools>kd -z C:\windows\Minidump\Mini011005-01.dmp
kd> .logopen c:\debuglog.txt
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q

Now you have a debuglog.txt in c:\, open it in notepad and post the content to this thre.ad
http://forums.techarena.in/showthread.php?t=80584 (start your own post if you decide to use this forum)

Sometimes Bsods can be a pain to figure out what the issue is. That should give you some resources to diagnose what it is and correct it.