Please help, my computer keeps crashing
- Thread starter xscomputer
- Start date
- Status
Hi Erik,
After I investigate your latest dump, I confirm it is hardware problem. On of your minidump crashes at IRQL x'1c' which is the symptom of hardware error. According to my statistics, 50% is faulty CPU, 33.3% is RAM, 16.6% is M/B.
Edit
I'm sorry I mixed up your problem with Erik.
After I investigate your latest dump, I confirm it is hardware problem. On of your minidump crashes at IRQL x'1c' which is the symptom of hardware error. According to my statistics, 50% is faulty CPU, 33.3% is RAM, 16.6% is M/B.
Edit
I'm sorry I mixed up your problem with Erik.
hondablaster
Posts: 22 +0
That stuff you guys are doing is way too complicated and silly.
Get www.memtest.org
Download it to CD and reboot During boot stage hit {whatever button bring up boot menu} and boot form CD it will do everything from there. IF you get ANY ERRORS you got a memory problem. (run it for 6 - 12 hours) You should remove all sticks and then repeat the test with one stick in at a time to find the source.
Second Lets say you pass a memtest. Then it could either be bad or over heating CPU or a power supply that is faulty.
Its hard to test the power but YOU CAN TEST THE CPU. get a program called prime 95 and set the application priority to 10 then go to the torture test tab and click the second button from the top and start test In place large ffts (by default it set to the third) if the program auto stops your CPU needs more voltage or is over heating. Get Motherboard monitor 5 to monitor temps if thats the case. Analyzing dumps is way over the top and i can tell from experiance those errors are form memory that is either incompatible or going bad. Try the memtest and see for yourself.
Get www.memtest.org
Download it to CD and reboot During boot stage hit {whatever button bring up boot menu} and boot form CD it will do everything from there. IF you get ANY ERRORS you got a memory problem. (run it for 6 - 12 hours) You should remove all sticks and then repeat the test with one stick in at a time to find the source.
Second Lets say you pass a memtest. Then it could either be bad or over heating CPU or a power supply that is faulty.
Its hard to test the power but YOU CAN TEST THE CPU. get a program called prime 95 and set the application priority to 10 then go to the torture test tab and click the second button from the top and start test In place large ffts (by default it set to the third) if the program auto stops your CPU needs more voltage or is over heating. Get Motherboard monitor 5 to monitor temps if thats the case. Analyzing dumps is way over the top and i can tell from experiance those errors are form memory that is either incompatible or going bad. Try the memtest and see for yourself.
Cpc2004, i took all the dimms of memory out and the problem still persist. I'll tray to explain the problem again, because now i don't know anymore if it is a problem with RAM.
If i'm not doing anything on the pc (only the background programs are working) nothing happens until one day as passed (more or less). If i'm on the net, it takes some time to the image freezes (hours maybe). If i use the PCTV, it takes only 10 to 20 min to freeze. If i use both internet and PCTV it takes a few min to freeze.. Sometimes when i'm using the PCTV, the image is frozen but i can still hear the sound of PCTV! is that a RAM problem? THE COMPUTER DOES NOT REBOOT. It only freezes..
I've tried the newest RAM module that i have (kingston 512Mb pc3200) but it happen with it to, i tried the oldest one and it also happen.. I don't know what to do anymore..
pleeeeaaase help me.... My first post (posted a few days ago) has the info about my pc, in case you need it.
thanks
If i'm not doing anything on the pc (only the background programs are working) nothing happens until one day as passed (more or less). If i'm on the net, it takes some time to the image freezes (hours maybe). If i use the PCTV, it takes only 10 to 20 min to freeze. If i use both internet and PCTV it takes a few min to freeze.. Sometimes when i'm using the PCTV, the image is frozen but i can still hear the sound of PCTV! is that a RAM problem? THE COMPUTER DOES NOT REBOOT. It only freezes..
I've tried the newest RAM module that i have (kingston 512Mb pc3200) but it happen with it to, i tried the oldest one and it also happen.. I don't know what to do anymore..
pleeeeaaase help me.... My first post (posted a few days ago) has the info about my pc, in case you need it.
thanks
It could be 1 of 3 areas.
1. Could be bad memory.
2. You may need to update BIOS.
3. Your Graphics card is overheating.
3a. Fans need to be inspected.
Theres a few places to check, and it could be software.
But make sure evreything is updated in your pc.
http://www.drivershq.com/
Have the site check too see if evreything is updated, and make sure nothing is blocking, like popus, firewall, so it can load the active x files it needs to check your pc.
1. Could be bad memory.
2. You may need to update BIOS.
3. Your Graphics card is overheating.
3a. Fans need to be inspected.
Theres a few places to check, and it could be software.
But make sure evreything is updated in your pc.
http://www.drivershq.com/
Have the site check too see if evreything is updated, and make sure nothing is blocking, like popus, firewall, so it can load the active x files it needs to check your pc.
Appreciate if someone can take a look of my post and help me out here!
Windows xp startup BSOD
Thanks a lot!
Windows xp startup BSOD
Thanks a lot!
i did the memtest for 5 hours and it didn't report any error, so it's not a bad memory. I've search for the bios update driver and the one i have it's ok. So if it's overheat of the graphics board, what can i do? I have 2 fans working and the Abit 9600XT has another one just for her..It helps if i move the PCTV board PCI near the graphics board to another slot PCI?
Computer resetting
Hi
I have a P4 3GH , 1GB RAM (2*512) , 120GB ATA Maxtor
I just bought a New HDD 250GB SATA maxtor,
and ever sinec I installed it, after a couple of hours, computer Restarts without any erros, warrnings,....
it usually happens more offen when wathcing a movie, but even if i leave the computer doing nothing, it does the same after a while,
My event viewer showed these savedumps
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (*)
I will attach a couple of my minidumps.
Could it be this new HDD, or RAM,or else
Should I go to that computer shop and tell them this is the problem?
Let me know if u get anything out of my minidumps.
Edit:
Forgot to mention this is a 0xc0000005, "0x1000007e (0xc0000005, 0xf53eed87, 0xf6671b04, 0xf6671800)"
Hi
I have a P4 3GH , 1GB RAM (2*512) , 120GB ATA Maxtor
I just bought a New HDD 250GB SATA maxtor,
and ever sinec I installed it, after a couple of hours, computer Restarts without any erros, warrnings,....
it usually happens more offen when wathcing a movie, but even if i leave the computer doing nothing, it does the same after a while,
My event viewer showed these savedumps
The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (*)
I will attach a couple of my minidumps.
Could it be this new HDD, or RAM,or else
Should I go to that computer shop and tell them this is the problem?
Let me know if u get anything out of my minidumps.
Edit:
Forgot to mention this is a 0xc0000005, "0x1000007e (0xc0000005, 0xf53eed87, 0xf6671b04, 0xf6671800)"
Hello,
I was wondering if I could get help understanding the output of the minidump files. I keep on getting the error Bad Pool Header at the login screen which causes the the infamous BSOD .... I also have problems with win2k.sys-
I've attached the minidump files- Can anyone help me out?
Much appreciated,
TeKKi
I was wondering if I could get help understanding the output of the minidump files. I keep on getting the error Bad Pool Header at the login screen which causes the the infamous BSOD .... I also have problems with win2k.sys-
I've attached the minidump files- Can anyone help me out?
Much appreciated,
TeKKi
Probably the BSOD is caused by faulty RAM.TeKKi said:
Suggestion
1. Reseat the memory stick to another memory slot
2. Downclock the ram
3. Clean the inside the computer case
4. Make sure that the ram is compatible to the motherboard
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
Crash Problem
Thanx alot for ur reply,
I was getting disappointed that there is no answer for my post
I attached more minidumps,
My computer is also giving out Internet through ICS, and I noticed this problem much more happens when the other computer starts downloading heavily, (it didn't happen for 1 day, when that computer was tunned off)
Strange though all these happened after connecting my new HDD, and never happened to me before.
and it seems that i am getting combination of bugcheck errors:
0x1000000a
0x1000007e
0x10000050
0x0000004e
0x00000044
0x100000d1
Thanx alot for ur reply,
I was getting disappointed that there is no answer for my post
I attached more minidumps,
My computer is also giving out Internet through ICS, and I noticed this problem much more happens when the other computer starts downloading heavily, (it didn't happen for 1 day, when that computer was tunned off)
Strange though all these happened after connecting my new HDD, and never happened to me before.
and it seems that i am getting combination of bugcheck errors:
0x1000000a
0x1000007e
0x10000050
0x0000004e
0x00000044
0x100000d1
Hi Shaharam,
After further investigation of your minidumps, I confirm that this is hardware problem. The faulty hardware may be CPU, RAM or overheat.
Findinig
Mini072405-01.dmp crashed wth CLI_FAULT (ie clear interrupt fault)
Mini082205-01.dmp crashed at IRQL x'1C' and the module list are corrupted
Mini091905-03.dmp crashed at hal+0x2a16
After further investigation of your minidumps, I confirm that this is hardware problem. The faulty hardware may be CPU, RAM or overheat.
Findinig
Mini072405-01.dmp crashed wth CLI_FAULT (ie clear interrupt fault)
Mini082205-01.dmp crashed at IRQL x'1C' and the module list are corrupted
Mini091905-03.dmp crashed at hal+0x2a16
Otmakus
Posts: 50 +0
Hi Shahram, this is just a suggestion, but since ur problem came up after u installed ur new HD, maybe ur PSU doesn't have enough wattage to support another HD, or it's been damaged. Try to get another PSU and install it to ur computer to confirm it (with ur specification, make sure u use at least a 400W PSU or even more)
From my experience, restarting computers are caused by bad PSU, bad RAM, overheating, or something wrong with the M/B (lots of heavily used old M/B capacitors leaked and cause the computer to restart by itself)
From my experience, restarting computers are caused by bad PSU, bad RAM, overheating, or something wrong with the M/B (lots of heavily used old M/B capacitors leaked and cause the computer to restart by itself)
Thank u "cpc2004" & "Otmakus", I had 2 RAM which I checked seperatly, but the problem stayed.
I was waiting to puchase a new PSU, to see the results (after all it is worth trying this first before a CPU check).
But I came to realize that the restarts almost always happened when the program "bitcomet 0.60" was open and in use for a couple of hours.
and it never happened even with the previous versions of this same program.
I have no idea how this program can make it look like a HardWare problem, or there is some Hardware problem that I am not aware of.
But It has never happened otherwise and it is now working absolutly fine, like before.
I was waiting to puchase a new PSU, to see the results (after all it is worth trying this first before a CPU check).
But I came to realize that the restarts almost always happened when the program "bitcomet 0.60" was open and in use for a couple of hours.
and it never happened even with the previous versions of this same program.
I have no idea how this program can make it look like a HardWare problem, or there is some Hardware problem that I am not aware of.
But It has never happened otherwise and it is now working absolutly fine, like before.
Keeps Crashing
A few days ago the computer kept restarting. I changed the settings so that i wouldn't just restart and i would get the blue screen. The error listed in on the blue screen is:
Stop: 0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000)
The system has also been restored to a date earlier this week before the puter started crashing, but this didn't help at all!
I have attached a few of the most recent minidumps.
Any help would be fabulous!
A few days ago the computer kept restarting. I changed the settings so that i wouldn't just restart and i would get the blue screen. The error listed in on the blue screen is:
Stop: 0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000)
The system has also been restored to a date earlier this week before the puter started crashing, but this didn't help at all!
I have attached a few of the most recent minidumps.
Any help would be fabulous!
Hi Sean & Corrine,
I've studied your minidumps and I believe that it is ram problem.
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 can pass memtest.
Suggestion
1. Reseat the memory stick to another memory slot
2. Downclock the ram
3. Clean the inside the computer case
4. Make sure that the ram is compatible to the motherboard
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
I've studied your minidumps and I believe that it is ram problem.
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 can pass memtest.
Suggestion
1. Reseat the memory stick to another memory slot
2. Downclock the ram
3. Clean the inside the computer case
4. Make sure that the ram is compatible to the motherboard
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
I face the same problem as Shahram. My com works fine normally, but when i run BitComet 0.59 for some time, time ranging from a few minutes to a few hours, my com will suddenly restart, not in the normal shutdown way but like when you hold down the on button on your computer that restart.
Any help is much appreciated.
Any help is much appreciated.
Hi,
You must follow the rule "one thread for a new case". Open a new thread. The experts at this forum will look into your problem.
The crash may be caused by faulty ram or device driver error. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump. Check system event 1001 and 1003 and it has the content of the blue screen.
Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......
Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000
Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here
Zip 5 to 6 minidumps to a zip file and attach it here. Techspot has an upper limit of 100K per attachment. I will study the dump and find out the culprit.
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.
You must follow the rule "one thread for a new case". Open a new thread. The experts at this forum will look into your problem.
The crash may be caused by faulty ram or device driver error. When Windows crashes with blue screen, it writes a system event 1001 or 1003 and a minidump to the folder \windows\minidump. Check system event 1001 and 1003 and it has the content of the blue screen.
Event ID: 1001
Source: Save Dump
Description:
The computer has rebooted from a bugcheck.The bugcheck was : 0xc000000a (0xe1270188, 0x00000002, 0x00000000, 0x804032100).
Microsoft Windows..... A dump was saved in: .......
Event Source: System Error
Event Category: (102)
Event ID: 1003
Description:
Error code 1000007f, parameter1 0000000d, parameter2 00000000, parameter3 00000000, parameter4 00000000
Control Panel -> Adminstrative Tools -> Event Viewer -> System -> Event 1001/1003. Copy the content and paste it back here
Zip 5 to 6 minidumps to a zip file and attach it here. Techspot has an upper limit of 100K per attachment. I will study the dump and find out the culprit.
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.
- Status
Latest posts
-
Worry your friends with this $9,420 flamethrower robot dog- themastergoose replied
