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

O

oatcoatedstoat

Active member
Joined
May 30, 2012
Posts
39
OS
Win 7 x64 OEM.

System Age
System was built in June 2011 from (supposedly) new components. PSU was replaced about 2 months ago when system failed to startup (there was a high pitched sound coming from the PSU).

Age of OS install
About a month ago, my system booted to a heavily pixelated swirly mess, unfortunately I don't have any captures of this. The system started normally after a cold boot. However it seemed sluggish so I decided to reformat after exhausting my limited knowledge when trying to diagnose the problem.

CPU
Intel i5-2500K

Video Card
ASUS HD 6850

Motherboard
ASUS P8P67-M PRO

PSU
XFX 850W (I may have gone a bit overboard after the 650W Corsair PSU failed).

System Manufacturer
A recently defunct firm called Easy PC.

I wish I had found a site like this months ago. I consider myself only semi capable with PC's, this sort of thing has me stumped.

I'll start at the beginning.

The build I ordered from Easy PC was meant to be ready overclocked, I think even without hindsight this was a stupid thing to do. When I first booted the PC, the first message was something along the lines of "Overclock failed". So I went into setup and set everything to default values and managed to boot to OS. When I contacted Easy PC they cited "Low voltage mains power" as the reason why the overclock failed (this sounds like rubbish to me, but then again I know nothing).

Ever since I have been plagued with 0x101 BSOD. They mainly seem to occur when the system is under stress, especially in unoptimised games which are in Beta and the like. I can't shake the feeling that the CPU is simply borked because of the failed overclock message I mentioned. I hope this isn't the case because I presume getting any kind of warranty support for the CPU will be impossible now that Easy PC has closed for business. I already voided the warranty for the rig when I replaced the PSU, this was after Easy PC had closed down.

I know virtually nothing about debugging BSOD, so I hope my ignorance doesn't anger you. I presume the script I ran collected all the information you need to debug. I also zipped a dxdiag file with the PERFMON report, in case I missed anything.

Thanks for reading.

Edit: Because I fail at proof reading.
Edit 2: Because I forgot about a reformat.
 
Last edited by a moderator:
Hi -

All 9 BSOD have bugcheck 0x101 = CPU hang

The usually are hardware related.

Run the Driver Verifier - see if any 3rd party drivers are flagged - https://www.sysnative.com/forums/showthread.php/29-Driver-Verifier-BSOD-related

Test Video - http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html?ltr=V
Test CPU - http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html

I'll ask others to review this as well.

Regards. . .

jcgriff2

