It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
General discussion (archive)Computer dying?(62 posts)(62 posts)
(62 posts)
Pages:
1
2
3
4
5
This is my favourite topic
Posted August 10, 2013
Can any of you help me out? I think my computer is about to die, as it's been getting bluescreens quite often. Well, not those old screens that turn blue, but a crash, followed by an error report stating bluescreen.

It did crash before, but it was few and far between. About a month ago it started getting those more frequently (curiously the crashes became more frequent after I bought a new mouse, probably irrelevant), crashing once day or so. Usually it freezes right after boot, when the desktop is loading. It just freezes, not closing down or anything, nor accepting any commands and I have to reset the system. Sometimes it freezes when idling. It has no clear pattern.

The error message states BCCode 124, which apparently means hardware failure. Any idea what component is about to give in? Graphics driver? Motherboard? Harddrive or even memory?

I really have no experience with this, so any help is appreciated.
No posts in this topic were marked as the solution yet. If you can help, add your reply
Posted August 10, 2013
I have no real experience of this, but my instinct says that you might be running out of memory. See if you have a lot of things running at startup, and if you can stop/remove any of them.
Posted August 10, 2013
Could be video card, software driver conflict or heat issue (my elementary guesses). Does it boot and work in safe mode?. Have u tried another mouse?
Posted August 10, 2013
Before telling you what's wrong, it is necessary to know exactly which error you are getting.

Also, need to know more about the specs:
CPU type, how much memory (how many DIMMs), type of video card, and most important of all, what operating system you are running (exact version).

The next thing is that if it is a Windows Bluescreen, it usually gives a STOP code with an hexadecimal number and some parameters (4 hexadecimal numbers in parenthesis), we will need that code.

After that, maybe we can tell what's wrong.

BTW, if you are not getting a blue screen, maybe you need to disable to automatically restart on error:

http://pcsupport.about.com/od/tipstricks/f/automatic-restart.htm
Post edited August 10, 2013 by Mentao
Posted August 10, 2013
avatar
KneeTheCap: Can any of you help me out? I think my computer is about to die, as it's been getting bluescreens quite often. Well, not those old screens that turn blue, but a crash, followed by an error report stating bluescreen.

It did crash before, but it was few and far between. About a month ago it started getting those more frequently (curiously the crashes became more frequent after I bought a new mouse, probably irrelevant), crashing once day or so. Usually it freezes right after boot, when the desktop is loading. It just freezes, not closing down or anything, nor accepting any commands and I have to reset the system. Sometimes it freezes when idling. It has no clear pattern.

The error message states BCCode 124, which apparently means hardware failure. Any idea what component is about to give in? Graphics driver? Motherboard? Harddrive or even memory?

I really have no experience with this, so any help is appreciated.
With this particular BSoD code, there should be more information in the Event Log. If you can get into Windows at all, open the Event Log and look for the appropriate entry; it may provide a hint about what the problem is.

If you can semi-reliably get the problem to show up at boot time, you might be able to use Safe Mode to figure it out; it shows you which drivers it's loading and if it freezes during that section, you will know the last driver it managed to load (and that driver would almost certainly be related to the problem).

If you're up for a more advanced troubleshooting technique, you can install the Debugging Tools and load a crash dump into it to get a lot of information about the crash - but it is really a tool targeted at people who know what they're doing. There's a guide here which should at least get you far enough to see the basic details which you can then pass on to us.
Post edited August 10, 2013 by Pidgeot
Posted August 10, 2013
This code could be related to a lot of hardware issues. In most cases, it means that Windows got a Machine check exception from the CPU.

This could be as simple as a failing ventirad, causing cpu overheating
Could be the motherboard
Could be the processor
Or the PSU not providing power enough anymore

Now, where to start ?

Open the case
Start the computer
Check the fan on the ventirad : does it function ?
Check the other fans
Check your bios to see if it mentions the cpu temperature

to provide further help, more info on the system would be welcome
Posted August 10, 2013
Don't forget to back up all valuable files on a lifeboat/external hdd. I wish I had done that six months ago.
Posted August 10, 2013
Open up your case and dust inside, backup any important data, if possible reinstall or have friend reset your OS, this might buy a few months to save up for a new machine.
Posted August 10, 2013
First try cleaning the fans, especially the CPU and the GPU fans.

