| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 60913 | 2005-08-17 23:15:00 | Kernal Stack In Page Error | DigitalMessiah (7649) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 381939 | 2005-08-17 23:15:00 | hey guys long time no see... don't know if you remember me, but im the one that was trying to directly lan XP with ME without the router a while back.... ok so i have had this problem for a while and i just thought i'd come back and bring it up now... i'm running windows XP Pro , latest video drivers... all the service packs and security updates.... no viruses, no spyware.... latest sound drivers... all the required stuff.... and after about maybe 6 months after a format, i will start getting blue screens saying Kernal Stack Inpage error, which im sure many of you have had before.... then it dumps the physical memory and i'm forced to reboot, it happens randomly, sometimes after i'm done playing a game, or when im doing a virus scan, mainly when im using a chunk of my physical memory.... but it starts happening around 6 months after a format, i do the same things prior to it occuring, gaming, scanning, e.t.c and then it gets so bad i need to reformat..... any idea how to prevent this from happening... because i lose ALOT of data when i reformat, i have an 80 gig HD while my mom only has 10 gig so i lose all my torrents.... any help would be appreciated |
DigitalMessiah (7649) | ||
| 381940 | 2005-08-17 23:24:00 | Dodgy RAM or a dying hard drive. | pctek (84) | ||
| 381941 | 2005-08-17 23:28:00 | i DID have a blue screen saying: Unmountable_Boot_Volume one time, cuz i had a blue screen when defragging my computer.... but i fixed it with a scan disk.... been kinda afraid to defrag again... also i got 4 ram bays, all filled, equalling out to 768.... |
DigitalMessiah (7649) | ||
| 381942 | 2005-08-17 23:40:00 | Try this memory test. http://www.memtest86.com/ Also look at these pages on how to trouble shoot this problem. Troubleshooting "Stop 0x00000077" or "KERNEL_STACK_INPAGE_ERROR" support.microsoft.com Troubleshooting "Stop 0x00000077" or "KERNEL_STACK_INPAGE_ERROR" support.microsoft.com aumha.org hth |
johnboy (217) | ||
| 381943 | 2005-08-18 00:32:00 | couldnt get that memtest to work... i don't have a floppy drive... and my CD burner and cd burner program is on the fritz.... so i tried mounting the image on a virtual drive, but it didnt work.... umm i did the other 3 links... all i could tell is, it was NOT a virus.... :/ if you have any other memory testers... ill do it |
DigitalMessiah (7649) | ||
| 381944 | 2005-08-18 00:39:00 | Try this. oca.microsoft.com hth |
johnboy (217) | ||
| 381945 | 2005-08-18 03:51:00 | Not a Boot Sector Virus • View the System Log in Event Viewer for additional error messages that help you determine the device that is causing the error. • Bad block. Stop 0x77 is caused by a bad block in a paging file, or a disk controller error, or in extremely rare cases it is caused when non-paged pool resources are unavailable. • If the first and second parameters are 0, then the stack signature was not found in the kernel stack. The cause of this issue is defective hardware. If the I/O status is C0000185 and the paging file is on a SCSI-based hard disk, you should verify the disk cabling and SCSI termination. • If the I/O status code is 0xC000009C or 0xC000016A, this normally indicates that the data could not be read from the disk due to a bad block. • If you can restart your computer after the error message, Autochk runs automatically and tries to map out the bad sector. If for some reason Autochk does not scan the hard disk for errors, manually start the disk scanner. If your computer is formatted with the NTFS file system, run Chkdsk /f /r on the system partition. You must restart your computer before the disk scan begins. If you cannot start your computer due to this issue, use the Command Console and run Chkdsk /r. • Defective or unreliable random access memory (RAM) is another common cause of this issue. • Verify that all the adapter cards in your computer are properly seated. • Ensure that all adapter card contacts are clean. • Disable system caching in the BIOS to see if this resolves the error. • If this does not resolve the issue, your computer mainboard (motherboard) may be damaged. |
pctek (84) | ||
| 381946 | 2005-08-19 16:18:00 | ok i mounted that image and it opened the folder, I386, and inside that folder was a 247kb file, with NO file extension.... the file name is WINDIAG... what do i do with that file extensionless file? also i woke up this morning to the blue screen the error was this STOP: 0x00000007 or somethin like that.... many zeroes before a real number i remember that, was just half a sleep so i neglected to write it all down haha |
DigitalMessiah (7649) | ||
| 381947 | 2005-08-20 00:35:00 | Stop 0x00000007 As I have said either you have faulty ram or your hard drive has problems . . distec . nl/infosheets/stop_messages . htm" target="_blank">www . distec . nl |
pctek (84) | ||
| 381948 | 2005-08-22 16:13:00 | turns out you guys were right, a little problem that i had forgotten to mention just happened again... more often then not, when i either get the blue screen and shut it off, and turn it back on, or shut down normally and turn it back on.... it will boot up the BIOS and then say "The amound of physical memory has decreased" press f1 to continue or press f2 to run the setup utility.... so i then shut it off right there again .... and turn it back on.... then it says "The amound of system memory has changed" meaning that it went back to normal.... im pretty mad though, two of the ram chips i have in here are no older then 2 years.... |
DigitalMessiah (7649) | ||
| 1 2 | |||||