locked
Blue Screen of Death stop code 0x124 RRS feed

  • Question

  • recently put this computer together (first time building one) after 1-2 hours of my pc being on it will blue screen any ideas on how to solve this problem any help appreciated

    SPECS:

    mother board:ASUS Maximus VI EXTREME LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 ATX Intel Motherboard

    memory:Corsair Dominator 16 GB (2 x 8 GB) DDR3 1600 MHz (PC3 12800) Desktop Memory CMP16GX3M2A1600C11

    processor:Intel Core i7-4790K Processor (8M Cache, up to 4.40 GHz) (BX80646I74790K)

    graphics card:EVGA GeForce GTX 770 Superclocked with ACX Cooler 4 GB GDDR5 256-Bit Dual-Link DVI-I/DVI-D HDMI DP SLI Ready Graphics Card 04G-P4-3774-KR

    hard drive:Western Digital Caviar Black 2 TB SATA III 7200 RPM 64 MB Cache Bulk/OEM Internal Desktop Hard Drive - WD2002FAEX

    Tuesday, September 9, 2014 6:55 PM

Answers

  • https://onedrive.live.com/redir?resid=905C1457C6DF5F1D%21122   dump files
    not sure if that'll work first time using this site

    MG

    These are called BCC124 and are related to hardware.  SInce "genuine Intel" is mentioned I would start by running a cpu stress test

    Try this free stress test:  http://www.mersenne.org/freesoft/

    Prime95 Setup;
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test.  If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
    The Test selection box and the stress.txt file describes what components that the program stresses.

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\New folder\090914-24367-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`03055890
    Debug session time: Tue Sep  9 14:39:35.781 2014 (UTC - 4:00)
    System Uptime: 0 days 1:06:56.654
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800ed61028, be000000, 100110a}
    
    Probably caused by : GenuineIntel
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa800ed61028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  f
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    STACK_TEXT:  
    fffff800`00ba8a98 fffff800`03409a3b : 00000000`00000124 00000000`00000000 fffffa80`0ed61028 00000000`be000000 : nt!KeBugCheckEx
    fffff800`00ba8aa0 fffff800`02f9e463 : 00000000`00000001 fffffa80`0ed64a60 00000000`00000000 fffffa80`0ed64ab0 : hal!HalBugCheckSystem+0x1e3
    fffff800`00ba8ae0 fffff800`03409700 : 00000000`00000728 fffffa80`0ed64a60 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
    fffff800`00ba8b40 fffff800`03409052 : fffffa80`0ed64a60 fffff800`00ba8e70 fffffa80`0ed64a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`00ba8c90 fffff800`03408f0d : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`00ba8cd0 fffff800`033fce88 : 00000000`15a10000 00000000`152cd400 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`00ba8d00 fffff800`02e864ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`00ba8d30 fffff800`02e86313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`00ba8e70 00000000`5d9b81ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`002eeeb4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5d9b81ee
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache
    
    FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
    
    Followup: MachineOwner
    ---------
    
    
    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 BSODs 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 and clear the CMOS.
    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 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    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.

    More advanced reading can be found here from a MS MVP IT PRO
    Text by H2SO4


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Michael_LS Friday, September 19, 2014 2:45 AM
    • Marked as answer by ZigZag3143x Wednesday, September 24, 2014 11:46 PM
    Tuesday, September 9, 2014 8:01 PM

All replies

  • Go to c:\windows\minidump, zip and post the dump file here for analysis

    Please always verify and test replies you get on this forum before applying them to a production environment!

    Tuesday, September 9, 2014 7:01 PM
  • https://onedrive.live.com/redir?resid=905C1457C6DF5F1D%21122   dump files
    not sure if that'll work first time using this site
    Tuesday, September 9, 2014 7:13 PM
  • From your dump, I see hardware error. 

    To resolve 0x124 errors, perform the steps listed here.

    http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html


    Please always verify and test replies you get on this forum before applying them to a production environment!

    Tuesday, September 9, 2014 7:51 PM
  • https://onedrive.live.com/redir?resid=905C1457C6DF5F1D%21122   dump files
    not sure if that'll work first time using this site

    MG

    These are called BCC124 and are related to hardware.  SInce "genuine Intel" is mentioned I would start by running a cpu stress test

    Try this free stress test:  http://www.mersenne.org/freesoft/

    Prime95 Setup;
    - extract the contents of the zip file to a location of your choice
    - double click on the executable file
    - select "Just stress testing"
    - select the "Blend" test.  If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
    - "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
    The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
    Then run the test for 6 to 24 hours - or until you get errors [b](whichever comes first)
    The Test selection box and the stress.txt file describes what components that the program stresses.

    Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\New folder\090914-24367-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*C:\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`03055890
    Debug session time: Tue Sep  9 14:39:35.781 2014 (UTC - 4:00)
    System Uptime: 0 days 1:06:56.654
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800ed61028, be000000, 100110a}
    
    Probably caused by : GenuineIntel
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: fffffa800ed61028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 000000000100110a, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  f
    
    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
    
    STACK_TEXT:  
    fffff800`00ba8a98 fffff800`03409a3b : 00000000`00000124 00000000`00000000 fffffa80`0ed61028 00000000`be000000 : nt!KeBugCheckEx
    fffff800`00ba8aa0 fffff800`02f9e463 : 00000000`00000001 fffffa80`0ed64a60 00000000`00000000 fffffa80`0ed64ab0 : hal!HalBugCheckSystem+0x1e3
    fffff800`00ba8ae0 fffff800`03409700 : 00000000`00000728 fffffa80`0ed64a60 fffff800`00ba8e70 fffff800`00ba8e00 : nt!WheaReportHwError+0x263
    fffff800`00ba8b40 fffff800`03409052 : fffffa80`0ed64a60 fffff800`00ba8e70 fffffa80`0ed64a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`00ba8c90 fffff800`03408f0d : 00000000`00000008 00000000`00000001 fffff800`00ba8ef0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`00ba8cd0 fffff800`033fce88 : 00000000`15a10000 00000000`152cd400 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`00ba8d00 fffff800`02e864ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`00ba8d30 fffff800`02e86313 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff800`00ba8e70 00000000`5d9b81ee : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`002eeeb4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5d9b81ee
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_cache
    
    FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}
    
    Followup: MachineOwner
    ---------
    
    
    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 BSODs 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 and clear the CMOS.
    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 3rd-party memtest86 utility to run many hours worth of testing. (6-8 passes to stress the ram out)
    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.

    More advanced reading can be found here from a MS MVP IT PRO
    Text by H2SO4


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Michael_LS Friday, September 19, 2014 2:45 AM
    • Marked as answer by ZigZag3143x Wednesday, September 24, 2014 11:46 PM
    Tuesday, September 9, 2014 8:01 PM
  • i did the stress test twice to be sure both times it ran for about 5 seconds before i blue screened. does the fact that it errors so quickly mean i should replace the processor reinstall windows or what? And thank you for all your help 

    P.S. i'm not overclocking anything

    Wednesday, September 10, 2014 5:52 AM
  • MG

    If Prime 95 crashed after 5 seconds it just makes it more likely that it is the CPU.  Have you run the RAM test, etc?
    • Edited by ZigZag3143x Wednesday, September 10, 2014 6:09 AM
    Wednesday, September 10, 2014 6:07 AM
  • they all ultimately end in me blue screening

    within 10 minutes

    • Edited by monkeygod113 Wednesday, September 10, 2014 7:57 AM
    Wednesday, September 10, 2014 7:56 AM
  • Then you have your answer. Before jumping off to get a new processor, follow the basic guide for managing blue screens as earlier posted. 

    Please always verify and test replies you get on this forum before applying them to a production environment!

    Wednesday, September 10, 2014 8:07 AM
  • i did everything on the guide even vanilla install windows 7 i still got a blue screen 124
    Thursday, September 11, 2014 2:42 AM
  • MG

    IF a clean install crashes with a BCC124 it is even more confirmation that it is hardware related.  You have not been very specific as to the results of the tests but my guess is it is either CPU or motherboard related.


    Wanikiya and Dyami--Team Zigzag

    Thursday, September 11, 2014 11:22 AM
  • with the prime 95 test i'm not sure what i'm supposed to be looking for if you could tell me i would more than happy to be more specific 
    Thursday, September 11, 2014 11:34 AM
  • Hi,

    Was your issue resolved?

    It most likely the hardware issue. Since you have tried the above suggestion, I recommend you had better do a hardware diagnoses.

    Look forward to your reply and tell us the current situation in order to provide further help.


    Karen Hu
    TechNet Community Support

    Monday, September 15, 2014 8:06 AM
  • To be frank, I am not good at fixing the computer problem. The same case once happened to me. I nearly lost my faith. At the end my friend recommended Windows Boot Genius to me. With this tool I successfully got the problem fixed. You can find the program in this page: {link removed}

    • Edited by ZigZag3143x Friday, November 21, 2014 12:56 PM Link removed
    • Edited by KarelRose Wednesday, November 26, 2014 3:07 AM
    Friday, November 21, 2014 7:44 AM