Second, Is one of the fans is making an unusual noise such if it grating? If positive, then you need to replace this fan.

For the hard disk, if is malfuntioning, surelly that you can heard frecuents clicks on it.
Posted August 10, 2013
As for the mouse, it's a standard low-budget USB mouse, surely that can't kill a computer?

Heat is also not the issue, at it seems the CPU is running at 30-35 degrees and the GPU at 35-40 degrees. During playing, they won't rise that much.

Event log for errors ? Where can I find that in Win 7 64bit?

As for specs, here they are
Amd Athlon II X4 634 processor
8 gigs of ram, DDR3
nVidia GeForce GTS450 graphics card
Asus motherboard, I think its M4N75TD
Hard drives are a tad old, but they're not emitting any unusual sounds.

All fans work, and there's no dust in the computer.
Posted August 10, 2013
How old is your computer?
Old computer have a tendency to literally "eat" themselves. Some cpu`s have been known to corrode in a way that the information that is transporting inside are jumping the "lanes", or leaking, to say it easy. But that can happen to any circuits that have been stressed/warm overtime.

Does it happens right before or after putting in username/password and is about to log in? I`m assuming you have windows since you never said anything about it....
Right after boot, press the boot up button (usually F8), start in safemode. As mentioned by the others it might be hardware related, but you harddrive might also have been corrupted physically or on files. And you don`t always get a warning sound when a HDD is about to kneel.

To access eventviewer; press windows button + r. write eventvwr and press enter.

EDIT: Ignore the first one, it isn`t that old.
Post edited August 10, 2013 by sanscript
Posted August 10, 2013
I had similar issues with a PC when the PSU was insufficient and failing after adding some ram.
Posted August 10, 2013
avatar
KneeTheCap: As for the mouse, it's a standard low-budget USB mouse, surely that can't kill a computer?

Heat is also not the issue, at it seems the CPU is running at 30-35 degrees and the GPU at 35-40 degrees. During playing, they won't rise that much.

Event log for errors ? Where can I find that in Win 7 64bit?

As for specs, here they are
Amd Athlon II X4 634 processor
8 gigs of ram, DDR3
nVidia GeForce GTS450 graphics card
Asus motherboard, I think its M4N75TD
Hard drives are a tad old, but they're not emitting any unusual sounds.

All fans work, and there's no dust in the computer.
If your information is right, then the issue is not overheating.

It could still be a mouse issue, try connecting it in another USB port, just in case.

Still, try disabling the automatic restart to get the STOP Code, if any and try this utility:

http://www.almico.com/sfdownload.php

Just to check your hard drive, since you say they are a tad old.

Don't make any changes with the utility, since you can fry your CPU/motherboard, just run the hard drive test. First run the Short test and if it passes and nothing is found you can try the extended test, be aware that the extended test does take a while (maybe a few hours), depending on the size of the hard drive.
Posted August 10, 2013
I had this happening recently too, that I suspected was infection related, though normal scans weren't showing anything. I did a root kit scan; apparently there were a couple items that weren't working properly but they had to do with programs, not hardware, and now the problem seems to have gone away. Have you done a search for your particular error to see if anyone else has it and has a solution?
Posted August 10, 2013
When you can boot, I recommend doing a dskchk (I forget the command to fix any broken sectors found, but google is your friend) reboot, let it scan the entire hard drive (s) which can take anywhere from 30 minutes to 2+ hours, and then do a memchk (I believe that's the command) on your RAM.

The fact that it's always crashed is a sign that something may be unseated on the motherboard. A standard procedure when a machine is crashing like this is to carefully remove and re-seat (push into the mobo) each item such as RAM, graphics card, etc. Not sure how it applies to your error code and if it's worth trying, though, and tbh I'm too lazy to look up your error code at the moment.

I'll catch you on Steam if you're online and see if we can find something to help you.

~Cym
Pages:
1
2
3
4
5
This is my favourite topic
Community
General discussion (archive)Computer dying?(62 posts)(62 posts)
(62 posts)