New
#1
Random BSOD
Had a BSOD at 07.04 evening, was not doing anything special.
Tryed to solve by myself with windbg but couldnot.
Please take a look.
Had a BSOD at 07.04 evening, was not doing anything special.
Tryed to solve by myself with windbg but couldnot.
Please take a look.
Take a look at this thread particularly for your error code: STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg
Code:Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Yusra\Downloads\PC-TATYANAS-09_04_2014_104349,66\040714-66986-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532 Machine Name: Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`032976d0 Debug session time: Mon Apr 7 20:13:07.850 2014 (UTC + 6:00) System Uptime: 1 days 11:30:33.759 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {31, 0, fffff880037d7180, 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: fffff880037d7180, 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: msiexec.exe CURRENT_IRQL: d STACK_TEXT: fffff880`0702bec8 fffff800`03120a4a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`037d7180 : nt!KeBugCheckEx fffff880`0702bed0 fffff800`030d36f7 : 00000000`00000000 fffff800`00000003 00000000`00026161 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4e3e fffff880`0702bf60 fffff800`03015895 : fffff800`0303b460 fffff880`0702c110 fffff800`0303b460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`0702c060 fffff800`030c6113 : 00000000`4d6039b2 fffff800`03244e80 00000000`00001000 fffff880`0702c200 : hal!HalpHpetClockInterrupt+0x8d fffff880`0702c090 fffff800`030ce9f6 : fffff800`03244e80 00000000`00000001 00000000`00000000 fffff880`0702c338 : nt!KiInterruptDispatchNoLock+0x163 fffff880`0702c220 fffff800`0308631a : fffff6fc`500430e8 fffffa80`0b22e860 fffff800`03304600 00000000`00000013 : nt!KeFlushMultipleRangeTb+0x266 fffff880`0702c2f0 fffff800`03085f18 : fffff8a0`0861c000 00000000`00000000 00000000`00000005 00000000`00000000 : nt!MiProtectPool+0x3a6 fffff880`0702c420 fffff800`033660b7 : 00000000`025f1000 00000000`00012f88 00000000`00001000 00000000`00000000 : nt!ExProtectPool+0x178 fffff880`0702c490 fffff800`03363845 : 00000000`00000008 00000000`00012f8f 00000000`00000013 00000000`00000004 : nt!HvpSetRangeProtection+0x12f fffff880`0702c4f0 fffff800`0336361c : fffff8a0`00b23010 fffff8a0`00b23010 fffff8a0`01e87e20 00000000`025f1690 : nt!HvMarkDirty+0x176 fffff880`0702c550 fffff800`03345eae : 00000000`025f1690 00000000`000025ef fffff8a0`00b23010 00000000`00000000 : nt!HvMarkCellDirty+0x150 fffff880`0702c5a0 fffff800`0334613b : 00000000`00000000 00000000`025f1000 00000000`00001000 00000000`00000000 : nt!HvpFindFreeCellInBin+0xe2 fffff880`0702c5e0 fffff800`033455b1 : 00000000`025f1000 00000000`00000001 00000000`00000010 00000000`00000000 : nt!HvpScanForFreeCellInViewWindow+0x24b fffff880`0702c660 fffff800`03345c32 : 00000000`00000010 fffff800`00000001 fffff8a0`00000010 00000000`00000000 : nt!HvpFindFreeCell+0x1ba fffff880`0702c6d0 fffff800`03345b42 : fffff8a0`00b23010 fffff8a0`00b23010 00000000`00000004 00000000`040aa190 : nt!HvpDoAllocateCell+0x72 fffff880`0702c730 fffff800`03347f6b : 00000000`00000002 fffff8a0`0a0d59a0 fffff8a0`00b23010 00000000`00000001 : nt!HvReallocateCell+0xc6 fffff880`0702c770 fffff800`03347dc8 : fffff8a0`00b23010 00000000`00000000 fffff8a0`0a0d59a0 fffff880`0702c988 : nt!CmpAddValueToList+0x4b fffff880`0702c7b0 fffff800`0337cc5f : 01cf526b`7bf5561e fffff880`0702cb60 fffff8a0`0a5e3380 00000000`00000000 : nt!CmpSetValueKeyNew+0x94 fffff880`0702c800 fffff800`0337d40e : fffff8a0`144856d0 fffff880`0702c988 00000000`00000001 00000000`014fd990 : nt!CmSetValueKey+0x39b fffff880`0702c940 fffff800`030c8e53 : 00000000`000002f0 00000000`00000005 00000000`00000000 00000000`00000001 : nt!NtSetValueKey+0x349 fffff880`0702ca70 00000000`779d18ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`014fd738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x779d18ba 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 ---------
Thank you very much for your help.
I updated bios yerstaday evening. Lets how it will work now.