A number of event log errors + BSOD's

[seth500]

In my administrative events log I have a number of errors all of which point to the service control manager. This is a new install and I have had the same system running once before with no problems. Memory is good, no overclocking, nothing overheating the power supply is good and it's also happening on my wife's computer as well which is a totally different setup all together. It can't just be coincidence, also on both computers error 41 keeps showing up which locks up her computer without writing a dump file and blue screens mine. This computer is not my main listed below in my specs it's an older Asus A8N-SLI board and all drivers are current, below I attached the dump files the first of which was already related to Asacpi.sys which has since been fixed. The latest dump of 8-2-2011 is which I am most concerned with. I have looked at it and it deals with win32k.sys which could be anything. Any help will be highly appreciated TIA Seth.

Edit: I just attached the last entries of the cbs log that sfc /scannow reparired..

 

[yowanvista]

Seems that there is a problem with the CPU itself

Run Prime 95 to test your CPU. Carefully the instructions in this tutorial: CPU - Stress Test with Prime95. Run 3 separate tests, one on each of the settings (Blend, Small FFTs, Large FFTs). Post back with your results

According to your dump file the issue is with your Processor. This occurs when the processor is non-responsive or is deadlocked.

Possible Solutions :

a) BIOS bug
b) a driver whose activity is causing the target processor to lock up
c) a hardware defect (temperature, voltage, dust

But its mainly caused by a defective CPU or outdated BIOS

Details about this bugcheck:
http://www.sevenforums.com/crash-loc...tml#post567135

Win 7 A Clock Interrupt... BSOD (101 Error)

*******************************************************************************
*                                                                             *
*                        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: 0000000000000060, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009e5180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT:  
fffff880`031b6528 fffff800`028e08f9 : 00000000`00000101 00000000`00000060 00000000`00000000 fffff880`009e5180 : nt!KeBugCheckEx
fffff880`031b6530 fffff800`028934b7 : fffff880`00000000 fffff800`00000001 00000000`00002626 fffff8a0`03059b01 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`031b65c0 fffff800`02e061c0 : 00000000`00000000 fffff880`031b6770 fffff800`02e223c0 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`031b66c0 fffff800`02885233 : 00000000`25cdb0e0 fffff800`02e223c0 fffffa80`07d6a010 fffffa80`00000001 : hal!HalpRtcClockInterrupt+0x130
fffff880`031b66f0 fffff800`0288e800 : fffff800`029fbe80 fffffa80`00000001 00000000`00000000 fffff880`031b6978 : nt!KiInterruptDispatchNoLock+0x163
fffff880`031b6880 fffff800`028cd7ec : fffff880`031b6c58 00000000`00000000 00000000`00000000 fffffa80`0489f010 : nt!KeFlushMultipleRangeTb+0x260
fffff880`031b6950 fffff800`028ca621 : fffffa80`03cfe680 00000000`00000000 fffff880`031b6c58 00000000`00000000 : nt!MmSetAddressRangeModified+0x2b0
fffff880`031b6a50 fffff800`028cdfa6 : fffffa80`07365b08 00000000`00000001 fffffa80`00000001 00000000`00001000 : nt!CcFlushCache+0x561
fffff880`031b6b50 fffff800`028ce968 : fffff880`00000000 fffff880`031b6c58 fffffa80`075cb730 fffff800`02a87898 : nt!CcWriteBehind+0x1c6
fffff880`031b6c00 fffff800`02893021 : fffffa80`03cf2260 fffff800`02b7f001 fffff800`02a878a0 00000000`00000002 : nt!CcWorkerThread+0x1c8
fffff880`031b6cb0 fffff800`02b2532e : 00000000`00000000 fffffa80`03cfe680 00000000`00000080 fffffa80`03ce8b30 : nt!ExpWorkerThread+0x111
fffff880`031b6d40 fffff800`0287a666 : fffff880`009e5180 fffffa80`03cfe680 fffff880`009eff40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


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_2_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE

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

 

[seth500]

Hi yowanvista appreciate the quick reply, I wish I could give the results of a stress test but it blue screens before the test is completed so there's that. I do have another cpu for this motherboard but before I do that I would like to check for a bios bug and other solutions if I may before I change out processors. Would flashing the bios get rid of a bug? Or is the procedure a bit more involved?

 

[yowanvista]

Hi yowanvista appreciate the quick reply, I wish I could give the results of a stress test but it blue screens before the test is completed so there's that. I do have another cpu for this motherboard but before I do that I would like to check for a bios bug and other solutions if I may before I change out processors. Would flashing the bios get rid of a bug? Or is the procedure a bit more involved?

If the issue lies in the BIOS then if might fix it or else you should get another CPU

 

[seth500]

Ok I try the flash first with the latest bios and then if that doesn't work then I have another cpu right here that I know works perfectly it just a tab bit slower..

 

[seth500]

well I changed out the processors and watching the temperatures between the two processors there was quite a big difference. The amd 5000 dual core was running pretty darn hot 195 degrees F. Where as the one I'm stress testing now is at 145 degrees F. Which is a 4400 dual core amd..seems to be working fine for now well see as the testing goes forward..

 

[seth500]

Hi yowanvista,

The other processor did the same thing it blue screened during the first test which was the short test and I do know the processor was good, also it gave the same BSOD error that you had originally. So what I did is I changed back to the other processor (5000) and made some changes in the power management section of bios it turns out that the ACPI Suspend Type was set to S3 (STR) when I set it to both S1 (POS) and S3 suspend type the whole system has stabilized and haven't had any blue screens (keeping fingers crossed)...