Komputer się resetuje... :/

[Sir_Wader]

Po włączeniu komputera po któreś chwili się resetuje (po pol godzinach, a nawet po 3h). Nie mam pojęcia co może to powodować, jeżeli to wirus lub inne badziewie to dziwne bo ostatnio nie wchodziłem w jakieś inne strony i nic “specjalnego” nie sciągałem

Pozdro

[Grzesiekk]

Witam

Sprawdź napięcia, temperatury (np.SpeedFan-em) i dobrze przeskanuj komputer.

[Joan (Joan Sunshine)]

Zdejmij reset na rzecz BSOD w Panelu sterowania > System > Zaawansowane > Uruchamianie i odzyskiwanie > odptaszyć Automatycznie uruchom ponownie. Po tym dostaniesz kod błędu z nazwą pliku pod spodem i wrzuć te dane tutaj.

[Sir_Wader]

%SystemRoot%\Minidump - to jest ten kod?

Temperatura itp. - http://img294.imageshack.us/img294/7424/beztytuubw5.jpg

i co z tą temperaturą?

[Joan (Joan Sunshine)]

To znaczy, że musimy obejrzeć minidumpy. Temperatura na moje oko ok.

Przeczytaj to: http://www.searchengines.pl/phpbb203/in … opic=50339 i wklej zawartość pliku minidump

[Sir_Wader]

Zawartość? Gdzie ona jest?

[Phylby (Adarek)]

http://www.google.pl/search?hl=pl&q=Deb … lr=lang_pl

[Sir_Wader]

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Sun Apr 2 15:50:51.906 2006 (GMT+1) System Uptime: 0 days 3:18:12.458 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 80566a34, f5400b64, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Followup: MachineOwner ---------

O to chodzi? To jest z jednego pliku, a ja mam tych plików więcej

[Phylby (Adarek)]

WARNING: Unable to verify timestamp for ntoskrnl.exe

ntoskrnl.exe - wskazuje na problem ze sprzetem . Nie na 100%

Coś nowego montowałeś ??

Kojarzysz z czymś .

Ps.

Tak na szybko co sie powinno /można zrobić :

Poluzowane karty docisnij . Wiatraki itp.

Wyczyść z paprochów wnętrze kompa i wszystkie wloty i wyloty .

Radiator dociska tam gdzie trzeba ??

Sprawdz tem. w kompie . Nie zapomnij o karcie graf. i zaśilaczu.( wentylacja)

Ps2.

Rzuć okiem czy kondensatory są całe . Powinny być nie napuchnięte.

Na górze i po bokach.

[Joan (Joan Sunshine)]

Trudno coś powiedzieć, bo tutaj nie ma wskazania na konkretny plik.

Powinno być np coś takiego (pod “Bugcheck Analysis”):

Probably caused by : nv4_disp.dll ( nv4_disp+8e95 )

Pogrubiony plik jest przykładem. Zdebuguj inne minidumpy skoro piszesz, że jest ich więcej i poszukaj na samym końcu takiej informacji

[Phylby (Adarek)]

Joan Pisz mu po ludzku.

Zdebuguj ??

Program sam zgłupiał .

W tej sytuacji nie dostanieś konkretu .

Wywali to co nie zna - standart >> ntoskrnl.exe

To znaczy to co wyżej pisałem .

Nawet sam MS nie podaje co to i jak . Ci w serwisach toże.

Wtedy w serwisie jedyna sprawdzona stradegia to podmiana części

[Joan (Joan Sunshine)]

Phylby - oki

W tym topiku, do którego link podałam to jest po prostu dosyć dokładnie opisane. Chodzi o to, żeby znaleźć takiego dupma, w którym będzie wskazany konkretny plik, bo tak to jest jak wróżenie z fusów.

Sir Wader - poszukaj na końcu wskazania na plik, tak jak napisałam.

Wywala komunikat o jądrze dlatego, że prawdopodobnie jest to problem sprzętowy, czyli najprędzej sterowniki. Zobaczymy co pokażą inne

[Phylby (Adarek)]

Narazie nie odpisałał czy go wyczyścił mechanicznie.I jakie to przyniosło efekty.

[Sir_Wader]

To reszta zawartości tych plików

