keanha
asked on
please help computer keeps restarting
hello,
the history:
for the last few weeks my computer has been locking up at random. it does not matter what application i am running but it does happen faster while playing games like civ4. when it does lock up the screen turns into a weird checkboard/grid of black and white. in order to restart i have to hold the power button down for 3 seconds and shut down. this happened about 4 or 5 times and then my computer started restarting after the "loading windows xp" screen would appear. i inserted my windows xp disk and ran chkdsk and fixed some disk errors. this still did not help so i decided to use the repair windows from the windows cd. after running the "repair" the system stopped restarting but it would not finish loading windows. the windows loading screen would come up for a second and then would disappear to a black screen with a cursor in the middle of screen. the cursor could be moved around but nothing else would happen. i decided it was some sort of hardware failure so i started swapping out components. first i swapped out the video card and tried 2 agp cards and 1 pci card. next i moved onto the ram. i moved the ram to different slots. then i inserted new ram. i put the old ram back into the computer and ran memtest86 for 6 hours and had 19 error. i checked the bios and the motherboard was set up to automatically detect the ram. however it was using the wrong voltage. it was running the ram at 2.65 volts instead of the manufactures recommended 2.60 volts. i set the voltage to 2.60 volts and ran memtest again for 6 hours and no errors. as a check i put the new memory in the system and ran memtest and did not have any errors. i tried the repair windows installation again with the same results. so i moved onto the hard drive. i did not want to perform a fresh install on the current hard drive so i put an older 10gig 7200 rpm maxtor that i had laying around. i started a fresh install but failed during "configuring windows". i tried it one more time and it worked fine. i let the system run for a few hours to check stability and thought i was in the clear then all of a sudden the system rebooted on its own when i went into the control panel. when i turned the sytem back on windows loaded and said it had recovered from a serious error and listed the following error signature
BCCode: 1000008e
BCP1: c0000005
BCP2: 80552ae5
BCP3: f8744b54
BCP4: 00000000
OSver: 5_1_2600
Product: 256_1
i would appreciate any advice. i did not rule out processor or motherboard because i do not have another one to use. oh yeah...i did put another power supply in the system but it was before i changed the voltage on the ram.
system specs
msi 865pe neo2
p4 2.6mhz 800mhz fsb
mushkin 2x256
maxtor 40gig 7200rpm
ati radeon 9200 128meg
cd burner
thank you
the history:
for the last few weeks my computer has been locking up at random. it does not matter what application i am running but it does happen faster while playing games like civ4. when it does lock up the screen turns into a weird checkboard/grid of black and white. in order to restart i have to hold the power button down for 3 seconds and shut down. this happened about 4 or 5 times and then my computer started restarting after the "loading windows xp" screen would appear. i inserted my windows xp disk and ran chkdsk and fixed some disk errors. this still did not help so i decided to use the repair windows from the windows cd. after running the "repair" the system stopped restarting but it would not finish loading windows. the windows loading screen would come up for a second and then would disappear to a black screen with a cursor in the middle of screen. the cursor could be moved around but nothing else would happen. i decided it was some sort of hardware failure so i started swapping out components. first i swapped out the video card and tried 2 agp cards and 1 pci card. next i moved onto the ram. i moved the ram to different slots. then i inserted new ram. i put the old ram back into the computer and ran memtest86 for 6 hours and had 19 error. i checked the bios and the motherboard was set up to automatically detect the ram. however it was using the wrong voltage. it was running the ram at 2.65 volts instead of the manufactures recommended 2.60 volts. i set the voltage to 2.60 volts and ran memtest again for 6 hours and no errors. as a check i put the new memory in the system and ran memtest and did not have any errors. i tried the repair windows installation again with the same results. so i moved onto the hard drive. i did not want to perform a fresh install on the current hard drive so i put an older 10gig 7200 rpm maxtor that i had laying around. i started a fresh install but failed during "configuring windows". i tried it one more time and it worked fine. i let the system run for a few hours to check stability and thought i was in the clear then all of a sudden the system rebooted on its own when i went into the control panel. when i turned the sytem back on windows loaded and said it had recovered from a serious error and listed the following error signature
BCCode: 1000008e
BCP1: c0000005
BCP2: 80552ae5
BCP3: f8744b54
BCP4: 00000000
OSver: 5_1_2600
Product: 256_1
i would appreciate any advice. i did not rule out processor or motherboard because i do not have another one to use. oh yeah...i did put another power supply in the system but it was before i changed the voltage on the ram.
system specs
msi 865pe neo2
p4 2.6mhz 800mhz fsb
mushkin 2x256
maxtor 40gig 7200rpm
ati radeon 9200 128meg
cd burner
thank you
With all the tests and changes done it reminds me of a situation I had at one time same issues exactly. The fix was in the on off switch at the front of the computer box. If you can by pass the switch with a remote switch and see if it becomes stable again.
keanha,
You may need to uninstall and reinstall the driver. Sometimes removing it from device manager, add/remove programs, and add/remove hardware, then rebooting, the system will find the card and you can reinstall the right driver.
Take a look at the below from a similar situation;
>>The failing module is SiSGRV.sys which is display card driver. The culprit is faulty display card. Do you overclock the display card?
BugCheck 1000008E, {c000001d, bf9e4eea, b55f5b78, 0}
Probably caused by : SiSGRV.dll ( SiSGRV+11eea )<<<
taken from :
https://www.experts-exchange.com/questions/21598339/Crash-Dump-Analysis-Help-BCCode-1000008e.html
You may need to uninstall and reinstall the driver. Sometimes removing it from device manager, add/remove programs, and add/remove hardware, then rebooting, the system will find the card and you can reinstall the right driver.
Take a look at the below from a similar situation;
>>The failing module is SiSGRV.sys which is display card driver. The culprit is faulty display card. Do you overclock the display card?
BugCheck 1000008E, {c000001d, bf9e4eea, b55f5b78, 0}
Probably caused by : SiSGRV.dll ( SiSGRV+11eea )<<<
taken from :
https://www.experts-exchange.com/questions/21598339/Crash-Dump-Analysis-Help-BCCode-1000008e.html
It crashes at windows kernel. As I don't have the minidump and I cannot confirm the culprit. Most probably it is casued by faulty ram. Reseat video card and memory stick to another memory slot and clean the dust inside the computer case.
BCCode: 1000008e
BCP1: c0000005
BCP2: 80552ae5 <-- Windows Kernel
BCP3: f8744b54
BCP4: 00000000
BCCode: 1000008e
BCP1: c0000005
BCP2: 80552ae5 <-- Windows Kernel
BCP3: f8744b54
BCP4: 00000000
ASKER
Frank519, tim qui and cpc2004,
i will give your suggestions a try and get back with you. i appreciate the advice.
is there a possibility that the problem is a bad power supply. the rails are fluctuating quite a bit but i do not know what the normal parameters are.
cpc2004....i will see if i can get the minidump
thanx again
i will give your suggestions a try and get back with you. i appreciate the advice.
is there a possibility that the problem is a bad power supply. the rails are fluctuating quite a bit but i do not know what the normal parameters are.
cpc2004....i will see if i can get the minidump
thanx again
Hey,
I had the same problem with my old box. I kept suspecting the ram all the while and it turned out to be the processor!! Replace your processor and check.
I had the same problem with my old box. I kept suspecting the ram all the while and it turned out to be the processor!! Replace your processor and check.
Hi Hey,
If it is faulty CPU, I will expect bugcheck 9C or crash at IRQL x'1c'. What is the bugcheck code of your problem?
If it is faulty CPU, I will expect bugcheck 9C or crash at IRQL x'1c'. What is the bugcheck code of your problem?
ASKER
i dont know if this makes a difference in anyones opinion this is happening to a system that is 2 years old and had been rock solid.
cpc2004....did you get the minidump i emailed to you?
cpc2004....did you get the minidump i emailed to you?
After examination of your minidumps. I confirm that the culprit is faulty ram. You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
Debug report of your minidumps
Mini103005-01.dmp BugCheck 10000050, {c1ec6b1c, 0, 804e94a2, 0}
Mini103005-01.dmp Probably caused by : memory_corruption ( nt!MiLocateAndReserveWsle+
STACK_TEXT:
efb6ac04 804eaa76 c050369c 0812304f 80d69680 nt!MiLocateAndReserveWsle+
efb6ac1c 804edd35 0812304f c002048c 80d69680 nt!MiAddValidPageToWorking
efb6ac4c 804edc3a 00000000 0812304f c002048c nt!MiCompleteProtoPteFault
efb6ac7c 804eab18 00000000 0812304f c002048c nt!MiResolveProtoPteFault+
efb6acf8 804e9235 00000000 0812304f c002048c nt!MiDispatchFault+0x147
efb6ad4c 804e0f07 00000000 0812304f 00000001 nt!MmAccessFault+0xcde
efb6ad4c 77a8d3a0 00000000 0812304f 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0156af40 00000000 00000000 00000000 00000000 0x77a8d3a0
FOLLOWUP_IP:
nt!MiLocateAndReserveWsle+
804e94a2 8b0c81 mov ecx,[ecx+eax*4]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiLocateAndReserveWsle+
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x50_nt!MiLocateAndReserve
BUCKET_ID: 0x50_nt!MiLocateAndReserve
Mini110305-01.dmp BugCheck 1000008E, {c0000005, 80552ae5, f8744b54, 0}
Mini110305-01.dmp Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+107 )
Mini110405-01.dmp BugCheck 1000007E, {c0000005, 804f1854, ebb6cc14, ebb6c910}
EXCEPTION_RECORD: ebb6cc14 -- (.exr ffffffffebb6cc14)
.exr ffffffffebb6cc14
ExceptionAddress: 804f1854 (nt!IoBuildPartialMdl+0x00
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00001188
Attempt to write to address 00001188
Suggestion
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
Make sure that the CPU fan works properly
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard
6. Check the bios setting about memory timing and make sure that it is on
If it still crashes, diagnostic which memory stick is faulty
1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram
Debug report of your minidumps
Mini103005-01.dmp BugCheck 10000050, {c1ec6b1c, 0, 804e94a2, 0}
Mini103005-01.dmp Probably caused by : memory_corruption ( nt!MiLocateAndReserveWsle+
STACK_TEXT:
efb6ac04 804eaa76 c050369c 0812304f 80d69680 nt!MiLocateAndReserveWsle+
efb6ac1c 804edd35 0812304f c002048c 80d69680 nt!MiAddValidPageToWorking
efb6ac4c 804edc3a 00000000 0812304f c002048c nt!MiCompleteProtoPteFault
efb6ac7c 804eab18 00000000 0812304f c002048c nt!MiResolveProtoPteFault+
efb6acf8 804e9235 00000000 0812304f c002048c nt!MiDispatchFault+0x147
efb6ad4c 804e0f07 00000000 0812304f 00000001 nt!MmAccessFault+0xcde
efb6ad4c 77a8d3a0 00000000 0812304f 00000001 nt!KiTrap0E+0xd0
WARNING: Frame IP not in any known module. Following frames may be wrong.
0156af40 00000000 00000000 00000000 00000000 0x77a8d3a0
FOLLOWUP_IP:
nt!MiLocateAndReserveWsle+
804e94a2 8b0c81 mov ecx,[ecx+eax*4]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!MiLocateAndReserveWsle+
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP:
STACK_COMMAND: kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x50_nt!MiLocateAndReserve
BUCKET_ID: 0x50_nt!MiLocateAndReserve
Mini110305-01.dmp BugCheck 1000008E, {c0000005, 80552ae5, f8744b54, 0}
Mini110305-01.dmp Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+107 )
Mini110405-01.dmp BugCheck 1000007E, {c0000005, 804f1854, ebb6cc14, ebb6c910}
EXCEPTION_RECORD: ebb6cc14 -- (.exr ffffffffebb6cc14)
.exr ffffffffebb6cc14
ExceptionAddress: 804f1854 (nt!IoBuildPartialMdl+0x00
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00001188
Attempt to write to address 00001188
ASKER
cpc2004,
thanks for the info....i really appreciate it. read through your comments below and correct me if i am wrong.
is it possible for ram to go bad after 2 years? if you have faulty ram will that corrupt the hard drive to a point were it would not boot anylonger?
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C) - temp around 46c
Make sure that the CPU fan works properly - fan works...properly?....it spins real fast
2. Reseat the memory stick to another memory slot - tried once but will try again
3. Downclock the ram - will try
4. Clean the dust inside the computer case - first thing i did
5. Make sure that the ram is compatible to the motherboard - not on the list on msi's website but like i said the system has been running for 2 years.
6. Check the bios setting about memory timing and make sure that it is on - set to auto but manually correct if outside manufactures specs?
thanks for the info....i really appreciate it. read through your comments below and correct me if i am wrong.
is it possible for ram to go bad after 2 years? if you have faulty ram will that corrupt the hard drive to a point were it would not boot anylonger?
1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C) - temp around 46c
Make sure that the CPU fan works properly - fan works...properly?....it spins real fast
2. Reseat the memory stick to another memory slot - tried once but will try again
3. Downclock the ram - will try
4. Clean the dust inside the computer case - first thing i did
5. Make sure that the ram is compatible to the motherboard - not on the list on msi's website but like i said the system has been running for 2 years.
6. Check the bios setting about memory timing and make sure that it is on - set to auto but manually correct if outside manufactures specs?
The faulty ram that I mean is that the ram has intermittent error. The error rate is very very small. If the hardware errors during kernel mode your windows will crash. If the hardware error occurs at user mode, the application will crash and windows will log the error to DrWatson Log. You can double check whether you have a huge DrWatson log (ie if the size of the log is > 1m)
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log
C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\user.dmp
ASKER
cpc2004
how come the error only happens in windows and not the bios too or msdos? is it because the ram is not being "stressed".
how come the error only happens in windows and not the bios too or msdos? is it because the ram is not being "stressed".
ASKER
I have removed the cards and memory and cleaned the dust out. I have run microsoft's memory test (extended test) on each individual ram in all four memory slots and no errors were reported. Then I put both ram chips back in and ran the memory test again. it has been running for a few hours now and still no errors. is there any possibility that the video card or power supply is bad?
cpc2004...i have a few more minidumps would you like to see those as well.
cpc2004...i have a few more minidumps would you like to see those as well.
ASKER
still no errors on memory after 4 hours of testing on extended test with extending mapping
is there anyway to check voltages under windows (ie program or utility)?
is there anyway to check voltages under windows (ie program or utility)?
It could be the memory on the ATI card is bad, which would make the card bad.
In my previous post, I mentioned some faulty ram can pass memtest. Reseat tbe memory stick to another memory slot and check whether your CPU is overheat or not.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Status
OK things arent much better but let me tell you what I have done.
I updated to the latest bios and tried to reinstall windows xp but it still failed during installation. So I went completely barebones and unplugged the floppy drive and disabled the usb, onboard sound and lan. Then I went into the bios and turned the off auto detect ram and set to the manu's settings of 2.6v 3,3,3,8 @ 400mhz. I put one stick of ram into the first slot and ran memtest86. It ran for 7-8 hours and passed all 77 tests. Next, I removed that stick of ram and put the other stick into the first slot and ran memtest and it passed 92 tests. After that I installed windows xp with just one ram stick in and was able to get the machine back up. After getting the machine back up I put the other stick into slot 3 (dual channel) and the system wouldnt load windows. It would restart itself before it could finish loading. I removed the second stick and powered up the machine. All was well. I thought this would be a good time to get some important documents backed up so I plugged in the original 40gig drive and COPIED the data to the primary drive. I told windows to send this to the CDR and tried burning the data. It failed once during the process (the system rebooted.....windows has recovered from a serious error) but worked the second time. So, at least my data is secure now.
With that all said...and someone please correct me.....I think I will order another motherboard and rma this one. It may still be the ram but running 77 and 92 tests would at least uncover some error. I will let you all know how it turns out. Thanks again for all your help.
OK things arent much better but let me tell you what I have done.
I updated to the latest bios and tried to reinstall windows xp but it still failed during installation. So I went completely barebones and unplugged the floppy drive and disabled the usb, onboard sound and lan. Then I went into the bios and turned the off auto detect ram and set to the manu's settings of 2.6v 3,3,3,8 @ 400mhz. I put one stick of ram into the first slot and ran memtest86. It ran for 7-8 hours and passed all 77 tests. Next, I removed that stick of ram and put the other stick into the first slot and ran memtest and it passed 92 tests. After that I installed windows xp with just one ram stick in and was able to get the machine back up. After getting the machine back up I put the other stick into slot 3 (dual channel) and the system wouldnt load windows. It would restart itself before it could finish loading. I removed the second stick and powered up the machine. All was well. I thought this would be a good time to get some important documents backed up so I plugged in the original 40gig drive and COPIED the data to the primary drive. I told windows to send this to the CDR and tried burning the data. It failed once during the process (the system rebooted.....windows has recovered from a serious error) but worked the second time. So, at least my data is secure now.
With that all said...and someone please correct me.....I think I will order another motherboard and rma this one. It may still be the ram but running 77 and 92 tests would at least uncover some error. I will let you all know how it turns out. Thanks again for all your help.
ASKER
Also....windows either fails to load or crashes quicker when the ram is in any of the other 3 slots.
It sounds like RAM problem and possibly mobo too.
ASKER
Well....before I order any more parts is there another way to determine if its the RAM or Mobo. Keeping in mind that I do not have another MB to swap out and try.
Another note: I run memtest86 v2.3 on the ram and it does not come up with any errors. It doesnt matter which slot the ram is in when running memtest. When I put both ram sticks in the mobo and try to boot windows the system becomes more unstable.
Another note: I run memtest86 v2.3 on the ram and it does not come up with any errors. It doesnt matter which slot the ram is in when running memtest. When I put both ram sticks in the mobo and try to boot windows the system becomes more unstable.
ASKER
FYI.....I purchased new ram and nada....the system still will not load windows xp without crashing/bsod......time for a new mobo
Sorry to hear about the bad mobo, I was hoping it was something less drastic.
Your windows crashes with faulty memory which include RAM, Level 2 (L2) SRAM cache, or video adapter RAM. One of the minidump crashes with IRQL x'1c'. According to my record for IRQL x'1c'. Both CPU and RAM has 35%
Occ %
Overheat 1 6
CPU 6 35
RAM 6 35
M/B 2 12
Software 1 6
Video Card 1 6
Suggestion
1. Both you replace the M/B. You had better stress test the CPU and make sure that CPU is healthy. Install prime95 to stress test the CPU. This is a windows tools and you can run the test at any time.
http://www.mersenne.org/freesoft.htm
2. Some faulty ram can pass memtest. Take out a memory stick and reboot. If the windows does not crash, the removed memory stick is faulty or the ram slot is bad. Reseat the in-use memory stick to suspected faulty ram slot. Reboot and let windows runs for a few hours. If windows crashes, the ram slot is faulty. Otherwise the unused memory stick is faulty.
Occ %
Overheat 1 6
CPU 6 35
RAM 6 35
M/B 2 12
Software 1 6
Video Card 1 6
Suggestion
1. Both you replace the M/B. You had better stress test the CPU and make sure that CPU is healthy. Install prime95 to stress test the CPU. This is a windows tools and you can run the test at any time.
http://www.mersenne.org/freesoft.htm
2. Some faulty ram can pass memtest. Take out a memory stick and reboot. If the windows does not crash, the removed memory stick is faulty or the ram slot is bad. Reseat the in-use memory stick to suspected faulty ram slot. Reboot and let windows runs for a few hours. If windows crashes, the ram slot is faulty. Otherwise the unused memory stick is faulty.
ASKER
OK...I think it is fixed now....I put a better power supply on the computer with the old ram and was able to install windows xp without a problem....So far I have installed the latest drivers and downloaded all the xp updates without a single problem....Right now the ram is set to manufacturer's specs of 3,3,3,8 @ 2.6 volts....I will let you all know if the problem persists.
Thanks for all your help and suggestions....it is greatly appreciated
keanha
Thanks for all your help and suggestions....it is greatly appreciated
keanha
keanha,
glad to hear it's working, if you feel any of the advice helped, please accept the helpful posts as answers and assign an excellent grade.
glad to hear it's working, if you feel any of the advice helped, please accept the helpful posts as answers and assign an excellent grade.
ASKER
YEAH......The new power supply is working like a charm.....no reboots and no BSOD's
One question though.....my cpu temperature is running lower......with the old power supply it would run about 115F....now it only runs about 95-100F.....has anyone heard of this happening
One question though.....my cpu temperature is running lower......with the old power supply it would run about 115F....now it only runs about 95-100F.....has anyone heard of this happening