bluescreen podczas odpalania płyt w fizycznym napędzie

przez **Bebok** » 09 Kwi 2012, 21:31

Problem pojawił się po instalacji nowego demon toolsa. Gdy wkładałem plyty z grami co jakiś czas pojawiał się bluescreen i restart. Próbowałem używac wirtualnych napędów ( myślałem że to uszkodzenia płyt) ale było to samo. Usunąłem deamona, zainstalowałem alcohol 52%, postarałem pozbyć się syfu. Podmieniłem sterowniki na systemowe, poczytałem i użyłem kilku programików i nic jest jeszcze gorzej. Błąd wyskakuje przy każdej grze z autostartem natomiast przy żadnej z danymi. Teraz nie mogę odpalić żadnej gry. To nie wirus. To jakiś błąd w sterownikach. AUTOfix wykrywa błąd z napędem ale nie wie jaki. Jak to naprawić?

przez **bajbus** » 09 Kwi 2012, 22:52

Sprobuj przwracania sytemu jesli nie pomorze opisz dokladnie kod tego bledu

przez **Palacio** » 10 Kwi 2012, 09:07

Podaj dokładną treść (kod) błędu. Napisz też czy to laptop czy komputer stacjonarny.

przez **Bebok** » 10 Kwi 2012, 10:45

Niestety nie mam włączonego przywracania systemu. To stacjonarny win xp oem

przez **kominekl** » 10 Kwi 2012, 12:48

Podaj odczyt minidump

debugging-tools-for-windows-t15501.html

przez **Bebok** » 10 Kwi 2012, 18:33

Kod: Zaznacz wszystko: Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini040912-07.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 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Mon Apr 9 13:30:11.984 2012 (GMT+2) System Uptime: 0 days 0:04:48.566 ********************************************************************* * 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 .............. Unable to load image fltmgr.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for fltmgr.sys *** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys Unable to load image aswSnx.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSnx.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, b7decab3, b2e168c0, 0} ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 : aswSnx.SYS ( aswSnx+104ef ) Followup: MachineOwner ---------

przez **Bebok** » 12 Kwi 2012, 17:21

0x0000008E ( 0xC 0000005 0x8052BA48 0xB350C82C 0x00000000 ) taki wyświetlił się komunikat na blue screen

przez **mateo8898** » 12 Kwi 2012, 18:43

Co do BSOD`a, odinstaluj Avasta, bo on go powoduje.

Co do napędu:
Mój komputer

Właściwości

Sprzęt

Menadżer Urządzeń

rozwiń gałąź "Stacje dysków CD ROM/DVD" i odinstaluj napęd

restart. Odinstaluj także sterownik SPTD tym

http://www.instalki.pl/programy/downloa ... /SPTD.html

przez **Bebok** » 14 Kwi 2012, 16:58

W BSOD pojawiła się informacja o błędzie z plikiem fltmgr.sys

bluescreen podczas odpalania płyt w fizycznym napędzie

bluescreen podczas odpalania płyt w fizycznym napędzie

Re: bluescreen podczas odpalania płyt w fizycznym napędzie

Re: bluescreen podczas odpalania płyt w fizycznym napędzie

Re: bluescreen podczas odpalania płyt w fizycznym napędzie

Re: bluescreen podczas odpalania płyt w fizycznym napędzie

Re: bluescreen podczas odpalania płyt w fizycznym napędzie

Re: bluescreen podczas odpalania płyt w fizycznym napędzie

Re: bluescreen podczas odpalania płyt w fizycznym napędzie

Re: bluescreen podczas odpalania płyt w fizycznym napędzie

Kto jest na forum