Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... HELP

Status
Not open for further replies.
S

sitchey

Member
Joined
Apr 30, 2013
Posts
13
Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... HELP

Hi Folks

I am having a large number of BSoD errors on a HP Pavilion Elite HPE-460 that I bought from a company. It’s a long story but the PC wasn’t fit for purpose as the hard drive was corrupt and the graphics card damaged (blinking screen with kernel crashes). However eBay somehow decided in its wisdom to back the company in my dispute rather than let me return the piece of crap. Anyway as I am stuck with it I wanted to try and get some value from it but am pulling my hair out with error after error.

I installed a new hard drive and graphics card and rebuilt the system as per the org specs from HP ie Windows7 x64 and installed all the original drivers from the HP website. However I am getting a large number of BSoD errors. The first one is the...

'clock interrupt was not received on a secondary processor...' stop: 0x00000101 crash.

I haven’t installed anything heavy on the PC as it was just a new build so at the time it crashed it had Office, Power ISO and AVG Internet Security 2013 running. On rebooting I got the lovely bootmgr error and as Windows repair couldn’t fix the error I had to format the drive and build again.

This time I went for Windows 8 Pro X64 encase it was a software issue. Again I haven’t installed many programs as I was just testing, but this time notice that the new BSoD screens seem to happen more frequent (t least twice a day) and particularly when I am coping and pasting files - even small ones or opening certain websites. The BSoD errors I have this time are:

'MACHINE_CHECK_EXCEPTION' and
'CLOCK_WATCHDOG_TIMEOUT'

I have attached two mini dump files (one for each of the Windows 8 BSoD) along with some photos of the BSoD from Windows 7 and 8.

I have searched many forums but can’t find a solution, especially as responses posted are for that person’s specific hardware/software issues.

If anyone could help me decipher the mini dumps and ultimately help me try and salvage a piece of crap you would help prevent a young man from premature balding ;)

The other specs of the PC are:

MOBO: HP IONA (MS-7613 Ver 1.1)
CPU: Intel iCore 7
RAM: 6GB (2GB X3)
BIOS: 6.12 (Latest from HP)
HD: WD5000AVDS

Attachments

win7-bsod-01.jpg win8-bsod-01.jpg win8-bsod-02.jpg
 

Attachments

Last edited by a moderator:
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

Hello and welcome to Sysnative! You've come to the right place. :)

A word of warning from me personally, I am busy with school and exams at the moment. I will do my best to get back to replies in a timely manner, however it is possible there may be a long delay. I apologise about that in advance, hope you understand.

Anyway, on we go.

Could you please follow the BSOD Posting Instructions since that provides more info than just the minidumps.

However, I have run the dumps you have given me.

Outdated 3rd Party Drivers

These drivers are ones manufactured by a 3rd Party (not Microsoft) and are either outdated or known causes of BSOD's.
To update the drivers to the latest version, follow the links below the drivers to find the manufacturer's website and the download location. If an update cannot be found, please uninstall the related software or device. The software can be uninstalled via Control Panel and the device through Device Manager. If you are stuck and require help, please let me know.


lmimirr.sys Tue Apr 10 23:32:45 2007 (461C108D)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
https://www.sysnative.com/drivers/driver.php?id=lmimirr.sys

RaInfo.sys Fri Jan 4 18:57:14 2008 (477E818A)
LogMeIn/RemotelyAnywhere Kernel Information Provider
https://www.sysnative.com/drivers/driver.php?id=RaInfo.sys

LMIRfsDriver.sys Mon Jul 14 17:26:56 2008 (487B7E50)
RemotelyAnywhere Mirror Miniport Driver or LogMeIn Mirror Miniport Driver
https://www.sysnative.com/drivers/driver.php?id=LMIRfsDriver.sys

HECIx64.sys Thu Sep 17 20:54:16 2009 (4AB293E8)
Intel Management Engine Interface
https://www.sysnative.com/drivers/driver.php?id=HECIx64.sys

AVer888RCIR_64.sys Fri Nov 13 06:20:12 2009 (4AFCFA9C)
AVerMedia Technologies H193 IR Driver for eHome
https://www.sysnative.com/drivers/driver.php?id=AVer888RCIR_64.sys

AVer888RC_64.sys Fri Nov 13 06:21:19 2009 (4AFCFADF)
AVerMedia Technologies CX23888 AVStream Video Capture Driver
https://www.sysnative.com/drivers/driver.php?id=AVer888RC_64.sys

PxHlpa64.sys Mon Oct 17 15:29:34 2011 (4E9C3BCE)
Sonic CD/DVD driver (used by many different CD/DVD programs)
https://www.sysnative.com/drivers/driver.php?id=PxHlpa64.sys

Rt630x64.sys Wed Oct 19 13:12:55 2011 (4E9EBEC7)
Realtek PCI/PCIe Adapters
https://www.sysnative.com/drivers/driver.php?id=Rt630x64.sys

SCDEmu.SYS Tue Nov 15 03:18:27 2011 (4EC1DA03)
PowerISO Virtual Drive driver
https://www.sysnative.com/drivers/driver.php?id=SCDEmu.SYS

