BlueScreen @ Vista x64

sHaRkS.p3

Ensign
Dabei seit
Juni 2008
Beiträge
159
Hey Leute.....

Habe schon das 2te mal innerhalb von 2 Wochen einen BlueScreen gehabt!

Woran könnte es liegen ?

Mein System:

Mainboard: ASUS P5N-E SLI
RAM: 4GB
CPU: Intel E6850
Grafik: GeForce 9600 GT 512MB
Vista Ultimate x64 SP1

Habe folgendes Kopieren können!

Code:
Problemsignatur:
  Problemereignisname:	BlueScreen
  Betriebsystemversion:	6.0.6001.2.1.0.256.1
  Gebietsschema-ID:	1031

Zusatzinformationen zum Problem:
  BCCode:	1e
  BCP1:	FFFFFFFFC0000005
  BCP2:	FFFFF80002AEEA16
  BCP3:	0000000000000000
  BCP4:	000000000002B000
  OS Version:	6_0_6001
  Service Pack:	1_0
  Product:	256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
  C:\Windows\Minidump\Mini122308-01.dmp
  C:\Users\Tobi\AppData\Local\Temp\WER-48438-0.sysdata.xml
  C:\Users\Tobi\AppData\Local\Temp\WER10E1.tmp.version.txt

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

werkam

Alter Meckermann
Dabei seit
Okt. 2001
Beiträge
61.834
Welche Fehlermeldung steht im Bluescreen? Du kannst die minidump auslesen mit dem Debugger.
 

sHaRkS.p3

Ensign
Ersteller dieses Themas
Dabei seit
Juni 2008
Beiträge
159
Also im Ordner C:\Windows\Minidump\Mini122308-01.dmp ist nix drin

Wie mach ich das denn mit den Rechten ?

Frohe Weihnachten @ aLL :)
 

werkam

Alter Meckermann
Dabei seit
Okt. 2001
Beiträge
61.834
Im Explorer>Extras>Ordneroptionen>Ansicht gibt es 2 Punkte den man setzen muss, um sich die ausgeblendeten Dateien/Ordner und die Systemdateien anzeigen zu lassen. Wenn Du allerdings eingestellt hast, dass keine "Kernelabbilder bei Fehlern" erstellt werden, suchst Du auch vergeblich.
 

Anhänge

werkam

Alter Meckermann
Dabei seit
Okt. 2001
Beiträge
61.834
Du erstellst keine Minidumps sondern komplette Speicherabbilder (memory.dump), deshalb sind die Minidumps nach einem Reboot wieder weg.
 

werkam

Alter Meckermann
Dabei seit
Okt. 2001
Beiträge
61.834
Es ist egal was Du einstellst, bei memory Dump wird der gesamte Inhat des Rams gespeichert, bei mini Dump nur ein Speicherabbild, öffnen kannst Du sie beide mit dem Debugger von M$, ist nur die Frage was Du damit anfangen kannst und wie gross der Aufwand sein soll, um die Fehler daraus auszulesen, wenn Du davon keinen Plan hast.
 

sHaRkS.p3

Ensign
Ersteller dieses Themas
Dabei seit
Juni 2008
Beiträge
159
Hatte gerade wieder ein BlueScreen beim CSS Spielen

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


Loading Dump File [C:\Users\Tobi\Desktop\Mini122908-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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`02847000 PsLoadedModuleList = 0xfffff800`02a0cdb0
Debug session time: Mon Dec 29 18:53:15.479 2008 (GMT+1)
System Uptime: 0 days 5:58:04.194
*********************************************************************
* 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 1E, {ffffffffc0000005, fffff800028af2dd, 0, d0}

Unable to load image \SystemRoot\system32\DRIVERS\nvmfdx64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmfdx64.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmfdx64.sys
*** WARNING: Unable to verify timestamp for hal.dll
*** ERROR: Module load completed but symbols could not be loaded for hal.dll
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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+                                    *
*********************************************************************
*********************************************************************
* 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+                                    *
*********************************************************************
Probably caused by : nvmfdx64.sys ( nvmfdx64+eced0 )

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

MagicAndre1981

Admiral
Dabei seit
Feb. 2004
Beiträge
7.455

sHaRkS.p3

Ensign
Ersteller dieses Themas
Dabei seit
Juni 2008
Beiträge
159
Habe jetzt n Treiber Update gemacht....

Mal sehen ob´s was gebracht hat!

Also auf den nächsten BlueScreen warten ^^

Danke nochmal für eure Hilfe :)
 
Top