Nachrichten

1

Windows Vista Forum / Re: immer blue screen

« am: 14. Dezember 2008, 16:38:00 »

neue meldung aus dem "problemberichtcenter"

Windows
Problem: Unerwartetes Herunterfahren
Dateien, die zur Problemlösung beitragen:
Mini121008-01.dmp
sysdata.xml
Version.txt
 Temporäre Kopie dieser Dateien anzeigen
Warnung: Wenn das Problem durch einen Virus oder ein sonstiges Sicherheitsrisiko verursacht wurde, kann der Computer durch das Öffnen einer Kopie der Dateien beschädigt werden.

2

Windows Vista Forum / Re: immer blue screen

« am: 14. Dezember 2008, 16:30:41 »

jawohl...

nach einem bugtest oder wie der hiess erhielt ich diese meldungen:



Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16754.x86fre.vista_gdr.080917-1612
Machine Name:
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Sun Dec 14 13:24:09.132 2008 (GMT+1)
System Uptime: 0 days 0:00:24.960
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd900c).  Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {c0761104, 0, 80775ba2, 9}

Page 48261 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffd900c).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd900c).  Type ".hh dbgerr001" for details
Probably caused by : fltmgr.sys ( fltmgr!FltpGetStartingCallbackNodeForCreate+38 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: c0761104, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 80775ba2, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 00000009, (reserved)

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

Page 48261 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffd900c).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd900c).  Type ".hh dbgerr001" for details

READ_ADDRESS:  c0761104

FAULTING_IP:
fltmgr!FltpGetStartingCallbackNodeForCreate+38
80775ba2 ff1504117680    call    dword ptr [fltmgr!_imp__FsRtlFindExtraCreateParameter (80761104)]

MM_INTERNAL_CODE:  9

IMAGE_NAME:  fltmgr.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4549acc2

MODULE_NAME: fltmgr

FAULTING_MODULE: 80756000 fltmgr

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  wininit.exe

CURRENT_IRQL:  0

TRAP_FRAME:  8bf889d4 -- (.trap 0xffffffff8bf889d4)
ErrCode = 00000000
eax=8bf88a60 ebx=859804f4 ecx=8bf88a6c edx=8bf88aa4 esi=85e4fc70 edi=00000000
eip=80775ba2 esp=8bf88a48 ebp=8bf88a64 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
fltmgr!FltpGetStartingCallbackNodeForCreate+0x38:
80775ba2 ff1504117680    call    dword ptr [fltmgr!_imp__FsRtlFindExtraCreateParameter (80761104)] ds:0023:80761104={nt!FsRtlFindExtraCreateParameter (81d790cf)}
Resetting default scope

LAST_CONTROL_TRANSFER:  from 81c8fbf4 to 81ca9ff2

STACK_TEXT: 
8bf889bc 81c8fbf4 00000000 c0761104 00000000 nt!MmAccessFault+0x106
8bf889bc 80775ba2 00000000 c0761104 00000000 nt!KiTrap0E+0xdc
8bf88a64 8076d9df 8a4643c8 8bf88a84 8bf88aaf fltmgr!FltpGetStartingCallbackNodeForCreate+0x38
8bf88ab0 81c27f9b 85478768 85468540 85e4fccc fltmgr!FltpCreate+0x1ef
8bf88ac8 81d96f4c 8bf830c0 8554b334 846c0b00 nt!IofCallDriver+0x63
8bf88b80 81deeef9 846c0b18 00000000 8554b290 nt!IopParseDevice+0xcff
8bf88c10 81dec6a5 00000000 8bf88c68 00000040 nt!ObpLookupObjectName+0x615
8bf88c70 81d839d4 0021e6c8 00000000 81dd0301 nt!ObOpenObjectByName+0x13c
8bf88ce4 81d8ec82 0021e6f0 80100080 0021e6c8 nt!IopCreateFile+0x5ec
8bf88d30 81c8caea 0021e6f0 80100080 0021e6c8 nt!NtCreateFile+0x34
8bf88d30 778c0f34 0021e6f0 80100080 0021e6c8 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0021e6f4 00000000 00000000 00000000 00000000 0x778c0f34


STACK_COMMAND:  kb

FOLLOWUP_IP:
fltmgr!FltpGetStartingCallbackNodeForCreate+38
80775ba2 ff1504117680    call    dword ptr [fltmgr!_imp__FsRtlFindExtraCreateParameter (80761104)]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  fltmgr!FltpGetStartingCallbackNodeForCreate+38

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x50_fltmgr!FltpGetStartingCallbackNodeForCreate+38

BUCKET_ID:  0x50_fltmgr!FltpGetStartingCallbackNodeForCreate+38

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



Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6000.16754.x86fre.vista_gdr.080917-1612
Machine Name:
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Sun Dec 14 13:24:09.132 2008 (GMT+1)
System Uptime: 0 days 0:00:24.960
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd900c).  Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {c0761104, 0, 80775ba2, 9}

Page 48261 not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffd900c).  Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd900c).  Type ".hh dbgerr001" for details
Probably caused by : fltmgr.sys ( fltmgr!FltpGetStartingCallbackNodeForCreate+38 )

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

3

Windows Vista Forum / Re: immer blue screen

« am: 14. Dezember 2008, 13:42:03 »

es handelt sich im übrigen um ein ACER TravelMate 7520 Notebook

4

Windows Vista Forum / immer blue screen

« am: 14. Dezember 2008, 13:37:56 »

huhu und guten tag, ich habe folgendes problem, ab und zu bzw. sehr oft bekomme ich einfach so einen bluescreen und der pc startet sich neu. nach dem start erhalte ich diese meldung:

Problemsignatur:
  Problemereignisname:   BlueScreen
  Betriebsystemversion:   6.0.6000.2.0.0.768.3
  Gebietsschema-ID:   1031

Zusatzinformationen zum Problem:
  BCCode:   50
  BCP1:   C0761104
  BCP2:   00000000
  BCP3:   80775BA2
  BCP4:   00000009
  OS Version:   6_0_6000
  Service Pack:   0_0
  Product:   768_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
  C:\Windows\Minidump\Mini121408-03.dmp
  C:\Users\kiwi\AppData\Local\Temp\WER-84599-0.sysdata.xml
  C:\Users\kiwi\AppData\Local\Temp\WER903D.tmp.version.txt

Lesen Sie unsere Datenschutzrichtlinie:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0407


Es ist original Vista, was beim Kauf dabei war "OEM"


wie kann man dieses umgehen?


vielen dank =)