Foro de InfoSpyware - Foro de Hijackthis - Foro de Virus

Buenas

Tengo el Windows Vista Home Basic (lo acaba de formatear y cuando pueda instalo el SP1 y el SP2) Intel Pentium Dual 2 GHz, 250 GB Disco duro, 3 GB de RAM.
El S.O me vino preinstalado. Antivirus Eset NOD32 Antivirus 4 (Actualizado)

Problemas:

1º Tuve que formatear porque al iniciarse.... se me quedaba con una pantalla negra y el icono del ratón

2º Pantallas azules

3º Lentitud (pero espero resolverlo con el SP1 y el SP2, pues cuando los tenia instalados me iba muy bien el PC) Y encima lo acaba de formatear....

Con el Windows Vista... he de tener el modo RAID IDE o AHCI?
Porque la BIOS la modificó mi hermano para instalarme el Windows XP. Hace 1 mes que quite el Win XP y puse el Win Vista y todo me iba bien. Hasta que me aparecen por la cara pantallas azules, se me reinicia solo y por ultimo no queria iniciarme el Win Vista.

He hecho un diagnostico de la memoria, todo bien.
Hice tambien un diagnostico al disco duro, todo bien.


Os ruego que me ayudeis porque ya no se que hacer.
Siempre con Windows... Siempre Problemas...........

Saludos y Muchas Gracias (un 10 al esfuerzo que estais haciendo por el foro)

Ya que no me respondéis voy a poner información adicional:

He formateado el Windows Vista y he puesto el Windows XP Professional SP2
Tambien me ha salido una pantalla azul.

Causante: NVENETFD.sys

Por lo que he podido buscar en internet... es un driver Ethernet de NVIDIA. También lo he comprobado en mi PC. Esta en la carpeta de controladores NVIDIA, en Ethernet.

He identificado el error con el programa: Debugging Tools for Windows (x86)

Lo he analizado poniendo !analyze -v y me ha salido esto:

Probably caused by : NVENETFD.sys ( NVENETFD+2a82 )

Followup: MachineOwner
---------

0: 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: 0ae0c948, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b4292c22, address which referenced memory

Debugging Details:
------------------

***** 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+ *
************************************************** *******************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a4bb0a9

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0ae0c948

CURRENT_IRQL: 2

FAULTING_IP:
tcpip!ARPRcv+276f
b4292c22 1083f8020f82 adc byte ptr [ebx-7DF0FD08h],al

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from b4292c22 to 805437d0

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8054ffac b4292c22 badb0d00 00000000 80550004 nt!Kei386EoiHelper+0x2834
80550020 b42948da 89f00878 00000002 00000005 tcpip!ARPRcv+0x276f
80550064 b4294a30 89f00878 00000000 000005b4 tcpip!ARPRcv+0x4427
805500b8 b428f3e2 89e2b2b0 00001050 c000021b tcpip!ARPRcv+0x457d
80550140 b428cef5 89bcd238 0a00a8c0 c3cde954 tcpip!IPTransmit+0x17a4
805501a0 b428cb19 00000020 89bcd238 b428f0b6 tcpip!IPFreeBuff+0x634
8055021c b428c836 b42cc5f0 89bcd238 896d6018 tcpip!IPFreeBuff+0x258
805502d4 b428b922 89bcd238 896d602c 000005c8 tcpip!IPRcvPacket+0x296
80550314 b428b84d 00000000 89828440 896d600a tcpip!ARPRcvPacket+0x128
80550350 b7d4cf45 89f3f440 00000000 00000001 tcpip!ARPRcvPacket+0x53
805503a4 b4a8aa82 00767e08 89bb56c0 00000001 NDIS!FddiFilterDprIndicateReceive+0xd4d
00000000 00000000 00000000 00000000 00000000 NVENETFD+0x2a82


STACK_COMMAND: kb

FOLLOWUP_IP:
NVENETFD+2a82
b4a8aa82 39aec4070000 cmp dword ptr [esi+7C4h],ebp

SYMBOL_STACK_INDEX: b

SYMBOL_NAME: NVENETFD+2a82

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NVENETFD

IMAGE_NAME: NVENETFD.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------








NECESITO AYUDA POR FAVOR. GRACIAS Y SALUDOS

sera mejor que sques y pongas tu tarjeta de video otra vez.