0x101 "A clock interrupt was not received on a secondary processor..."

All is worth noting, Bruce....

I learn something new everyday; retaining it ... another matter especially where hardware is concerned! :smile:
 
Well, I ran Prime95 for two hours on the small FFTs setting. Came out with no errors and temperatures stable around 60degC. Oddly (or perhaps not I really don't know) one core was consistently hotter than the others running at around 65degC. I haven't removed the drivers flagged by verifier.exe yet or changed anything in setup.

Perhaps the Zone Alarm removal tool was the solution, I'll let you know if I get a x101 in which case I will get rid of those flagged drivers.
 
Just an aside here. You've got some of the best troubleshooters on the web here, and they're all trying to have you fix things that they've noticed.
As you can tell, everyone has a different opinion. Luckily this is a great bunch of people and we tend to respect each others opinions.

So, if you're confused, or just want some extra explanation, please feel free to ask.
And, FYI, if you ask me for extra explanation - I will gladly talk until your eyes glaze over! :0)

Good luck!
 
I'm mainly pleased I'm getting so many responses! I'm just trying to take James' advice and take only 1 action and wait for a x101. I'll follow each persons advice in turn when the previous measure fails.

Although thinking back as well. Before running that ZA remover I did HD diagnostics the night before with Seatools, which passed at the end. So if my PC remains stable now it could be down to either one of those steps...
 
Last edited:
OK just had a x101 5 mins ago while running a game. Odd that Prime95 didn't trigger one but a game did? Anyway I guess I'll get on to removing those drivers Usasma listed first.
 
Then
- rename the driver from AsUpIO.sys to AsUpIO.BAD
- use Autoruns (you should have it installed from the jcgriff2 report generation) to search for any instances of AsUpIO.sys. When you find them, disable them by removing the checkmark in the far left column.
- Reboot the system and see if it works!
- If not, boot with the System Repair Disc and use System Restore to restore the system to a point before you renamed the file and disabled the Autoruns entries.
Click to expand...

I'm having trouble with the very first step, I can't seem to locate AsUpIO.sys. Is there a folder where all the driver files are stored?
 
That's a good thing (that you can't find it). It may have been a remnant from an earlier dump file.
Check in C:\Windows\System32\drivers. If it's not there, don't sweat it - we can wait and see if it rears it's ugly head in another BSOD later on.
 
Well the drivers you suggested as problematic aren't there usasma, I must have got them all by uninstalling. Maybe my latest BSOD will be informative now that those drivers are dealt with. I'll attach the dump to this post.
 
Last edited by a moderator:
Here's the location of the older drivers:
WinRing0x64.sys is a new one (I think) - but it's also old and I've seen it cause problems in the past.
Please update it or remove the program associated with it.
0: kd> lm vm asio
start end module name
fffff880`03f0b000 fffff880`03f11000 AsIO (deferred)
Image path: \SystemRoot\SysWow64\drivers\AsIO.sys
Image name: AsIO.sys
Timestamp: Mon Aug 23 21:53:02 2010 (4C7325FE)
CheckSum: 0000C2D9
ImageSize: 00006000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lm vm asupio
start end module name
fffff880`03f05000 fffff880`03f0b000 AsUpIO (deferred)
Image path: \SystemRoot\SysWow64\drivers\AsUpIO.sys
Image name: AsUpIO.sys
Timestamp: Sun Jul 05 22:21:38 2009 (4A515FB2)
CheckSum: 0000EDF8
ImageSize: 00006000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

0: kd> lm vm winring0x64
start end module name
fffff880`08f77000 fffff880`08f7e000 WinRing0x64 (deferred)
Image path: \??\C:\PerfLogs\New folder\WinRing0x64.sys
Image name: WinRing0x64.sys
Timestamp: Sat Jul 26 09:29:37 2008 (488B26C1)
CheckSum: 00011908
ImageSize: 00007000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Click to expand...

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
Code: 
[font=lucida console]
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
avgtdia.sys       Sun Mar 18 23:53:32 2012 (4F66ADBC)
avgmfx64.sys      Fri Dec 23 07:08:12 2011 (4EF46F2C)
avgrkx64.sys      Mon Jan 30 22:11:41 2012 (4F275BED)
avgidsha.sys      Wed Apr 18 22:19:15 2012 (4F8F7623)
HECIx64.sys       Tue Oct 19 19:33:43 2010 (4CBE2AD7)
avgldx64.sys      Tue Feb 21 22:57:53 2012 (4F4467C1)
AsUpIO.sys        Sun Jul 05 22:21:38 2009 (4A515FB2)
AsIO.sys          Mon Aug 23 21:53:02 2010 (4C7325FE)
atikmpag.sys      Thu Apr 05 21:10:44 2012 (4F7E4294)
Rt64win7.sys      Fri Jun 10 02:33:15 2011 (4DF1BAAB)
AtihdW76.sys      Thu Feb 23 07:30:12 2012 (4F463154)
atikmdag.sys      Thu Apr 05 21:48:25 2012 (4F7E4B69)
avgidsfiltera.sys Fri Dec 23 07:05:40 2011 (4EF46E94)
cpuz135_x64.sys   Fri Mar 09 03:56:55 2012 (4F59C5D7)
avgidsdrivera.sys Fri Dec 23 07:05:21 2011 (4EF46E81)
[Color=Red]WinRing0x64.sys   Sat Jul 26 09:29:37 2008 (488B26C1)[/Color]
[/font]