`

BSOD SUMMARY
Code: 
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050812-35100-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Tue May  8 14:49:24.392 2012 (GMT-4)
System Uptime: 0 days 6:04:09.781
BugCheck 101, {31, 0, fffff88002f65180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`02f65180 00000000`00000002
BiosVersion = 1004
BiosReleaseDate = 11/24/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\052112-22339-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 21 08:21:05.292 2012 (GMT-4)
System Uptime: 0 days 1:45:34.655
BugCheck 101, {31, 0, fffff880009ea180, 1}
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`009ea180 00000000`00000001
BiosVersion = 1004
BiosReleaseDate = 11/24/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\052512-29530-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 25 08:27:25.149 2012 (GMT-4)
System Uptime: 0 days 2:04:24.164
BugCheck 101, {31, 0, fffff880009ea180, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgidsagent.ex
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = 1004
BiosReleaseDate = 11/24/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\052512-29920-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri May 25 06:22:14.251 2012 (GMT-4)
System Uptime: 0 days 1:28:45.640
BugCheck 101, {31, 0, fffff880009ea180, 1}
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`009ea180 00000000`00000001
BiosVersion = 1004
BiosReleaseDate = 11/24/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\052612-37143-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat May 26 09:30:07.531 2012 (GMT-4)
System Uptime: 0 days 0:10:17.546
BugCheck 101, {31, 0, fffff880009ea180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Launcher.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = 1004
BiosReleaseDate = 11/24/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\052712-24835-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun May 27 16:05:46.191 2012 (GMT-4)
System Uptime: 0 days 0:32:06.206
BugCheck 101, {31, 0, fffff880009ea180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgmfapx.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = 1004
BiosReleaseDate = 11/24/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\052912-26098-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue May 29 08:32:24.061 2012 (GMT-4)
System Uptime: 0 days 2:49:52.450
BugCheck 101, {31, 0, fffff880009ea180, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
BiosVersion = 1004
BiosReleaseDate = 11/24/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\052912-27097-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue May 29 16:21:50.279 2012 (GMT-4)
System Uptime: 0 days 7:48:46.294
BugCheck 101, {31, 0, fffff88002f65180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Launcher.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`02f65180 00000000`00000002
BiosVersion = 1004
BiosReleaseDate = 11/24/2011
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\053012-21590-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 30 10:37:58.278 2012 (GMT-4)
System Uptime: 0 days 0:15:22.668
BugCheck 101, {31, 0, fffff880009ec180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Launcher.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
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


	    
             
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   

           [url=https://www.sysnative.com][color=#000033][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  
[/font]
 
Hi there,

Yeah, we're prolly dealing with some faulty hardware here. Unfortunately, one can't tell from the minidump. 0x101 crashdumps can only be debugged with access to at least a kernel dump. It's the MEMORY.DMP file located in your Windows directory. Zip it up and upload it using some website like MirrorCreator.com or some other metaupload site, since it'll be way too big for here.

Btw, I noticed your syslog is smothered in bad block errors from your HD(s). You may wanna do a chkdsk on em. Use the Disk Check tool (CHKDSK) in Windows for each drive, and make sure both options are selected. Restart after you set all of em up for disk checking, since one or more will ask that you restart to initiate the check. Just so you know, while 0x101 often is caused by CPU failure, anything else can cause it too, including HD problems, so check those out first.
 
Thanks for the quick replies guys.

I ran memtest and it passed all tests with no errors. After that I ran the driver verifier, it flagged a driver immediately before reaching desktop. I have attached the associated dump file.

I'll move on to testing CPU and video next.

Edit: Regarding CHKDSK, I have done this quite recently and came up with nothing but I will try it again I suppose, after CPU and Video. I do have an external HDD which went out of comission recently. Though I suppose the syslog (I don't even know what this is) would be referring to the main drive. I'll upload the kernel dump soon, not at the relevant computer at the time of writing.
 
Last edited by a moderator:
In this crashdump, you have some old Zone Alarm drivers (May 2011) that's playing foul by referencing a user handle when in kernel mode. I personally can't see how this would cause 0x101 bugchecks, but it may be beyond my current expertise to understand the correlation. Still, you will want to update Zone Alarm. Though honestly, you'll probably want another firewall solution. I can't tell you how many times I and others have been bereft of sanity generated by its buggy nature. I personally can't point you to any viable alternatives, unfortunately, but I'm sure others can, and it'd be better off than using Zone Alarm.

As for the syslog entries, the latest drive issue was detected yesterday. The latest event that recorded a bad block, however, was on the 25th, and that was referencing \Device\Harddisk2\DR2, so I could see that as your external drive. The other drive issues though are reported from \Device\Harddisk1\DR1, so that's most likely your Windows drive. Understand that both drives did report bad blocks.
 
Reported bad blocks call for a hard drive diagnostic. Here's the procedure that I suggest: http://www.carrona.org/hddiag.html

Interestingly there's only 1 hard drive (with 2 partitions in your system) - it's listed as Disk 0. There is a 1gB USB flash drive attached that is listed as Disk 1. Still, a hard drive diagnostic is called for.

Zone Alarm - we see too many issues with this, and they're not always real easy to diagnose. I suggest uninstalling it to see if it's causing the problem. If you must use a 3rd party firewall extension, I suggest this free tool that offers finer control of the Windows Firewall: http://www.sphinx-soft.com/Vista/order.html The Driver Verifier memory dump blames it, so it's got to be removed in order to test it.

This is most likely a hardware error. They (hardware errors) are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues
- low-level driver problems (such as the problems that we see with ZoneAlarm)
- or even malware (scanned for when we ask for hardware diagnostics from http://www.carrona.org/initdiag.html or http://www.carrona.org/hwdiag.html ).

You have a number of older drivers that need to be updated. If no update is available, then they should be removed from your system.
Links to the Driver Reference Table (DRT) are included to help you figure out where to update them from:

AsUpIO.sys Sun Jul 05 22:21:38 2009 (4A515FB2)
ASUS hardware monitoring software related - you'll have to go through each installed Asus program to figure out which one it is.
http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys

hamachi.sys Thu Feb 19 05:36:41 2009 (499D3639)
LogMeIn Hamachi Virtual etwork interface driver
http://www.carrona.org/drivers/driver.php?id=hamachi.sys

cm11264.sys Wed Nov 25 04:52:46 2009 (4B0CFE6E)
C-Media USB Audio Driver (WDM) in this case it probably belongs to your Sennheiser 3D G4ME1 device
http://www.carrona.org/drivers/driver.php?id=cm11264.sys (description not uploaded to the DRT yet - it will be after I post this)

I only ran the last memory dump and have attached the details below.

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)
avgrkx64.sys Mon Jan 30 22:11:41 2012 (4F275BED)
avgidsha.sys Wed Apr 18 22:19:15 2012 (4F8F7623)
avgmfx64.sys Fri Dec 23 07:08:12 2011 (4EF46F2C)
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)
vsdatant.sys Fri May 06 01:31:14 2011 (4DC387A2)
HECIx64.sys  Tue Oct 19 19:33:43 2010 (4CBE2AD7)
hamachi.sys  Thu Feb 19 05:36:41 2009 (499D3639)
atikmdag.sys Thu Apr 05 21:48:25 2012 (4F7E4B69)
AtihdW76.sys Thu Feb 23 07:30:12 2012 (4F463154)
Rt64win7.sys Fri Jun 10 02:33:15 2011 (4DF1BAAB)
asmtxhci.sys Wed Jan 26 21:19:16 2011 (4D40D624)
cm11264.sys  Wed Nov 25 04:52:46 2009 (4B0CFE6E)
asmthub3.sys Wed Jan 26 21:19:26 2011 (4D40D62E)
[/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=avgrkx64.sys
http://www.carrona.org/drivers/driver.php?id=avgmfx64.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=vsdatant.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=hamachi.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=Rt64win7.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys

BSOD BUGCHECK SUMMARY
Code: 
[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053012-24398-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 30 13:20:23.823 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:34.213
*** WARNING: Unable to verify timestamp for vsdatant.sys
*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
Probably caused by : vsdatant.sys ( vsdatant+8f733 )
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
BUGCHECK_STR:  0xc4_f6
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_vsdatant+8f733
Bugcheck code 000000C4
Arguments 00000000`000000f6 00000000`0000015c fffffa80`05faa340 fffff880`0417c733
BiosVersion = 3602
BiosReleaseDate = 04/24/2012
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3310
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]
 
I didn't even know I had any ASUS programs still installed, even looking at my installed programs now I can't see anything. I uninstalled all ASUS programs when I read somewhere that they can cause instability. Am I missing the point though? Is there a way to get rid of unwanted drivers other than uninstalling programs?

I have no idea what Zone Alarm drivers from May 2011 are doing on my machine, I reformatted about a month ago so surely this doesn't make sense? Regardless I have uninstalled Zone Alarm.

I've also uninstalled Hamachi and Sennheiser 3DG4ME1 for now, since they both were apparently up to date.

I'm certainly not Overclocking right now, but as I described in my first post, my system was initially overclocked by the company I paid to build it, this overclock failed when I booted for the first time and I reverted to defaults.

I've uploaded the MEMORY.dmp file for kernel debugging to http://mir.cr/IIPAFHGR.

I'll get on to doing the HDD diagnostics and afterward stress test the CPU as you recommend.

Thanks for all your help so far.
 
How to safely remove a driver:
- Make a System Restore point
- Make a System Repair Disc (Start...All Programs...Maintenance...Create a System Repair Disc)
- Make sure that the System Repair Disc works and that you can reach System Restore with it.

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.

Just FYI - this doesn't always work. But if it doesn't there are other things that we can do to work around it.
 
Last edited:
oatcoatedstoat said:
The build I ordered from Easy PC was meant to be ready overclocked, I think even without hindsight this was a stupid thing to do. When I first booted the PC, the first message was something along the lines of "Overclock failed". So I went into setup and set everything to default values and managed to boot to OS. When I contacted Easy PC they cited "Low voltage mains power" as the reason why the overclock failed (this sounds like rubbish to me, but then again I know nothing).

Ever since I have been plagued with 0x101 BSOD. They mainly seem to occur when the system is under stress, especially in unoptimised games which are in Beta and the like. I can't shake the feeling that the CPU is simply borked because of the failed overclock message I mentioned. I hope this isn't the case because I presume getting any kind of warranty support for the CPU will be impossible now that Easy PC has closed for business. I already voided the warranty for the rig when I replaced the PSU, this was after Easy PC had closed down.
Thanks for reading.
Click to expand...
In your case, x101 is due to low vcore. SO, no, it's not a bunch of rubbish. When you reset to defaults, how did you do so? Also, you did not list your Memory and amount.
 
Additional information from the kernel dump that makes me think this is Zone Alarm we're dealing with:

Code: 
Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff880009ec180, 1}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009ec180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

Debugging Details:
------------------


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Launcher.exe

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`08cd6918 fffff800`02cd7f3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`009ec180 : nt!KeBugCheckEx
fffff880`08cd6920 fffff800`02c8ace7 : 00000000`00000000 fffff800`00000001 00000000`00002711 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`08cd69b0 fffff800`031f4895 : fffff800`0321a460 fffff880`08cd6b60 fffff800`0321a460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`08cd6ab0 fffff800`02c7d713 : 00000000`77157bbb fffff880`08cd6b01 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`08cd6ae0 00000000`7518cffd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
00000000`0008e350 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7518cffd


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

Followup: MachineOwner
---------

[COLOR=#008000]//check all running processors to see what's going on.[/COLOR]

0: kd> !running -it

System Processors:  (000000000000000f)
  Idle Processors:  (0000000000000000) (0000000000000000) (0000000000000000) (0000000000000000)

       Prcbs             Current         (pri) Next            (pri) Idle
  0    fffff80002df3e80  fffffa8006261060 ( 8)                       fffff80002e01cc0  ................

Child-SP          RetAddr           Call Site
fffff880`08cd6918 fffff800`02cd7f3a nt!KeBugCheckEx
fffff880`08cd6920 fffff800`02c8ace7 nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`08cd69b0 fffff800`031f4895 nt!KeUpdateSystemTime+0x377
fffff880`08cd6ab0 fffff800`02c7d713 hal!HalpHpetClockInterrupt+0x8d
fffff880`08cd6ae0 00000000`7518cffd nt!KiInterruptDispatchNoLock+0x163
00000000`0008e350 00000000`00000000 0x7518cffd

[COLOR=#ff0000]  1    fffff880009ec180  fffff880009f6fc0 ( 0) fffffa800394f540 (22) fffff880009f6fc0  ................

Child-SP          RetAddr           Call Site
00000000`00000000 00000000`00000000 0x0[/COLOR]

  2    fffff88002f65180  fffffa80036aead0 (16) fffffa80036ae5e0 (23) fffff88002f6ffc0  ................

Child-SP          RetAddr           Call Site
fffff880`03316740 fffff800`02c6afe4 nt!KeFlushMultipleRangeTb+0x260
fffff880`03316810 fffff800`02cf94f5 nt!MiAgeWorkingSet+0x64a
fffff880`033169c0 fffff800`02c6b116 nt! ?? ::FNODOBFM::`string'+0x4cd46
fffff880`03316a40 fffff800`02c6b5cb nt!MmWorkingSetManager+0x6e
fffff880`03316a90 fffff800`02f17e6a nt!KeBalanceSetManager+0x1c3
fffff880`03316c00 fffff800`02c71f06 nt!PspSystemThreadStartup+0x5a
fffff880`03316c40 00000000`00000000 nt!KiStartSystemThread+0x16

  3    fffff88002fd7180  fffffa80037c02c0 (11) fffffa80065ffb50 (21) fffff88002fe1fc0  ................

