Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

0x0000101 CPU error?


  • Please log in to reply
2 replies to this topic

#1 Hexonloire

Hexonloire

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:34 AM

Posted 26 October 2011 - 10:51 PM

Hi there,

This error 0x0000101, started out when my friend got this computer and has been fairly intermittent, but persistent for over 10 months now. Only in the last month however, the pc has become unusable, blue screening roughly 5-6 times a day, with no discernable pattern. Under load, not underload, it doesn't seem to matter. From what I've heard, this could just be a faulty CPU (as this person has had this issue from day 1 of buying this pc). It's still under warranty, so we're currently looking at that avenue - however, we would rather fix the issue without losing all their data if we can. I've heard that this issue can be due to bad drivers, bad hardware, bad software, bad anything. It's way too general to start just trying to delete everything and see how it goes.

Does anyone have experience with this issue? Or is there any way that I can narrow down possible bad areas? I'll link the system specs and the error code below.

Win7 Premium 32bit (6.1, Build 7601)
MB: P67A-UD3R
CPU: Intel Core i5-2500 @ 3.30Ghz, ~3.66ghz
RAM: 4096MB
GeForce GTX460 SE 2525MB

Event log error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x00000031, 0x00000000, 0x8ed36120, 0x00000003). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 102511-17690-01.

edit: I had wondered if they had overclocked the cpu at the shop that the person bought it from (it did mention overclocking on the invoice, but I wasn't sure as to why), so I slowed it down to 2.6ghz. It was no more stable than before.

edit2: Also, after debugging the minidump, I've received this:

*******************************************************************************
* *
* 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: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 8ed36120, The PRCB address of the hung processor.
Arg4: 00000003, 0.

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

*** WARNING: Unable to verify timestamp for SRTSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for SRTSP.SYS
*** WARNING: Unable to verify timestamp for SYMEFA.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA.SYS

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: ccsvchst.exe

CURRENT_IRQL: 1c

STACK_TEXT:
b472c3bc 830bca2f 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
b472c3f8 830bc07e 00002711 00000000 00024900 nt!KeAccumulateTicks+0x242
b472c438 830bbf2b 830bdddb 2dd899c8 00000000 nt!KeUpdateRunTime+0x145
b472c494 830c0bd7 b472c41b b472c41b 000000d1 nt!KeUpdateSystemTime+0x613
b472c494 830bdddb b472c41b b472c41b 000000d1 nt!KeUpdateSystemTimeAssist+0x13
b472c528 83078bc8 00000001 00000000 830d7a03 nt!KiIpiSendPacket+0x7f
b472c564 830f31d7 b472c5b0 00000000 b472c5b0 nt!KeFlushMultipleRangeTb+0x26f
b472c644 830dfcd1 c061b2f0 00000003 00000000 nt!MiFlushTbAsNeeded+0x12e
b472c684 83160487 0004365b 00000001 85cb5000 nt!MiAllocatePagedPoolPages+0x567
b472c6e8 830dc634 00000001 00002258 00000ff0 nt!MiAllocatePoolPages+0x1f
b472c740 83161132 00000000 00000001 00002258 nt!ExpAllocateBigPool+0xa6
b472c7a0 a8731118 00000001 00002254 61456153 nt!ExAllocatePoolWithTag+0x12d
WARNING: Stack unwind information not available. Following frames may be wrong.
b472c7bc a87489cd 00002254 00000000 b472c81c SRTSP+0x59118
b472c7d8 a8730134 aa680000 b472c81c deadbee0 SRTSP+0x709cd
b472c828 a86e89fc 8dbdd008 a47ff548 89ac7980 SRTSP+0x58134
b472c9b4 8cb2765c a47ff620 40000000 0000000d SRTSP+0x109fc
b472ca00 8cb2b569 8cb13ab8 a47ff548 0000000d SYMEFA+0xa665c
b472ca30 8cb288cf 8681b560 8681b4f0 00226004 SYMEFA+0xaa569
b472cadc 8cb16931 8681b4f0 89aad038 85d67848 SYMEFA+0xa78cf
b472cafc 8307858e 85d67848 8681b4f0 8681b4f0 SYMEFA+0x95931
b472cb14 8326ba31 89aad038 8681b4f0 8681b560 nt!IofCallDriver+0x63
b472cb34 8326ec03 85d67848 89aad038 00000000 nt!IopSynchronousServiceTail+0x1f8
b472cbd0 832b549c 85d67848 8681b4f0 00000000 nt!IopXxxControlFile+0x6aa
b472cc04 8307f1fa 00000168 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
b472cc04 76f470b4 00000168 00000000 00000000 nt!KiFastCallEntry+0x12a
0456e524 00000000 00000000 00000000 00000000 0x76f470b4


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: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE

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

Edited by Hexonloire, 26 October 2011 - 11:31 PM.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,734 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:07:34 PM

Posted 27 October 2011 - 10:21 AM

<<...so we're currently looking at that avenue - however, we would rather fix the issue without losing all their data if we can.>>

If that's true...you can simply clone the hard drive...or move data files to another drive/system...and then utilize the warranty provisions.

I'm not saying this is a warranty issue...just telling you how to overcome the aspect you mentioned.

Louis

#3 Hexonloire

Hexonloire
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:10:34 AM

Posted 28 October 2011 - 02:35 AM

Thanks for the reply.

Yeah, there are ways around it, but also I would ideally like an answer to this question. It's tricky, has me very interested, and would be good to know so if I see it again it can be solved.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users