Thema: Schwerwiegender Fehler bei "bewegten"Bildern

Hey
Mein Pc stürzt jetzt seitdem ich AnyDvd benutze bei jeder art von Video ab
Ja auch Spiele etc.
Thread dazu http://board.gulli.com/thread/121574...-lg-gsa-4167b/

Bluescreen wird gleich ausgewertet

Grafikkarte ist die 8800GTX

Ist AnyDVD der übeltäter?

Wichtig


Kelshan,Deco... ich brauch euch !

Der Link geht nicht. Hast du mal versucht, AnyDVD einfach noch mal zu deinstallieren? Wenn es dann wieder läuft, hast du deinen Übeltäter sicher. Wenn nicht, kann es trotzdem an dem Programm liegen. Vielleicht installiert das einen Video-Codec, mit dem der Rechner dann nicht richtig klar kommt.

Habs deinstalliert und jetzt ne Systemwiederherstellung gemacht

Bringt alles nichts

Der Bluescreen sagt halt iwas mit Less or Equal

Hast du beizeiten den Grafiktreiber geändert? Also einen neuen installiert oder so? Der Bluescreen könnte auch auf ein Treiberproblem hindeuten, aber mit der spärlichen Info ist das natürlich schwer zu sagen. Ggf. einfach mal komplett deinstallieren und neu installieren. Schaden kann es nicht.

Die Fehlermeldung müsste IRQL_NOT_LESS_OR_EQUAL heißen.
Ist der Interruptzugriff von Peripheriegeräten auf den CPU.
Kann durch einen defekten Treiber oder auch durch Codex passieren. Ich tippe auf Mainboardtreiber (+ Soundkarte).

Bluescreen :

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



Sorry für den langen Text

Ich hab die Treiber komplett deinstalliert und dann neuinstalliert