Author Topic: Help me My comp is going mad (Read 1346 times)

Tenzis · « **on:** April 25, 2003, 09:49:41 pm »

Help me

i hoe one of you can anwser this question cause my comp is in serious truble atm.

Kernal_data_inpage_Error

what is that?? i am getting it all the time and would like to know if i can fix it, it makes my comp go down all the time....

quisit · « **Reply #1 on:** April 25, 2003, 09:58:21 pm »

Little more information please. Is this happening in AO. If so, is it random, onload, on exit, in the first 20 minutes, etc.
If it's not AO is it during computer boot, shutdown, program execution, etc, etc.

<edit>
Are you using WinXP? Did you add/replace any hardware recently? Was this a STOP 0x7A error code by chance? What's the second error code?
0xC000009A
0xC000009C
0xC000009D
0xC000016A
0xC0000185
or something else?

Usually this code indicates a hardware defect. Either hard drive, RAM, or possibly even Video RAM.
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmd_stp_fvlq.asp
</edit>

Stongrel · « **Reply #2 on:** April 25, 2003, 09:58:43 pm »

Kernel... backbone of your OS is fubar. Run a virus scan... and reformat your HD. You running Win98? There's nothing I'm aware of to correct problems with your kernel. The fact that you're having trouble booting/shutdown means there's a major problem.

Nalika · « **Reply #3 on:** April 25, 2003, 10:02:50 pm »

I don't know about that reformat stong...every time i hear a n00b ask me to fix his computer, the first words are usually "Windows was broken so i formatted it"....please don't format right away! just run a virus check and get a fresh windows install.

And if you're not running 2k, shame on you.

Stongrel · « **Reply #4 on:** April 25, 2003, 10:06:33 pm »

If its a virus it might require a complete reformat. But read on why I said... virus scan first.

Tenzis · « **Reply #5 on:** April 25, 2003, 10:08:48 pm »

I am positive it is not a virus, and it happends randomly, when i play AO when i don't and the time is different all the time, it goes in Blue Screen and then i have to re-boot, i did a re-instalation on it a few days ago and it didn't go away.

the file mrxsmb.sys is also mentioned in the blue Screen if that helps.

Nalika · « **Reply #6 on:** April 25, 2003, 10:09:07 pm »

might. just never reformat on a whim....i don't even attempt to help the people who did that before, i tell em i'm busy.

EDIT:that file has to do with SAMBA connectivity...that's what i use to connect to my windows shares from my linux gateway...which means your problem has to do with your network. If you're connected directly to the internet via a cable modem, someone might be using a buffer overflow to crahs you, either on purpose of simply all over their subnet maliciously...get back to me on your network setup, mmkay?

Qin · « **Reply #7 on:** April 25, 2003, 10:10:43 pm »

If you are on XP first try last known good configuration by pressing F8 on bootup.

Or try reinstallig windows does not matter which you will not lose your data but it might repair the fucked file.

If all else fails Format the fucker

quisit · « **Reply #8 on:** April 25, 2003, 10:10:59 pm »

Tenzis, do you know the second code I asked about? How bout new hardware?

Tenzis · « **Reply #9 on:** April 25, 2003, 10:11:17 pm »

well my comp needed it anways as i had so much junk on it, and my Boot on the comp was like 5 mins so i had to do it

Nalika · « **Reply #10 on:** April 25, 2003, 10:13:48 pm »

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&q=mrxsmb.sys+crash

quisit · « **Reply #11 on:** April 25, 2003, 10:14:00 pm »

Had to do what? format? That probably won't fix it Tenzis.
Try a "chkdsk /f /v" in a command prompt.

Nalika · « **Reply #12 on:** April 25, 2003, 10:14:57 pm »

Quote from: Tenzis

well my comp needed it anways as i had so much junk on it, and my Boot on the comp was like 5 mins so i had to do it

...

Tenzis · « **Reply #13 on:** April 25, 2003, 10:15:34 pm »

ok i can't remember what code it was, but it will happen again soon and then i will post the code, and yes i am running XP and it is not the graphic card, i just changed it to see if it was the problem, but it is not.

quisit · « **Reply #14 on:** April 25, 2003, 10:16:46 pm »

k, I really recommend the chkdsk command. It'll will make you reboot to do the check.

Nalika · « **Reply #15 on:** April 25, 2003, 10:18:06 pm »

