My computer crashed few minutes ago when i was trying to play a game ( Counter Strike: Source ). When it was shutting down, there were blue screen with text saying something about hardware and errors. I just want to know, if my system is okay, This computer is brand new. Link to dmp file: http://www.mediafire.com/?tfyrrzd40omfdcv Thanks in advance. :) - Benjamin

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" re-installation 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 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. Re-seat 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. ===================================================== Background Information: Windows passes on the hardware error report in the form of a "stop 0x124" because it can't do anything else once the hardware has signaled an uncorrectable fault condition. In technical terms, the vast majority of stop 0x124 crashes correspond to "Machine Check Exceptions" (MCEs) issued by the processor to alert the software to the existence of a hardware problem. It's possible for drivers to indirectly induce hardware to register MCEs by "driving" in ways that are confusing to the hardware, but from a user's point of view that distinction is so subtle as to be invisible. It is important to note that there are many different possible MCE triggers, and one machine's stop 0x124 is likely to be entirely different to another's. Hence, it is best not to place too much emphasis on very specialized ways in which other individuals have resolved their own 0x124 problems - the more exotic the other machine's MCE solution, the less likely it is to apply to your own setup. It is possible - but painful - to interpret the hardware's error report. It's passed along in the so-called "MCi_Status" register, the contents of which are generally visible as bugcheck parameters 3 and 4 on the BSOD screen, as well as in the corresponding minidump. The trouble is that the hardware's complaints are almost never "practical", in the sense that they would explain what is wrong in layman's terms and include a recommendation for how to fix it. Instead, it's esoteric stuff which is intended for hardware specialists and driver developers. Interpreting MCi_Status Contents: This is not a viable troubleshooting methodology for most cases of stop 0x124 crashes, both because of the procedure's complexity and the impracticality of the resultant output. It is included here for the sake of completeness, and in case anyone should wish to go to the extreme in an attempt to understand recalcitrant stop 0x124 crashes on their machine. Interpreting the numbers a matter of consulting information published by Intel and AMD. The MCi_Status register contents are a bitmask, and each individual bit has a very specific meaning. Reference: http://download.intel.com/design/pro...als/253668.pdf http://www.amd.com/us-en/assets/cont...docs/24593.pdf Machine Check Exception - Wikipedia, the free encyclopedia As an example, a hypothetical stop 0x124 crash may pass on an MCi_Status from the hardware whose contents are below: 1011001000000000000000000001100000000110000000000000111000001111 3210987654321098765432109876543210987654321098765432109876543210 ___6_________5_________4_________3_________2_________1 Interpretation is performed based on the position of each significant bit, starting from "63" on the far left and ending with bit "0" on the far right: 63: VAL - MCi_STATUS register valid 61: UC - Error uncorrected 60: EN - Error enabled 57: PCC - Processor context corrupt 36: component has received a parity error on the RS[2:0]# pins for a response transaction. 35: (Reserved) 27/26/25: Bus queue error type = "Response Parity Error" (011) MCA [15:0]: 0000 1110 0000 1111 000F 1PPT RRRR IILL F: "Normal" filtering (0) PP: Generic (11) T: Request did not time out (0) RRRR: Generic Error (0000) II: Other transaction (11) LL: Memory hierarchy level "generic" (11) Thanks to Andre (H2SO4) for the text and use of this information.MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag

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" re-installation 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 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. Re-seat 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. ===================================================== Background Information: Windows passes on the hardware error report in the form of a "stop 0x124" because it can't do anything else once the hardware has signaled an uncorrectable fault condition. In technical terms, the vast majority of stop 0x124 crashes correspond to "Machine Check Exceptions" (MCEs) issued by the processor to alert the software to the existence of a hardware problem. It's possible for drivers to indirectly induce hardware to register MCEs by "driving" in ways that are confusing to the hardware, but from a user's point of view that distinction is so subtle as to be invisible. It is important to note that there are many different possible MCE triggers, and one machine's stop 0x124 is likely to be entirely different to another's. Hence, it is best not to place too much emphasis on very specialized ways in which other individuals have resolved their own 0x124 problems - the more exotic the other machine's MCE solution, the less likely it is to apply to your own setup. It is possible - but painful - to interpret the hardware's error report. It's passed along in the so-called "MCi_Status" register, the contents of which are generally visible as bugcheck parameters 3 and 4 on the BSOD screen, as well as in the corresponding minidump. The trouble is that the hardware's complaints are almost never "practical", in the sense that they would explain what is wrong in layman's terms and include a recommendation for how to fix it. Instead, it's esoteric stuff which is intended for hardware specialists and driver developers. Interpreting MCi_Status Contents: This is not a viable troubleshooting methodology for most cases of stop 0x124 crashes, both because of the procedure's complexity and the impracticality of the resultant output. It is included here for the sake of completeness, and in case anyone should wish to go to the extreme in an attempt to understand recalcitrant stop 0x124 crashes on their machine. Interpreting the numbers a matter of consulting information published by Intel and AMD. The MCi_Status register contents are a bitmask, and each individual bit has a very specific meaning. Reference: http://download.intel.com/design/pro...als/253668.pdf http://www.amd.com/us-en/assets/cont...docs/24593.pdf Machine Check Exception - Wikipedia, the free encyclopedia As an example, a hypothetical stop 0x124 crash may pass on an MCi_Status from the hardware whose contents are below: 1011001000000000000000000001100000000110000000000000111000001111 3210987654321098765432109876543210987654321098765432109876543210 ___6_________5_________4_________3_________2_________1 Interpretation is performed based on the position of each significant bit, starting from "63" on the far left and ending with bit "0" on the far right: 63: VAL - MCi_STATUS register valid 61: UC - Error uncorrected 60: EN - Error enabled 57: PCC - Processor context corrupt 36: component has received a parity error on the RS[2:0]# pins for a response transaction. 35: (Reserved) 27/26/25: Bus queue error type = "Response Parity Error" (011) MCA [15:0]: 0000 1110 0000 1111 000F 1PPT RRRR IILL F: "Normal" filtering (0) PP: Generic (11) T: Request did not time out (0) RRRR: Generic Error (0000) II: Other transaction (11) LL: Memory hierarchy level "generic" (11) Thanks to Andre (H2SO4) for the text and use of this information.MS-MVP 2010, 2011, 2012 Sysnative.com Team ZigZag

