BSOD Under Stress - A Clock Interrupt was not recieved

[Etot]

Full BSOD: A clock interrupt was not received by a secondary processor within the allocated time interval.


Hi,

I just built a computer for the first time and it seems to be working fine except for this single BSOD I keep getting. At first I thought it happened just at random times until I started realizing a pattern. First thing I realized was that it only happened when I was playing World of Warcraft for about an hour. I checked my CPU temp while playing WoW and it seemed to go up from 28 to about 38-45. That doesn't seem right to me. But it seems that when it gets to around that 45-50 degrees celcius, it gets this BSOD. I confirmed this when I tried to play Assassin's Creed: Revalations. Apparently AC using more memory and heats up the CPU much quicker than WoW. I get the BSOD the second the I load my save. Also, I tried to do the stress test mentioned in this post: http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html. I was not monitoring my CPU temp when I did it, but I got the same BSOD the second I started the "Small FFTs" test.

If anyone could help me I would be extremely thankful. I guess I should mention this is my first time building a computer. I ordered all the parts off the internet and put them together myself about two weeks ago.

System specs:
OS: Windows 7 Home Premium x64 (bought retail and installed manually)
Processor: QuadCore Intel Core i7-2600, 4018 MHz
Motherboard: Asus P8P67-M Pro
Memory: Corsair Vengeance (4 x 4 GB DDR3)
Graphics: NVIDIA GeForce GTX 550 Ti (1024 MB)

Thanks for any help at all,
Ethan


*Attached system health report and dump files.

 

[JMH]

* You have Symantec which is a frequent cause of BSOD's.
I suggest you remove and replace it with Microsoft Security Essentials AT LEAST TO TEST

http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

* Re STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshooting.
Please read carefully through this link.

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

* I see you also need to install SP1.
Run the update readiness tool and then update to SP-1

Ensure you install the correct 64 or 32 bit option for your system)

Download the System Update Readiness Tool (64bit)

Download the System Update Readiness Tool (32bit)

http://windows.microsoft.com/installwindows7sp1

* I note you have RTCore64.sys{Related to RTCore64.sys MSI Afterburner from Micro-Star Int'l Co. Ltd.}
Suggest you update or remove it.

 

[Etot]

Thanks for the help JMH,

I followed the steps provided and uninstalled Synamatec and installed Microsoft Security Essential, but was still getting the BSOD.

I read the post you mentioned (http://www.sevenforums.com/crash-loc...oubleshtg.html) and I updated all my drivers. Then it said to run the video stress test: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net. The second I pressed the link my computer froze and got a blue screen. It seems that any stress test I have done instantly gives me a BSOD...

 

[JMH]

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

 

[Etot]

Okay here are the Minidump files.

I noticed today that whenever I play a game (as I mentioned before) my temperature rises significantly.. But that's not what seems to cause the BSOD, I think it is the CPU usage, which also skyrockets. Especially when playing AC. I even put it on the lowest graphics settings but CPU usage jumps up to 95-100%. Is this normal?

 

[zigzag3143]

Okay here are the Minidump files.

I noticed today that whenever I play a game (as I mentioned before) my temperature rises significantly.. But that's not what seems to cause the BSOD, I think it is the CPU usage, which also skyrockets. Especially when playing AC. I even put it on the lowest graphics settings but CPU usage jumps up to 95-100%. Is this normal?

Your most recent crash is still related to the Clock_watchdog bug check as indicated in post #2.

Since we dont know what the cpu and ram usage is/was when the crash occurred we can only give you generic do's and dont's.


To narrow the focus can you run these two tests.

Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[Etot]

Thanks for the continued support.

I just wanted to give a quick update. I updated my BIOS after finally figuring out how. I then installed 6 windows updates including Windows 7 Service Pack 1. I did the Driver Verifier and have had that running for a few hours with no BSODs. I was able to play AC with no BSOD aswell (played for about an hour). So I don't know if this means the problem is fixed or not. I will attach the dump files just incase they are needed. Also, I couldn't do the RAM Test (Memtest86+) because I don't currently have any CDs to put it on and run it. I will get some tomorrow and do that if you still think it is necessary. But as for now, I am hoping it is fixed.

One more question though. I still notice my CPU usage going up to about 90% while playing games and the temperature increasing by 10-20 degrees celcius. Is this normal with the processor I have? I have liquid CPU cooling by the way. (Corsair H80 Liquid CPU Cooler)

 

[zigzag3143]

Thanks for the continued support.

I just wanted to give a quick update. I updated my BIOS after finally figuring out how. I then installed 6 windows updates including Windows 7 Service Pack 1. I did the Driver Verifier and have had that running for a few hours with no BSODs. I was able to play AC with no BSOD aswell (played for about an hour). So I don't know if this means the problem is fixed or not. I will attach the dump files just incase they are needed. Also, I couldn't do the RAM Test (Memtest86+) because I don't currently have any CDs to put it on and run it. I will get some tomorrow and do that if you still think it is necessary. But as for now, I am hoping it is fixed.

One more question though. I still notice my CPU usage going up to about 90% while playing games and the temperature increasing by 10-20 degrees celcius. Is this normal with the processor I have? I have liquid CPU cooling by the way. (Corsair H80 Liquid CPU Cooler)

I notice you have a file RTCore64.sys which is a known cause of BSOD's. It is dated 2005 and needs to be updated (or removed)

ALSO

I do notice Symantec which is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST
http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

 

[Etot]

I located and updated RTCore64.sys, (EVGA Precision I think) and downloaded the Norton Removal Tool. I had already gone into Add/Remove Programs and uninstalled Norton though. I don't know if that messes with the removal tool, because I started the tool, and nothing ever came up. I can see it running under Processes though. What can I do to get it to work? Or is it working? I do already have Microsoft Security Essentials though.

 

[JMH]

I had already gone into Add/Remove Programs and uninstalled Norton though. I don't know if that messes with the removal tool, because I started the tool, and nothing ever came up. I can see it running under Processes though. What can I do to get it to work? Or is it working?

FYI.
Norton {and other Anti Virus programs} often leave remnants remaining when uninstalled via Control Panel.
These remnants can create instability. Thus the "need" for the appropriate uninstall tool.
When your DMP file is analyzed it will be confirmed or otherwise re Norton.

 

[Etot]

I tried running the Norton Removal Tool and after about 10 minutes it finally opened and allowed me to fully remove Symantec. So it should be gone now.

Attached current DMP files.

 

[zigzag3143]

I tried running the Norton Removal Tool and after about 10 minutes it finally opened and allowed me to fully remove Symantec. So it should be gone now.

Attached current DMP files.

Most recent crash Related to DrvAgent64.SYS DriverAgent Direct I/O for 64-bit Windows from Phoenix Technologies. I would remove it at least to test.

 

[Etot]

Hey,

It's been a while and I've been crash free up until two minutes ago...
I attached the dump files so we can see what the cause of this one was.

Thanks.

EDIT: I just found and deleted DrvAgent64.sys if that was the cause of the crash.

 

[zigzag3143]

Hey,

It's been a while and I've been crash free up until two minutes ago...
I attached the dump files so we can see what the cause of this one was.

Thanks.

EDIT: I just found and deleted DrvAgent64.sys if that was the cause of the crash.

The majority of these are called Clock_Watchdog error. Read here about it and you might want to turn driver verifier off by typing verifier /reset.


http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html