Bluescreens nicht auswertbar - brauche Hilfe

[Teutonnen]

Servus, in letzter Zeit habe ich sehr gehäuft Bluescreens (alleine heute 6 und ich hab Windows erst frisch installiert...) - leider kann ich weder über osronline.com noch über windbg.exe irgendwelche brauchbaren Informationen herausholen. Beide meinen immer, dass die Kernel-Symbole falsch seien.

Ich bin bei windbg.exe nach dieser Anleitung hier vorgegangen:
http://extreme.pcgameshardware.de/k...-bluescreen-wie-jetzt-weiter.html#post1595813

-> SDK heruntergeladen, das Debug-Tool installiert und die x64-Version gestartet (ich benutze Windows 7 Home Premium 64 bit)
-> auf Files/Symbol File Path den Link kopiert (SRV*C:\symbols*http://msdl.microsoft.com/download/symbols)
-> .dmp via Open Crash dump geladen
-> !analyze -v in der Kommandozeile eingegeben, noch einmal Enter gedrückt. Dann werkelt er ein paar Sekunden und spuckt noch einmal genau das Gleiche aus.


Die Internetseite spuckt die genau gleichen Zeilen aus, das hilft mir also auch nicht weiter...

Spoiler

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


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

Symbol search path is: C:\symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02c1c000 PsLoadedModuleList = 0xfffff800`02e5f6d0
Debug session time: Sun Oct 13 00:03:25.136 2013 (UTC + 2:00)
System Uptime: 0 days 4:48:12.964
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+75b90 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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 ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

MODULE_NAME: nt

FAULTING_MODULE: fffff80002c1c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 521ea035

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x1E

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002c895be to fffff80002c91b90

STACK_TEXT:
fffff880`0331a928 fffff800`02c895be : fffffa80`07c30000 fffffa80`01b60800 fffff880`0331b0a0 fffff800`02cbca90 : nt+0x75b90
fffff880`0331a930 fffffa80`07c30000 : fffffa80`01b60800 fffff880`0331b0a0 fffff800`02cbca90 00000000`00000000 : nt+0x6d5be
fffff880`0331a938 fffffa80`01b60800 : fffff880`0331b0a0 fffff800`02cbca90 00000000`00000000 fffff800`02cbc75d : 0xfffffa80`07c30000
fffff880`0331a940 fffff880`0331b0a0 : fffff800`02cbca90 00000000`00000000 fffff800`02cbc75d fffff800`02ea03e0 : 0xfffffa80`01b60800
fffff880`0331a948 fffff800`02cbca90 : 00000000`00000000 fffff800`02cbc75d fffff800`02ea03e0 fffff800`02de10c4 : 0xfffff880`0331b0a0
fffff880`0331a950 00000000`00000000 : fffff800`02cbc75d fffff800`02ea03e0 fffff800`02de10c4 fffff800`02c1c000 : nt+0xa0a90


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+75b90
fffff800`02c91b90 4883ec28 sub rsp,28h

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+75b90

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

Vielleicht könnte mir jemand helfen und die minidumps untersuchen, ich hab sie mal in einem Zip-Ordner hier angehängt.

MfG
Teutonnen

 

[Smil0r]

Hast du denn irgendwas verändert seid dem die Probleme bestehen?
Mal Windows Ereignisanzeige unter Kritisch nachgeschaut was da so steht?

 

[Teutonnen]

Hier mal ein Auszug aus der Ereignisanzeige:


-> Ist immer das Gleiche, ich finde den Fehler einfach nicht.



Hmm.. Ich hab die alte gtx 570 mal kurz eingebaut gehabt, der Käufer wollte ein Video haben, dass sie noch geht. Das war aber noch auf dem alten Windows, das hab ich wie gesagt heute neu aufgesetzt und da sind keine Treiberleichen oder ähnliches drauf.

Ansonsten nur ne 250gb SSD und neuen RAM eingebaut, wobei ich beim RAM beide Riegel je ca. 10 Stunden durch Memtest gejagt habe und die anscheinend in Ordnung sind.

Die CPU hat diese Programme hier stabil und jeweils unter 70°C mitgemacht:
Prime95 Custom FFT 960k - 8 Stunden
Prime95 smallFFTs - 8 Stunden
Intel Burn Test (mit Default-Einstellungen) - 5 Stunden

Die Grafikkarten haben je etwa 20 Durchläufe Heaven und Valley hinter sich.

Zudem spiele ich fast täglich BF3, BFBC2, Far Cry 3, Rome 2 oder LoL.

Die 250gb SSD ist auch nicht die Systemplatte, von daher schliesse ich die auch mal aus - da sollte eigentlich nur die jeweilige Anwendung crashen.




UPDATE:
-> Hab mal nen anderen LAN-Treiber installiert, mal schauen, ob der was bringt.

Ich finde die originale Treiber-CD leider ums Verrecken nicht mehr, mit den Treibern ist er über ein Jahr lang wunderbar gelaufen und ich Depp verlier die CD

 

[Angelo-K]

Da gibts n programm namens bluescreenviewer, mit dem kann man minidumps auslesen...

 

[Smil0r]

Ein Software Problem scheint es nicht zu sein. Ich würde auf Netzteil Probleme tippen.
Hast du vielleicht ein anderes Netzteil zum testen? Ansonsten schau dir mal das Mainboard genau an.

 

[Teutonnen]

@Angelo-K
Kannte ich nicht, aber hier mal der entsprechende Screen:

 

[Smil0r]

Also ich halt da ja nichts von. Man sollte vielleicht eher systematisch jede Komponente überprüfen.
Deswegen Versuche eher mal die Festplatte auf Fehler zu überprüfen.
Z.b. Mit HDTach.
Hab dir ja schon in meinem vorherigen Post geschrieben woran es auch liegen kann.

 

[Teutonnen]

Ein anderes NT hatte ich schon da, ja. Be Quiet Dark Power Pro 1200W, halt das Testgerät vom Laden, in dem ich manchmal aushelfe.
Den Rest schau ich mir mal an.

 

[Smil0r]

Bin nicht sicher ob das Netzteil von der Leistung her reicht....

 

[Teutonnen]

kA, ist wohl einfach pauschal das Testgerät für alles xD


€: Ich probier's einfach mal mit einem Cmos Reset, vielleicht hat das Mobo-BIOS ja ne Macke. Kann ich da den Rest der Hardware einfach angeschlossen lassen oder soll ich alles komplett entfernen?

 

[Smil0r]

Warum solltest du? Wüsste nicht was passieren sollte.

 

[Teutonnen]

Keine Ahnung - vielleicht, weil ich im Moment keine 500.- übrig habe und fragen billiger ist, als neu zu kaufen^^
Eine Graka muss ich sowieso ausbauen, sonst komme ich nicht an die Batterie ran.

 

[Smil0r]

Ich hab extra für sowas eine kleine Taste beim o.c. Muss ich da manchmal ran. Ich Klemm nie was ab. Aber ok das ist auch wieder kein komplettes CMOS reset

 

[Teutonnen]

Naja, die Batterie muss ich aber schon rausnehmen, oder? xD

-> Batterie raus, warten, bis kein Strom mehr auf dem Mobo ist, Jumper umstecken, 30 Sekunden drauf lassen, wieder zurück und dann müsste alles auf Default sein, wenn ich das richtig im Kopf habe.

 

[Smil0r]

Paar mal power knopf drücken. Dadurch beschleunigst du das Saft auspressen. Netzkabel vorher trennen

 

[Teutonnen]

Ok, dann probier ich das gleich mal.
€ Eigentlich könnten wir das per PM machen, aber hey... So gibt's Posts dazu xD

 

[Smil0r]

Ich wieso?
Vielleicht weis ja jemand anderes noch was was uns nicht einfällt

 

[Teutonnen]

Bin gerade die ganzen BIOS-Settings am rausschreiben, das ist ja nachher (wenns funktioniert) alles back to default.

 

[derGronf]

Hallo Teutonnen,

es kann auch durchaus vorkommen, das bei der Installation von Windoof was schief gelaufen ist. Ich installier an der Stelle gerne Windoof neu mal neu. Bevor ich Stunden auf die Fehlersuche gehe, lieber 30 Minuten Windoof neu machen.

Im Grunde habt ihr ja sonst alles abgearbeitet, was man tun könnte. Ich lgaube auch nicht, dass dein Bios irgendwas damit zu tun hat. Aber vielleciht hilft es. Und abstecken oder so muss du nicht. Und eigentlich reiht Jumper umstecken. Nur wenn du Panik schiebst, musst du auch die Batterie rausmachen. Hab ich allerdings schon seit Jahren nicht mehr gesehn.

derGronf

 

[Teutonnen]

Naja, ich hab dieses Jahr eine Augen-OP (ca. 10k €) anstehen, ich muss sparen wo es nur geht.

-> Da frage ich lieber bei jedem Scheiss 2x nach, kostet ja nix xD

Windows habe ich übrigens schon 2x neu installiert, mit dem neuen LAN-Treiber scheinen die Bluescreens jedenfalls weniger geworden zu sein (gestern von 13:00 bis 0:50 6 Stück, heute den ganzen Tag erst 1 und irgendwie auf einmal 1.7MB/s Download anstatt 1.2 )