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

Based off of your first post, I was able to get most of what I needed. Your CPU and MoBo should still be under warranty with the manufacturer. If you email them and explain the situation pertaining to the builder of the PC now being defunct, they should be willing to honor the warranty on their parts.
 
Nice! Must be quick though, I received the PC on the 24th of June last year. I will get on it right away.

Edit: Looking at the warranty information from ASUS now. They give a 3 year warranty policy as standard, but does this extend to me as an indirect purchaser of the parts?

Edit 2: Well from the wording of the Intel warranty for CPU I guess it does still extend to me for the 3 year period. I'm guessing I should leave out the overclocking part though.
 
Vir Gnarus, just an (uninformed) thought:

Is it possible that x101 BSOD's occuring at the same time as network activity is just a coincidence? The only correlation that I notice is that the BSOD happen when I am running a game. I can't think of an instance of a BSOD when I have simply been browsing the web for example. Or are you talking about network activity on the timescale of the processor? i.e. the processor was working on a network related task when the BSOD occured. I lack the knowledge to use more specific (correct) language than this, I hope you have some idea of what I'm trying to ask.
 
I just ran memtestCL and got errors in two test iterations producing a total of 1953 errors, is this number of errors indicative of a bad graphics card? It certainly looks significant....
 
In every case the CPU was involved in network activity on the faulting CPU core. I can look further and ascertain exactly what kind of network activity was going on at your request but I personally don't think it's exactly necessary: boiling it down to network seems really only as far as we need to go.

Concerning the MemtestCL, I'm actually in the process of reconsidering it as a recommended GPU tester as it's known for giving false positives frequently on AMD cards especially, because it runs off of old deprecated OpenCL code. The false positives always show up in the random block test, so if that's the only portion of the test you're getting errors from, you can most likely ignore them.
 
Yes, the MemtestCL errors were from only the random block test. I've contacted ASUS explaining that the motherboard is the problem. I wanted to link this thread but with the mention of overclocking I thought that would be a bad idea.
 
Got a reply from ASUS regarding the motherboard:
In this situation, please adjust the timing and voltage of the memory moduels according to the spec and manual of them.
If no effort, please try the latest version of chipset driver from the following URL:
http://support.asus.com.cn/Download...n7.zip#Intel_Chipset_V9201015_XPVistaWin7.zip
If no effort, please clear the cmos to load default settings and try again.
If it doesn't work, I suggest you to take the motherboard out of case and keep the necessary components(a CPU, one memory in A1, a video card, a HDD in SATA1 and a ODD) onboard to re-install a new clear OS. Then use 3D-Mark only to detect the state of your devices.
If it is not helpful, please change another OS CD and test again.
If the problem still exists, if possible, please change or clean the necessary components to test again.
Click to expand...

Since setup defaults my RAM frequency to 1337 MHz it would be a bad idea to force it to 1300 MHz?

The link they gave for the latest chipset driver is broken, but I found it myself and it is older than the one I already had installed.

I haven't tried clearing CMOS, mainly because the video card blocks my access to the battery and I'm reluctant to mess about with PC innards unless I really have to. Would this actually help?

The final step they suggest seems way beyond my comfort zone, I've never tried mounting or dismounting a motherboard (I'm guessing they are checking for short circuiting with the case). This would mean reformatting again I suppose (or buying another HDD), unless I can temporarily make a partition to run a clean copy of the OS. Another problem is only having one copy of Windows available, I recall that you can run Windows for a while without activating it, might be wrong about that though.
 
Hi, just popping in to answer a few of your questions :)

I haven't tried clearing CMOS, mainly because the video card blocks my access to the battery and I'm reluctant to mess about with PC innards unless I really have to. Would this actually help?
Click to expand...

It may help. I usually reset the CMOS after I add or remove hardware, or mess with the BIOS settings a lot when troubleshooting a memory issue and I have to constantly switch timings, voltages, etc. In case you do not know of course, clearing the CMOS essentially brings the BIOS back to default settings. The most important part however of clearing the CMOS is the rebuilding of the DMI Pool. The DMI Pool is a table that is used by the OS to determine which devices are available.

If I am helping a user troubleshoot BSOD related issues, and it's starting to lean towards hardware being the issue based off of evidence, and possible evidence for memory (memory corruption, etc) I always recommend a clearing of the CMOS before running a Memtest to ensure the memory will or will not be stable at default settings.

The final step they suggest seems way beyond my comfort zone, I've never tried mounting or dismounting a motherboard (I'm guessing they are checking for short circuiting with the case).
Click to expand...

Most likely. Do not fret, uninstalling and reinstalling a motherboard from a case is not difficult, but as always, just be very careful.. you don't want to cause ESD to the motherboard. When removing the board, ground yourself.

I recall that you can run Windows for a while without activating it, might be wrong about that though.
Click to expand...

Correct.

Also, your cooperation is worth noting, and for that I'm sure we all thank you. You're the kind of person we analysts dream of assisting :lol:
 
Thanks for the kind words E-peen.

Well I will probably wait for my next BSOD before I take action, I suppose there's a chance updating the network drivers stopped them. One practical issue with removing the motherboard: where do I rest it while running it from outside the case? I assume it's a bad idea to just rest it on my desk, I think I need some sort of anti static material....
 
oatcoatedstoat said:
Thanks for the kind words E-peen.
One practical issue with removing the motherboard: where do I rest it while running it from outside the case? I assume it's a bad idea to just rest it on my desk, I think I need some sort of anti static material....
Click to expand...

It's not such a bad idea honestly. Usually, if I don't have the anti static bag / wrapper that the motherboard originally came in, a piece of wood or cardboard works fine. Just be careful.
 

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

Back
Top