BSOD when booting. Error 0x00000101

Hi again. Just wondering whether anybody has any opinions or advice on this for me?

Just wondering whether anybody has any advice at all on this?

STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Start with the above and post back if you need help after reading through that guide.

writhziden said:

STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

Start with the above and post back if you need help after reading through that guide.

Thanks for the reply, it's nice that someone out of the 150+ that have viewed my thread, has actually taken the time to offer some help.

I've read those posts you have linked, and I have a couple of issues.

1) My BSOD screen doesn't mention the clock watchdog timeout anywhere, so I'm a little confused as to whether this is the same error or not.

2) I can't run any of those stress tests or driver test as my machine won't boot to the desktop at all. Even in safe mode. I've done some hardware diagnosis on the memory modules and gfx card, by removing them from the M/B and seeing if that maybe is a reason for the BSOD. Like a faulty memory module, or gfx card, but the same BSOD error happens. So short of doing a clean install of the OS or buying a new CPU, I'm sort of at a loss personally now.

And if it is the CPU, which is hardware, I don't actually see what doing a full re-install of my OS will do. I don't ever remember a piece of software being able to magically repair a piece of faulty hardware.

As you can see in the link I gave, I found out that a clean re-install can resolve the error you are getting. In most cases, a 0x101 BugCheck is due to a hardware problem, but there are some times when the clock interrupt is caused by a faulty driver, software conflict, or a damaged Windows installation.

And yes, your blue screen image you attached is consistent with the Watchdog Timeout crash.


You may want to read through Clean Reinstall - Factory OEM Windows 7 which will guide you in backing up any important data you have on the system and doing a fresh install of Windows 7. Hopefully you are one of the rare cases where the 0x101 BugCheck is software related and not hardware related. Best of luck!

writhziden said:

As you can see in the link I gave, I found out that a clean re-install can resolve the error you are getting. In most cases, a 0x101 BugCheck is due to a hardware problem, but there are some times when the clock interrupt is caused by a faulty driver, software conflict, or a damaged Windows installation.

And yes, your blue screen image you attached is consistent with the Watchdog Timeout crash.


You may want to read through Clean Reinstall - Factory OEM Windows 7 which will guide you in backing up any important data you have on the system and doing a fresh install of Windows 7. Hopefully you are one of the rare cases where the 0x101 BugCheck is software related and not hardware related. Best of luck!

Cheers. I'll have a read of the info now and see what I decide to do.

So, this morning I've managed to boot into safe mode only. Any attempt to boot into Windows normally fails every time. So as I can only boot into safe mode, I"m unable to run a system health report as that function isn't available in safe mode.

I can try and attach the .dmp file to this post if i'm quick before it crashes on me. Even in safe mode. If that's any help

Managed to be able to boot into the desktop for long enough to run the performance test. So I've attached it to this post now. The .dmp files have been attached to the previous post. Hope this can help me get some more specific info

All crashes were 0x124 or 0x101 crashes. It is safe to say this is a hardware issue. I gave you the 0x101 crash information in a previous post with the link: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg





BugCheck 0x124

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.

   Warning

Before 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.
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• Run all but the advanced tests with SeaTools for HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• 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:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. 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. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  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.