Hi , Perform the steps from the article and check whether the issue persists. https://support.steampowered.com/kb_article.php?ref=9402-MKEN-1517 Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.Tracy Cai TechNet Community Support

Hi , Perform the steps from the article and check whether the issue persists. https://support.steampowered.com/kb_article.php?ref=9402-MKEN-1517 Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.Tracy Cai TechNet Community Support

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa80096bc028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: hl2.exe CURRENT_IRQL: f STACK_TEXT: fffff800`00ba8a98 fffff800`03608a3b : 00000000`00000124 00000000`00000000 fffffa80`096bc028 00000000`be000000 : nt!KeBugCheckEx fffff800`00ba8aa0 fffff800`0319ab03 : 00000000`00000001 fffffa80`0721a9c0 00000000`00000000 fffffa80`0721aa10 : hal!HalBugCheckSystem+0x1e3 fffff800`00ba8ae0 fffff800`03608700 : 00000000`00000728 fffffa80`0721a9c0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263 fffff800`00ba8b40 fffff800`03608052 : fffffa80`0721a9c0 fffff800`00ba8e70 fffffa80`0721a9c0 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff800`00ba8c90 fffff800`03607f0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff800`00ba8cd0 fffff800`035fbe88 : 00000000`00000001 00000000`65e122b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff800`00ba8d00 fffff800`0308baac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff800`00ba8d30 fffff800`0308b913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff800`00ba8e70 00000000`76f91725 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 00000000`1827f698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f91725 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE Followup: MachineOwner --------- -------------------------------------------- Bug Check Code 0x124: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557321%28v=vs.85%29.aspx As I see, there is something wrong with the processor. Please start by updating its driver and your firmware / BIOS and then check results. If this does not help, contact Intel / your manufacturer Technical Support for assistance. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* WHEA_UNCORRECTABLE_ERROR (124) A fatal hardware error has occurred. Parameter 1 identifies the type of error source that reported the error. Parameter 2 holds the address of the WHEA_ERROR_RECORD structure that describes the error conditon. Arguments: Arg1: 0000000000000000, Machine Check Exception Arg2: fffffa80096bc028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: hl2.exe CURRENT_IRQL: f STACK_TEXT: fffff800`00ba8a98 fffff800`03608a3b : 00000000`00000124 00000000`00000000 fffffa80`096bc028 00000000`be000000 : nt!KeBugCheckEx fffff800`00ba8aa0 fffff800`0319ab03 : 00000000`00000001 fffffa80`0721a9c0 00000000`00000000 fffffa80`0721aa10 : hal!HalBugCheckSystem+0x1e3 fffff800`00ba8ae0 fffff800`03608700 : 00000000`00000728 fffffa80`0721a9c0 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263 fffff800`00ba8b40 fffff800`03608052 : fffffa80`0721a9c0 fffff800`00ba8e70 fffffa80`0721a9c0 00000000`00000000 : hal!HalpMcaReportError+0x4c fffff800`00ba8c90 fffff800`03607f0d : 00000000`00000004 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e fffff800`00ba8cd0 fffff800`035fbe88 : 00000000`00000001 00000000`65e122b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55 fffff800`00ba8d00 fffff800`0308baac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff800`00ba8d30 fffff800`0308b913 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff800`00ba8e70 00000000`76f91725 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 00000000`1827f698 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f91725 STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner MODULE_NAME: hardware IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_MAE Followup: MachineOwner --------- -------------------------------------------- Bug Check Code 0x124: http://msdn.microsoft.com/en-us/library/windows/hardware/ff557321%28v=vs.85%29.aspx As I see, there is something wrong with the processor. Please start by updating its driver and your firmware / BIOS and then check results. If this does not help, contact Intel / your manufacturer Technical Support for assistance. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Thanks for help, and sorry for replying in such long time. I think the problem was bin folder in CS:S. I deleted it and this hasn't happened since.

Thanks for help, and sorry for replying in such long time. I think the problem was bin folder in CS:S. I deleted it and this hasn't happened since.