Jede Menge Bluescreens

[Chaoswave]

AW: Bluescreen + SMART error

Mir ist grad mal wieder... das Windoof abgeschmiert. Mit Bluescreeen in dem stand hauptsächlich:

The system was shutdown to prevent damage blablabla

der ZahlenCode der immer dabei ist bestand nur aus 0en.

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


EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.

FAULTING_IP: 
+6530373163336634
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

EXCEPTION_RECORD:  fffff8800338ba68 -- (.exr 0xfffff8800338ba68)
ExceptionAddress: fffff800032912c1 (nt!PoIdle+0x00000000000005b1)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME:  fffff8800338bb10 -- (.trap 0xfffff8800338bb10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000006f68c9307 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80051a9ba8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032912c1 rsp=fffff8800338bca0 rbp=0000000000000000
 r8=0000000000000000  r9=00000006726bec71 r10=0000000000005419
r11=fffff88003363100 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!PoIdle+0x5b1:
fffff800`032912c1 ff15198f1200    call    qword ptr [nt!_imp_KeQueryPerformanceCounter (fffff800`033ba1e0)] ds:1aa9:fffff800`033ba1e0=00000000005a28e6
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000327b46e to fffff80003283710

STACK_TEXT:  
fffff880`0338ab58 fffff800`0327b46e : 00000000`00000000 fffff880`0338ae88 fffff880`0338b2d0 fffff800`032b0668 : nt!KeBugCheck
fffff880`0338ab60 fffff800`032a940d : fffff800`03491edc fffff800`033cadac fffff800`03213000 fffff880`0338ba68 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`0338ab90 fffff800`032b0a90 : fffff800`033d2b14 fffff880`0338ac08 fffff880`0338ba68 fffff800`03213000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`0338abc0 fffff800`032bd9ef : fffff880`0338ba68 fffff880`0338b2d0 fffff880`00000000 00000000`00000001 : nt!RtlDispatchException+0x410
fffff880`0338b2a0 fffff800`03282d82 : fffff880`0338ba68 00000000`00000000 fffff880`0338bb10 fffff880`03363180 : nt!KiDispatchException+0x16f
fffff880`0338b930 fffff800`0328168a : fffff880`03363180 00000000`00000001 fffff880`0338bb78 00001f80`000000a0 : nt!KiExceptionDispatch+0xc2
fffff880`0338bb10 fffff800`032912c1 : 00000000`0037134f fffffa80`051a80a8 fffff880`0336dfc0 00000000`00000001 : nt!KiGeneralProtectionFault+0x10a
fffff880`0338bca0 fffff800`0328bebc : fffff880`03363180 fffff880`00000000 00000000`00000000 fffffa80`04f270f0 : nt!PoIdle+0x5b1
fffff880`0338bd80 00000000`00000000 : fffff880`0338c000 fffff880`03386000 fffff880`0338bd40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`0327b46e 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e

Followup: MachineOwner

 

[Chaoswave]

AW: Bluescreen + SMART error

neuer Bluescreen

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006cf00da, The address that the exception occurred at
Arg3: fffff8800a077a18, Exception Record Address
Arg4: fffff8800a077280, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP: 
RTKVHD64+950da
fffff880`06cf00da 8b18            mov     ebx,dword ptr [rax]

EXCEPTION_RECORD:  fffff8800a077a18 -- (.exr 0xfffff8800a077a18)
ExceptionAddress: fffff88006cf00da (RTKVHD64+0x00000000000950da)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT:  fffff8800a077280 -- (.cxr 0xfffff8800a077280)
rax=0000000000000000 rbx=01cb55cb480e68c8 rcx=fffff88005ca8084
rdx=0000088200000000 rsi=fffffa80062be160 rdi=fffffa80062be160
rip=fffff88006cf00da rsp=fffff8800a077c50 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000371359 r10=000000000000678e
r11=fffffa8004c0e168 r12=0000000000000001 r13=0000000000000000
r14=fffff78000000014 r15=fffff880033d9f40
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
RTKVHD64+0x950da:
fffff880`06cf00da 8b18            mov     ebx,dword ptr [rax] ds:002b:00000000`00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  NULL_DEREFERENCE

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b00e0
 0000000000000000 

