Pc spielt keine bewegten Bilder mehr ab

[Scarred]

Hi
Hatte eine NTSC 1 DVD hier und sie auch per VLC und AnyDVD zum laufen gebracht
Dann bin ich mitten im Video auf Deinterlacen->Angleichen gegangen und dann ist der Pc mit diesem Bluescreen abgeschmiert

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


Loading Dump File [C:\WINDOWS\Minidump\Mini082908-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 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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri Aug 29 11:26:29.656 2008 (GMT+2)
System Uptime: 0 days 0:05:09.402
*********************************************************************
* 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 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 1000000A, {16, 1c, 0, 804e1745}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for atkosdmini.dll
*** ERROR: Module load completed but symbols could not be loaded for atkosdmini.dll
*** WARNING: Unable to verify timestamp for atkdisp.dll
*** ERROR: Module load completed but symbols could not be loaded for atkdisp.dll
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
********************************************************************** ***
*** ***
*** ***
*** 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 : atkosdmini.dll ( atkosdmini+1370 )

Followup: MachineOwner


Das passiert jetzt jedes mal wenn ich Spiele oder Videos gucken will
Es kommt 2 Sec. Bild...Bild friert ein.Batz Bluescreen und Neustart


Was mache ich falsch ? Treiber wurde neuer installiert
AnyDVD entfernt und eine Systemwiederherstellung gemacht was aber auch nix brachte


Bin echt verzweifelt

 

[nicoc]

... versuche mal folgendes: Treiber deinstallieren-> Neustart im abgesicherten Modus-> Treiberreste mit Driver Cleaner/Sweeper deinstallieren-> Neustart im normalen Modus und Neuinstallation der Nvidia-Treiber.

 

[Scarred]

Google findet nix nützliches yu Cleaner/Sweeper

 

[cyrano]

Also mein Google wirft mir b ei dem Begriff "Driver Cleaner" ~ 964.000 Begriffe aus wobei die ersten 4 Direkte Downloadlinks sind

 

[Scarred]

So habs gemacht
Aber ich hab langsam schiss das meine Hardware durch die andauernden Bluescreens put geht ;(

 

[rueckspiegel]

keine angst, ... hardware geht davon nicht kapput! das ist einfach nur nen softwareproblem!

deine hardware geht kapput, wenn du nen kühler abschraubst oder wild gegen deinen pc trittst, ...

einzig und alleine die daten wären etwas ingefahr, aber die kann man auch sichern ;-)

 

[Mydgard]

Wenn Du ganz sicher gehen willst, Installier Windows Neu ... wenn Du vorgesorgt hast, hast Du bei der ersten Installation gleich ein Image erstellt, das einspielen dauert ja nur ca. 15 Min.

 

[Scarred]

Ne hab ich nicht

Aber ich hab ein TuneUp Backup irgendwie xD

 

[Scarred]

Wie kann ich nun das Problem beheben ?

 

[nicoc]

... meinen Tipp schon mal angewandt?

 

[Scarred]

Ja
Auch nix gebracht
Leider

 

[Scarred]

Bitte um Hilfe

 

[nicoc]

... Windows neu installieren (deffekte Hardware lässt sich aber noch nicht ausschliessen). Andere Möglichkeit sehe ich nicht.

 

[Scarred]

Was kann den kaputt sein ? Die Grafikkarte ?

 

[Scarred]

Ich hab grad gespielt =D

Ich hab gestern abend asus gamer osd entfernt und grafiktreiber neu installiert

ausserdem hab ich die reste von vlc gelöscht

und es geht
wie geil =D

wisst ihr wo ich schnell ein kleines video runterladen kann um zu gucken ob das auch geht ?=