pomoc

[st_szer 0]

Witam

 

Kolega poprosił mnie abym sprawdził co sie dzieje z jego kompem, mowił ze czesto mus sie resetuje, wyłancza sypie błędami. Obecnie włączyłem BSODa i sprawdziłem podgląd zdarzeń gdzie są błędy które sięciąglę powtarzają System:

Urządzenie \Device\Ide\IdePort1 nie odpowiedziało w ramach ustalonego limitu czasu.

 

Aplikacje

 

Aplikacja powodująca błąd mplayerc.exe, wersja 6.4.8.2, moduł powodujący błąd mplayerc.exe, wersja 6.4.8.2, adres błędu 0x00084c08

 

oraz zastoswowałem sie do FAQ które pszedstawia gusioo

 

Microsoft ® Windows Debugger Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini121105-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 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 1) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30

Debug session time: Sun Dec 11 20:57:18.765 2005 (GMT+1)

System Uptime: 0 days 2:36:57.336

*********************************************************************

* 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 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 User Symbols

Loading unloaded module list

..........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 100000EA, {81aa6d88, 81a65db8, 818cdbd8, 1}

 

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

 

*** WARNING: Unable to verify timestamp for win32k.sys

*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Unable to load image watchdog.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for watchdog.sys

*** ERROR: Module load completed but symbols could not be loaded for watchdog.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: watchdog!_DEFERRED_WATCHDOG ***

*** ***

*************************************************************************

Probably caused by : win32k.sys ( win32k+134430 )

 

Followup: MachineOwner

---------

 

Następnie

 

Microsoft ® Windows Debugger Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\WINDOWS\Minidump\Mini121305-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 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 1) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30

Debug session time: Tue Dec 13 12:39:28.359 2005 (GMT+1)

System Uptime: 0 days 0:03:18.921

*********************************************************************

* 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 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 User Symbols

Mini Kernel Dump does not contain unloaded driver list

Unable to load image nv4_disp.dll, Win32 error 2

*** WARNING: Unable to verify timestamp for nv4_disp.dll

*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck EA, {81a06020, 81a067c8, 81a6f2b8, 1}

 

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

 

Unable to load image watchdog.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for watchdog.sys

*** ERROR: Module load completed but symbols could not be loaded for watchdog.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: watchdog!_DEFERRED_WATCHDOG ***

*** ***

*************************************************************************

Probably caused by : nv4_disp.dll ( nv4_disp+20f09 )

 

Followup: MachineOwner

---------

 

Wynika ze rozwiązanie jest podmiana pliku win32k.sys oraz sterowniki do karty graficznej nv4_disp.dll

Kolega posiada karte NVIDA GeForce2 GTS/GeForce2 Pro

Skąd moge pobrać sterowniki do tej karty, prosił bym o link.

Jeszcze jedna sprawa posiada płytę która ma wbudowany kontroler RAID gdzie w menadzer zadań pokazuje konflikt sprzętowy, posiada jeden HDD, czy można dany kontroler wyłączyć w BIOSIe, prosze o pomoc w naprawie sprzetu mojego kumpla

[Colicab 3]

stery masz na nvidia.com

 

wyedytuj temat na zgodny z regulaminem