Hallo...
Ich meld mich auch mal wieder Urlaubszeit ist nun ja endlich vorbei...
Also mal zurück zu meinem Problem mit der Festplatte.
Ich hab es dank TestDisk geschafft meine ganzen Daten zu retten echt ein geiles Programm...
Nun sieht es wie folgt aus
Habe zwei neue Platten drin
eine Samsung HD103SJ und eine Samsung 502HJ
hab soweit alles im System wiederhergestellt...
lief ne Weile super aber es geht wieder los mit den abstürzen
WinDbg sagt:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff68000022f98, dc30000027b96867, fffff680000598d8}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3a2 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000022f98
Arg3: dc30000027b96867
Arg4: fffff680000598d8
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_403
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: chrome.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002f4a6c8 to fffff80002ed8740
STACK_TEXT:
fffff880`0a0c3328 fffff800`02f4a6c8 : 00000000`0000001a 00000000`00000403 fffff680`00022f98 dc300000`27b96867 : nt!KeBugCheckEx
fffff880`0a0c3330 fffff800`02f09381 : 00000000`00000000 fffff680`00022ff8 fffffa80`09a853f0 e5500000`298c2867 : nt! ?? ::FNODOBFM::`string'+0x31ef2
fffff880`0a0c34e0 fffff800`02f0bdf9 : fffffa80`00000000 00000000`04badfff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x408
fffff880`0a0c36a0 fffff800`031f11d0 : fffffa80`091b1160 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0a0c37c0 fffff800`031f15db : fffff900`00000000 00000000`044a0000 fffffa80`00000001 fffff900`c306fc00 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0a0c3880 fffff800`02ed7993 : 00001a35`0a0c3990 00000000`00000020 fffffa80`09a853f0 00000000`00000000 : nt!NtUnmapViewOfSection+0x5f
fffff880`0a0c38d0 fffff800`02ed3f30 : fffff960`001751b2 00000000`00000001 00000000`00000000 fffff900`c306fcd0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0a0c3a68 fffff960`001751b2 : 00000000`00000001 00000000`00000000 fffff900`c306fcd0 00000000`00000000 : nt!KiServiceLinkage
fffff880`0a0c3a70 fffff960`00175534 : ffffffff`00000000 fffff880`00000000 fffff900`c306fcd0 fffff800`00000000 : win32k!SURFACE::bDeleteSurface+0x3a2
fffff880`0a0c3bc0 fffff960`00136645 : ffffffff`db051a35 fffff900`c306fcd0 00000000`00001a35 fffff800`02f22113 : win32k!bDeleteSurface+0x34
fffff880`0a0c3bf0 fffff800`02ed7993 : fffffa80`099f2b60 fffff880`0a0c3c01 fffffa80`0779c180 00000000`ffffffff : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`0a0c3c20 00000000`735b2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0022eb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x735b2dd9
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!SURFACE::bDeleteSurface+3a2
fffff960`001751b2 e9d6010000 jmp win32k!SURFACE::bDeleteSurface+0x57d (fffff960`0017538d)
SYMBOL_STACK_INDEX: 8
SYMBOL_NAME: win32k!SURFACE::bDeleteSurface+3a2
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c483f
FAILURE_BUCKET_ID: X64_0x1a_403_win32k!SURFACE::bDeleteSurface+3a2
BUCKET_ID: X64_0x1a_403_win32k!SURFACE::bDeleteSurface+3a2
Followup: MachineOwner
---------
irgendwie MEMORY MANAGEMENT....
mh ich häng nochmal was von den Einstellungen an
vielleicht bekommen wir das ja mal in den Griff
Achja im BIOS habe ich die DRAM Voltage auf 1,660 V eingestellt..
Liebe Grüße