FOLLOWUP_IP: 
RTKVHD64+950da
fffff880`06cf00da 8b18            mov     ebx,dword ptr [rax]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000001674 to fffff88006cf00da

STACK_TEXT:  
fffff880`0a077c50 00000000`00001674 : 00000000`00000000 fffffa80`062be160 00000000`00000408 00000000`00080408 : RTKVHD64+0x950da
fffff880`0a077c58 00000000`00000000 : fffffa80`062be160 00000000`00000408 00000000`00080408 fffff880`08369416 : 0x1674


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  RTKVHD64+950da

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49756b63

STACK_COMMAND:  .cxr 0xfffff8800a077280 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_RTKVHD64+950da

BUCKET_ID:  X64_0x7E_RTKVHD64+950da

Followup: MachineOwner

hab jetzt mal im Bios mehr Saft fürn RAM gegeben und die SPD einstellungen genommen für die Latenzen...

 

[simpel1970]

AW: Bluescreen + SMART error

Beim letzten Absturz war der Realtec Audio Treiber die Ursache. Installiere mal den aktuellsten Treiber: Realtek HD Audio-Treiber Download - ComputerBase

 

[Chaoswave]

AW: Bluescreen + SMART error

okay danke
habs gemacht

Ich hab ne vermutung vor an die Bluescreens ohne richtige Fehler kommen. Das PCGH Downsampling ding ist schuld.... Hat mein Rechner irgendwie nicht so gerne 10sec nach dem start ratzt mir mein Windoof weg.
Ich vermute es liegt daran und an dem OC. MItlerweile bekomm ich nämlich nen Fehler nach 1sec linx und prime, vorher hatter der nach 12 std nicht mal nen Fehler. Hab das OC nun raus genommen und hoff das läuft jetzt.

 

[simpel1970]

AW: Bluescreen + SMART error

Ok. Dann teste mal ohne OC (hättest ruhig erwähnen können, dass dein Sys OC ist ... ich hätte aber auch danach fragen könnne ).

 

[Chaoswave]

AW: Bluescreen + SMART error

ich dachte das wär klar nach den CPUZ screens....

 

[simpel1970]

AW: Bluescreen + SMART error

Wo du Recht hast, hast du Recht...

 

[Chaoswave]

AW: Bluescreen + SMART error

sodele. neuigkeiten
in den letzen 2 tagen ist mir mein rechner ca 3x abgeschmiert. hauptsächlich bei installationen oder updates.
in der letzten haleb stunde dann direkt 3x.
einmal mittendrin ohne irgendwas, also war nur windows an, keine spiele oder sonst irgendwas. dann nach dem reboot sofort wieder weg, und dann grade als ich den beitrag zum ersten mal schreiben wollte direkt wieder weg -.-
anschlüsse hab ich grade nach dem letzten mal alle abgezogen und an andere aufm mb gehängt, strom sitzt auch...

woran liegt es?
oc ist raus. komplettes bios resettet, seit 3 tagen
das sind die von heute

Use !analyze -v to get detailed debugging information.

BugCheck 100000B8, {fffffa8005d3e570, fffff8800336efc0, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : snapman.sys ( snapman+18e71 )

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

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

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffffa8005d3e570, Original thread which is the cause of the failure
Arg2: fffff8800336efc0, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


FAULTING_THREAD:  fffffa8005d3e570

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xB8

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003292992 to fffff800032915da

STACK_TEXT:  
fffff880`03393630 fffff800`03292992 : fffff880`033d5180 fffffa80`05d3e570 fffffa80`00000000 fffffa80`05cf6f58 : nt!KiSwapContext+0x7a
fffff880`03393770 fffff800`03294cff : 00000000`00000000 fffff880`03364180 0000000f`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`03393800 fffff880`01dd0e71 : fffff880`01de3100 fffff880`00000000 00000000`00000000 fffffa80`049f2c00 : nt!KeWaitForSingleObject+0x19f
fffff880`033938a0 fffff880`01de3100 : fffff880`00000000 00000000`00000000 fffffa80`049f2c00 fffff880`03364180 : snapman+0x18e71
fffff880`033938a8 fffff880`00000000 : 00000000`00000000 fffffa80`049f2c00 fffff880`03364180 fffff880`01de3140 : snapman+0x2b100
fffff880`033938b0 00000000`00000000 : fffffa80`049f2c00 fffff880`03364180 fffff880`01de3140 fffffa80`04ae7bb8 : 0xfffff880`00000000


STACK_COMMAND:  .thread 0xfffffa8005d3e570 ; kb

FOLLOWUP_IP: 
snapman+18e71
fffff880`01dd0e71 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  snapman+18e71

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: snapman

