Hallöchen

Habe folgendes Problem mein OS Vista x64 stürzt öfters unerwartet ab, dabei ist es egal welche Anwendungen laufen oder nicht ist also kein Softwareproblem. Ich habe auch Prime95 24h laufen lassen können und es gab absolut keine Probleme oder Bluescreens. Auch Memtest86 fand keine Fehler. Ich bin wirklich am verzweifeln. Ich habe mir die dump file mal angeschaut und auch schon gegoogelt aber bezieht sich leider alles nur auf xp und hilft mir daher nicht weiter...

Zu meinem System:
Intel i7
DDR3 Ram Nanya 1333MHZ
ATI HD 4870

In der Dump file steht problem caused by hardware, leider kann ich damit nicht viel anfangen vllt. könnt Ihr mehr herauslesen. Ich bin über jede Hilfe sehr dankbar. Danke schonmal im Voraus


Jetzt die dmp. file:



Microsoft (R) Windows Debugger Version 6.11.0001.402 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini030109-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`01e4e000 PsLoadedModuleList = 0xfffff800`02013db0
Debug session time: Sun Mar 1 13:21:37.144 2009 (GMT+1)
System Uptime: 0 days 1:31:08.101
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
...................
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008932030, be000000, 800400}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : hardware

Followup: MachineOwner
---------

Du mußt zunächst einen symbol-path setzen, sonst funktioniert das Debuggen nicht.
Use the Microsoft Symbol Server to obtain debug symbol files

Alternative: Dump hochladen und den Link hier posten

Zitat von cad

Alternative: Dump hochladen und den Link hier posten

http://uploaded.to/?id=7frb1x

habs leider mit dem debuggen nicht hinbekommen. Hoffe Ihr könnt weiterhelfen. Danke schonmal

Motherboardtreiber aktuell?

http://downloadcenter.intel.com/Product_Search.aspx?Prod_nm=Intel+i7&x=28&y=7〈=deu&MissingSearchTxt=Bitte+geben+Sie+einen+g%C3%BCltigen+Produktnamen%2C+Dateinnamen+oder+eine+Produkt-ID-Nr.+ein.

Alle Windows Updates auch?

Kennst Du Dich im Bios aus, bzw. traust Dir zu, da etwas zu ändern?

Übertaktet?

Mehr Angaben zu Deiner Hardware wären auch nicht schlecht

Das dumpfile macht mich nicht schlauer. Ob's was bringt, weiß ich nicht:

Setze den symbol path unter: File - symbol path file
srv*%tmp%\dbg-symbols* http://msdl.microsoft.com/download/symbols

Lade dein dumpfile unter file - open crash dump

Gib am unteren Eingabepromt ein:
!sym noisy
!reload /f
!analyze -v

-> Mal kucken, ob was Sinnvolles dabei rauskommt.

Was sagt die Ereignisanzeige eigentlich? [Win-Taste]+r -> eventvwr.msc eingeben

Motherboard Treiber sind natürlich aktuell, auch das neueste BIOS ist aufgespielt. CPU ist minimal übertaktet auf 3,2 ghz aber ich geb ihm genügend saft ... die bluescreens treten auch ohne übertaktung (standart takt) auf. Klar kenn ich mich im Bios aus , ich hab den pc aktuell mit dem standart takt laufen.
Was heißt macht dich nicht schlauer =)? Ich kenn mich damit ja leider sogut wie gar nicht aus, was sollen diese "Befehle" bringen will nicht nur eintippen sondern auch wissen was ich mache . Kollege von mir meinte das Vista mit den 6GB Ram nicht zurecht kommt, zumindest bei der Installation und es deswegen fehler gibt?Aber hatte keine Fehler bei der Installation, die Rams hab ich ja 2 Stunden mit memtest überprüft 0fehler.

Hardware:
Asus P6T Deluxe
Core i7 @ 2.67ghz
ATI HD 4870 (Palit Vision 1GB RAM)
Ram Nanya 3x2 GB @ 1333MHZ. 9 9 9 24 Timings.
Western Digital 620GB
Lüfter ist ein Noctua drauf also zu heiß wirds der hardware auch nicht.

Habe gerade den Befehl in die Eingabepromt eingegeben, soll ich posten was dabei rauskommt? Ich glaub das sprengt den Rahmen

Poste mal, bin gespannt, ob Du die gleiche Auswertung hast wie ich

* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, MCA_ASSERT
Arg2: fffffa8008932030, Address of WHEA_ERROR_RECORD structure
Arg3: 00000000be000000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 0000000000800400, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error

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


WHEA_ERROR_RECORD: !errrec fffffa8008932030

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: SearchIndexer.e

CURRENT_IRQL: f

STACK_TEXT:
fffffa60`005f3958 fffff800`01e0f72a : 00000000`00000124 00000000`00000000 fffffa80`08932030 00000000`be000000 : nt!KeBugCheckEx
fffffa60`005f3960 fffff800`01f713c3 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalBugCheckSystem+0x12e
fffffa60`005f39d0 fffff800`01e0f097 : fffffa60`00000c3e fffffa60`005f3bb0 fffffa60`005f3c30 00000000`00000000 : nt!WheaReportHwError+0x243
fffffa60`005f3a30 fffff800`01ea25b1 : 00000000`00000058 fffffa60`005f3c30 00000000`0b472550 00000000`00000000 : hal!HalpMcaExceptionHandler+0xf3
fffffa60`005f3a70 fffff800`01ea23f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x71
fffffa60`005f3bb0 000007fe`f7b0fe5c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
00000000`0b6a91c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`f7b0fe5c


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel

