Problem w postaci BSOD 0x00000101

Całe forum

Przeszukaj

Całe forum

Użytkownicy

Tryb drzewa \| Tryb normalny Problem w postaci BSOD 0x00000101
thermalfake Ostatni Mohikanin Liczba postów: 13.580	Post: #4 RE: Problem w postaci BSOD 0x00000101 CLOCK_WATCHDOG_TIMEOUT (101) Uwalona płyta albo procesor (skłaniałbym się ku temu), błąd ewidentnie wskazuje na usterkę sprzętową. Na forum jest już kilka wątków na ten temat w których odpowiadałem. Kod: Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [G: \Downloads\112811-12994-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: symsrvsymsrv.dllc: \symbhttp: //msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16841.amd64fre.win7_gdr.110622-1503 Machine Name: Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`03045e70 Debug session time: Mon Nov 28 23: 11: 23.387 2011 (UTC + 1: 00) System Uptime: 0 days 0: 22: 43.729 Loading Kernel Symbols ............................................................... ................................................................ ......... Loading User Symbols Loading unloaded module list ......... ****************************************************************************** * * * Bugcheck Analysis * * * ***************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 101, {31, 0, fffff88002f64180, 2} 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: fffff88002f64180, The PRCB address of the hung processor. Arg4: 0000000000000002, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe CURRENT_IRQL: d STACK_TEXT: fffff880`075b0438 fffff800`02e26463 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f64180 : nt!KeBugCheckEx fffff880`075b0440 fffff800`02e80c87 : 00000000`00000000 fffff800`00000002 00000000`00002711 00000000`00000000 : nt! ? : FNODOBFM: `string'+0x4d8e fffff880`075b04d0 fffff800`033ee895 : fffff800`03413460 fffff880`075b0680 fffff800`03413460 00000000`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`075b05d0 fffff800`02e74ab3 : fffff800`02ff2e80 00000000`00000001 fffffa80`0470c900 fffff880`0ffd1a90 : hal!HalpHpetClockInterrupt+0x8d fffff880`075b0600 fffff800`02e379e9 : fffff800`02ff2e80 fffff880`075b0810 fffffa80`05335b60 00000000`7ef53000 : nt!KiInterruptDispatchNoLock+0x163 fffff880`075b0790 fffff800`03173298 : 00000000`00000000 fffff880`075b0c60 fffff800`02e08000 c473ed5d`3db48818 : nt!KeFlushProcessWriteBuffers+0x65 fffff880`075b0800 fffff800`03173f15 : 00000000`01cdf150 fffff800`0316fe3a 00000000`00000000 00000000`00000246 : nt!ExpQuerySystemInformation+0x1368 fffff880`075b0ba0 fffff800`02e77813 : 00000000`00000000 fffff880`075b0c60 ffffffff`fffe7960 000007fe`f8df0b00 : nt!NtQuerySystemInformation+0x4d fffff880`075b0be0 00000000`7740fa1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`00d1f638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7740fa1a 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 --------- W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu. Jak mądrze zadawać pytania? - przejrzyj poradnik na forum. Nie udzielam porad via PW. 28.11.2011 23:53
Podziękowania od:

Wiadomości w tym wątku

Problem w postaci BSOD 0x00000101 - greififreud - 28.11.2011, 23:00

RE: Problem w postaci BSOD 0x00000101 - peciaq - 28.11.2011, 23:04

RE: Problem w postaci BSOD 0x00000101 - greififreud - 28.11.2011, 23:25

RE: Problem w postaci BSOD 0x00000101 - thermalfake - 28.11.2011 23:53

RE: Problem w postaci BSOD 0x00000101 - techdive - 29.11.2011, 00:22

RE: Problem w postaci BSOD 0x00000101 - greififreud - 29.11.2011, 18:56

RE: Problem w postaci BSOD 0x00000101 - greififreud - 29.11.2011, 19:55

RE: Problem w postaci BSOD 0x00000101 - thermalfake - 29.11.2011, 23:11

RE: Problem w postaci BSOD 0x00000101 - techdive - 29.11.2011, 19:34

Podobne wątki
Wątek:	Autor	Odpowiedzi:	Wyświetleń:	Ostatni post
BSOD	Moloch4	0	819	05.07.2019 11:29 Ostatni post: Moloch4
BSOD Windows 7	luzbluzoner	0	1.317	17.12.2016 20:25 Ostatni post: luzbluzoner
Częsty ekrad BSOD	kubajed	0	1.279	03.10.2016 17:46 Ostatni post: kubajed
kolorowy wskaźnik w postaci paska wizualizującego stopień zapełnienia dysku	bravek	3	1.515	13.08.2016 04:14 Ostatni post: beabea
Kod błędu:0x00000101	manel	2	1.678	21.06.2016 10:08 Ostatni post: manel
Rozwiązany -Windows 7 64-bit Problem z bluescreen'ami (BSOD)	jacob776	6	3.846	04.12.2015 17:45 Ostatni post: jacob776

« Starszy wątek | Nowszy wątek »

Autor: greififreud
Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 0 głosów.