Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Foro referente al sistema operativo Windows 7
strangy
Usuario linuxero
Usuario linuxero
Mensajes: 6
Registrado: 11 Sep 2012, 18:45
Contactar:

Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor strangy » 11 Sep 2012, 19:44

Hola a todos. Nunca crei que esto me pasaria a mi y tuviera que pedir ayuda en este foro. Normalmente lo suelo arreglar por mi mismo leyendo, pero veo que esto del pantallazo es muy comun y siempre muy distinto para cada ordenador. Asi que viendo que ya no puedo mas o dejo los datos de mi ordenador y toda la informacion que he podido recabar.

Mi ordenador:

Placa base: ASUS M2N68-AM
Procesador: AMD Phenom X4 9850 Black Edition
Memoria: Kingston KVR800D2N6/2G X 2

La memoria esta recien comprada porque creia que los pantallazos eran por la memoria.
Los pantallazos me suelen salir de todas las maneras. He desinstalado los drivers de la grafica, los del chipset, etc. Los he vuelto a instalar los que vienen en la pagina de ASUS. He reinstalado Windows 7 dos veces.

Aqui os dejo el informe del programa whocrashed. Siempre me dice lo mismo que es por algun bug de algun driver, pero que no sabe de cual es.

Texto:
System Information (local)
--------------------------------------------------------------------------------

