Neue Cpu Immer wieder Bluescrren....

Hallo,
Ich habe mir bei ebay eine Cpu ersteigert in der Beschreibung stand Guter Zustand. Also gehe ich davon aus das die CPU in Ordnung ist.
Mein System
Motherboard: Elitegroup GeForce6100PM-M2 (V2.0)
CPU Alt: AMD x2 3800+
CPU Neu: AMD x4 9600 wird laut herstellerseite auch unterstützt
RAM: 2x 1 GB
HDD 500GB + 160 GB beide Sata
NT: 550 W Noname
Grafikkarte: Geforce GT 240

W 7 Enterprise

Also zum Problem wenn ich die *Neue* CPU einbaue fährt der Rechner hoch und es kommt in unregelmäßigen Abständen ein Bluescreen. Ich habe das Gefühl das der Bluecreen erst kommt wenn der rechner zur ruhe kommt habe 15 min nen BD Film laufen lassen ohne Probs kaum hat ich den Player zu BS ... 15 Min BF BC 2 gezockt ohne probleme. Ich bin jetzt nicht so der PC Freak kriege aber doch eigentlich immer alles hin nur bei diesem Problem scheitere ich grad. Mit dem x2 läuft der Rechner ohne Probleme. Ich gehe also davon aus das entweder irgendwas falsch eingestellt ist oder die CPU doch im hintern ist....

Hier noch der Bluescreen:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) 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 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e4f000 PsLoadedModuleList = 0xfffff800`0308ce50
Debug session time: Sun Oct 17 10:04:51.429 2010 (UTC + 2:00)
System Uptime: 0 days 0:06:21.380
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols

Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88002f63180, 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: fffff88002f63180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT: 
fffff880`009a9768 fffff800`02e6d453 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : nt!KeBugCheckEx
fffff880`009a9770 fffff800`02ec7de7 : fffffa80`00000000 fffff800`00000002 00000000`000186a0 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`009a9800 fffff800`02e10895 : fffff800`02e35460 fffff880`009a99b0 fffff800`02e35460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`009a9900 fffff800`02ebbc33 : 00000000`3a7f722d fffff800`03039e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`009a9930 fffff800`02ef4da1 : 43f00000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`009a9ac0 fffff800`02ecd63c : 00000000`00000000 fffff6fc`40004308 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x79
fffff880`009a9b00 fffff800`02f06b79 : fffff6fc`40004308 00000000`00000034 fffff800`03039e80 00000000`00000100 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`009a9bd0 fffff800`02f0674f : ffffffff`ffffffff 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
fffff880`009a9c10 fffff800`03163c06 : fffffa80`018c9b60 00000000`00000080 fffffa80`018c9040 fffff800`02e9dc19 : nt!MmZeroPageThread+0x7da
fffff880`009a9d40 fffff800`02e9dc26 : fffff800`03039e80 fffffa80`018c9b60 fffff800`03047c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


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

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: fffff88002f63180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT: 
fffff880`009a9768 fffff800`02e6d453 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : nt!KeBugCheckEx
fffff880`009a9770 fffff800`02ec7de7 : fffffa80`00000000 fffff800`00000002 00000000`000186a0 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`009a9800 fffff800`02e10895 : fffff800`02e35460 fffff880`009a99b0 fffff800`02e35460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`009a9900 fffff800`02ebbc33 : 00000000`3a7f722d fffff800`03039e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`009a9930 fffff800`02ef4da1 : 43f00000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`009a9ac0 fffff800`02ecd63c : 00000000`00000000 fffff6fc`40004308 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x79
fffff880`009a9b00 fffff800`02f06b79 : fffff6fc`40004308 00000000`00000034 fffff800`03039e80 00000000`00000100 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`009a9bd0 fffff800`02f0674f : ffffffff`ffffffff 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
fffff880`009a9c10 fffff800`03163c06 : fffffa80`018c9b60 00000000`00000080 fffffa80`018c9040 fffff800`02e9dc19 : nt!MmZeroPageThread+0x7da
fffff880`009a9d40 fffff800`02e9dc26 : fffff800`03039e80 fffffa80`018c9b60 fffff800`03047c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


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

0: kd> !analyse -v
No export analyse found
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: fffff88002f63180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

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


BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  d

STACK_TEXT: 
fffff880`009a9768 fffff800`02e6d453 : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`02f63180 : nt!KeBugCheckEx
fffff880`009a9770 fffff800`02ec7de7 : fffffa80`00000000 fffff800`00000002 00000000`000186a0 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4dfe
fffff880`009a9800 fffff800`02e10895 : fffff800`02e35460 fffff880`009a99b0 fffff800`02e35460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`009a9900 fffff800`02ebbc33 : 00000000`3a7f722d fffff800`03039e80 00000000`00000000 00000000`00000000 : hal!HalpHpetClockInterrupt+0x8d
fffff880`009a9930 fffff800`02ef4da1 : 43f00000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`009a9ac0 fffff800`02ecd63c : 00000000`00000000 fffff6fc`40004308 00000000`00000000 00000000`00000000 : nt!KxFlushEntireTb+0x79
fffff880`009a9b00 fffff800`02f06b79 : fffff6fc`40004308 00000000`00000034 fffff800`03039e80 00000000`00000100 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`009a9bd0 fffff800`02f0674f : ffffffff`ffffffff 00000000`000000ff 00000000`00000000 00000000`00000000 : nt!MiZeroPageChain+0x14e
fffff880`009a9c10 fffff800`03163c06 : fffffa80`018c9b60 00000000`00000080 fffffa80`018c9040 fffff800`02e9dc19 : nt!MmZeroPageThread+0x7da
fffff880`009a9d40 fffff800`02e9dc26 : fffff800`03039e80 fffffa80`018c9b60 fffff800`03047c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9d80 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a99b0 00000000`00000000 : nt!KxStartSystemThread+0x16


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

Ich bin für jede Hilfe dankbar und hab google schon ohne ende gequält...