How to fix the incorrigible Whea error!

I just got a new card (PowerColor Radeon HD 7950) and whenever I try to play a game a blue screen comes up saying Whea_Uncorrectable_Error. I know that I need to post my Minidump files but now I know how. Please explain to me how to publish the file and I will! Thank you very much!

Risk

I would start by removing Symantec and using the built-in Defender.

Symantec is a common cause of BSOD.
I remove and replace it with Microsoft Security Essentials at LEAST FOR TESTER
http://us.Norton.com/support/kb/web_view.jsp?wv_type=public_web&docURL=20080710133834EN
Use it to Norton 360 http://Symantec.pcperformancetools.com/Norton-360-how-to-uninstall.html 

If after that you still break

Stop 0 x 124 is a hardware error
If you are overclocking try to reset your settings to standard processor and see if that helps.
If you keep getting the BSOD here are things more than you may want.
This is usually hardware related, defective heat, memory or processor even if it is "possible" he is associated (rare) driver.

Stop 0 x 124 - what it means and what to try
Synopsis:
A "stop 0 x 124" is fundamentally different from many other types of bluescreens because it arises from a complaint of material.
Stop 0 x 124 minidumps contain very little concrete information, and it is therefore necessary to address the problem as a case of material in an unknown state of distress.

Generic troubleshooting ' Stop 0 x 124 ":

1) to ensure that none of the hardware components are overclocked. Material which is pushed beyond its design specifications - by overclocking - may malfunction in unpredictable ways.
(2) ensure that the machine is sufficiently cooled.
If there is doubt, open the side of the case (be aware of all the relevant conditions guaranteed!) PC and direct an electric fan squarely to the motherboard. Who will rule on most cooling problems (lack of).
3) update all drivers related to materials: video, sound, RAID (if applicable), NIC... anything that interacts with a piece of hardware.
It is best to run the latest drivers anyway.
(4) update the BIOS of your motherboard according to the manufacturer's instructions.
Their website should provide detailed instructions on the brand and model-specific procedure.
(5) rarely, bugs in the operating system may cause "false positives" 0 x 124 events where the hardware wasn't complaining, but Windows thought otherwise (because of the bug).
At the time of writing, Windows 7 does not have to suffer from a defect, but it is nevertheless important to keep Windows up-to-date.
6) trying (stress) test these hardware components that can be put to the test artificially.
The most obvious examples are the RAM and HDD (s).
For the RAM, use diagnostics from built-in memory (run MDSCHED) or the utility memtest86 3rd - party to run plenty of evidence of hours of testing.
For hard drives, verify if CHKDSK /R finds any problems on (s), including "bad sectors".
Unreliable RAM, in particular, is mortal, as well as software, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result the diagnostic utilities does not guarantee that the RAM is free of any defect - only that none have been encountered during the test passes.
7) as the last of the non-invasive troubleshooting steps, perform a "Vanilla" Windows reinstallation: just the OS itself without additional applications, games, utilities, updates, new drivers - or ANYTHING that does not come from the Windows 7 disc.


Who stops working mitigate the problem of the 0 x 124, jump to the next step.
If you run the "Vanilla" installation long enough to convince yourself that not a single 0 x 124 accident occurred, start installing applications and updates slowly, always stopping between successive additions long enough to get an idea of the question if the machine is still free of 0 x 124 breaks down.
Smash back, obviously the latest addition of software may be somehow connected to the root cause.
If the stop error 0 x 124 persist despite the above steps, and the equipment is under warranty, consider to go back and ask for a replacement that does not suffer periodic MCE events.
Be aware that want to perform the subsequent hardware troubleshooting steps can, in some cases, void your warranty:
(8) clean and carefully remove the dust inside the machine.
Reinstall all memory modules and connectors.
Use a can of compressed air to clean the RAM DIMM supports 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 that can be eliminated.
Obviously, this type of testing is much easier if you have access to equivalent components in order to perform swaps.

If you are in the situation to have completed all the steps above without a resolution of the symptom, unfortunately the most likely reason is that the error message is literally correct - something is fundamentally wrong with the hardware of the machine.

Tags: Windows

Similar Questions

Maybe you are looking for