http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=avgtdia.sys
http://www.carrona.org/drivers/driver.php?id=avgmfx64.sys
http://www.carrona.org/drivers/driver.php?id=avgrkx64.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=avgldx64.sys
http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=cpuz135_x64.sys
http://www.carrona.org/drivers/driver.php?id=WinRing0x64.sys

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053112-24195-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Thu May 31 15:41:14.090 2012 (UTC - 4:00)
System Uptime: 0 days 5:09:43.479
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ec180 00000000`00000001
BiosVersion = 3602
BiosReleaseDate = 04/24/2012
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 
Last edited:
WinRing0x64.sys is associated with RealTempGT but I can't find RealTempGT on my program list to uninstall. I located its files in "C:\PerfLogs\New folder" but couldn't find an uninstaller among those files. Should I just delete the folder or disable the driver file using the .BAD method you described before?

Although if I don't run Realtemp I think WinRing0x64.sys shouldn't be an issue, since autorun.exe didn't pick it up.
 
Last edited:
I'd check Autoruns to see if/where WinRing0x64.sys is loading.
The info in the DRT (Driver Reference Table) is as accurate as we can research - but we don't know all the programs that use the WinRing0x64.sys libraries.

You can remove them using the same method as I describe previously. But it's a good idea to try them one at a time in case there's a problem when removing them.

Good luck!
 
Also try WHERE command.

Bring up elevated Admin cmd prompt -
START | type cmd.exe | RIGHT-click on cmd.exe | "Run as Administrator" | type/ paste the following -
Code: 
[font=lucida console]
where /r c:\ /f /t WinRing0x64.sys > 0 & start notepad 0
[/font]

It may take a few minutes.

A Notepad will open wth the results.

Regards. . .

jcgriff2
 
Just to let you know that it's better that you run Prime95 on Blend as it'll also pressure your L2 cache as well as your RAM, and to run it at least 8-9 hours, so overnight. Also, realize that minidumps are absolutely and completely worthless to diagnose 0x101 bugchecks. At least a kernel dump is required. The MEMORY.DMP is always replaced by the latest crashdump generated by your PC.

I fear that I may only have enough expertise to partially diagnose the issue. While the kernel dump did indeed show me that previously Zone Alarm and your network drivers (you did update them, right?) were involved in that particular 0x101 bugcheck, I don't think I'll be able to ascertain exactly why it locked up without being able to manually reconstruct an x64 callstack from scratch, which is quite a nightmare even to more advanced debug analysts. I'm aware what to do afterwards, but that one step just continues to be puzzling to me since it's so radically different than doing the same for x32 callstacks. I can still give it a go again with another kernel dump to try and correlate a pattern between the latest crash and the one I analyzed previously, but I cannot be 100% sure that I'll be able to discover what did it exactly. I'll continue to research on it, but it may be a good while till I get the hang of it.

Anyways, your best bet right now is to just keep using Driver Verifier and let it work its magic on any new crashdumps you may come across. Remember to not select IRP Logging, Low Resource Sim or Force Pending I/O Requests checks, while selecting all others.
 
Zone Alarm should be dealt with but I think I should address the network drivers you mention Vir Gnarus. When you mentioned NIC drivers I thought you were talking about some component of Zone Alarm. Are these Network drivers something you would get from your motherboard manufacturer? I looked on your DRT but I could find anything labelled NIC, I really am clueless =(.

So my plan of action after this Network driver update is to run Prime 95 again according to Vir Gnarus' advice. I can't use RealTempGT to monitor temperatures now, so I installed Speedfan. However Speedfan seems to be very confused, claiming my CPU temp is -10degC. I'm looking about for some speedfan documentation telling me I need to cailbrate temperatures somehow. Haven't found anything yet.

Finally regarding the Driver Verifier, I didn't know this worked off of the latest crashdump. I thought it just ran through all the drivers on your system and created a crashdump once it found a driver which it didn't like.

The next time I get a x101 should upload the kernel dump again?
 
Last edited:
Btw, if you can give me a kernel dump that was caused from Driver Verifier, that could greatly assist in tracking down cause.

Oh, in addition, here's a couple other hardware tests you can do:

RAM: Memtest86+ - 7+ passes
GPU: MemtestCL - Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK as it requires OpenCL)

Also, please provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load. If you can get the system to crash during high load logging, that's even better.
 
oatcoatedstoat said:
Zone Alarm should be dealt with but I think I should address the network drivers you mention Vir Gnarus. When you mentioned NIC drivers I thought you were talking about some component of Zone Alarm. Are these Network drivers something you would get from your motherboard manufacturer? I looked on your DRT but I could find anything labelled NIC, I really am clueless =(.

So my plan of action after this Network driver update is to run Prime 95 again according to Vir Gnarus' advice. I can't use RealTempGT to monitor temperatures now, so I installed Speedfan. However Speedfan seems to be very confused, claiming my CPU temp is -10degC. I'm looking about for some speedfan documentation telling me I need to cailbrate temperatures somehow. Haven't found anything yet.

Finally regarding the Driver Verifier, I didn't know this worked off of the latest crashdump. I thought it just ran through all the drivers on your system and created a crashdump once it found a driver which it didn't like.

The next time I get a x101 should upload the kernel dump again?
Click to expand...

Speed Fan can be inaccurate. CoreTemp or RealTemp are better. HWMonitor(which Vir Gnarus covers below) is good for watching your voltages, system wide, as well.

By chance, have you had any more x101s lately?
 
@James. My most recent x101 was yesterday around 8.46pm GMT, I uploaded the associated minidump in post # 31. I can't use RealTemp because it used a driver which came up in the recent x101. Will try CoreTemp though. However if minidumps aren't useful to diagnose x101 maybe I should just use RealTemp anyway...

@Vir Gnarus I already passed every test that Memtest86+ threw at me. I'm not sure I can run MemTestCL because HD 6xxx series ATI aren't supported according to the documentation (or is this why I need to install ATI APP SDK ?)
 
Last edited:

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top