bluescreen nach "energie sparen"

so hallo,

naja, nach stand-by schmiert mir der PC mit einem Bluescreen ab.
Habe mir windebugging tool geholt, alles nach Anleitung gemacht und kopiere hier gleich mal den Text, den ich nach der Analyse bekommen habe (kann damit leider selber nichts anfangen).

In der Hoffung, dass mir jemand helfen kann,

Martin



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


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

Symbol search path is: SRV*c:\windows\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18327.amd64fre.vistasp2_gdr.101014-0432
Machine Name:
Kernel base = 0xfffff800`02857000 PsLoadedModuleList = 0xfffff800`02a1bdd0
Debug session time: Thu Aug 11 03:01:01.076 2011 (UTC + 2:00)
System Uptime: 1 days 0:00:25.479
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {7, 2aaad, 4, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+ae26 )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000007, A driver has unlocked a page more times than it locked it
Arg2: 000000000002aaad, page frame number
Arg3: 0000000000000004, current share count
Arg4: 0000000000000000, 0

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


BUGCHECK_STR: 0x4E_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: msiexec.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff8000290619d to fffff800028b1490

STACK_TEXT:
fffffa60`075f4f58 fffff800`0290619d : 00000000`0000004e 00000000`00000007 00000000`0002aaad 00000000`00000004 : nt!KeBugCheckEx
fffffa60`075f4f60 fffff800`028f1f01 : fffffa80`0412ee00 00000000`00000004 00000000`00000000 fffffa80`00800070 : nt! ?? ::FNODOBFM::`string'+0xae26
fffffa60`075f4fa0 fffff800`02aa0433 : fffffa80`05c1b4b0 fffffa80`00000000 fffffa80`00000000 00000000`0000003f : nt! ?? ::FNODOBFM::`string'+0x22390
fffffa60`075f50a0 fffffa60`013365d2 : 00000000`00000000 00000000`00000000 fffffa80`068ecc10 fffffa80`077eda50 : nt!MmPrefetchPages+0xef
fffffa60`075f50f0 fffffa60`01309794 : fffffa80`077eda50 fffffa60`075f5300 00000000`0000002c fffff880`0d6db000 : Ntfs!NtfsPrefetchFile+0x7a2
fffffa60`075f5220 fffffa60`012ee145 : fffffa80`077eda50 00000000`00000000 fffffa80`068ecc10 00000000`00000000 : Ntfs! ?? ::NNGAKEGL::`string'+0x14b1a
fffffa60`075f5260 fffffa60`00774e91 : 00000000`00000000 fffffa80`068ecc10 00000000`00000001 fffffa80`077eda50 : Ntfs!NtfsFsdFileSystemControl+0x145
fffffa60`075f5310 fffffa60`007916e2 : fffffa80`06103940 fffffa80`04f4abf0 fffffa80`06103900 fffffa60`075f5758 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x211
fffffa60`075f5380 fffff800`02b148ae : fffffa80`068ecf01 00000000`00001810 fffffa80`068ecfb0 fffffa80`06103900 : fltmgr!FltpFsControl+0x102
fffffa60`075f53e0 fffff800`02b2588a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x5be
fffffa60`075f5510 fffff800`02c50ef1 : fffff880`09cf9720 ffffffff`fffdb610 fffffa60`075f5678 fffff800`02c50cc1 : nt!NtFsControlFile+0x56
fffffa60`075f5580 fffff800`02c5136c : fffff880`116fe62e fffffa60`075f5750 00000000`00000009 fffffa60`075f5750 : nt!PfpPrefetchEntireDirectory+0x121
fffffa60`075f5630 fffff800`02c51577 : 00000000`00000000 fffff880`00000000 00000000`00000050 00000000`00000000 : nt!PfSnPrefetchMetadata+0x1cc
fffffa60`075f5730 fffff800`02c5199f : 00000b54`e6f0d0a2 fffffa80`073c6c10 fffff880`116f2000 00000000`00000000 : nt!PfSnPrefetchScenario+0x137
fffffa60`075f5990 fffff800`02b82201 : 00000000`00000000 00000000`f3744dfd fffffa80`05442b80 00000000`00000000 : nt!PfSnBeginAppLaunch+0x35f
fffffa60`075f5a60 fffff800`02b3b851 : fffffa80`04e00860 fffffa80`05442b80 fffff880`00000002 fffffa60`14050800 : nt! ?? ::NNGAKEGL::`string'+0x40e20
fffffa60`075f5a90 fffff800`028ee77a : fffffa60`019d2180 00000000`77bd65f0 fffff800`02b3b74c fffffa80`04e00860 : nt!PspUserThreadStartup+0x105
fffffa60`075f5ae0 fffff800`028ee6ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16
fffffa60`075f5c20 00000000`77bd65f0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn
00000000`0019f828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77bd65f0


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+ae26
fffff800`0290619d cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+ae26

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4cb7275f

