Bluescreen bei win7

Dieses Thema im Forum "Hardware Probleme" wurde erstellt von cama, 24.01.2011.

  1. cama

    cama Neuer Benutzer

    Dabei seit:
    24.01.2011
    Beiträge:
    2
    Zustimmungen:
    0
    hiho
    ich hab seit längeren immer mal wieder Bluescreens. diese tauchen bei zocken programmieren oder einfach bei surfen auf.


    Mein System:
    phenom 2 x4 965 Be
    geforce gtx 468
    4 GB DDR2 RAM 800 MHz
    GA-MA790X-DS4 (Motherboard)
    500 Watt Netzteil

    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Windows\Minidump\012411-14960-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 (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02e55000 PsLoadedModuleList = 0xfffff800`03092e50
    Debug session time: Mon Jan 24 18:09:08.164 2011 (UTC + 1:00)
    System Uptime: 0 days 0:10:52.005
    *********************************************************************
    * 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
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck F4, {3, fffffa800562eb30, fffffa800562ee10, fffff800031cf240}
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    unable to get nt!KiCurrentEtwBufferOffset
    unable to get nt!KiCurrentEtwBufferBase
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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 : csrss.exe
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa800562eb30, Terminating object
    Arg3: fffffa800562ee10, Process image file name
    Arg4: fffff800031cf240, Explanatory message (ascii)
    
    Debugging Details:
    ------------------
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    unable to get nt!KiCurrentEtwBufferOffset
    unable to get nt!KiCurrentEtwBufferBase
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command 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:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
    
    MODULE_NAME: csrss
    
    FAULTING_MODULE: 0000000000000000 
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    PROCESS_OBJECT: fffffa800562eb30
    
    IMAGE_NAME:  csrss.exe
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xF4
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`038de0e8 fffff800`03252142 : 00000000`000000f4 00000000`00000003 fffffa80`0562eb30 fffffa80`0562ee10 : nt+0x71f00
    fffff880`038de0f0 00000000`000000f4 : 00000000`00000003 fffffa80`0562eb30 fffffa80`0562ee10 fffff800`031cf240 : nt+0x3fd142
    fffff880`038de0f8 00000000`00000003 : fffffa80`0562eb30 fffffa80`0562ee10 fffff800`031cf240 00000000`024b1900 : 0xf4
    fffff880`038de100 fffffa80`0562eb30 : fffffa80`0562ee10 fffff800`031cf240 00000000`024b1900 fffffa80`0562eb30 : 0x3
    fffff880`038de108 fffffa80`0562ee10 : fffff800`031cf240 00000000`024b1900 fffffa80`0562eb30 fffff800`031fe269 : 0xfffffa80`0562eb30
    fffff880`038de110 fffff800`031cf240 : 00000000`024b1900 fffffa80`0562eb30 fffff800`031fe269 ffffffff`ffffffff : 0xfffffa80`0562ee10
    fffff880`038de118 00000000`024b1900 : fffffa80`0562eb30 fffff800`031fe269 ffffffff`ffffffff fffffa80`06338610 : nt+0x37a240
    fffff880`038de120 fffffa80`0562eb30 : fffff800`031fe269 ffffffff`ffffffff fffffa80`06338610 fffffa80`0562eb30 : 0x24b1900
    fffff880`038de128 fffff800`031fe269 : ffffffff`ffffffff fffffa80`06338610 fffffa80`0562eb30 fffffa80`0562eb30 : 0xfffffa80`0562eb30
    fffff880`038de130 ffffffff`ffffffff : fffffa80`06338610 fffffa80`0562eb30 fffffa80`0562eb30 ffffffff`ffffffff : nt+0x3a9269
    fffff880`038de138 fffffa80`06338610 : fffffa80`0562eb30 fffffa80`0562eb30 ffffffff`ffffffff 00000000`00000008 : 0xffffffff`ffffffff
    fffff880`038de140 fffffa80`0562eb30 : fffffa80`0562eb30 ffffffff`ffffffff 00000000`00000008 fffffa80`0562eb30 : 0xfffffa80`06338610
    fffff880`038de148 fffffa80`0562eb30 : ffffffff`ffffffff 00000000`00000008 fffffa80`0562eb30 00000000`c0000006 : 0xfffffa80`0562eb30
    fffff880`038de150 ffffffff`ffffffff : 00000000`00000008 fffffa80`0562eb30 00000000`c0000006 fffffa80`06338610 : 0xfffffa80`0562eb30
    fffff880`038de158 00000000`00000008 : fffffa80`0562eb30 00000000`c0000006 fffffa80`06338610 fffff800`03182c74 : 0xffffffff`ffffffff
    fffff880`038de160 fffffa80`0562eb30 : 00000000`c0000006 fffffa80`06338610 fffff800`03182c74 ffffffff`ffffffff : 0x8
    fffff880`038de168 00000000`c0000006 : fffffa80`06338610 fffff800`03182c74 ffffffff`ffffffff 00000000`00000001 : 0xfffffa80`0562eb30
    fffff880`038de170 fffffa80`06338610 : fffff800`03182c74 ffffffff`ffffffff 00000000`00000001 fffffa80`0562eb30 : 0xc0000006
    fffff880`038de178 fffff800`03182c74 : ffffffff`ffffffff 00000000`00000001 fffffa80`0562eb30 fffff6fb`00000008 : 0xfffffa80`06338610
    fffff880`038de180 ffffffff`ffffffff : 00000000`00000001 fffffa80`0562eb30 fffff6fb`00000008 00000000`746c6644 : nt+0x32dc74
    fffff880`038de188 00000000`00000001 : fffffa80`0562eb30 fffff6fb`00000008 00000000`746c6644 fffff880`038de200 : 0xffffffff`ffffffff
    fffff880`038de190 fffffa80`0562eb30 : fffff6fb`00000008 00000000`746c6644 fffff880`038de200 00000000`00000000 : 0x1
    fffff880`038de198 fffff6fb`00000008 : 00000000`746c6644 fffff880`038de200 00000000`00000000 00000000`00000000 : 0xfffffa80`0562eb30
    fffff880`038de1a0 00000000`746c6644 : fffff880`038de200 00000000`00000000 00000000`00000000 00000000`024b0dd0 : 0xfffff6fb`00000008
    fffff880`038de1a8 fffff880`038de200 : 00000000`00000000 00000000`00000000 00000000`024b0dd0 00000000`024b1390 : 0x746c6644
    fffff880`038de1b0 00000000`00000000 : 00000000`00000000 00000000`024b0dd0 00000000`024b1390 00000000`0010001f : 0xfffff880`038de200
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    Followup: MachineOwner
     
  2. AdMan

    schau mal hier: Windows-Wartungs-Tool. Viele Probleme lassen sich damit einfach beheben. Oftmals ist der PC dann auch schneller!
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren.
  3. #2 xandros, 24.01.2011
    xandros

    xandros IT Consultant, Cisco Registered Partner
    Moderator

    Dabei seit:
    05.07.2007
    Beiträge:
    25.881
    Zustimmungen:
    91
    Ort:
    Umkreis Duisburg, neben Mannheim, hinter Hamburg
    Unvollstaendige Angabe! Oder ist das nur ein Onboard-Chip?

    0xF4.... Bug Check 0xF4: CRITICAL_OBJECT_TERMINATION

    Ursachen koennen verdammt viele existieren....
    Steht in der Ereignisanzeige nichts weiter dazu? Da verstecken sich gelegentlich auch interessante Hinweise.
     
  4. #3 cama, 26.01.2011
    Zuletzt bearbeitet: 26.01.2011
    cama

    cama Neuer Benutzer

    Dabei seit:
    24.01.2011
    Beiträge:
    2
    Zustimmungen:
    0
    hupala da hab ich mich verschrieben meinte diese hier
    Palit GeFrorce gtx460 das ist keine on board karte.

    Welche Ereignisanzeige meinst du?

    EDIT: hab nach gegoogelt und folgende Fehler waren bei Windows-Protokolle->System zu sehen

    Dieser kommt beim Bluescreen:
    Der Dienst "TBPanel" wurde aufgrund folgenden Fehlers nicht gestartet:
    Das System kann die angegebene Datei nicht finden.
     
Thema: Bluescreen bei win7
Besucher kamen mit folgenden Suchen
  1. unable to load image ntoskrnl.exe win 7

    ,
  2. csrss.exe bluescreen windows 7 0xf4

    ,
  3. win 7 32bit a process or thread crucial to system operation has unexpectedly exited or been terminated

    ,
  4. fehlercode f4 parameter 0x3 ntoskrnl.exe,
  5. you can run .symfix; .reload to try to fix the symbol path and load symbols. module_name: csrss,
  6. csrss.exe bluescreen win7,
  7. der dienst tbpanel wurde aufgrund folgenden fehlers nicht gestartet
Die Seite wird geladen...

Bluescreen bei win7 - Ähnliche Themen

  1. Neuling braucht Hilfe bei Grafikkarte, Bluescreen/Absturz und Internet Baustellen

    Neuling braucht Hilfe bei Grafikkarte, Bluescreen/Absturz und Internet Baustellen: Hallo. Ich bin relativer Neuling in der Materie Hardware/Software... Vor wenigen Jahren ging meine Festplatte hinüber - warum auch immer... Ich...
  2. Immer wieder auftretende Bluescreens

    Immer wieder auftretende Bluescreens: Hallöchen mal ne Frage, Ich habe auf einem HP ProBook 640 G1 ständig Probleme mit Bluescreens. Per bluescreenviewer hab ich folgendes ermitteln...
  3. Umzug von Win7 auf neue Festplatte zu Win10

    Umzug von Win7 auf neue Festplatte zu Win10: Guten Abend! Vorab: Dieser Beitrag ist wahrscheinlich etwas Themenübergreifend. Ich würde gerne die Chance des kostenlosen Upgrades von Win7 auf...
  4. Ram nicht kompatibel bluescreen?

    Ram nicht kompatibel bluescreen?: QVL liste: http://download.gigabyte.eu/FileList/Memory/mb_memory_ga-h97-hd3.pdf Pc daten: Netzteil: be quiet 530w cpu :...
  5. Heimnetzgruppe - Win7, 10, iOS

    Heimnetzgruppe - Win7, 10, iOS: Also wie schon oben habe ich FrageN zum Thema Netzwerkgruppe. Und zwar folgender Sachbestand. Ich habe einen Rechner auf Win 10 (LAN), mein Bruder...