IMAGE_NAME:  snapman.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45265d99

FAILURE_BUCKET_ID:  X64_0xB8_snapman+18e71

BUCKET_ID:  X64_0xB8_snapman+18e71

Followup: MachineOwner

Use !analyze -v to get detailed debugging information.

BugCheck 100000B8, {fffff880033dffc0, fffffa8005ea8540, 0, 0}

Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for snapman.sys
*** ERROR: Module load completed but symbols could not be loaded for snapman.sys
Probably caused by : snapman.sys ( snapman+18e71 )

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

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

ATTEMPTED_SWITCH_FROM_DPC (b8)
A wait operation, attach process, or yield was attempted from a DPC routine.
This is an illegal operation and the stack track will lead to the offending
code and original DPC routine.
Arguments:
Arg1: fffff880033dffc0, Original thread which is the cause of the failure
Arg2: fffffa8005ea8540, New thread
Arg3: 0000000000000000, Stack address of the original thread
Arg4: 0000000000000000

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


FAULTING_THREAD:  fffff880033dffc0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xB8

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003286992 to fffff800032855da

STACK_TEXT:  
fffff880`033fd400 fffff800`03286992 : fffffa80`060a1060 fffff800`037f2b7f fffffa80`05c3ff48 fffffa80`05c3ff58 : nt!KiSwapContext+0x7a
fffff880`033fd540 fffff800`03288cff : fffffa80`0499bd88 00000000`00000001 0000000f`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`033fd5d0 fffff880`01c18e71 : fffff880`01c2b100 fffff880`00000000 00000000`00000000 fffffa80`049f1c00 : nt!KeWaitForSingleObject+0x19f
fffff880`033fd670 fffff880`01c2b100 : fffff880`00000000 00000000`00000000 fffffa80`049f1c00 fffff880`033d5180 : snapman+0x18e71
fffff880`033fd678 fffff880`00000000 : 00000000`00000000 fffffa80`049f1c00 fffff880`033d5180 fffff880`01c2b140 : snapman+0x2b100
fffff880`033fd680 00000000`00000000 : fffffa80`049f1c00 fffff880`033d5180 fffff880`01c2b140 fffffa80`04ae3618 : 0xfffff880`00000000


STACK_COMMAND:  .thread 0xfffff880033dffc0 ; kb

