[nav12]

I have recently purchased an assembled PC of following configurations

Intel i5-2500 @3.3Ghz
4 GB ddr3 ram
1 TB hard disk
Geforce 210 1 GB ddr3
Windows 7 Ultimate

BSOD screen with following statement has been appearing frequently - "a clock interrupt was not received from a secondary processor".

Technical Information:

*** STOP: 0x00000101 (0x0000000000000031, 0x0000000000000000, 0xfffff88002fd7180,
0x0000000000000003)

Initially I thought that BSOD occurs during high load applications.But now BSOD occurs once in one or two days even when PC is idle.The core temperature is at safe limits.(40-50c according to Coretemp).I am not overclocking the PC.

I have informed the condition to the seller(PC is under warranty) and they checked and removed the graphics card and sent it for repair informing me that problem is with the GPU.I have not received the graphics card back,but I am still having the same BSOD.

The minidump file is attached.

Please help me solve this problem.

Thanks
Nav12

 

[VirGnarus]

Unfortunately 0x101 bugchecks cannot be analyzed without at least a kernel dump. You'll need to provide one by grabbing the MEMORY.DMP file located in your Windows directory, stuffing it in a zip or other archive file, and then uploading it to a 3rd-party filesharing site and sending us a link.

If you wish, you may also turn on Driver Verifier and hope it catches anything.

 

[nav12]

Please instruct how to get MEMORY.DMP

 

[VirGnarus]

It should be present in your Windows directory, typically C:/Windows. If it is not, somehow your system failed to make a kernel dump. Usually this is because one or more of these conditions was met:

• Your paging file is too small or does not exist. It must be at least half your RAM just in case.
• Your paging file is not located on the Windows partition (drive letter).
• Your Windows partition does not have enough space on it to make the file.
• Corruption of the hard drive drivers was detected or the Windows partition (or drive it's on) was not accessible at the time.

Check to make sure the first 3 items listed is not the cause. Kernel dump files are usually around 1/4 to 1/2 the size of your RAM. Make sure your paging file settings are correct to accommodate this, and check that your hard drive has enough space on it.

There's also the chance that your system was set up not to make kernel dumps but only minidumps. However usually this only occurs if you manually set it to do so. By default it should make kernel dumps. To check, go to your Start menu and type Advanced system settings. Go there and click the button for Startup and Recovery. Under Write debugging information there's a drop-down menu. The current option should be Kernel memory dump. If it is not, set it to such.

 

[nav12]

I re-enabled Kernel memory dump.Will post the dump as soon as BSOD occurs.

 

[nav12]

BSOD again occured today.Two days ago system got stuck without showing bluescreen.The link for kernel dump is given below.

MEMORY.7z

Please analyse the dump and guide me to overcome this BSOD problem.

 

[VirGnarus]

Thanks, I'm going to look through it now. Just as a notice, debugging these kind of bugchecks can take a good bit of time for me, and yours is an especially odd one in comparison, and will make initial debugging difficult.

In the meantime, while I work on this, I recommend you start going through a number of hardware tests. Perhaps one of them may come up with something. If more than one shows errors, we may be looking at a bad power supply or motherboard. Anyways, tests are as followed:


RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)
GPU: MemtestG80/CL - Run twice (if any of the tests work on your GPU)
Drives: Seatools - All basic tests aside from the Fix all or the advanced ones.

All of these (excluding MemtestG80/CL) are included in the UBCD if you prefer a Live CD environment (which is a good environment to test hardware on). Note that Prime95 is called Mersenne Prime Test in the UBCD. Also, if you want, provide us temps/voltages using HWInfo with Sensors only option checked. Log two 30-minute instances: one for idle, and one for high load.

 

[VirGnarus]

Ok, I went back to it. Originally I thought it very strange what it pulled up in the beginning, but I found out for certain something is odd, and after googling became aware that this a bug in Windows. Unfortunately, because of this bug the kernel dump you provided is useless in having me find the cause of your 0x101 bugchecks. However, there is a hotfix for exactly this specific circumstance that I've come across when debugging it.

Please install the hotfix present here. Then when you experience another crash, upload the new kernel dump file to us. Hopefully this hotfix will resolve my problem debugging (the symptoms are exactly identical). Thanks.

 

[VirGnarus]

Hi, has another BSOD occurred since Feb 10?

 

[nav12]

Another BSOD again occured yesterday.I had installed the hotfix as instructed.The link for new kernel dump is given below.

MEMORY.7z

Please analyse and help me to solve the problem.

 

[VirGnarus]

