Gå til innhold
Trenger du hjelp med PCen? Still spørsmål her! ×

CLOCK_WATCHDOG_TIMEOUT_2_PROC - BlueScreen


Anbefalte innlegg

Her lenge fått random BlueScreens, varier alt fra 2 ganger om dagen til 1 gang i månened.

Har nå gått 3-4 måneder siden sist, men fikk en igjen idag, og har bestemt meg for å løse problemet en gang for alle.

 

PC-en består av:

Intel E8400 @ 3GHz (ikke tuklet med)

4GB RAM

4 HDDer (Alle Samsung, 500GB til 2TB disker)

AMD Radion 4800 GPU

700W PSU

 

Problemet oppstår alltid når jeg ser på en film/episode(bare 1080p) eller bruker tunge programmer som Photoshop.

Aldri under spill eller vanlig surfing.

Trodde først det var minnet, men i dump-filen står det: CLOCK_WATCHDOG_TIMEOUT_2_PROC, så jeg antar det har noe med prosessoren å gjøre.

 

Tror jeg kjørte dump-filen riktig:

 

 

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\Windows\MEMORY.DMP]

Kernel Summary Dump File: Only kernel address space is available

 

Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432

Machine Name:

Kernel base = 0xfffff800`02246000 PsLoadedModuleList = 0xfffff800`0240add0

Debug session time: Thu Jun 2 12:31:19.588 2011 (UTC + 2:00)

System Uptime: 0 days 3:03:21.066

Loading Kernel Symbols

.........................................Unable to read NT module Base Name string at 009308b8`009309c8 - NTSTATUS 0xC0000141

Missing image name, possible paged-out or corrupt data.

.Unable to read KLDR_DATA_TABLE_ENTRY at 00930ba0`00930b20 - NTSTATUS 0xC0000141

 

Loading unloaded module list

..................................................

WARNING: .reload failed, module list may be incomplete

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 101, {61, 0, fffffa60005ec180, 1}

 

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: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: fffffa60005ec180, The PRCB address of the hung processor.

Arg4: 0000000000000001, 0.

 

Debugging Details:

------------------

 

 

OVERLAPPED_MODULE: Address regions for '_________________' and 'Unknown_Module_fa800459`bd1004c0' overlap

 

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_2_PROC

 

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

 

CURRENT_IRQL: d

 

STACK_TEXT:

fffffa60`052a66d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx

 

 

STACK_COMMAND: kb

 

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

 

FOLLOWUP_NAME: MachineOwner

 

MODULE_NAME: Unknown_Module

 

IMAGE_NAME: Unknown_Image

 

DEBUG_FLR_IMAGE_TIMESTAMP: 0

 

BUCKET_ID: ZEROED_STACK

 

Followup: MachineOwner

 

 

Noen forslag til hva som kan gjørs for å fikse problemet?

Lenke til kommentar

Opprett en konto eller logg inn for å kommentere

Du må være et medlem for å kunne skrive en kommentar

Opprett konto

Det er enkelt å melde seg inn for å starte en ny konto!

Start en konto

Logg inn

Har du allerede en konto? Logg inn her.

Logg inn nå
×
×
  • Opprett ny...