FOLLOWUP_IP: 
snapman+18e71
fffff880`01c18e71 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  snapman+18e71

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: snapman

IMAGE_NAME:  snapman.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45265d99

FAILURE_BUCKET_ID:  X64_0xB8_snapman+18e71

BUCKET_ID:  X64_0xB8_snapman+18e71

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

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


EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.

FAULTING_IP: 
+6239646235323165
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000327d46e to fffff80003285710

STACK_TEXT:  
fffff880`033fa8e8 fffff800`0327d46e : fffffa80`03d8ffe4 00000000`00000000 fffff880`033fb0f0 fffff800`032b2668 : nt!KeBugCheck
fffff880`033fa8f0 fffff800`032ab40d : fffff800`03493b7c fffff800`033cde84 fffff800`03215000 fffff880`033fb050 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`033fa920 fffff800`032b2a90 : fffff800`033d4b14 fffff880`033fa998 fffff880`033fb050 fffff800`03215000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`033fa950 fffff800`032b406a : fffff880`033fb050 fffff880`033fb0f0 00001b4b`00000001 00001fff`00001fff : nt!RtlDispatchException+0x410
fffff880`033fb030 fffff800`0328e610 : fffffa80`05944010 fffff880`053c1376 0000000f`00000000 00000000`00000000 : nt!RtlRaiseStatus+0x4e
fffff880`033fb5d0 fffff880`01c19089 : 00000000`00000001 fffffa80`00000001 fffff880`033d3180 fffff880`01c2b100 : nt!KeReleaseMutant+0x260
fffff880`033fb680 00000000`00000001 : fffffa80`00000001 fffff880`033d3180 fffff880`01c2b100 fffffa80`04b018e8 : snapman+0x19089
fffff880`033fb688 fffffa80`00000001 : fffff880`033d3180 fffff880`01c2b100 fffffa80`04b018e8 fffff880`01c14767 : 0x1
fffff880`033fb690 fffff880`033d3180 : fffff880`01c2b100 fffffa80`04b018e8 fffff880`01c14767 ffffd8f0`00002710 : 0xfffffa80`00000001
fffff880`033fb698 fffff880`01c2b100 : fffffa80`04b018e8 fffff880`01c14767 ffffd8f0`00002710 fffffa80`04af47c0 : 0xfffff880`033d3180
fffff880`033fb6a0 fffffa80`04b018e8 : fffff880`01c14767 ffffd8f0`00002710 fffffa80`04af47c0 fffffa80`060dae00 : snapman+0x2b100
fffff880`033fb6a8 fffff880`01c14767 : ffffd8f0`00002710 fffffa80`04af47c0 fffffa80`060dae00 fffffa80`04b018e8 : 0xfffffa80`04b018e8
fffff880`033fb6b0 ffffd8f0`00002710 : fffffa80`04af47c0 fffffa80`060dae00 fffffa80`04b018e8 fffffa80`04af4bc0 : snapman+0x14767
fffff880`033fb6b8 fffffa80`04af47c0 : fffffa80`060dae00 fffffa80`04b018e8 fffffa80`04af4bc0 fffff880`01c1e59a : 0xffffd8f0`00002710
fffff880`033fb6c0 fffffa80`060dae00 : fffffa80`04b018e8 fffffa80`04af4bc0 fffff880`01c1e59a fffffa80`060daec0 : 0xfffffa80`04af47c0
fffff880`033fb6c8 fffffa80`04b018e8 : fffffa80`04af4bc0 fffff880`01c1e59a fffffa80`060daec0 fffffa80`060daec0 : 0xfffffa80`060dae00
fffff880`033fb6d0 fffffa80`04af4bc0 : fffff880`01c1e59a fffffa80`060daec0 fffffa80`060daec0 fffffa80`04b018e8 : 0xfffffa80`04b018e8
fffff880`033fb6d8 fffff880`01c1e59a : fffffa80`060daec0 fffffa80`060daec0 fffffa80`04b018e8 fffffa80`049d0870 : 0xfffffa80`04af4bc0
fffff880`033fb6e0 fffffa80`060daec0 : fffffa80`060daec0 fffffa80`04b018e8 fffffa80`049d0870 fffffa80`04403f20 : snapman+0x1e59a
fffff880`033fb6e8 fffffa80`060daec0 : fffffa80`04b018e8 fffffa80`049d0870 fffffa80`04403f20 fffff880`01ba284d : 0xfffffa80`060daec0
fffff880`033fb6f0 fffffa80`04b018e8 : fffffa80`049d0870 fffffa80`04403f20 fffff880`01ba284d 00000000`00004000 : 0xfffffa80`060daec0
fffff880`033fb6f8 fffffa80`049d0870 : fffffa80`04403f20 fffff880`01ba284d 00000000`00004000 fffff880`01c1df72 : 0xfffffa80`04b018e8
fffff880`033fb700 fffffa80`04403f20 : fffff880`01ba284d 00000000`00004000 fffff880`01c1df72 fffff800`03215000 : 0xfffffa80`049d0870
fffff880`033fb708 fffff880`01ba284d : 00000000`00004000 fffff880`01c1df72 fffff800`03215000 fffffa80`043513d0 : 0xfffffa80`04403f20
fffff880`033fb710 fffff880`01bb49bb : fffffa80`060daec0 fffffa80`043513d0 fffffa80`0413b1c8 fffffa80`060f4000 : volsnap!VspAsynchronousIo+0x9d
fffff880`033fb750 fffff880`01bb4dbc : 00000000`00136f31 00000000`00000000 fffffa80`043513b8 00000000`00136f31 : volsnap!VspWriteTableUpdates+0x29b
fffff880`033fb7e0 fffff880`01bb4f5e : fffffa80`04351340 00000000`00000000 fffffa80`0413b1b0 00000000`00000000 : volsnap!VspWriteVolumePhase32+0x15c
fffff880`033fb840 fffff880`01b9fbe5 : fffffa80`060d7010 fffffa80`05728a90 fffffa80`04b1e190 fffffa80`04b1e190 : volsnap!VspWriteVolumePhase3+0xee
fffff880`033fb880 fffff800`03287d26 : fffffa80`060d748b 00000000`00000000 00000000`00000000 fffffa80`060d7010 : volsnap!VspPerformanceWrapperCompletionRoutine+0x55
fffff880`033fb8d0 fffff880`01a518ee : fffffa80`04823210 fffffa80`04808c01 00000000`00000008 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`033fb9b0 fffff800`03287d26 : 00000000`00000000 fffff880`00f06f1e fffff880`00000000 fffff880`00000000 : CLASSPNP!TransferPktComplete+0x1ce
fffff880`033fba30 fffff880`010026cb : fffff880`03b25010 fffffa80`047ff901 fffffa80`03ef0f80 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`033fbb10 fffff880`010028d3 : 00000000`00000000 00000000`000000f3 00000000`00000000 fffffa80`04806060 : storport!RaidUnitCompleteRequest+0x1fb
fffff880`033fbbf0 fffff880`00f074ce : fffffa80`046f3000 00000000`00000002 fffffa80`046f3750 fffff880`04cc98f8 : storport!RaidpAdapterDpcRoutine+0x53
fffff880`033fbc30 fffffa80`046f3000 : 00000000`00000002 fffffa80`046f3750 fffff880`04cc98f8 fffff880`033d3180 : sptd+0x424ce
fffff880`033fbc38 00000000`00000002 : fffffa80`046f3750 fffff880`04cc98f8 fffff880`033d3180 00000000`00000000 : 0xfffffa80`046f3000
fffff880`033fbc40 fffffa80`046f3750 : fffff880`04cc98f8 fffff880`033d3180 00000000`00000000 fffff880`033d7f40 : 0x2
fffff880`033fbc48 fffff880`04cc98f8 : fffff880`033d3180 00000000`00000000 fffff880`033d7f40 00000000`00000022 : 0xfffffa80`046f3750
fffff880`033fbc50 fffff880`033d3180 : 00000000`00000000 fffff880`033d7f40 00000000`00000022 00000000`00000000 : atikmdag+0x1d8f8
fffff880`033fbc58 00000000`00000000 : fffff880`033d7f40 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffff880`033d3180