I noticed this latest crashdump of yours isn't a 0x101 bugcheck but a 0x7F. A brief glance at it showed what appeared to be an illegal access to an object. This was during network operations that looked to be involved with local network operations (as in data between one local computer to yours). Is this correct? Do you have more than one computer on your home network? Is there anything you were doing at the time (like grabbing files, streaming media, etc.) from it?

Again, this is just from a couple minute glance. I can dig further to get exact details, but I'd figure I'd ask you some questions while I'm going through this, to get a perspective from the user.

I want to make mention that in the relevant data both avast and ZoneAlarm were involved. The Avast driver is relatively new (Nov 2011), but the ZoneAlarm firewall driver is collecting dust (May 2010). You will want to look about getting it and avast updated, as well as network drivers. Though I may add there have been times here at TSF where the only resolution was removing ZoneAlarm altogether - it can be quite buggy.

I will continue to peruse through the crashdump. Go ahead and perform everything I instructed and see if that resolves your problems.

 

[nav12]

Thank you for your fast response.But I have no other PC and is not connected to any other local computer.I think I was just copying some files to external hard disk at the time of BSOD.

Avast says it is already up to date.(Release date- 18/2/2012).I will update Zonealarm and if necessary will uninstall it.

 

[darkwarlord]

not to hijack this guys thread, but i had the problem back when w7 came out :banghead: clock issue... now after some time, new drive an all i installed w7SP1 ... hours in, i got this bsod once again. :angry:

trying out that hotfix you posted, ill post back either hours or 1-2days if it occurs. :thumb:

4gb ram
amd athlon phenomblack x4 2.3ghz
4770 radeaon gpu

 

[VirGnarus]

That's unusual, maybe I was reading the callstack improperly. It initially looks like local network activity (computer browsing), but I'll look more thoroughly once I have time. Sorry for the delays on this.

 

[VirGnarus]

not to hijack this guys thread, but i had the problem back when w7 came out :banghead: clock issue... now after some time, new drive an all i installed w7SP1 ... hours in, i got this bsod once again. :angry:

trying out that hotfix you posted, ill post back either hours or 1-2days if it occurs. :thumb:

4gb ram
amd athlon phenomblack x4 2.3ghz
4770 radeaon gpu

The hotfix will not resolve your problem. What it's for is to correct the 0x101 bugchecks generated on certain PCs so that us debuggers will be able to use them. Otherwise everything that is saved is all wrong and the crashdumps become worthless to us.

A 0x101 clock watchdog bugcheck can occur for any myriad of reasons, from CPU malfunctioning, to driver conflicts, to buggy drivers, and so on. If you are having these issues, please create your own thread, and make sure to provide us a kernel dump (file named MEMORY.DMP in Windows directory). The minidumps will not help us on analyzing causes of 0x101 bugchecks.

 

[VirGnarus]

Hey nav12, an update. I'm still running through the callstack (it's big) and ascertaining what's going on. I'm new to dealing with network protocol stacks for Windows so I'm reading up on it as I go. In the meantime, has anything changed so far since you've updated/removed ZoneAlarm?

 

[nav12]

I have updated zonealarm to its latest version (10.1.079.00).Till today I have no trouble with BSODs.Will update if any occurs.

 

[nav12]

Another x101 BSOD occurred today.The new Kernel dump is attached.Please analyse and reply.

http://www.mediafire.com/?a28t053zoxipq9d

 

[VirGnarus]

K, I have it an will get to work on it whenever I have the chance. Initial skimming showed it was doing network-related operations, which are similar to what was present in the previous crashdump you presented. I noticed in this case VM-related (Virtual Machine) functions, all from VM network drivers that are woefully outdated (2007). Please ensure that your network drivers are up to date, and I might add that you may need to remove Virtual PC or update it. This is all from speculation (like the Zonealarm) but it's stuff we can work on while I'm busy trying to analyze.

Right now analysis is going to be rather ugly. I will need to reconstruct a callstack from the ground up, then analyze it to figure cause (which will also mean disassembling and reconstructing code flow). Suffice to say, it will be brutal.

In the meantime, aside from the aforementioned recommendations, you may also wish to turn on Driver Verifier. These types of crashes DV doesn't help with very much, but there is always the possibility DV could snag an offending driver, which would be of great benefit. Any crashes that you believe are being caused by DV you can submit the minidumps for (kernel dumps are not necessary). You can do this in addition with providing us a JCGriff Report. Finally, you can do a couple of hardware tests as a just-in-case:

RAM: Memtest86+ - 7+ passes
CPU: Prime95 - Torture Test; Large FFTs; overnight (9+ hours)

 

[nav12]

Jcgriff report is attached.