FAILURE_BUCKET_ID: X64_0x4E_7_nt!_??_::FNODOBFM::_string_+ae26

BUCKET_ID: X64_0x4E_7_nt!_??_::FNODOBFM::_string_+ae26

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

Im Stack Verlauf sind Probleme mit dem Dateisystem und dem Filtermanger erkennbar.

-ansonsten läuft das System fehlerfrei?
-ist es immer der gleiche Stopfehler, der beim Bluescreen angezeigt wird (in diesem Fall der Stop 0x4E Fehler)?
-Installiere den aktuellsten Grafikkarten- und Chipsatztreiber
-Führe eine Checkdisk-Prüfung durch (Eingabeaufforderung als Admin starten "chkdsk /f /r" eingeben (ohne "").
-Was für eine Viren- u. Firewallsoftware nutzt du?
-Was für Hardware steckt in deinem System?

-ansonsten läuft das System fehlerfrei?
Eigentlich schon. Habe manchmal Spielabstürtze, aber sonst nichts.

-ist es immer der gleiche Stopfehler, der beim Bluescreen angezeigt wird (in diesem Fall der Stop 0x4E Fehler)?
Nein, hab verschiedene. Habe aber mehrmals Memoryfehler; werde daher die Tage mal Memtest86 über Nacht laufen lassen, vielleicht ist ja ein Riegel futsch oder beide.

-Installiere den aktuellsten Grafikkarten- und Chipsatztreiber
Habe ich immer.

-Führe eine Checkdisk-Prüfung durch (Eingabeaufforderung als Admin starten "chkdsk /f /r" eingeben (ohne "").
Gestern gemacht. Bei Step 5 wurden paar Sachen geändert. Gibt es da vielleicht ein Log? (war zum Schluss außer Haus und habe es deshalb nicht aufschreiben können)

-Was für eine Viren- u. Firewallsoftware nutzt du?
Avira Personal, Malwares' Anti Malware

-Was für Hardware steckt in deinem System?
Intel Core 2 Quad Q6600 @ 2.40
Gigabyte GA-EP43-DS3L
2 mal 2 GB DDR2 SDRAM
ATI Radeaon HD 4800 1024 GB von Sapphire
Samsung HD502IJ ATA 500 GB
HL-DT-ST DVDRAM
onboard Sound und Netzwerk

Nein, hab verschiedene. Habe aber mehrmals Memoryfehler; werde daher die Tage mal Memtest86 über Nacht laufen lassen, vielleicht ist ja ein Riegel futsch oder beide.

Zum Vergrößern anklicken....

Das würde ich auch machen.

Den Chkdsk Log findest du z.B. in der Ereignisanzeige: Windows Logs -> Anwendungen -> "Wininit"

Hier hab ich mal das log von chkdsk:

Protokollname: Application
Quelle: Microsoft-Windows-Wininit
Datum: 14.09.2011 17:18:39
Ereignis-ID: 1001
Aufgabenkategorie:Keine
Ebene: Informationen
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: Martin-PC
Beschreibung:


Checking file system on C:
The type of the file system is NTFS.
Volume label is Lokaler Datenträger.

A disk check has been scheduled.
Windows will now check the disk.
303168 file records processed.

1749 large file records processed.

0 bad file records processed.

2 EA records processed.

57 reparse records processed.

388766 index entries processed.

0 unindexed files processed.

303168 security descriptors processed.

Cleaning up 1702 unused index entries from index $SII of file 0x9.
Cleaning up 1702 unused index entries from index $SDH of file 0x9.
Cleaning up 1702 unused security descriptors.
42800 data files processed.

CHKDSK is verifying Usn Journal...
37422760 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x3a742b5000 for 0x5000 bytes.
Read failure with status 0xc000009c at offset 0x3a742b8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a742b9000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a742b9000 for 0x1000 bytes.
Windows replaced bad clusters in file 31198
of name \Windows\winsxs\AM7B2D~1.180\avcstrm.sys.
Read failure with status 0xc000009c at offset 0x3a74435000 for 0x5000 bytes.
Read failure with status 0xc000009c at offset 0x3a74438000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a74439000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a74439000 for 0x1000 bytes.
Windows replaced bad clusters in file 31391
of name \Windows\System32\DRIVER~1\FILERE~1\CXFALP~1.INF\CPNOTI~1.AX.
Read failure with status 0xc000009c at offset 0x3a742ba000 for 0x7000 bytes.
Read failure with status 0xc000009c at offset 0x3a742ba000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a742bb000 for 0x6000 bytes.
Read failure with status 0xc000009c at offset 0x3a742bb000 for 0x1000 bytes.
Windows replaced bad clusters in file 38885
of name \Windows\System32\DRIVER~1\FILERE~1\PRNOK0~1.INF\Amd64\OK1200X1.PPD.
303152 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
16132131 free clusters processed.

Free space verification is complete.
Adding 6 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

488382463 KB total disk space.
423315548 KB in 189101 files.
112884 KB in 42801 indexes.
24 KB in bad sectors.
425479 KB in use by the system.
65536 KB occupied by the log file.
64528528 KB available on disk.

4096 bytes in each allocation unit.
122095615 total allocation units on disk.
16132132 allocation units available on disk.

Internal Info:
40 a0 04 00 e9 89 03 00 86 79 06 00 00 00 00 00 @........y......
47 0b 00 00 39 00 00 00 00 00 00 00 00 00 00 00 G...9...........
30 c7 a1 77 00 00 00 00 50 23 c9 ff 00 00 00 00 0..w....P#......

Windows has finished checking your disk.
Please wait while your computer restarts.

Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-09-14T15:18:39.000Z" />
<EventRecordID>44000</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>Martin-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is Lokaler Datenträger.

A disk check has been scheduled.
Windows will now check the disk.
303168 file records processed.

1749 large file records processed.

0 bad file records processed.

2 EA records processed.

57 reparse records processed.

388766 index entries processed.

0 unindexed files processed.

303168 security descriptors processed.

Cleaning up 1702 unused index entries from index $SII of file 0x9.
Cleaning up 1702 unused index entries from index $SDH of file 0x9.
Cleaning up 1702 unused security descriptors.
42800 data files processed.

CHKDSK is verifying Usn Journal...
37422760 USN bytes processed.

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0x3a742b5000 for 0x5000 bytes.
Read failure with status 0xc000009c at offset 0x3a742b8000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a742b9000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a742b9000 for 0x1000 bytes.
Windows replaced bad clusters in file 31198
of name \Windows\winsxs\AM7B2D~1.180\avcstrm.sys.
Read failure with status 0xc000009c at offset 0x3a74435000 for 0x5000 bytes.
Read failure with status 0xc000009c at offset 0x3a74438000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a74439000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a74439000 for 0x1000 bytes.
Windows replaced bad clusters in file 31391
of name \Windows\System32\DRIVER~1\FILERE~1\CXFALP~1.INF\CPNOTI~1.AX.
Read failure with status 0xc000009c at offset 0x3a742ba000 for 0x7000 bytes.
Read failure with status 0xc000009c at offset 0x3a742ba000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0x3a742bb000 for 0x6000 bytes.
Read failure with status 0xc000009c at offset 0x3a742bb000 for 0x1000 bytes.
Windows replaced bad clusters in file 38885
of name \Windows\System32\DRIVER~1\FILERE~1\PRNOK0~1.INF\Amd64\OK1200X1.PPD.
303152 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
16132131 free clusters processed.

Free space verification is complete.
Adding 6 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

488382463 KB total disk space.
423315548 KB in 189101 files.
112884 KB in 42801 indexes.
24 KB in bad sectors.
425479 KB in use by the system.
65536 KB occupied by the log file.
64528528 KB available on disk.

4096 bytes in each allocation unit.
122095615 total allocation units on disk.
16132132 allocation units available on disk.

Internal Info:
40 a0 04 00 e9 89 03 00 86 79 06 00 00 00 00 00 @........y......
47 0b 00 00 39 00 00 00 00 00 00 00 00 00 00 00 G...9...........
30 c7 a1 77 00 00 00 00 50 23 c9 ff 00 00 00 00 0..w....P#......

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

Adding 6 bad clusters to the Bad Clusters File.
...
24 KB in bad sectors

Zum Vergrößern anklicken....

Checkdisk hat hier defekte Sektoren gefunden.

Poste bitte noch ein Screenshots von CrystalDiskInfo: http://crystalmark.info/software/CrystalDiskInfo/index-e.html

So, hier der Screenshot

Ähm, ich hoffe, dass es diemal funtioniert.

Die Festplatte macht nicht mehr den besten Eindruck. Das "Vorsicht" bezieht sich zwar "nur" auf die aktuell schwebenden Sektoren, allerdings sind auch weitere Lesefehler verzeichnet. Dies könnte auf Oberflächenprobleme hindeuten.

Hättest du eine andere Festplatte, die Ersatzweise eingebaut werden könnte?