2

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Fri May 12 16:01:51.562 2006 (GMT+1) System Uptime: 0 days 0:27:33.139 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols Unable to load image ipnat.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for ipnat.sys *** ERROR: Module load completed but symbols could not be loaded for ipnat.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {1f88c110, 2, 1, f8c15816} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image tcpip.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for tcpip.sys *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys Unable to load image RT2400.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for RT2400.sys *** ERROR: Module load completed but symbols could not be loaded for RT2400.sys Unable to load image NDIS.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for NDIS.sys *** ERROR: Module load completed but symbols could not be loaded for NDIS.sys Probably caused by : ipnat.sys ( ipnat+e816 ) Followup: MachineOwner ---------

3

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Mon Jul 17 17:09:53.640 2006 (GMT+1) System Uptime: 0 days 0:00:46.187 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols Unable to load image tcpip.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for tcpip.sys *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000D1, {b, 2, 0, f8d0d8a8} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image TDI.SYS, Win32 error 2 *** WARNING: Unable to verify timestamp for TDI.SYS *** ERROR: Module load completed but symbols could not be loaded for TDI.SYS Probably caused by : TDI.SYS ( TDI+3e4 ) Followup: MachineOwner ---------

4

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Fri Sep 8 22:36:09.625 2006 (GMT+1) System Uptime: 0 days 0:58:42.180 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 80567d26, f896c8f8, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Followup: MachineOwner ---------

5

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Tue Sep 26 19:57:15.093 2006 (GMT+1) System Uptime: 0 days 0:42:30.668 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols Unable to load image portcls.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for portcls.sys *** ERROR: Module load completed but symbols could not be loaded for portcls.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, fb9d08d4, f52658a4, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image ks.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for ks.sys *** ERROR: Module load completed but symbols could not be loaded for ks.sys *** WARNING: Unable to verify timestamp for cmuda.sys *** ERROR: Module load completed but symbols could not be loaded for cmuda.sys Unable to load image sysaudio.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for sysaudio.sys *** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys Probably caused by : portcls.sys ( portcls+128d4 ) Followup: MachineOwner ---------

6

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Mon Dec 11 14:39:31.968 2006 (GMT+1) System Uptime: 0 days 1:08:19.516 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {2f333e0, 2, 0, 804d90aa} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Followup: MachineOwner ---------

7

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Mon Dec 11 20:00:50.156 2006 (GMT+1) System Uptime: 0 days 0:20:27.717 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {2f333e0, 2, 0, 804d90aa} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Followup: MachineOwner ---------

8

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Tue Dec 12 17:30:23.812 2006 (GMT+1) System Uptime: 0 days 3:29:36.366 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols Unable to load image Ntfs.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for Ntfs.sys *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {0, 2, 1, 804e6de3} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Followup: MachineOwner ---------

9

Microsoft ® Windows Debugger Version 6.4.0007.2 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C] 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420 Debug session time: Tue Dec 12 20:58:45.921 2006 (GMT+1) System Uptime: 0 days 0:08:17.472 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** 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 unloaded module list … Loading User Symbols Unable to load image cmuda.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for cmuda.sys *** ERROR: Module load completed but symbols could not be loaded for cmuda.sys *** WARNING: Unable to verify timestamp for portcls.sys *** ERROR: Module load completed but symbols could not be loaded for portcls.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, fc052f15, f53017e8, 0} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image ks.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for ks.sys *** ERROR: Module load completed but symbols could not be loaded for ks.sys Unable to load image sysaudio.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for sysaudio.sys *** ERROR: Module load completed but symbols could not be loaded for sysaudio.sys Probably caused by : cmuda.sys ( cmuda+7af15 ) Followup: MachineOwner ---------

[Joan (Joan Sunshine)]

Probably caused by : cmuda.sys

Przeinstaluj sterowniki do karty dźwiękowej bo to ich wina

[Sir_Wader]

No własnie przypomniało mi się, że nie dawno gdy włączałem komputer odrazu 4 razy “pipkało” i musiałem wciśnąć F1 i pisało coś tam Drive (wiem, że chodzi o sterowniki :P).

Aha i jak juz odptaszyłem to coś tam “nie uruchamiaj komputera ponownie” jak pisałes to już komp nie bedzie mi się resetował?