Bluescreen bei win7

Computer Forum

Zurück   Computer Forum - PC Forum - ModernBoard.de > Computerprobleme > Hardware Probleme

RB

Sie betrachten gerade: Bluescreen bei win7


Antwort
Alt 24.01.2011, 17:46 Bluescreen bei win7 #1
Neuer Benutzer
 
Registriert seit: 24.01.2011
Beiträge: 2
Standard Bluescreen bei win7

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

Alt 24.01.2011, 21:10 Bluescreen bei win7 #2
C8H10N4O2 - Geniesser
 
Benutzerbild von xandros
 
Registriert seit: 05.07.2007
Ort: Nordamerika, CA, NB
Beiträge: 18.684
xandros eine Nachricht über MSN schicken xandros eine Nachricht über Yahoo! schicken xandros eine Nachricht über Skype™ schicken
Standard AW: Bluescreen bei win7

Zitat:
Mein System:
...
geforce gtx 468
...
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.
Alt 26.01.2011, 11:06 Bluescreen bei win7 #3
Neuer Benutzer
Themenstarter
 
Registriert seit: 24.01.2011
Beiträge: 2
Standard AW: Bluescreen bei win7

Zitat:
Unvollstaendige Angabe! Oder ist das nur ein Onboard-Chip?
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.
Antwort

RB

Thema: Bluescreen bei win7


Themen-Optionen Thema durchsuchen
Thema durchsuchen:

Erweiterte Suche
Ansicht

Ähnliche Themen für: Bluescreen bei win7
Thema Autor Forum Antworten Letzter Beitrag
Bluescreen Problem unter Win7 (64bit) !! Hilfe
Guten Morgen Liebe Leute =) habe ein dringendes Problem mit Windows 7 und zwar folgendes: Hab mir am Wochenende einen Komplett neuen Rechner...
Salvation24 Windows 7 Probleme 30 28.10.2010 08:11
EQ für win7
nabend, unter win7 gibt`s für meine onboard soundkarte (realtek high definition audio) nur einen treiber bzw. proggi bei dem ich keine frequenzen...
adijact Windows 7 Probleme 2 11.08.2010 13:23
Win7 x84 oder Win7 x64 für Magix Video Deluxe 15
Hallo, würdet ihr dass 32 bit oder das 64 bit Betriebssystem empfehlen? Ich hab (bald) 4 GB Arbeitsspeicher und denke auch daran in ZUkunft auf 8 GB...
Adrian:) Windows Probleme 3 29.07.2010 20:36
4 GB Ram auf Win7 64Bit --> Bluescreen
Hi liebes Board ;-) Nachdem ich hier schon ziemlich lange nicht mehr war, melde ich mich direkt mit einem Problem zurück :P Und zwar würde ich...
Medrian Hardware Probleme 7 17.11.2009 20:55
Win7 U x64 Probleme
Leute ich habe 2 Probleme seit dem ich Win7 Ultimate x64 habe.... 1. GrafikProblem: Wenn ich jetzt Videos anschaue habe mehr kleine Pixel zu sehen...
aL3ks3y Windows 7 Probleme 11 01.09.2009 22:38

Zurück   Computer Forum - PC Forum - ModernBoard.de > Computerprobleme > Hardware Probleme

Besucher kamen mit folgenden Begriffen auf die Seite

csrss.exe bluescreen windows 7 0xf4

Powered by vBadvanced CMPS v3.2.2


Sie betrachten gerade: Bluescreen bei win7