The last two days the computer has rebooted itself a few times. Tonight it rebooted three times. I finally got a stop error, then it rebooted again. the stop error said:
Generic host process for win32 service
Generic host process for win32 service has encountered a problem and needs to close. We are sorry . . . . . . inconvienience.
0x77ef3664 reference memory at 0xff000035.
The memory could not be read.
Error signatures:
SzAppName: svchost.exe SzAppver: 5.1.2600.2180 SzModName: rpcr74.dll
Szmodver: 5.1.2600.2180 offset: 00083664
I thought there was a problem with reading a memory module, so I opened it up and swapped the two memory modules. I also noticed my heat sink and fan were dirty, so I took it off, cleaned it up, added new heat sink lube, and reinstalled it.
After I restarted it, i heard two fast beeps, followed by 8 single beeps, then a few seconds later two more fast beeps and one short beep. My manual doesn't tell me what those codes are. I have a P4 socket 478 PCChips M922LU P4-Northwood. Any idea?
I cant get a picture to come up, nothing happens after the beeps. Do I need to reset the Bios? What to do from here? I dont think it is a hard drive problem. The report that came up for microsoft said something about a device driver error, but its now not even getting that far. I didnt take the CPU out. I grounded myself. What if I do take the Cpu out? Should I take everything out and just leave the power going to the Motherboard and see what happens with that? I once had this type of problem on a dell, and I took everything out and added them back one by one, and it got rid of the short somewhere in there. Any ideas. Help please.
UPDATE--------------------
This has an AMIB BIOS BTW.
I took everything out, just left the power supply connected to the mobo, after I disconnected it and reconnected it. It beep 3 long beeps. I took this to mean no memory, so I tried each memory modual individually, and both time the computer beeped as I stated above, with nothing else in it. 2 fast beeps, followed by 8 short beeps, then 2 more fastbeeps and another beep.
Is the mobo fried? The processor maybe? I do have 4 Identical computers, as far as mobos and memory go. if not sure, maybe its the cpu, I could try to take another cpu and swap it, or maybe take my cpu and put it in the other computer. If my computer fried my cpu, i wouldnt want to put another good cpu in there and fry it also. I dont think a bad cpu would fry a mobo. Can a bad mobo fry a cpu?
Ive been thinking of upgrading the cpu anyway. How can one tell if it is a bad cpu?
UPDATE #2 ----------------------
After I took everything out, it and it did the same beeps, I did some research on the beeps on another computer. Non seemed to fit exactly, but it seemed like it had to do with memory and video. So I went back and put the video card in, and started it up. It started and stopped when looking for the hard drives, with no beeps, so I reconnected everything and have had no issues since.
QUESTION; Does this sound like I solved the problem, like a short or something, OR could this be a sign that something is going bad. I let the computer sit for about an hour after my last try and before reconnecting everything. I have left the computer on, rebooting multiple times so far with no problems. I ran all kinds of stuff to look for spyware, adware, viruses, etc and found absolutely nothing.
Generic host process for win32 service
Generic host process for win32 service has encountered a problem and needs to close. We are sorry . . . . . . inconvienience.
0x77ef3664 reference memory at 0xff000035.
The memory could not be read.
Error signatures:
SzAppName: svchost.exe SzAppver: 5.1.2600.2180 SzModName: rpcr74.dll
Szmodver: 5.1.2600.2180 offset: 00083664
I thought there was a problem with reading a memory module, so I opened it up and swapped the two memory modules. I also noticed my heat sink and fan were dirty, so I took it off, cleaned it up, added new heat sink lube, and reinstalled it.
After I restarted it, i heard two fast beeps, followed by 8 single beeps, then a few seconds later two more fast beeps and one short beep. My manual doesn't tell me what those codes are. I have a P4 socket 478 PCChips M922LU P4-Northwood. Any idea?
I cant get a picture to come up, nothing happens after the beeps. Do I need to reset the Bios? What to do from here? I dont think it is a hard drive problem. The report that came up for microsoft said something about a device driver error, but its now not even getting that far. I didnt take the CPU out. I grounded myself. What if I do take the Cpu out? Should I take everything out and just leave the power going to the Motherboard and see what happens with that? I once had this type of problem on a dell, and I took everything out and added them back one by one, and it got rid of the short somewhere in there. Any ideas. Help please.
UPDATE--------------------
This has an AMIB BIOS BTW.
I took everything out, just left the power supply connected to the mobo, after I disconnected it and reconnected it. It beep 3 long beeps. I took this to mean no memory, so I tried each memory modual individually, and both time the computer beeped as I stated above, with nothing else in it. 2 fast beeps, followed by 8 short beeps, then 2 more fastbeeps and another beep.
Is the mobo fried? The processor maybe? I do have 4 Identical computers, as far as mobos and memory go. if not sure, maybe its the cpu, I could try to take another cpu and swap it, or maybe take my cpu and put it in the other computer. If my computer fried my cpu, i wouldnt want to put another good cpu in there and fry it also. I dont think a bad cpu would fry a mobo. Can a bad mobo fry a cpu?
Ive been thinking of upgrading the cpu anyway. How can one tell if it is a bad cpu?
UPDATE #2 ----------------------
After I took everything out, it and it did the same beeps, I did some research on the beeps on another computer. Non seemed to fit exactly, but it seemed like it had to do with memory and video. So I went back and put the video card in, and started it up. It started and stopped when looking for the hard drives, with no beeps, so I reconnected everything and have had no issues since.
QUESTION; Does this sound like I solved the problem, like a short or something, OR could this be a sign that something is going bad. I let the computer sit for about an hour after my last try and before reconnecting everything. I have left the computer on, rebooting multiple times so far with no problems. I ran all kinds of stuff to look for spyware, adware, viruses, etc and found absolutely nothing.