computer name: STRANGY-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) 9850 Quad-Core Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 1878253568 total
VM: 2147352576, free: 1975914496



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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Tue 11/09/2012 16:47:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091112-18969-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xC2 (0x7, 0x1097, 0xC0209, 0xFFFFF8A00A1B3570)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 11/09/2012 16:47:51 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr!FltReferenceContext+0xAB)
Bugcheck code: 0xC2 (0x7, 0x1097, 0xC0209, 0xFFFFF8A00A1B3570)
Error: BAD_POOL_CALLER
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Administrador de filtros del sistema de archivos de Microsoft
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Tue 11/09/2012 16:44:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091112-12885-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xA (0xFFFFF6FB7EC000C8, 0x2, 0x0, 0xFFFFF8000294567B)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 11/09/2012 15:44:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091112-12464-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x50 (0xFFFFFA80A8BBE8A8, 0x0, 0xFFFFF800028AEF8C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 11/09/2012 12:48:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091112-11559-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x50 (0xFFFFFA80FF7A4480, 0x0, 0xFFFFF800028E9C0C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 11/09/2012 12:30:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091112-12121-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80017E5810, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.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 which cannot be identified at this time.


On Tue 11/09/2012 12:04:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091112-15818-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80006546C0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.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 which cannot be identified at this time.


On Tue 11/09/2012 11:20:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091112-18018-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800161C3D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.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 which cannot be identified at this time.




Saludos y muchas gracias por vuestra ayuda.

Avatar de Usuario
helheim
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 5001
Registrado: 20 Abr 2008, 11:38
Agradecido : 24 veces
Agradecimiento recibido: 169 veces
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor helheim » 11 Sep 2012, 20:47

Hola, bienvenido al Foro.

Has realizado ya un chkdsk?. Te lo pregunto porque dices que has instalado dos veces Windows 7 y uno de los pantallazos apunta al archivo fltmgr.sys. Este archivo es Administrador de archivos del sistema y podría dar errores (provocando un pantallazo) ante un fallo en el disco.

Comprueba que las conexiones del disco estén bien sujetas.

Un saludo.
La experiencia es una llama que alumbra quemando (Benito Pérez Galdós)

strangy
Usuario linuxero
Usuario linuxero
Mensajes: 6
Registrado: 11 Sep 2012, 18:45
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor strangy » 11 Sep 2012, 21:11

Acabo de hacerselo y tenia errores en un disco secundario al que accedi posiblemente para instalar algun driver.

En el tiempo que has tardado en contestar me ha saltado otro pantallazo. Te lo pego y te comento.


On Tue 11/09/2012 19:37:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091112-12838-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0xC5 (0x18000000408, 0x2, 0x0, 0xFFFFF800029B6B05)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.


On Tue 11/09/2012 19:37:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xC5 (0x18000000408, 0x2, 0x0, 0xFFFFF800029B6B05)
Error: DRIVER_CORRUPTED_EXPOOL
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.


En el momento que me ha saltado estaba jugando a un juego en flash que es por lo que normalmente antes me salian los pantallazos. Tambien tenia un juego de poker independiente del google chrome. Y que yo recuerde, creo que tambien tenia abierto el Aida 64 , pero sin hacer nada.

Saludos y gracias por contestar

Avatar de Usuario
helheim
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 5001
Registrado: 20 Abr 2008, 11:38
Agradecido : 24 veces
Agradecimiento recibido: 169 veces
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor helheim » 12 Sep 2012, 12:29

strangy escribió:Acabo de hacerselo y tenia errores en un disco secundario al que accedi posiblemente para instalar algun driver.
Cómo que para instalar algun driver?.

Cuántos discos duros tienes instalados?.

Qué parámetros usaste con el comando chkdsk?.

strangy escribió:La memoria esta recien comprada porque creia que los pantallazos eran por la memoria.
Cuántos módulos de memoria tienes y cuántos has sustituido?.

El hecho de que te pegue tantos pantallazos distintos hace pensar que pudiera ser de algún módulo RAM.

Un saludo.
La experiencia es una llama que alumbra quemando (Benito Pérez Galdós)

strangy
Usuario linuxero
Usuario linuxero
Mensajes: 6
Registrado: 11 Sep 2012, 18:45
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor strangy » 13 Sep 2012, 19:34

Supongo que para instalar los drivers de la grafica y el chipset de la placa.

Tengo 2 discos duros y me dio error en el que tengo los datos, no el SO.

Primero escribi solo chkdsk, en el disco del SO no me dio errores, en el de datos me los dio, asi que escribi chkdsk /F y me corrigio los errores.

Ese disco duro lo tengo quitado ahora mismo.

Ahora mismo tiene 2 modulos de 2 GB kingston DDR2 a 800Mhz

Antes tenia 2 modulos diferentes de 1 GB cada uno, me daba pantallazos asi que le quite uno. Me seguia dando pantallazos, lo cambie por el otro, seguia dandomelos y compre los dos modulos kingston. Osea, de la memoria ya no creo que sea. Supongo que sera de la placa base pero es que me veo negro para encontrar una para mi procesador!!! Vamos que si veo alguna es algo raro pero muy caras. Por si no lo he dicho antes, mi procesador es un AMD Phenom X4 9850 Black Edition.

Saludos y gracias

Avatar de Usuario
helheim
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 5001
Registrado: 20 Abr 2008, 11:38
Agradecido : 24 veces
Agradecimiento recibido: 169 veces
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor helheim » 13 Sep 2012, 21:38

strangy escribió:Antes tenia 2 modulos diferentes de 1 GB cada uno, me daba pantallazos asi que le quite uno. Me seguia dando pantallazos, lo cambie por el otro, seguia dandomelos y compre los dos modulos kingston. Osea, de la memoria ya no creo que sea. Supongo que sera de la placa base pero es que me veo negro para encontrar una para mi procesador!!!
Esta sería otra posibilidad... Puede que la peor de todas, a decir verdad.

Hace poco tuve un problema "parecido" y finalmente me tocó cambiar la placa base. Y lo peor es que se llevo con ella un módulo de ram de los que tenía.

Un saludo.
La experiencia es una llama que alumbra quemando (Benito Pérez Galdós)

Avatar de Usuario
Souto
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 10665
Registrado: 25 Feb 2008, 10:21
Ubicación: Galicia
Agradecido : 6 veces
Agradecimiento recibido: 647 veces
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor Souto » 14 Sep 2012, 11:18

Es ciertamente enrevesado. Tiene mala leche. Puede ser cualquier cosa y me imagino que estás ya harto de hacer comprobaciones.
Yo no descartaría que un driver te esté haciendo la puñeta. Hay una forma de comprobarlo:
http://support.microsoft.com/kb/244617
Lamentablemente ando muy mal de tiempo como para explicar esto paso a paso.
Mira a ver si te ayuda en algo.

Saludos
Qui dove il mare luccica e tira forte il vento

strangy
Usuario linuxero
Usuario linuxero
Mensajes: 6
Registrado: 11 Sep 2012, 18:45
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor strangy » 15 Sep 2012, 22:08

Perdon por el retraso en mi respuesta. Windows cada vez me da mas fallos. Sobre todo con paginas en flash. He instalado la ultima version de los drivers de NVIDIA.

Ya me da errores de todo tipo. El ultimo es del usb. Yo creo que va a ser la placa, ya que es muy raro que me falle todo.

Un disco duro mal, vale. Lo quito y listo. Me ha vuelto a dar error de ntfs.sys
Un modulo de memoria, vale. Lo cambio por otro y arreglado. ¿Pero 5 modulos de memoria van a estar mal?
Se me reinicia con el error de ubs.sys y al arrancar no me funciona el raton inalambrico ni el disco duro externo. tengo q2ue desenchufarlos y volverlos a enchufar.

En cuanto termine este mensaje hare una comprobacion de los controladores a ver lo que me dice windows con el verifier tal y como me ha puesto souto.

Muchas gracias por vuestra ayuda. A ver si al final puedo arreglarlo o al menos identificar correctamente el error.

Saludos

strangy
Usuario linuxero
Usuario linuxero
Mensajes: 6
Registrado: 11 Sep 2012, 18:45
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor strangy » 17 Sep 2012, 16:19

Aqui os vuelvo a dejar los ultimos que me han salido. Como se especifica al final, hay un total de 51 crash dumps. Estos lson los ultimos 15.

Texto:
On Mon 17/09/2012 11:47:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-12324-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFF8A0FF89B4A0, 0x0, 0xFFFFF800028EABD4, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 17/09/2012 11:47:01 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: fileinfo.sys (fileinfo+0xA2E3)
Bugcheck code: 0x50 (0xFFFFF8A0FF89B4A0, 0x0, 0xFFFFF800028EABD4, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fileinfo.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: FileInfo Filter Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 17/09/2012 10:25:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-11809-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFBC8036D71F78, 0x0, 0xFFFFF880019ABB81, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 17/09/2012 9:15:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-11419-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC5 (0x7, 0x2, 0x1, 0xFFFFF800029B7617)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.


On Mon 17/09/2012 7:02:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-11481-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002906FB2, 0x1, 0x60)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 17/09/2012 3:00:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-12121-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88006343FF8, 0xFFFFF88006343850, 0xFFFFF800028A4619)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Mon 17/09/2012 1:52:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091712-11653-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC5 (0x9000000008, 0x2, 0x0, 0xFFFFF800029B8B05)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.


On Sun 16/09/2012 18:53:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-14258-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x12A66, 0x2, 0x0, 0xFFFFF80002AC40C7)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 16/09/2012 17:58:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-12963-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x34 (0xF06, 0xFFFFFFFFC0000420, 0x0, 0x0)
Error: CACHE_MANAGER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
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 which cannot be identified at this time.