Child-SP          RetAddr           Call Site
fffff880`09462880 fffff800`02cb5acd nt!KxFlushEntireTb+0x93
fffff880`094628c0 fffff800`02cd9e90 nt!KeFlushTb+0x119
fffff880`09462940 fffff800`02c8de8d nt! ?? ::FNODOBFM::`string'+0xae02
fffff880`09462980 fffff800`02c7f2ee nt!MmAccessFault+0xa7d
fffff880`09462ae0 00000000`6862ce6a nt!KiPageFault+0x16e
00000000`0e29fba0 00000000`00000000 0x6862ce6a

[COLOR=#008000]//PRCB of Proc1 matches up with the PRCB of the failing processor mentioned in the bugcheck code (Arg3). Let's look at more info on it:[/COLOR]

0: kd> !prcb 1
PRCB for Processor 1 at fffff880009ec180:
Current IRQL -- [COLOR=#ff0000]0[/COLOR]
Threads--  Current fffff880009f6fc0 Next fffffa800394f540 Idle fffff880009f6fc0
Processor Index 1 Number (0, 1) GroupSetMember 2
Interrupt Count -- 0014c1cb
Times -- Dpc    00000004 Interrupt 0000001e 
         Kernel 0000b7d7 User      00002c49 

[COLOR=#008000]//Notice current IRQL is at 0. Let's confirm:[/COLOR]

0: kd> !irql 1
Debugger saved IRQL for processor 0x1 -- [COLOR=#ff0000]0 (LOW_LEVEL)[/COLOR]

[COLOR=#008000]//It appears IRQL is at 0, but again, this may be erroneous, given that we aren't really getting a good context of the processor right now. Observe:[/COLOR]

0: kd> ~1

1: kd> r
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=0000000000000000 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl nz na pe nc
cs=0000  ss=0000  ds=0000  es=0000  fs=0000  gs=0000             efl=00000000
00000000`00000000 ??              ???

