Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD, Error: A clock interrupt was not received on a secon.....


03 Feb 2012   #1

Windows 7 Home Premium 64bit
 
 
Random BSOD, Error: A clock interrupt was not received on a secon.....

I will try to provide as much information as I can so that anyone willing can please help me out:

-I've ran both the FurMark test and the Prime95 tests.

Both tests seemed to have stabilized temperature readings (~78C) after running them for a while and the laptop continued to run fine.

-Typically my cursor will hang or freeze and then the BSOD occurs - I see very briefly display glitches for half a second before the BSOD.

-The error states: "A clock interrupt was not received on a secondary processor...". BlueScreenView shows bug check code of: 0x00000101

-This doesn't happen when I'm playing games (played Singularity on high settings for hours on end; it does happen more frequently when I have many tabs or windows open in Chrome

-I have tried to run MemTest but it doesn't even go through a full 100% pass before shutting down around the 45% mark, typically about 12 minutes into the process. The computer just shuts down, but I noticed no errors are reported before that happens.

-I have done a complete reinstall of Windows but the error still persists.

Also, I get an error when trying to generate the Performance report that says that it "timed out" so I am unable to provide that in my zip file. I have run the Driver Verifier and selected all the drivers that weren't provided by Microsoft and restarted but didn't get any BSOD. I haven't tried it *with* the Microsoft drivers checked. (Also, does it run in the background on startup or am I supposed to see something - I didn't see anything when it boot up into Windows).

I would be immensely appreciative for any help. Thank you.

-----------------
Specs:

-Win 7 x64
-Original install
-OEM
-Age of hardware: Oct. 2011
-Age of OS: since I just reinstalled it a few hours ago: 2/3/2012

The laptop: http://www.staples.com/Samsung-Serie...product_376050

My System SpecsSystem Spec
.

03 Feb 2012   #2

Windows 7 Home Premium 64 Bit
 
 

Start with STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg, and then let us know if you need further assistance.
My System SpecsSystem Spec
03 Feb 2012   #3

Windows 7 Home Premium 64bit
 
 

I have read and done the things posted in that thread extensively (did you not read my post?)

-FurMark and Prime 95 tests ran
-Updated the BIOS
-Ran Driver Verifier

I was hoping someone could take a look at my dump files.

I am attaching my latest MEMORY.dmp file for anyone to take a look to help:

http://www.**************/?n0jpikvxro20n62
My System SpecsSystem Spec
.


03 Feb 2012   #4

Windows 7 Home Premium 64 Bit
 
 

You had not mentioned the BIOS update. I will check the temperatures for your CPU to see if they are within acceptable limits. I believe they are since laptops are usually designed to get to 100 C (checked and confirmed, 100 C is the max).

Also, since you cannot get through Memtest86+, either your memory is bad, or the ISO did not burn correctly. Try the bootable USB version, and if you still cannot run Memtest86+, do the following steps to clear all BIOS and memory corruption.
Note: If you are using a RAID controller, this will reset the RAID and you will lose your data. Backup all important files and make a system image before proceeding with this step if you have multiple hard drives in a RAID configuration. .
  1. Go into your BIOS and load default settings to clear the CMOS memory.
  2. Save Settings and exit the BIOS.
  3. Shut down and turn off the computer.
  4. Unplug the computer from the wall or surge protector (then remove the battery if it is a laptop).
  5. Hold down the power button for 30 seconds. This closes the circuit and ensures all power from components is drained to clear the software connections between the BIOS and hardware and clear any corruption in the temporary memory.
  6. (If it is a laptop, plug the battery back into the laptop and then) Plug the computer back into the wall.
  7. Turn it on to reinitialize the software connections between the BIOS and hardware, and post back your results.
If you are unsure whether you are running a RAID configuration, do the following steps.
  1. Click Start Menu
  2. Right Click My Computer/Computer
  3. Click Manage
  4. Click Device Manager from the list on the left
  5. Expand Disk Drives and check for RAID manufacturers (use Google or ask us by typing in manufacturers listed in your Disk Drives list)

