New
#21
Mb or proccessor?
Should i change my motherboard or proccessor they in warranty
Should i change my motherboard or proccessor they in warranty
Why this bug 101 occured if temp r really fine?
but sir my built is only 4months old y it hung even for 1 time?
1000 of reason's ..... could be a bad software or driver or a manufacturing defect or temperatures .... we can't just say from 1 BSOD why it hung and for what reason ... and why it should even hang for even 1 time...
Its like asking why I got sick... i do all the things right.. but still fell sick.....
It as philosophical question
Sorry but I'm not GOD... I'm are just human beings... i don't have answers for everything !
but what exactly bug report says?
here it is
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, fffff880033d5180, 3}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880033d5180, The PRCB address of the hung processor.
Arg4: 0000000000000003, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffff880`07c9e438 fffff800`03067443 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`033d5180 : nt!KeBugCheckEx
fffff880`07c9e440 fffff800`030c35f7 : 00000000`00000000 fffff800`00000003 00000000`00002711 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`07c9e4d0 fffff800`0300a895 : fffff800`0302f460 fffff880`07c9e680 fffff800`0302f460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`07c9e5d0 fffff800`030b73f3 : fffff800`03233e80 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`07c9e600 fffff800`0307a2c9 : fffff880`102de6f3 fffffa80`07e03000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`07c9e790 fffff800`033b5e58 : 00000000`00000000 fffff880`07c9ec60 fffff800`03049000 fffff880`07c9e960 : nt!KeFlushProcessWriteBuffers+0x65
fffff880`07c9e800 fffff800`033b6e49 : 00000000`02959800 fffff800`033b29ee 00000000`00000000 fffffa80`071859c0 : nt!ExpQuerySystemInformation+0x1368
fffff880`07c9eba0 fffff800`030ba153 : 00000000`00000000 fffff880`07c9ec01 ffffffff`fffe7960 000007fe`00000000 : nt!NtQuerySystemInformation+0x4d
fffff880`07c9ebe0 00000000`7790021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`030defc8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7790021a
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_4_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
hello sir 101 bug occured again plz suggest something see the file attached
here it is sir