On Sun 16/09/2012 17:20:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-12651-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0xFFFFFA800236BF10, 0x2, 0x0, 0xFFFFF80002888442)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 16/09/2012 11:43:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-17440-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC5 (0x12756, 0x2, 0x1, 0xFFFFF800029F9617)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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 which cannot be identified at this time.


On Sun 16/09/2012 9:42:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-17690-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002BB2F39, 0xFFFFF88006F8FAF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sun 16/09/2012 9:19:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091612-12043-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xC1 (0xFFFFF9800AB24F90, 0xFFFFF9800AB24D83, 0x9BC078, 0x23)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the driver wrote to an invalid section of the special pool.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 15/09/2012 18:25:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-10857-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88002F9A328, 0xFFFFF88002F99B80, 0xFFFFF8800101FDE5)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sat 15/09/2012 17:35:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-11247-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80038FD2D0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.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 which cannot be identified at this time.



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

51 crash dumps have been found and analyzed. Only 15 are included in this report. 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:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 190.38 , NVIDIA Corporation)

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.


Si leeis al final, pone que puede ser de los drivers de nvidia. Pues desde que le he instalado los ultimos que hay en la web de nvidia ma salen mas errores.
A ver si no va a ser de la placa y va a ser de los drivers de verdad...

Avatar de Usuario
cdi32
Usuario linuxero
Usuario linuxero
Mensajes: 6
Registrado: 27 Sep 2012, 17:05
Contactar:

Re: Pantallazo azul. Ya no se que mas hacer. Ayuda por favor

Mensajepor cdi32 » 28 Sep 2012, 13:34

mmm, a mi m epaso algo parecido con tantos errores de golpe y era un dichoso driver de la grafica, (hace tiempo de esto)
Si tines la grafica nvidia pueda ser qu ela grafica de problemas, haz lo siguiente que por probar no pierdes nada y yo lo arreglé así:

1-desinstalas los drivers de la grafica, todos¡¡ incluido softawares paralelos etc
2-limpia todos los registros invalidos con un programa de limpieza de registros asi ya de paso te borrara registros obsoletos y matas 2 pajaros de 1 tiro (haz un back up por si acaso) :lol:
3- despues de hacer estos pasos reinstala los drivers de la grafica actualizados, reinicias y a ver que tal.

como consejo opcional de comprobación en caso de seguir igual:

1-reinstalar el s.o en modo de reparación y volver a reinstalar la actualización de la grafica
2-no se bien si tu grafica está en algún slot de tu pc o va integrada en caso de ir en un slot comprueba en tu bios que el slot donde esta dicha targeta esta correectamente puesto ya que algunas targetas graficas pueden ir a 16x o son pci express o simplemente pci normal o agp ya mas obsoleto, comprueba dicha compatibilidad y no estaria de mas actualizar la biso de tu pc mirando en el fabricante exactamente el modelo de tu pc e instalar dicha bios actualizada (en w7 tarea muy sencilla)
3- si con esto sigue igual y por lo que mencionas en los errores hace mencion de la grafica, coje mete otra grafica en un slot , la que sea +- decente y prueba a ver
ya de paso si abres el pc comprueba que las conexiones a la grafica de alimentación estan bien fijadas.
Sin con todo esto te sigue igual o te da otros errores "extraños" ya seguramente tienes dañada la placa base.
Espero pudier aayudarte y ya nos diras que tal va la cosa.

Un saludo


Volver a “Windows 7”

¿Quién está conectado?

Usuarios navegando por este Foro: Bing [Bot] y 3 invitados