1: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

[COLOR=#008000]//No saved registers, no saved stack. Clearly we're dealing with a stuck CPU core here and it won't respond to anything. It still has saved the currently running thread, so we'll grab that and then dump the raw thread stack:[/COLOR]

1: kd> !thread 
THREAD fffff880009f6fc0  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 1
Not impersonating
DeviceMap                 fffff8a0000060f0
Owning Process            fffff80002e02180       Image:         Idle
Attached Process          fffffa800369d040       Image:         System
Wait Start TickCount      9772           Ticks: 49373 (0:00:12:50.223)
Context Switch Count      4467919        IdealProcessor: 1             
UserTime                  00:00:00.000
KernelTime                00:11:22.722
Win32 Start Address nt!KiIdleLoop (0xfffff80002c78e70)
Stack Init fffff88002f1bc70 Current fffff88002f1bc00
Base [COLOR=#0000ff]fffff88002f1c000 [/COLOR]Limit [COLOR=#ff8c00]fffff88002f16000 [/COLOR]Call 0
Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
Child-SP          RetAddr           : Args to Child                                                           : Call Site
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0

1: kd> dps [COLOR=#ff8c00]fffff88002f16000 [/COLOR][COLOR=#0000ff]fffff88002f1c000[/COLOR]
fffff880`02f16000  00000000`00000000
fffff880`02f16008  00000000`00000000
fffff880`02f16010  00000000`00000000
fffff880`02f16018  00000000`00000000
fffff880`02f16020  00000000`00000000
fffff880`02f16028  00000000`00000000
fffff880`02f16030  00000000`00000000
fffff880`02f16038  00000000`00000000

...

fffff880`02f19250  00000000`00000007
fffff880`02f19258  fffff880`02f19950
fffff880`02f19260  fffff880`02f192c0
[COLOR=#ff0000]fffff880`02f19268  fffff880`02c38fd5*** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys
 vsdatant+0x38fd5[/COLOR]
fffff880`02f19270  fffffa80`04f7ecc8
fffff880`02f19278  00000000`00000074
fffff880`02f19280  fffffa80`06635230

...

fffff880`02f19328  fffffa80`04b822d0
fffff880`02f19330  00000000`00000007
[COLOR=#ff0000]fffff880`02f19338  fffff880`0401b698*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
 Rt64win7+0x1b698[/COLOR]
fffff880`02f19340  00000000`00000001
fffff880`02f19348  fffff800`02cac180 nt!RtlpGetStackLimits+0x14

[COLOR=#008000]//As you can tell just perusing the stack that we're dealing with network activity. Notice the two 3rd-party drivers involved. Let's look each one up:[/COLOR]

1: kd> lmvm rt64win7
start             end                 module name
fffff880`04000000 fffff880`04085000   Rt64win7   (no symbols)           
    Loaded symbol image file: Rt64win7.sys
    Image path: \SystemRoot\system32\DRIVERS\Rt64win7.sys
    Image name: Rt64win7.sys
    Timestamp:        [COLOR=#ff0000]Fri Jun 10 02:33:15 2011[/COLOR] (4DF1BAAB)
    CheckSum:         0008B67F
    ImageSize:        00085000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
1: kd> lmvm vsdatant
start             end                 module name
fffff880`02c00000 fffff880`02c95000   vsdatant   (no symbols)           
    Loaded symbol image file: vsdatant.sys
    Image path: \SystemRoot\system32\DRIVERS\vsdatant.sys
    Image name: vsdatant.sys
    Timestamp:        [COLOR=#ff0000]Fri May 06 01:31:14 2011[/COLOR] (4DC387A2)
    CheckSum:         0007EB69
    ImageSize:        00095000
    File version:     10.0.217.0
    Product version:  10.0.217.0
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.0 Driver
    File date:        00000000.00000000
    Translations:     0409.04e4
    CompanyName:      Check Point Software Technologies LTD
    ProductName:      [COLOR=#ff0000]ZoneAlarm Firewalling Driver[/COLOR]
    InternalName:     VSDATANT.SYS
    OriginalFilename: VSDATANT.SYS
    ProductVersion:   10.0.217.000
    FileVersion:      10.0.217.000
    FileDescription:  [COLOR=#ff0000]ZoneAlarm Firewalling Driver[/COLOR]
    LegalCopyright:   Copyright © 1998-2011, Check Point, LTD

Bingo. Zone Alarm and the NIC drivers were involved. Both are getting pretty stale in age, and ZoneAlarm already has a reputation for being bugridden. At least they are courteous enough to make their entire header nonpageable so as to give us all the details on the module.

I would like to progress further to determine exactly how Zone Alarm or whatever else it is that's locking this CPU up. It would mean attempting to generate a callstack and then backtracking through it. I may not have the expertise enough to journey in this endeavor, but I'll give it a go.
 
@James. As you can tell I have no real idea what I'm doing in setup. So when the overclock failed I just went through all the advanced tabs hitting the key to default the values and change everything I could find to auto.

My RAM is 4GB Corsair DDR3 all in a single slot. Looking at CPU-Z it says DRAM frequency 668.9MHz.

I've run the Zone Alarm removal tool and I'm going to sort out all those other rogue drivers under usasma's direction.
 
Last edited:
Since this was a prebuilt PC, and you note the majority of problems(x101 BSODs) occurred after a failed attempt at overclock, I am pretty sure you have something still set wrong. Most BIOS' offer two FULL default settings. When you load into the BIOS, you should see a "Set Optimized Defaults" and "Set Fail-Safe Defaults" at the bottom of the screen. They will have a "F(X)" key associated with them. Try loading the Optimized settings first. See if the problems persist. If so, try the "Fail-Safe" settings. Too low of voltage to the VCore will cause the x101, commonly. May be nothing, may be everything.
 
@James. When I first booted the PC after receiving it from Easy PC, the overclock they implemented had failed. This is why I went about resetting to defaults without knowing what I'm doing. So I have no idea if the PC was stable before they tried the overclock. I'll have another go at resetting defaults for sure, with a mind to try these Fail Safe settings.

Regarding Zone Alarm, I had another x101 after uninstalling Zone Alarm. This x101 was before running the removal tool though. I'll get rid of all those rogue drivers first then start doing CPU stressful stuff to see if another x101 occurs.
 
The Overclock failed message is usually the ram speed on these boards, a failed boot because of 1600 speed ram (2x 800), and it down clocks to the default 1333 speed. (2x 666.5) seeing yours at 1337.8 (2x 668.9) is a bit strange,
 
Wrench97 said:
The Overclock failed message is usually the ram speed on these boards, a failed boot because of 1600 speed ram (2x 800), and it down clocks to the default 1333 speed. (2x 666.5) seeing yours at 1337.8 (2x 668.9) is a bit strange,
Click to expand...

Yeah, that would indicate a base clock change. I am certain that there are some settings that are still invalid. Add to that the single 4gb stick, well, you can see where I'm going.
 
Another thing to note about the single stick would be whether or not CPUz is reporting it as dual or single channel.
Some newer boards can run a single stick as dual, with double sided ram each side is a channel hence the reason you see Dell's and HP's with 3 gig installed 1, 2ig and 1, 1gig or 3 1, gig sticks.
 

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

Back
Top