Sign in with
Sign up | Sign in
Your question

PC hardware crashing

Tags:
  • Hardware
  • Power Supplies
  • Systems
Last response: in Systems
Share
October 12, 2014 3:31:06 PM

Ok so here is the deal my brother installed a new gpu and power supply into a new tower (the old one wasn't working the button was broken) about 5 months ago, and the computer has been crashing ever since. so to describe the crash it happens like this; while i was playing civ 5 and listening to yanni in about 30 min of playing civ it just shutdown and then the pc restarts and it says windows has recovered from an unexpected shutdown this happens a lot not just playing civ but with a lot of games now i should say that some days or even weeks it doesn't crash and its fine. now this happened before then it stopped crashing for a while now its doing it again. ok so here is what it says Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004EC7038
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

i have no idea what this means can someone please help me. At first i thought it was a virus but i did a full scan with bit defender and nothing came up. I have a feeling that it is the hard drive but not sure. Now on a side note my brother installed a 7970 xfx amd card but it was crashing so much that i put back in my old card witch is a 7850 xfx amd. when i put back the old card it stop crashing but it seems to be back at it again. Ok to tell you what is inside my pc is i have a corsair CX600 power, a amd fx 6300 it had 6 cores and runs at 3.50 GHz, and i have 8 GB of ram i don't know the company and don't want to take it out :)  my motherboard is a asrock 960GM/U33S3 FX. my system heat is about 24c if you need anymore info please ask me is i spent so much time and money that i don't really have; to get this PC so i really need help fixing this. Ohh one more thing when i am not playing a game it doesn't crash as often it is very very rare for it to crash while just watch a movie or listening to music and only happened like once or twice

More about : hardware crashing

October 13, 2014 2:06:00 AM

Bug Check 0x124 is WHEA_UNCORRECTABLE_ERROR

It is almost always down to a hardware issue.


- Remove any over-clocking you may have.
- Install HWMonitor and check your temperatures aren't getting high. Run Prime95 to heavily stress the CPU.
- Download MemTest and burn the iso to a CD/DVD. Use this to test your RAM. Let it run for a good few hours.
- If your motherboard has on-board graphics try using those (just as a test).
- Update all hardware drivers to their newest versions.
Here is a troubleshooting guide from a Microsoft MVP on the matter...



Stop 0x124 is a hardware error
If you are overclocking try resetting your processor to standard settings and see if that helps.
If you continue to get BSOD here are some more things you may want to consider.
This is usually heat related, defective hardware, memory or even processor though it is"possible" that it is driver related (rare).

Stop 0x124 - what it means and what to try
Synopsis:

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.
Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.

2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.

3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware.
It is good practice to run the latest drivers anyway.

4) Update the motherboard BIOS according to the manufacturer's instructions.
Their website should provide detailed instructions as to the brand and model-specific procedure.

5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially.
The most obvious examples are the RAM and HDD(s).
For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors".
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps.
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes.
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the hardware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events.
Be aware that attempting the subsequent hardware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine.
Reseat all connectors and memory modules.
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
m
0
l
!