​

BSOD Analysis

I have a feeling that these BSODs may be related to a hardware error of sorts. The first dump is the one that is intriguing me.

Code: 
Unable to read KTHREAD address fffffa8007cb23b8
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

You should not see Unknown_Image in dumps. It's indicative of a hardware fault.

Other factors that indicate potential hardware faults:

Code: 
MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
Arguments:
Arg1: 0000000000000000
Arg2: fffff880013eead0
Arg3: 0000000000000000
Arg4: 0000000000000000

BUGCHECK_STR:  0x9C_GenuineIntel

A 0x9c bugcheck, or MACHINE_CHECK_EXCEPTION, is very similar to a 0x124 bugcheck. The 0x124 is normally indicative of a CPU faliure, but can be other hardware faults.

0x9c_GenuineIntel is also indicative of a CPU fault.

Enable Driver Verifier for now to see if a 3rd party driver can be identified --> https://www.sysnative.com/forums/bs...river-verifier-blue-screen-death-related.html

Perform some basic hardware tests:

RAM - Please run Memtest86+ to check your RAM. A tutorial on how to do this is available here: Test RAM With Memtest86+ - Sysnative Forums

HDD - Check your HDD for errors using Seatools. A tutorial for this is available here: Hard Drive (HDD) Diagnostics - Sysnative Forums

If they both pass, we will run some stress tests.

Also, next time you have a BSOD, please could you navigate to C:\Windows and upload MEMORY.DMP. This is a full kernel dump. It will be too large to upload here. Please zip it up and upload it to a file sharing site such as SkyDrive or Dropbox. SkyDrive is the recommended one.


Regards,
Stephen
 
Last edited:
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

Crashdumps provided so far aren't worth much. The one shows a machine check, but won't reveal what the error was because it wasn't recorded (the crashdump is incomplete/corrupt). The other one showed an issue with what may be disk (NTFS) activity, be can't be sure, as the data necessary to extrapolate on this is private and only accessible to those with access to MSDN resources.

I'm not sure why you wish to continue salvaging this system. It's already displayed its share of issues, and it seems by the time you end up fixing it - if this does end up being a hardware problem, which most likely it is - you'll end up just making a new one just about. Sounds like you're better off just grabbing the new card and drive and scrapping the rest for something more reliable.

Anyways, if you still wish to persist, as Tekno noted, we need more info, so follow the steps he gave. Also, I'll add to try out Prime95 from the UBCD. It's called Mersenne Prime Test and it's under CPU section. You'll need to run it several hours if possible. Hopefully your CPU cooler is prepared to take the heat, since the test will run the CPU at maximum heat. If the test crashes or errors, you may very well have a CPU problem, with there also being a chance it being the power supply or motherboard.
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

thanks guys. I wasn't sure on what to provide as this is the first machine I had that has played up as bad as this. Ill post back with comments later

thanks for input so far!
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

sitchey said:
However eBay somehow decided in its wisdom to back the company in my dispute rather than let me return the piece of crap.
Click to expand...

Hi -

I agree with Tekno Venus & Vir Gnarus.

I suggest that you tell eBay that they did in fact sell you a piece of garbage, show them this thread is need be & demand a refund/ replacement.

If we can help you further in this matter, please let us know -- we will do all we can to help you.

Regards. . .

jcgriff2
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

jcgriff2 said:
sitchey said:
However eBay somehow decided in its wisdom to back the company in my dispute rather than let me return the piece of crap.
Click to expand...

Hi -

I agree with Tekno Venus & Vir Gnarus.

I suggest that you tell eBay that they did in fact sell you a piece of garbage, show them this thread is need be & demand a refund/ replacement.

If we can help you further in this matter, please let us know -- we will do all we can to help you.

Regards. . .

jcgriff2
Click to expand...

I tried the ebay route but they backed the seller as he said that me opening the machine to check the graphics card voided the warranty! even though the were no security seals
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

OK running some more tests as we speak

Memtest was running for a few hours and found no issues so the RAM is ok

Am currently running the CPU stress tester on the UBCD. It has been running for 4 hours and so far apart form the tested numbers changing all I can see on screen is "^CCA^CCA". Not sure what that means? It hasn't crashed in that time so hopefully a good sign on the CPU but will let it run overnight.

I also have a autoboot Fedora Live CD so will run that to try and see if I can eliminate the hardware as the cause.

After that I will log back into windows, update those drivers and when I get another BSoD will upload the Memory.DMP for analysis.

Thanks for your input folks so far :) As I said I am kind of stuck with this PC now and would like to see what can be done to salvage something.
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

· OS - Windows 8
· x64
· What was original installed OS on system? - Windows 7 x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - Retail but currently needs activated
· Age of system (hardware) - 1 year
· Age of OS installation - 1 day
· CPU - Intel i7 2.8GHZ
· Video Card - Replaced OEM nvidia with Sapphire HD6570
· MotherBoard - HP IONA (MS-7613 Ver 1.1)
· Power Supply - HP 460w
· System Manufacturer - HP
· Exact model number - HP Pavilion Elite HPE-360uk

