locked
Someone Help. Blue Screen Problem Signature, What does this mean? How do I fix it? RRS feed

  • Question

  • OS Version: 6.1.7600.2.0.0.256.1

    Locale ID: 1033

     

    Additional:

    BCCode: 124

    BCP1: 00000000

    BCP2: 856928FC

    BCP3: 00000000

    BCP4: 00000000

    OS Version: 6_1_7600

    Service Pack 0_0

    Product 256_1

     

    Please, I need to know what this information means and how can I fix it? Thank you, you may contact me at York899@aol.com
    Tuesday, December 7, 2010 1:51 AM

Answers

  • you have a fatal hardware error:

    Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

    This bug check indicates that a fatal hardware error has occurred.

    http://msdn.microsoft.com/en-us/library/ff557321%28VS.85%29.aspx


    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Thursday, December 9, 2010 5:52 PM
    • Marked as answer by Arthur Xie Monday, December 13, 2010 6:04 AM
    Tuesday, December 7, 2010 2:37 PM
  • You may boot in Clean Boot Mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging




    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Monday, December 13, 2010 6:04 AM
    Thursday, December 9, 2010 6:05 AM

All replies

  • you have a fatal hardware error:

    Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR

    This bug check indicates that a fatal hardware error has occurred.

    http://msdn.microsoft.com/en-us/library/ff557321%28VS.85%29.aspx


    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Proposed as answer by Andre.Ziegler Thursday, December 9, 2010 5:52 PM
    • Marked as answer by Arthur Xie Monday, December 13, 2010 6:04 AM
    Tuesday, December 7, 2010 2:37 PM
  • You may boot in Clean Boot Mode.

    Perform a clean startup to determine whether background programs are interfering with your game or program

    If the issue persists in Clean Boot Mode you can try to check the driver signature. To do so, in Start Search box enter sigverif.exe. Then click the start button in “File Signature Verification”. In the result list, please pick up *.sys files, rename one of them and then shut down or restart to check if the issue still occurs. If the issue persists, rename another *.sys file listed in the result of driver signature verifying, and check result again. By doing so we can determine which un-singed driver is the root cause.

    Another way is enable muni-dump and use Windbg. Please refer:

    How to read the small memory dump files that Windows creates for debugging




    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
    • Marked as answer by Arthur Xie Monday, December 13, 2010 6:04 AM
    Thursday, December 9, 2010 6:05 AM