gdputerseffedagain

[happygobrokey]

yes my computer is yet again giving me a hard time. it will randomly crash following a click sound, i feel like it's running out of memory, but i am never doing anything intensive. like it hangs when i try to open some program or even choosing an open window from the bottom bar, then on restart it gives me all these errors, sometimes it goes to a dos screen and comes up disk error, other times it says missing/corrupt file "/windows/system/config" or something, and occasionally it will boot windows normally.

most of the time i just reboot, press f6, no boot to safe mode etc menu and the reboot fails. off and on a couple more times and i can get windows. wtf? after this happened once, i even put in the bootable cd, and it seemed to have fixed it, i figure maybe copying some windows files from it to repair.

over a week later it happened a second time. figuring the end was close i copied everything i wanted to keep over to the external drive and format/reinstalled windows. first day, i stayed offline, and installed all my programs i had, all the antivirus, some of the recreational programs. rebooted several times over the course.

next day, plugged in, got IE7, updated antivirus etc. and visited websites. no p2p/limewire/torrent activity. used msn, and watched movies on my hard drive. but yet i get the same fails as before, after formatting the hard drive and putting fresh windows.

i'm worried i'm uberhacked, because i think my keyboard is cacking up sometimes too, the p key actually deletes sometimes and another key is like home or up arrow and makes you start typing in the middle of your sentence. hate this scheisswindows! that or my computer is just dead. i don't think i'm overrunning my ram though, i never have before, and i don't do any grand tasks, even less than i used to.

i could get my machine to run age of empires 3 in the past, but it lagged only when there were like 20 cannons firing. so i don't think watching a video and a website and msn is going to fail 512 of ram. i think i should bump up my page file since the fresh install, just to be safe. i probably don't have the latest flash and javas either, since the reinstall.

what the hell could be going on? this is lame. argh

 

[bryand]

Hi Happy. Seems I read other threads lately here about similar problems. Have you tried the following?

1. Run at least 2 different spyware scans - I use spybot and adaware (both free).
2. Clean your registry using hijackthis or similar utility.
3. Make sure you have ALL windows updates.
4. Clean the inside of the PC and even unplug and re-plug in cables and ram sticks.

I help troubleshoot computer problems at work and am frequently asked by friends and family to fix their computer problems but I am not a professional computer guy so feel free to take this advise or leave it.

 

[happygobrokey]

after a fresh install, i would hope i would be spyware free.

i feel like i was a part of one of those threads you speak of. anyway, and yeah i got 86 windows updates, but didn't help it from crashing.

and i was thinking the same thing about the ram stick, probably one of the two sticks is toast so the one @ 256MB (-25% to shared video) alone can't handle it.

still don't compute about windows being corrupted. i think i'm closer to being onto it, but i'm not looking to really fix it anyhow. rebooting up to 6 or more times after a crash is a bitch, but my intent was to get this computer real "dirty" doing lots of file sharing and test-driving everything i downloaded before allowing it to be moved over to my external and to go onto my new machine when i get one, and format/fresh install down the road before i give it away.

but i had like 10 gigs of stuff i hadn't played first at the time i got scared of the crashes which i moved over to the external without testing. but then again if the crashes were already happening it must have been something i already have on there and have also used since the fresh install.

oh well. setting the thing to hibernate after 20 minutes idle kept it from crashing while i was at work, and it came out of hibernation no sweat. it's a sloppy workaround, but this computer is nothing but a whore to me now, and i will abuse the daylights out of it until the time to get rid of it draws nearer.

thanks for your reply, though, man. oh and the error message on the BSOD on failure is kernel_stack_inpage_error, i haven't googled it yet, so i guess i'm not as onto the trail as i claimed, but i have some facts recorded about it.

 

[winbig]

after a fresh install, i would hope i would be spyware free.

i feel like i was a part of one of those threads you speak of. anyway, and yeah i got 86 windows updates, but didn't help it from crashing.

and i was thinking the same thing about the ram stick, probably one of the two sticks is toast so the one @ 256MB (-25% to shared video) alone can't handle it.

still don't compute about windows being corrupted. i think i'm closer to being onto it, but i'm not looking to really fix it anyhow. rebooting up to 6 or more times after a crash is a bitch, but my intent was to get this computer real "dirty" doing lots of file sharing and test-driving everything i downloaded before allowing it to be moved over to my external and to go onto my new machine when i get one, and format/fresh install down the road before i give it away.

but i had like 10 gigs of stuff i hadn't played first at the time i got scared of the crashes which i moved over to the external without testing. but then again if the crashes were already happening it must have been something i already have on there and have also used since the fresh install.

oh well. setting the thing to hibernate after 20 minutes idle kept it from crashing while i was at work, and it came out of hibernation no sweat. it's a sloppy workaround, but this computer is nothing but a whore to me now, and i will abuse the daylights out of it until the time to get rid of it draws nearer.

thanks for your reply, though, man. oh and the error message on the BSOD on failure is kernel_stack_inpage_error, i haven't googled it yet, so i guess i'm not as onto the trail as i claimed, but i have some facts recorded about it.

If that's the error that keeps coming up, it's more than likely a hardware problem, if a virus scan comes back clean.

The following applies to Windows 2000, but I don't feel that it'd be any different for XP.

Error Message:

KERNEL_STACK_INPAGE_ERROR

Explanation:

This Stop message indicates that the requested page of kernel data from the paging file could not be read into memory. It might have been caused by a bad block (sector) in a paging file, a disk controller error, a defective motherboard, failing RAM, or because the stack signature in the kernel stack was not found. In extremely rare cases, it is caused when nonpaged pool resources run out.

User Action:

If the stack signature in the kernel stack is not found, the likely cause is defective hardware. Check the disk cabling and SCSI termination for problems. In addition, check your computer for viruses using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. Another cause of the Stop message might be that the data could not be read from the disk due to a bad block (sector). If you can restart the system after the error, Autochk runs automatically and attempts to map the bad sector to prevent its further use. If Autochk does not scan the hard disk for errors, you can manually launch the disk scanner. Run Chkdsk /f /r on the system partition. Restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r . Caution: If your system partition is formatted with the FAT file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOSbased hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks. Another common cause of this Stop message is failing RAM. Run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. Check that all the network adapters in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure network adapter contacts are clean. In addition, check the System Log in Event Viewer for additional error messages that might help pinpoint the device causing the error. Disabling memory caching of the BIOS might also resolve this error. Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at

You do not have permission to view link Log in or register now.

.

You do not have permission to view link Log in or register now.

 

[bryand]

oh well. setting the thing to hibernate after 20 minutes idle kept it from crashing while i was at work, and it came out of hibernation no sweat. it's a sloppy workaround, but this computer is nothing but a whore to me now, and i will abuse the daylights out of it until the time to get rid of it draws nearer.

The next time you have to reboot can you copy and paste the log in the event viewer? This should pinpoint the problem. As you probably know by now, a 77x error can be a dozen different things.