Komp Na Gwarancji ,winxpsp2,restart

[zeus0]

Od grudnia 2004 (zainstalowałem nagrywarkę DVD) komp okazyjnie się restartuje . Po instalacji nagrywarki sytem się uruchamiał ale nie gasła dioda twardego dysku . Ściągnąłem firmware i zainstalowałem , problemik z diodą znikł . Oto opis minidumpa :

 

Microsoft ® Windows Debugger Version 6.4.0007.2

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\OKNA\Minidump\Mini030605-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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20

Debug session time: Sun Mar 6 07:26:04.296 2005 (GMT+1)

System Uptime: 0 days 4:44:23.865

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

* 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 unloaded module list

.................

Loading User Symbols

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

Unable to load image fetnd5.sys, Win32 error 2

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

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

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 100000D1, {0, 2, 0, f83c4c49}

 

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

 

Probably caused by : fetnd5.sys ( fetnd5+22f7 )

 

Followup: MachineOwner

---------

 

kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)

An attempt was made to access a pageable (or completely invalid) address at an

interrupt request level (IRQL) that is too high. This is usually

caused by drivers using improper addresses.

If kernel debugger is available get stack backtrace.

Arguments:

Arg1: 00000000, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000000, value 0 = read operation, 1 = write operation

Arg4: f83c4c49, address which referenced memory

 

Debugging Details:

------------------

 

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

 

 

MODULE_NAME: fetnd5

 

FAULTING_MODULE: 804d7000 nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 3b5818a8

 

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

unable to get nt!MiSessionPoolStart

unable to get nt!MiSessionPoolEnd

00000000

 

CURRENT_IRQL: 2

 

FAULTING_IP:

NDIS+22c49

f83c4c49 f60001 test byte ptr [eax],0x1

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0xD1

 

LAST_CONTROL_TRANSFER: from f88102f7 to f83c4c49

 

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

f89511e4 f88102f7 0028eed8 f8951b04 00000001 NDIS+0x22c49

f8951fa0 f8810053 81f8f000 f8951fd0 00000000 fetnd5+0x22f7

81f984b8 00000000 00000000 00000000 00000000 fetnd5+0x2053

 

 

FOLLOWUP_IP:

fetnd5+22f7

f88102f7 ?? ???

 

SYMBOL_STACK_INDEX: 1

 

FOLLOWUP_NAME: MachineOwner

 

SYMBOL_NAME: fetnd5+22f7

 

IMAGE_NAME: fetnd5.sys

 

STACK_COMMAND: kb

 

BUCKET_ID: WRONG_SYMBOLS

 

Followup: MachineOwner

---------

 

lub tak :

 

Microsoft ® Windows Debugger Version 6.4.0007.2

Copyright © Microsoft Corporation. All rights reserved.

 

 

Loading Dump File [C:\OKNA\Minidump\Mini030405-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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20

Debug session time: Fri Mar 4 18:00:38.921 2005 (GMT+1)

System Uptime: 0 days 0:24:52.484

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

* 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 unloaded module list

.........

Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 10000050, {ffffffd8, 0, 80573d30, 0}

 

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

 

 

Followup: MachineOwner

---------

 

kd> !analyze -v

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

* *

* Bugcheck Analysis *

* *

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

 

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced. This cannot be protected by try-except,

it must be protected by a Probe. Typically the address is just plain bad or it

is pointing at freed memory.

Arguments:

Arg1: ffffffd8, memory referenced.

Arg2: 00000000, value 0 = read operation, 1 = write operation.

Arg3: 80573d30, If non-zero, the instruction address which referenced the bad memory

address.

Arg4: 00000000, (reserved)

 

Debugging Details:

------------------

 

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

 

 

MODULE_NAME: nt

 

FAULTING_MODULE: 804d7000 nt

 

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

 

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

unable to get nt!MiSessionPoolStart

unable to get nt!MiSessionPoolEnd

ffffffd8

 

FAULTING_IP:

nt+9cd30

80573d30 ff75d8 push dword ptr [ebp-0x28]

 

MM_INTERNAL_CODE: 0

 

CUSTOMER_CRASH_COUNT: 1

 

DEFAULT_BUCKET_ID: DRIVER_FAULT

 

BUGCHECK_STR: 0x50

 

LAST_CONTROL_TRANSFER: from 804df06b to 80573d30

 

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

f4f02d34 804df06b 000000e4 ffffffff 00cbeca8 nt+0x9cd30

f4f02d64 7c90eb94 badb0d00 00cbec14 00000000 nt+0x806b

00cbec9c 7c864800 00cbecd8 00000000 00000728 0x7c90eb94

00cbeccc 0046fcb3 00000002 000000e4 00a2e19c 0x7c864800

00000000 00000000 00000000 00000000 00000000 0x46fcb3

 

 

STACK_COMMAND: .bugcheck ; kb

 

FOLLOWUP_NAME: MachineOwner

 

BUCKET_ID: WRONG_SYMBOLS

 

Followup: MachineOwner

---------

 

Komputer był w lutym dwa razy ( po pięć) dni w serwisie Vobis-u i nic nie stwierdzono . Co teraz ? Pomocy...

Edytowane 6 Marca 2005 przez zeus0

[Nyny]

Odszukaj co to za plik fetnd5.sys i zobacz co za program z niego korzysta. Sproboj go wtedy odinstalowac i zobaczyc co i jak

[zeus0]

Odszukaj co to za plik  fetnd5.sys  i zobacz co za program z niego korzysta. Sproboj go wtedy odinstalowac i zobaczyc co i jak

1313257[/snapback]

sterownik do karty sieciowej , ściągnąłem juz nowy pod winxpsp2 , zobaczymy.....

[Ouara]

miałem to samo

żadne sterowniki nie pomogły - instalowałem najnowsze, najstarsze, ze strony producenta m,obo, ze strony nvidiii do chipsetu(...cokowlwiek wymyślisz to przerabiałem...)

karta była wspawana na mobo

wyłączyłem w biosie, zakupiłem nową na PCI i jak ręką odjął

[kuruś]

Spróbuj z przywracaniem systemu chociaż nie polecam w ostateczności odpal konsole odzyskiwania systemu.

Edytowane 10 Lipca 2005 przez qura16

[zeus0]

Dzięki za zainteresowanie....tylko co ja mam powiedzieć faciom w serwisie ? (gwarancja 5 lat !!!)

[Nyny]

Jak masz kompa na gwarancji i masz plomby to lepiej zanies go do serwisu. Tak bedzie najlepiej bo jak sam cos bedziesz rozkrecal to sracisz gwarancje