Bluescreen aus dem keiner schlau wird.. :(

Diskutiere Bluescreen aus dem keiner schlau wird.. :( im Win7 - 64-Bit Version Forum im Bereich Windows 7 Forum; Hallo ihr da, :) ich habe wie in der Topic steht ein riesen Problem mit ständig wiederkehrenden Bluescreens und keiner meiner Bekannten findet...

pwnika

Threadstarter
Dabei seit
24.10.2012
Beiträge
1
Alter
29
Hallo ihr da, :)
ich habe wie in der Topic steht ein riesen Problem mit ständig wiederkehrenden Bluescreens und keiner meiner Bekannten findet eine Löung. Nun frage ich euch doch mal.
Ich muss gleich von anfang an sagen, dass mein PC schlapp gemacht hat und ich mir jetzt ein neues Motherboard und einen dazupassenden Prozessor sowie Arbeitsspeicher geholt habe. Alles eingebaut, Windows 7 64bit neu rauf. Treiber von der CD installiert fürs Motherboard. Ja und nun das Problem..

Immer wenn ich Windows starte läuft alles ohne Probleme. Fange ich denn aber an zu arbeiten, also eig. reicht schon wenn ich updates installieren will, bekomme ich einen Bluescreen.

Ich habe gelesen, dass ich die dmp datein auslesen soll. Dies habe ich gemacht aber daraus werde ich erstrecht nicht schlau.

Kann mir einer von euch erklären was das hier zu bedeuten hat?

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


Loading Dump File [E:\102412-29608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a1b000 PsLoadedModuleList = 0xfffff800`02c58e50
Debug session time: Wed Oct 24 10:48:35.130 2012 (UTC + 2:00)
System Uptime: 0 days 0:05:10.722
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.....................
Loading User Symbols
Loading unloaded module list
.........
*** WARNING: Unable to verify timestamp for Ntfs.sys
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880070663e8, fffff88007065c40, fffff80002aae6c1}

***** 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 ***
*** ***
*************************************************************************
Probably caused by : ntoskrnl.exe ( nt+936c1 )

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

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

NTFS_FILE_SYSTEM (24)
If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
parameters are the exception record and context record. Do a .cxr
on the 3rd parameter and then kb to obtain a more informative stack
trace.
Arguments:
Arg1: 00000000001904fb
Arg2: fffff880070663e8
Arg3: fffff88007065c40
Arg4: fffff80002aae6c1

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

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

MODULE_NAME: nt

FAULTING_MODULE: fffff80002a1b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

EXCEPTION_RECORD: fffff880070663e8 -- (.exr 0xfffff880070663e8)
ExceptionAddress: fffff80002aae6c1 (nt+0x00000000000936c1)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000800a
Attempt to read from address 000000000000800a

CONTEXT: fffff88007065c40 -- (.cxr 0xfffff88007065c40)
rax=0000000000060870 rbx=0000000000008000 rcx=0000000000008000
rdx=fffffa80046b7801 rsi=0000000000000000 rdi=fffffa800459d610
rip=fffff80002aae6c1 rsp=fffff88007066620 rbp=00000000a000000c
r8=000000000000000b r9=0000000000000727 r10=fffff8800129c700
r11=fffff88007066788 r12=00000000a0000003 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
nt+0x936c1:
fffff800`02aae6c1 440fb7410a movzx r8d,word ptr [rcx+0Ah] ds:002b:00000000`0000800a=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x24

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff88000000001 to fffff80002aae6c1

STACK_TEXT:
fffff880`07066620 fffff880`00000001 : 00000000`00000002 fffffa80`045b0a40 fffff880`0124b734 fffffa80`045bf810 : nt+0x936c1
fffff880`07066628 00000000`00000002 : fffffa80`045b0a40 fffff880`0124b734 fffffa80`045bf810 00000000`00000000 : 0xfffff880`00000001
fffff880`07066630 fffffa80`045b0a40 : fffff880`0124b734 fffffa80`045bf810 00000000`00000000 00000000`00000001 : 0x2
fffff880`07066638 fffff880`0124b734 : fffffa80`045bf810 00000000`00000000 00000000`00000001 fffff880`0125968a : 0xfffffa80`045b0a40
fffff880`07066640 fffffa80`045bf810 : 00000000`00000000 00000000`00000001 fffff880`0125968a fffffa80`045bfbb0 : Ntfs+0xb734
fffff880`07066648 00000000`00000000 : 00000000`00000001 fffff880`0125968a fffffa80`045bfbb0 00000000`00000001 : 0xfffffa80`045bf810


FOLLOWUP_IP:
nt+936c1
fffff800`02aae6c1 440fb7410a movzx r8d,word ptr [rcx+0Ah]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+936c1

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

STACK_COMMAND: .cxr 0xfffff88007065c40 ; kb

BUCKET_ID: WRONG_SYMBOLS

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


Danke schonmal im Vorraus, vielleicht bekomme ich ja mit eurer hilfe meinen PC wieder zum laufen.
 
S

Schnick-Schnack

Gast
:welcome

Welche Hardware ist verbaut ?

Mainboard

CPU

RAM´s
(Insbesondere welche RAM´s und wie viele , und wieviele Steckplätze werden dbzgl. auf dem Board vermendet und sind die RAMs richtig bzw. richtigen steckplatz eingesteckt)

HDD/SSD

Die gesamte Verkabelung auf richtigen und ordnungsgemäßen "Sitz" prüfen , evtl. korregieren .

Gruß

Schnick-Schnack
 
Thema:

Bluescreen aus dem keiner schlau wird.. :(

Bluescreen aus dem keiner schlau wird.. :( - Ähnliche Themen

BSOD KMODE_EXCEPTION_NOT_HANDLED in PpmPerfSelectProcessorState: Hi everyone! I was asked to investigate a KMODE_EXCEPTION_NOT_HANDLED BSOD on a Windows 10 system. Its current (minimal) configuration is...
Mehrere Blue Screens nach Neuinstallation: Hallo Zusammen, ich habe mir neulich einen neuen Rechner zusammengebaut. Verbaut ist: AMD Ryzen 5 2600 6x 3.40GHz So.AM4 BOX 16GB (2x...
Outlook.com: Ic bekomme kein Emails mehr, aber beim senden sind alle da....wenn ich eine Email an mich senden bekomme ich diese Antwort...This is the mail...
Meine Mails landen bei Hotmail/Outlook im Junk: Hallo werte Community! Vielleicht kann mir irgendjemand hier ein Antwort bieten! Wir ein kleines Schulungsunternehmen und haben eine Mailserver...
Why doesn't rightclicking a start menu app and clicking on "open file location" open the actual file location but a weird shortcut location instead on: On Windows 10 rightclicking a start menu app and clicking on "open file location" doesn't open the files' "actual location" but just a folder in...
Oben