Saturday, February 09, 2013 7:45 PMProblem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
OS Version: 6_1_7600
Service Pack: 0_0
Files that help describe the problem:
Read our privacy statement online:
If the online privacy statement is not available, please read our privacy statement offline:
Saturday, February 09, 2013 10:21 PM
Could you supply the dumps supplied at:
If you're unaware of how to do so, open "My Computer", click the location bar up top, and replace the information with those file locations to reveal the file.
Saturday, February 09, 2013 11:21 PM
Sunday, February 10, 2013 2:25 AM
The actual error that's getting returned is: CLOCK_WATCHDOG_TIMEOUT
The logs tell me this is happening in 'iw5sp.exe' (Call of Duty), so I assume this crash only occurs when you're doing things like playing games. Not accusing you of anything, but if by some chance this is a cracked copy of the game and it only occurs when you play this game, it could have to do with improper DRM removal from the exe.
Anyway, this crash seems to be happening when a stack is overflown in either the CPU and GPU, and it's probably the drivers fault, although it could be the hardware.
Things you can try:
- This is the most likely to fix your problem. Update to the latest video card and CPU drivers (in your case you have an i7-2600k) If there are no updates, do a repair on the drivers, or completely uninstall and then re-install them. Also, make sure that your BIOS is up to date. Here is the link to your specific motherboard's drivers: http://www.asus.com/Motherboard/P8P67M_PRO/#support_Download
- Re-install NET. Framework. The crash could be linked to broken dependencies that the game uses.
- Run an anti-virus scan using Malwarebytes, and run an anti-virus scan using AVG, Avast! or Kaspersky Free.
- Run an 'sfc /scannow' in cmd. You can do this by typing 'cmd' in the start menu, right clicking it, and running as administrator. Then type 'sfc /scannow' without quotes, hit enter, and wait for it to finish. If it said it fixed some problems, reboot. Otherwise, try the 5th solution.
- If you have built your computer yourself, there is a chance that your processor is loose and seated improperly. Check to make sure that your processor is locked in tight, if you didn't latch it down all the way it's definitely a possibility that it could be loose.
I know these solutions sound very generic, but I didn't copy and paste any of this information. I'm not one to read machine code so I can't step through the crash debug step-by-step, but I can definitely narrow it down to a driver issue coming from either your GPU or CPU, and these are just some ways that I think you'll be able to fix it.
I hope this helped!
- Edited by hackitfast Sunday, February 10, 2013 2:26 AM
Sunday, February 10, 2013 2:32 AMModerator
STOP 0x101: CLOCK_WATCHDOG_TIMEOUT Troubleshooting
Here's a good thread on http://www.sysnative.com/forums/showthread.php/1248-0x101-quote-A-clock-interrupt-was-not-received-on-a-secondary-processor-quote
What you're looking for will be in one of the following categories:
a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust, RFI, outright borkedness...) ?I wonder about CPU defect also)
So, check the drivers http://www.carrona.org/dvrref.php
Then check the inside of the case (temperature, voltage, dust, etc).
Then run hardware stress tests
Try this free video stress test: http://www.ozone3d.net/benchmarks/fur/
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit
Try this free stress test: Free Software - GIMPS
- 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 (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.
More Video Stress Tests:
1. Thanks to Vir Gnarus (http://www.sysnative.com/forums/members/vir-gnarus.html) for finding this video memory test: https://simtk.org/home/memtest
Alternate download link (w/o registration) located here: http://folding.stanford.edu/English/DownloadUtils
2. Two other video stress tests (may be more stressful than FurMark):
NOTE: I have had reports that some ISP's will block this website
Video Memory stress Test - http://nvworld.ru/utilities/vmt/
Artifact Locator - http://nvworld.ru/utilities/alocator/
Sorry, but I don't read the language that this website is made in.
3. Another interesting test that came to my attention: http://www.ocbase.com/perestroika_en/index.php?Download
USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!
CPU Stress Tests:
Only need to run 1 or 2 of the tests under most circumstances. I haven't used any of the tests myself, so I listed all that I was able to find.
- the test(s) suggested at this link are bootable: http://www.techsupportforum.com/foru...ml#post2232929
Then try replacing parts.
Then look up the versions of your BIOS to see what changes were done.
Recently it was found (here: BSOD Stop 0x00000101 and Stop 0x0000009c ) that a wipe and reinstall of Windows fixed a STOP 0x101 problem. I'd have to recommend at least running SFC.EXE /SCANNOW on any PC that has this problem (simply because it's too easy easy to do and it may fix things).
MS-MVP 2010, 2011, 2012 Team ZigZag
- Marked As Answer by Oats44 Sunday, February 10, 2013 4:14 AM
Sunday, February 10, 2013 2:36 AMSeems like I wasn't too far off ;)
Sunday, February 10, 2013 4:20 AM
Yes, it only crashes when I play games, and I can also assure you that game is 100% legal.
Thank you for the help!
Sunday, February 10, 2013 4:20 AMThank you for taking the time to help me!
Sunday, February 10, 2013 7:21 PMModeratorOur pleasure and good Luck
MS-MVP 2010, 2011, 2012 Team ZigZag