STACK_COMMAND:  kb

FOLLOWUP_IP: 
snapman+19089
fffff880`01c19089 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  snapman+19089

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: snapman

IMAGE_NAME:  snapman.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45265d99

FAILURE_BUCKET_ID:  X64_0x1E_0_snapman+19089

BUCKET_ID:  X64_0x1E_0_snapman+19089

Followup: MachineOwner

der ist von gestern mittag

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


EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.

FAULTING_IP: 
+6239646235323165
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800032cf46e to fffff800032d7710

STACK_TEXT:  
fffff880`033fa8e8 fffff800`032cf46e : fffff880`00000014 fffffa80`050a4170 fffff880`033fb0f0 fffff800`03304668 : nt!KeBugCheck
fffff880`033fa8f0 fffff800`032fd40d : fffff800`034e5b7c fffff800`0341fe84 fffff800`03267000 fffff880`033fb050 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`033fa920 fffff800`03304a90 : fffff800`03426b14 fffff880`033fa998 fffff880`033fb050 fffff800`03267000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`033fa950 fffff800`0330606a : fffff880`033fb050 fffff880`033fb0f0 00001b4b`00000001 00001fff`00001fff : nt!RtlDispatchException+0x410
fffff880`033fb030 fffff800`032e0610 : fffffa80`06138760 fffff800`032e2e67 0000000f`00000000 00000000`00000000 : nt!RtlRaiseStatus+0x4e
fffff880`033fb5d0 fffff880`01d98089 : 00000000`00000000 fffffa80`00000001 fffff880`033d3180 fffff880`01daa100 : nt!KeReleaseMutant+0x260
fffff880`033fb680 00000000`00000000 : fffffa80`00000001 fffff880`033d3180 fffff880`01daa100 fffffa80`04b02b30 : snapman+0x19089


STACK_COMMAND:  kb

FOLLOWUP_IP: 
snapman+19089
fffff880`01d98089 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  snapman+19089

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: snapman