100k creds says it's not the disk. Betting it's just a fubar'd network setup.

Tenzis · « **Reply #16 on:** April 25, 2003, 10:37:23 pm »

ok i just did the chkdsk on the comp now, and there was no error as far as i could see, hmm maby i should run a few tests with Norton utilities, don't know if it would help.....

as for the Code, i will be sure to post it soon as i will get it within 1 hour hehe, and Nal ok 100k on it

quisit · « **Reply #17 on:** April 25, 2003, 10:45:41 pm »

Good to hear chkdsk was clear. So I assume you haven't replaced any other hardware recently? Even RAM?
If you want to test your RAM you can search the web for DocMemory2.0.
It's a DOS based utility that will put your systems RAM through it's paces. The kind of test were you start it and go to bed. Get up the next day, go to work, come home, go to bed... Test might be done when you wake up... again. It's really worth it though for these kinds of computer issues.

<edit>DocMemory</edit>

Tenzis · « **Reply #18 on:** April 26, 2003, 12:40:38 am »

Ok i got the code....

STOP: 0x00000077 that is the one it comes with..... does that help you?

Battlefreak · « **Reply #19 on:** April 26, 2003, 12:57:19 am »

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmd_stp_ogli.asp

Quote

Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.

Resolving the Problem
The following suggestions are specific to Stop 0x70 errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

Stop 0x77 messages can be caused by bad sectors in the virtual memory paging file or a disk controller error. In extremely rare cases, depleted nonpaged pool resources can cause this error. If the first and third parameters are zero, the stack signature in the kernel stack is missing, which is an error typically caused by defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the requested data could not be found. You can try to correct this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in the future, starts automatically. If Autochk fails to run, you can manually perform the integrity check yourself by following the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix. For more information about Autochk and Chkdsk, see "Troubleshooting Disks and File Systems" in this book.

Another cause of Stop 0x77 messages is defective, malfunctioning, or failed memory hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added new hardware recently, remove and replace it to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the system manufacturer to determine if the component has failed.

The problem might also be due to cracks, scratched traces, or defective components on the motherboard. If all else fails, take the system motherboard to a repair facility for diagnostic testing.
Problems that cause Stop 0x77 messages can also cause Stop 0x7A messages. For more information about Stop 0x7A messages, see "Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR" later in this appendix.

For more information about Stop 0x77 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x00000077, and 0x77.

quisit · « **Reply #20 on:** April 26, 2003, 01:15:21 am »

Battlefreak beat me to the reply there

If chkdsk came up clean it would be a good idea to try the DocMemory program. Though, if you haven't replaced your system's memory recently I don't believe the memory could be the problem.

Tenzis · « **Reply #21 on:** April 26, 2003, 11:35:09 am »

i think i will try that, to see if it finds anyhing.

Could it be the HDD? as it is rather old and could be about to die...

quisit · « **Reply #22 on:** April 27, 2003, 06:33:55 am »

It could be the HDD. Just because chkdsk didn't find anything doesn't mean much. One of those Norton tools should be good for testing that. Though Norton Utilities have been going downhill for years now.

Caleena · « **Reply #23 on:** April 27, 2003, 11:59:47 am »

Hard Drives, I know a little about. I can dig you out a decent cloning tool.

The stop error is an undocumented bad sector on your hard drive. Probably caused by general wear on the platter surface, and heads causing a tiny amount of dust inside your hard drive stopping a read occaisinaly. Hard drives, unless OEM, come with a warranty for a reason. They have definate lifespans. Some give a 1,000,000 hour usage guarantee, however if you read the fine print, that is running at like 2800 rpm. Which as we know is not the deal.

Personaly, i would clone an image of your hard drive to a new hard drive, then use disk managment in XP to partition the rest of the space on your new drive. As you will definatley buy a bigger drive. a)if your hard drive is old it WILL fail eventualy, if it isn't already b)it could be the hard drive showing signs of old age already.

I deal with about 50-100 hard drives a week, from personal and buisiness users, that have been using the same hard drive for more than three to four years. Honestly its worth the investment to replace them after about two to three years of regular use.

quisit · « **Reply #24 on:** April 28, 2003, 12:56:25 pm »

Tenzis,
Anything new with the comp? Was wondering what the 4 parameters are for the 0x77 BSOD?