locked
BSOD 0x00000124 for Windows 7 64 bit RRS feed

  • Question

  • Can anybody help me with this issue? I am unsure how to output the log to a dump file for further analysis.

    My computer info is:

       Processor: 2.30 GHz AMD Phenom 9600 Quad-Core

       MB: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H

       Video Cards: ATI Radeon HD 3200 onboard video, Radeon HD 4670
     
       OS: Windows 7 64 bit

    I've been checked the hotfixes offered by Microsoft but there aren't any available for Windows 7 64 bit. I do not know if the hotfixes for Windows Vista 64 bit can be used to fix this problem or not.

    I've tried updating my BIOS and then restoring my BIOS to its factory settings but neither seemed to work. I've installed drivers via windows update, from the gigabyte website, and from the ATI website trying to update to the latest drivers. I've used Ultimate Boot CD to test my RAM and HDD, I've used Hot CPU Tester Pro 4 to test my CPU, I've tried using my PCI-E video card and my onboard video card (separately of course), but all these tests have not shown any errors or problems with the hardware devices. The only ones that I haven't really tested are my PSU and MB (the sound card is onboard). I've even performed a clean installation of windows 7 64 bit (previously using Windows Vista 32 bit) but the problem still persists. I am not sure what else to test without just buying new hardware.

    This error normally happens when I play a video game (like World of Warcraft) but lately when I try to install patches or games in general I seem to get the BSOD.

    Can anyone help me please? Just let me know if you would need more information about my system or how I can get to my logs (the dump files) so I can provide more information.

    Thanks
    • Moved by Carey FrischMVP Monday, August 16, 2010 2:47 AM Moved to relevant forum category (From:Windows 7 Installation, Setup, and Deployment)
    Monday, August 16, 2010 1:19 AM

Answers

  • Please zip and upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps.

    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/
    • Marked as answer by Arthur Xie Friday, August 20, 2010 10:02 AM
    Monday, August 16, 2010 11:26 AM
  • You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel 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

    You may paste the result in your next post for analyzing.


    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 Friday, August 20, 2010 10:02 AM
    Wednesday, August 18, 2010 6:38 AM

All replies

  • In order to troubleshoot your problem we need to know more detailed specs of your system hardware.

    1. Go to Start > Run, and type msinfo32, look under the Components section for hardware identification
    2. Go to Control Panel > Device Manager and look for any entry that has a yellow flag beside it
    3. The manufacturer name and model number of your PC, if applicable
    4 Please fill out your computers specs in the User Control Panel here on the site as well. It will then appear next to your name. look at my posting and you'll see the drop-down arrow.

    The exact make and model of your motherboard would be of great help also.
    Are you using the 32-bit or 64-bit version?
    Was it a "clean" install or an upgrade?
    Are you dual-booting?
    Monday, August 16, 2010 8:08 AM
  • Please zip and upload the dmp files from the folder C:\Windows\Minidump to your Skydrive [1] (copy the dmp files first to your desktop, if you can't upload them) and post a link here, so that I can look at the dumps.

    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/
    • Marked as answer by Arthur Xie Friday, August 20, 2010 10:02 AM
    Monday, August 16, 2010 11:26 AM
  • You may boot in Clean Boot Mode as BSOD can be caused by programs that are running in kernel 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

    You may paste the result in your next post for analyzing.


    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 Friday, August 20, 2010 10:02 AM
    Wednesday, August 18, 2010 6:38 AM
  • My 1st guess would be that the PC is overheating somewhere.

    (CPU Fan/Heatsink, Video Card or Case Veni

    Tuesday, July 1, 2014 8:16 PM