IMAGE_NAME:  snapman.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45265d99

FAILURE_BUCKET_ID:  X64_0x1E_0_snapman+19089

BUCKET_ID:  X64_0x1E_0_snapman+19089

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

 

[Chaoswave]

AW: Bluescreen + SMART error

ich hätte auch noch zwei vom 21.9 und eine vom 20.9
soll ich die auch noch hochladen?
so wie es aussieht gehört das snapman irgendwie zu acronis
snapman.sys Windows Prozess - Was ist das?
würde es was bringen mein true image home runter zu werfen? lief bis vor 4 tagen ja noch alles halbwegs und warum schmiert der rechner ab wenn ich was installiere?! so wie es aussieht hat die snapman.sys was mit nem screenshot zu tun oder nicht?....

 

[Chaoswave]

AW: Bluescreen + SMART error

am 21. waren es jeweils partmgr.sys und snapshot.sys
am 20. war es 3x snapman

 

[utacat]

AW: Bluescreen + SMART error

snapman.sys Windows Prozess - Was ist das?

Lies dir das mal durch. Hat was mit diesen Programmen zu tun.

Gruß utacat

 

[simpel1970]

so wie es aussieht gehört das snapman irgendwie zu acronis

So ist es. Deinstalliere die Acronis Produkte.

 

[Chaoswave]

Und wenn ich die dann wieder drauf packe? Hab ich die Probleme dann theoretisch immer noch oder wieder?

 

[simpel1970]

Die hättest du dann wieder (sofern die Acronis-Treiber tatsächlich für die Probleme verantwortlich sind). Also am besten deinstallieren und testen, ob die Probleme dann weg sind.

Um welche Acronis Produkte (incl. Versionsnummern) handelt es sich?

 

[Chaoswave]

handelt sich zum einen um True Image Home 2010 (mitlerweile Build 7.046, hat sich grad als ich die Version checken wollte selbst geupdatet.

Was aber theorethisch möglich dafür verantwortlich sein könnte ist das Disk Director Suite in Englisch Version 10 Build 2.160
Das ist ungefähr zu dem Zeitpunkt drauf als die ersten Screens anfingen...
Ich schmeiß erst mal nur das runter und guck obs daran lag weil True Image ging ja vorher

 

[simpel1970]

Acronis TI Home 2010 läuft eigentlich problemlos unter Win7.
Acronis Disk Director 10 läuft nicht fehlerfrei unter Win7 - 64bit (erst ab Version 11). Daran könnte es liegen.

 

[Chaoswave]

ja das wirds vermutlich sein...
hab nur den Director gekickt und ich konnte ganz normal zocken und was installieren. Wird wohl daran gelegen haben
Vielen dank soweit^^

 

[simpel1970]

Gern geschehen. Wenn noch was sein sollte...