Foro de elhacker.net

Bueno, lo primero, saludos a todos!
Tengo una duda y espero que puedan resolvérmela. Verán, desde que instalé w7 hace unos meses, me salen pantallazos azules de vez en cuando, cosa que con windows XP en dos años no me ha pasado. He formateado varias veces, pero me siguen saliendo, y no se si pueden ser de compatibilidad, o de que... ¿?
Creo recordar que hasta fecha de hoy me ha dado 3 distintos, con las siguientes cadenas de comprobación de error:
 1) BAD_POOL_CALLER
 2) SYSTEM_PTE_MISUSE
 3) MEMORY MANAGEMENT
Sobre todo, los dos primeros son los más frecuentes. Y la cosa es que con XP apenas me ha dado pantallazos en largo tiempo. ¿Alguien tiene alguna idea?
Gracias con antelación!

Hola juanma

Puede que tengas que actualizar los controladores: LAN y demás...

un saludo.

A mi me ocurrió con un equipo, se colgaba aleatóriamente y con mensajes poco aclaratórios, al final el problema estaba en un módulo de memoria.

Prueba la memoria con Memtest, puede que tengas algún módulo defectuoso.
http://www.memtest.org/

He probado a analizar con drivergenius y me da mensaje de que tengo todos los drivers actualizados, voy a probar con drivereasy y después le haré el test de memoria, y si no probaré a dejar cada módulo por individual por un tiempo (tengo 1 kingston de 2gb y otro hynix de 1gb)
Un saludo!

---

Buenas! Ya he actualizado los drivers con drivereasy, con que ahora me esperaré a ver si me sigue dando problemas. Os iré informando! En caso de que me sigan dando pantallazos, ya probaré lo de la ram.
Gracias a todos :)

---

Bueno, hasta ahora sigue sin haberme vuelto a dar ningún pantallazo azul, ojalá se haya solucionado. Muchas gracias! Si me vuelve a aparecer el problema aviso.
Un saludo

Vaya! Parece que por hablar me ha vuelto el problema -.-' jeje
Acabo de quitarle el módulo de un 1GB, a ver qué resultados me da
:D

lo mas probable en ese caso! es que tengas la memoria ram defectuosa!! metele un buen tested para corregir algun sector defectuoso!! 

:O Se pueden reparar los sectores en la ram? Pues entonces mejor le paso el memtest; creía que lo único que hacía era analizar el módulo.
Gracias! :)

No no se pueden, se pueden aislar con una prueba intensiva, pero si se daña, se daña, punto.

Difiero con la teoría de la memoria RAM, mirate bien lo del pantallazo, aquí tienes unas utilidades

 http://daraxblog.blogspot.com.es/2011/04/utilidades-para-leer-los-pantallazos.html

Ayer me volvió a dar otro, con tan solo el módulo de 2GB que no creo que esté defectuoso, es de hace un año y pico y el otro tiene al menos 4 o 5 años.
Probaré el Who Crashed a ver qué me dice, porque el bluescreenview básicamente me dice las cadenas de comprobación que puse al principio, lo demás no sé como ultilizarlo para buscar solución.
Vale vale, eso si lo veo más lógico, que los aisle.
En breves postearé a ver qué me dice el Who Crashed.
Hasta pronto!

Os copio los detalles del Who Crashed (parece ser que tengo que actualizar fetn62.sys, pero ahora a ver si lo encuentro.

Welcome to WhoCrashed (HOME EDITION) v 4.01
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.

Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

computer name: JUANMA-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Pentium(R) D CPU 2.80GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 2145902592 total
VM: 2147352576, free: 1966538752




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 18/01/2013 21:25:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011813-41953-01.dmp
This was probably caused by the following module: fetn62.sys (fetn62+0x172F)
Bugcheck code: 0xDA (0x504, 0xFFFFFFFFC06B1DA0, 0x11, 0x563B4)
Error: SYSTEM_PTE_MISUSE
file path: C:\Windows\system32\drivers\fetn62.sys
product: VIA Rhine Family Fast Ethernet Adapter
company: VIA Technologies, Inc.
description: NDIS 6.2 miniport driver
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: fetn62.sys (NDIS 6.2 miniport driver, VIA Technologies, Inc. ).
Google query: VIA Technologies, Inc. SYSTEM_PTE_MISUSE



On Fri 18/01/2013 21:25:48 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fetn62.sys (fetn62+0x172F)
Bugcheck code: 0xDA (0x504, 0xFFFFFFFFC06B1DA0, 0x11, 0x563B4)
Error: SYSTEM_PTE_MISUSE
file path: C:\Windows\system32\drivers\fetn62.sys
product: VIA Rhine Family Fast Ethernet Adapter
company: VIA Technologies, Inc.
description: NDIS 6.2 miniport driver
Bug check description: This indicates that a page table entry (PTE) routine has been used in an improper way.
There is a possibility this problem was caused by a virus or other malware.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: fetn62.sys (NDIS 6.2 miniport driver, VIA Technologies, Inc. ).
Google query: VIA Technologies, Inc. SYSTEM_PTE_MISUSE



On Wed 16/01/2013 15:46:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011613-23906-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xB191C)
Bugcheck code: 0x1A (0x5100, 0xFFFFFFFFC04A9C08, 0x1, 0xFFFFFFFF8B3DE929)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

fetn62.sys (NDIS 6.2 miniport driver, VIA Technologies, Inc. )

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.