Alternatively:
  1. Login as an adminstrative user.
  2. Click Start Menu
  3. Click Control Panel
  4. Click Hardware and Sound
  5. Click Device Manager (the last link under Devices and Printers)
  6. Expand Disk Drives and check for RAID manufacturers (use Google or ask us by typing in manufacturers listed in your Disk Drives list)

See if you can run Memtest86+ after those steps. If not, contact the laptop manufacturer and see if you can get parts repaired/replaced as the motherboard/CPU/RAM modules (one of the three) are likely faulty.
My System SpecsSystem Spec
03 Feb 2012   #5

Windows 7 Home Premium 64bit
 
 

Thank you writhziden for the replies, I really appreciate it.

I cleared the CMOS and reset all BIOS settings to Default already so I will try to perform the next step.

Will report back to you if MemTest goes through.
My System SpecsSystem Spec
03 Feb 2012   #6

Windows 7 Home Premium 64bit
 
 

Hi writhziden,

So I did the steps you told me and I ran MemTest.

Usually before the laptop would shutdown right when Test #7 started.

However, I tried starting at Test #7 instead and the laptop ran it fine. However, at around the 11 minute marker, it shutdown (just like before). I noticed that regardless of the test, the laptop shutsdown at around 11:14.

Test #7 seems to kick up the fan of the laptop a lot more than the other tests, but again, running the other tests that didn't seem as intensive still yielded shutoff at ~11 min.

In regards to the Prime95 stress test, how long should it run for and what temperature should I stop it at to prevent any damage? I don't want to run it so long that it does more harm.

I've also attached my report from HWiNFO64.
My System SpecsSystem Spec
03 Feb 2012   #7

Windows 7 Home Premium 64 Bit
 
 

You should run each of the prime95 tests for ~3 hours or until errors show up. If the temperature starts getting close to 100 C, say over 90 C, report here.
My System SpecsSystem Spec
03 Feb 2012   #8

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
You should run each of the prime95 tests for ~3 hours or until errors show up. If the temperature starts getting close to 100 C, say over 90 C, report here.
Temp stays constant at a max of 79C.

No errors reported so far and no weird issues during the tests.

Frankly have no idea except to send it in for repairs if it happens again, but frankly, it hasn't BSOD'd since yesterday.

The last thing to do would be to run Driver Verifier again but go through all my drivers perhaps (incl. Microsoft ones?)
My System SpecsSystem Spec
03 Feb 2012   #9

Windows 7 Home Premium 64 Bit
 
 

If you run Verifier, it is a bad idea to include the Microsoft drivers. That will definitely cause crashes and they will not be conclusive. Do you know what steps you have done since the last crash that may have resolved the problem? The BIOS update perhaps?
My System SpecsSystem Spec
03 Feb 2012   #10

Windows 7 Home Premium 64bit
 
 

Quote   Quote: Originally Posted by writhziden View Post
If you run Verifier, it is a bad idea to include the Microsoft drivers. That will definitely cause crashes and they will not be conclusive. Do you know what steps you have done since the last crash that may have resolved the problem? The BIOS update perhaps?
Perhaps it's the BIOS update but it remains to be seen if everything is actually 'fixed.' I think I ran FurMark and Prime95 before the update and they still went fine.

It's annoying because the BSOD happens randomly and intermittently, but not that often, but it still happens.

And the reasons as to why MemTest shows no errors but shuts off the laptop after 11 minutes (every time too, regardless of test) is probably the only thing that makes me question if anything is fixed, and whether it is a RAM problem or not. If it was a RAM problem, I would think errors would crop up. If it was overheating, I'd think running Prime95 for 3 hours+ would cause problems.

All in all a very confusing and inconclusive issue. Thanks again for responding writhziden
My System SpecsSystem Spec
Reply

 Random BSOD, Error: A clock interrupt was not received on a secon.....




Thread Tools




Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 07:11 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33