Ill upload the rest as per the BSoD posting instructions when Im logged back into Windows on the machine
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

I ran cpu stress tester 2.0 for over 12hrs last night. I think everything seems ok with the CPU as it kept running through the test cycles and didnt crash or overheat. I also run the prime cpu test on the UBCD but it didnt run for long so I uploaded an image from that test.

I will update the drivers mentioned above this weekend and will also upload a copy of the memory.drm file

IMG_1956.jpg IMG_1958.jpg
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

Hello,

You said you ran memtest86+ for a few hours, how many passes did it complete? It needs to run for a minimum of 7 passes in order to get a reliable result. This generally takes all night at least. If it ran for less than 7 passes, please run it again. The more passes the better, I have seen it take >20 passes to detect an error.

Hardware is the number one suspect here, it is very unlikely to be anything else IMHO.

I have some powerful stress tests linked below. You will NEED to keep an eye on your temperatures. Use one of the following pieces of software:



Run these tests with your PC at idle - i.e. nothing else in the background. Please do not use your PC whilst the tests are running.

Run Prime95 (64bit/32bit) Run the Blend for a few hours. Report back if CPU temperatures reach dangerous levels, if the system crashes, or if hardware errors are discovered by the diagnostics. A full tutorial on how to do this is availible here: https://www.sysnative.com/forums/hardware-tutorials/3908-prime95-hardware-stress-testing.html. It is effectively the same as the Mersenne Prime Test on UBCD but I am more familiar with the windows version. Run the Blends test for as long as possible.

Then run the Intel BurnTest found here --> |MG| IntelBurnTest 2.54 Download. Run this on Maximum and for 50 tests. I ran 10 on my system and it took 300 seconds, so 50 should be plently. Do more if you wish/are running it over night. Check output results to results.log and upload the log here when complete.

Then run Furmark following the tutorial found here --> https://www.sysnative.com/forums/hardware-tutorials/3907-furmark-display-card-stress-test.html.

Apologies for the length of time these tests take, but they are the only way we can find and test out hardware errors.

Regards,
Stephen
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

Hi Stephen

I can the test overnight and this morning and this is what I found

Memtest86
Ran for 18hrs and it did 18 passes with no errors found. So cant be a memoey fault.

Prime98
Ran it in windows with Real Temp monitoring the temperatures. The program ran fine for approx 3 hours with no errors detected and the max temp recorded was 76 degrees. However I left the PC for a bit after this and it did crash and restart by the time I got back, so not sure why that was?

IntelBurn
This is were it got interesing. I can the burn test and after a few secs it crashed with the BSoD error message 'clock watchdog timeout.' I was running the test on the standard profile. On reboot I ran it again and this time it completed 1 pass fine but crashed on the 2nd pass. I have uploaded the output log

Does it look like the CPU is the issue?

thanks
 

Attachments

Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

I also had zipped up my MEMORY.DMP file for you which you can download here
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

This is looking more and more like a CPU fault.

Those results were in line with what I was predicting. Memtest has passed which is what I was expecting. We can pretty much discount RAM from the potential issue list.

I linked to the Intel Burn test for exactly that reason. If something was going to make it crash, that was going to be the program. As a comparison, my PC can run at least 10 passes without issue (I've only bothered testing 10 passes). If the system is stable, the test should be able to run for hours.

I am currently downloading the MEMORY.DMP file (my internet is slow!) and will post back once I've run analysis on it.

However, CPU is almost certainly the culprit here.

Regards,
Stephen
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

Hmmm... The zip file you have given me is corrupt and even my trusty Disk Internal Zip Repairer can't fix the file. So, could you please try and zip the file back up again and send it to me again please. Thanks!

Stephen
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

RE: my above post.

Don't worry - I've downloaded it again and it's OK this time.
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

I've only had time for a quick analysis of the dump during a revision break. :)

This dump is a 0x116 VIDEO_TDR_FAILURE bugcheck, different from the others. This dump type usually indicates a graphics card fault. It's a surprising bugcheck.

Try updating your AMD Drivers following this procedure --> https://www.sysnative.com/forums/wi...cards-driver-only-installation-procedure.html

I see the AVG Anti-Virus driver in the stack:
Code: 
fffff880`06b355f8  fffff880`06b356a0
fffff880`06b35600  fffff880`042bd158*** ERROR: Module load completed but symbols could not be loaded for [B]avgidsdrivera.sys[/B]
 avgidsdrivera+0x29158

Replace AVG with Microsoft Security Essentials
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

thats wierd if its the new graphics card. But i updated the AMD driver as that guide stated

When you say replace AVG are you saying just remove it for Microsoft SE?
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

ok both done
 
Re: Numerous BSoD errors ('MACHINE_CHECK_EXCEPTION' & 'CLOCK_WATCHDOG_TIMEOUT')... H

Good. :)

We'll see how this runs. I doubt it'll fix the root cause (I'm still thinking the CPU is the real problem here), but we can cross our fingers.

Stephen
 
Status
Not open for further replies.

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

Back
Top