Hello. I apologize for my bad English. I need help with my OS.
BSOD is usually going while watching on-line video.
I've some problems with downloading Windows_NT6_BSOD_jcgriff2. Here is dump files and config.
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 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.
Stop 0x124 - what it means and what to try
Thanks for information.
I've never overclocked anything. All devices are new. And I've checked CPU and memory by Prime 95 for 7 hours, My GPU by furmark with preset 1080 and burn-in test for 30 minutes. Also I've updated all drivers.
BSOD is never go while playing games or watching video from HDD.
Since you are using an SSD, some things to check:
- Is the SSD firmware up to date?
- Is your BIOS up to date?
- Are your chipset drivers up to date?
- Are your hard disk controller drivers up to date?
writhziden,
1. SSD OSZ Vertex 3, firmware - 2.22, was checked by CrystalDiskInfo 4.6.2 - it's OK.
2. MB GA-Z68MA-D2H-B3 rev 1.3 BIOS - F10
3. All chipset and controller drivers are up to date from this link:
http://www.gigabyte.ru/products/page...ownload/driver
they are the same like here:
GIGABYTE - Motherboard - Socket 1155 - GA-Z68MA-D2H-B3 (rev. 1.3)
4. Video driver is up to date by Nvidia Panel automatically.
I've switched off the second HDD and the PCI Express x16 video card. No result, same BSOD with integrated video card.
Today was one BSOD while gaming and three while watching online video.
So I've made 8 steps from "Generic "Stop 0x124" Troubleshooting Strategy". I can't made the 9th step because I haven't equivalent components
What else i can check before going to the shop's support?
Do you have the same problem if you install Windows on the HDD instead of the SDD? That is one part of 9 you could check. If you have the same problem, that would rule out the SSD as a problem. If you do not have the same problem, either the SSD is bad or it is incompatible with a piece of hardware or driver installed on the system.
Yes, I've installed Windows on the HDD, switched off SDD. Same problem:
On Wed 16.05.2012 16:52:40 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800805D028, 0xBE200000, 0x5110A)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown WHEA_UNCORRECTABLE_ERROR
P.S. Again while watching online video
My guess would be you have a faulty motherboard, CPU, or memory module. May also be a PSU issue. Here are the steps I usually give for these issues:You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.
WarningBefore you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer.WARNING: The steps that follow can void your warranty!!!
For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.
- If you are overclocking any hardware, please stop.
- Monitor temperatures during the following tests.
Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
- Follow the steps for doing CPU stress test using IntelBurnTest
- Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
- Shut down and turn off your computer.
- Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
- Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
- Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.
Remember to read closely through Stop 0x124 - what it means and what to try for the crash.
It was CPU. But it is not broken. I've changed motherboard, but it didn't help. I've bought intel 2500k and it works without BSOD. I think it was incompatibility with p67-68 chipset motherboards
Glad you found the solution. Thank you for posting back.
Quote