I have recently build a new computer and it has been crashing about 6 times this month, mainly during games. Please help this is frustrating... I would really appreciate it
This is the picture of the blue screen I have taken: Image - TinyPic - Free Image Hosting, Photo Sharing & Video Hosting
The dmps and msinfo32 summary are in this url from skydrive: https://skydrive.live.com/embed?cid=...G3-O9QTgsgu_h0
Ok so looking at the files provided, it appears that you are having hardware errors, but it may not be, so the first things to do:
Check for an update to your BIOS, this can be found on the motherboard manufacturers webpage.
If your are doing any overclocking please stop, this kind of error can often indicate a failed overclock.
After working on the stuff that Dsprague mentioned, you'll want to test your CPU using Prime95 on Large FFTs setting for a few hours. Make sure your CPU isn't getting cooked while running it by watching temperatures on Hwinfo with Sensors only option selected. Watch for the first 30 minutes, if it stabilizes at a good temp, then leave it for the duration of the test. If the system crashes during the test, send us the crashdump.
Also, if you have any software installed that came with your motherboard, uninstall all of it. This includes software that adds or improves features, as well as monitoring or overclocking software. Only keep and update device drivers for your motherboard, such as audio and network drivers.
Anyways, the thing is all your crashdumps report the same issue: that there's something wrong with your CPU's internal L2 data cache. My diagnosis right now is that your CPU is bad and needs replacing, and I'm quite confident on this being the reason, but I do know that BIOS and motherboard utility software can cause this problem too. Overclocking and temp problems can also generate it.
yea I think I havent updated the bios from the website I just put in the motherboard disk and downloaded whatever was in there. Was that the problem? I just got 2 more bsod in less than 10 min apart today and I have just downloaded the bios update from the site. Will see how it goes. One more thing to I have to download all versions of bios or just the latest one or is the last one an improvement over all the other updates?
Some useful reading ...
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. Otherwise, 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 harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. Be aware that attempting the subsequent harware 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.
This crashes only happen in game and Im wonder if it has to do with my graphics card driver software that I downloaded for my 7870 its called the "catalyst control center" for radeon graphics amd and I can control the brightness and colors from there. Each time I get on the desktop screen after login into my computer, my screen starts up at a darker color than changes up to a brighter color immediately like after 2 seconds. Idk if that driver is the problem that is forcing the bsod?
Vir Gnarus, it did crash 10-15 min into the prime95 test. The temperature was stable core 0 and 1 at 54-56 celcius and temp3 at 59-60 celsius all the other temperatures were about 40 celsius (I used speedfan to check temperatures).
Here is another sf diagnostics tool analysis file:
Yeah, it's the same WHEA error during Prime95 thread activity. Get that CPU replaced.
Quote