BUCKET_ID: X64_0x124_GenuineIntel

Followup: MachineOwner

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

Teste die Ramspeicher bitte einzeln
C1E Support -> Was hast Du im Bios eingestellt?

Danke für die schnelle Antwort. Sehe da prime95.exe hab aber auch eine dump file da ist es dllhost.exe also wie gesagt kommt überhaupt nicht auf die anwendung an. Ram hab ich einzeln ausgetestet. 0 Fehler




*
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80089f9c6e, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.

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

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************

BUGCHECK_STR: 0x124_GenuineIntel

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: prime95.exe

CURRENT_IRQL: f

STACK_TEXT:
fffffa60`005f3958 fffff800`0233e72a : 00000000`00000124 00000000`00000000 fffffa80`089f9c6e 00000000`be000000 : nt!KeBugCheckEx
fffffa60`005f3960 fffff800`01f423c3 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000001 : hal!HalBugCheckSystem+0x12e
fffffa60`005f39d0 fffff800`0233e097 : fffffa60`00000c3e fffffa60`005f3bb0 fffffa60`005f3c30 00000000`00000000 : nt!WheaReportHwError+0x243
fffffa60`005f3a30 fffff800`01e735b1 : 00000000`105ed300 fffffa60`005f3c30 00000000`0c4dc760 00000000`00000000 : hal!HalpMcaExceptionHandler+0xf3
fffffa60`005f3a70 fffff800`01e733f5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x71
fffffa60`005f3bb0 00000000`0046a23b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0xf5
00000000`02af70f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x46a23b


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN

BUCKET_ID: X64_0x124_GenuineIntel__UNKNOWN

Followup: MachineOwner
---------

Shit, mehr sah ich auch nicht. Irgendwas in der Ereignisanzeige zu sehen? Vermutlich nicht. Daher bleibt dir vorerst nur eine defensive config, d.h. Abstöpseln und Deaktivieren was geht. Keine Übertaktung, minimalen RAM, usb-controller deaktivieren, audio..., video sofern onboard video vorhanden usw.

Sicher, dass du auschließlich 64bit kompatible Hardware und Software (v.a. Treiber) einsetzt?

Zitat von cad

Teste die Ramspeicher bitte einzeln
C1E Support -> Was hast Du im Bios eingestellt?

Nachtrag: 2 Stunden Memtest finde ich nicht aussagekräftig genug

@Dale

Ich bin wirklich neugierig, wo der Fehler liegt

Edit: Hast Du auf die Entmagnetisierung geachtet?

defensive config mit diesem "traum-pc" darf nicht wahr sein ich heul gleich ^^, ja verwende ausschließlich 64bit software extra neuste software etc. von asus seite runtergeladen nix gebracht. Was kannst du mir den noch empfehlem? Hat sonst noch irgendwer einen Tipp das System ist brandneu, "leider" selber zusammengebaut hab aber auf Hardware geachtet die gut zusammenarbeitet. Darf ja nicht wahr sein

sorry hab die frage ganz übersehen c1e support ist disabeld, hat mit stromsparen zutun bzw taktet ja die core runter, wer will schon weniger leistung ? Der Fehler trat aber auch mit c1e support enabled auf leider hab ja jetzt standard settings @ bios, und standarspannungen was mir gar nicht gefällt weil die auf auto viel zu hoch eingestellt sind... ich hab mich nach mehreren OC Foren orientiert und dem cpu auch genug vcore gegeben.
Als Beispiel:
i7 @ 3.5ghz , 167 MHZ x Multi 20 , Turbo on
1.27vcore dürften hier völlig ausreichen
den ram hab ich immer mit der vom hersteller vorgesehen Spannung betrieben also max 1.65
qpi core auf 1.3
cpu pll volt auf 1,88
... Aber wie gesagt auch mit dem Standard Settings krieg ich Bluescreens.

Ok werde heute über nacht mal memory testen aber ich schätze eher nicht das es daran liegt ihc lasse mich aber gerne eines besseren belehren.

Danke cad das du so neugierig dranbleibst

Naja, bei vista - erst recht vista64 - strecke ich die Waffen und ein debugging-Kenner bin ich auch nicht. Mit defensiv meine ich, du sollst erstmal mögliche Fehlerquellen ausschalten, sonst suchst du dir den Wolf. Ich frage jetzt zum letzten Mal nach der Ereignisanzeige. -> System /Warnungen, Fehler irgendwas?

Sofern msinfo32.exe bei dir funktioniert oder ein ähnlich lautender Befehl vorhanden ist (msinfo*.exe), führe den mal aus und suche nach Hardwarekonflikten/IRQ-Mehrfachbelegungen/Problemgeräten.

Die Treiber beziehst du besser vom Hersteller direkt. Oft sind sie aktueller, keinesfalls aber älter .

@cad: jo, aber meine Hoffnung ist gering