Pantallazos azules (fuente de alimentación)

[backfuture]

@Kernel1.0:

Mira la salud de tu disco duro, los dos últimos errores que comentas apuntan hacia ahí.

El Spin Retry Count aumentó desde que lo vi la última vez hace meses, pero vamos, los discos no me preocupan.

Creo que puede venir por los drivers de la gráfica, que me acabo de fijar que son para windows vista, mi gráfica no tiene soporte para windows 7.

http://support.amd.com/us/gpudownload/windows/Legacy/Pages/radeonaiw_vista32.aspx?type=2.4.1&product=2.4.1.3.13&lang=English

En breves me compraré la 5770, esperemos que sea problema de los drivers de la gráfica y no de otra cosa

[backfuture]

Otro más:

irql_not_less_or_equal

Información adicional del problema:
BCCode: a
BCP1: FFFFFFFC
BCP2: 00000002
BCP3: 00000000
BCP4: 82A7B99F

Edito: otro más

Información adicional del problema:
BCCode: a
BCP1: FFFFFFFC
BCP2: 00000002
BCP3: 00000000
BCP4: 82A8499F

Pues parece que es del disco duro, por cada bsod un puntito más a Spin retry count, ya van 13

[Fassou]

Bájate las SeaTools y chequea el HDD, porque no tiene buena pinta :nono:

Salu2!

[Mystique]

si no te pasa las seatools, prueba a cambiar el disco duro de sitio en la caja, de calbe de alimentacion y de datos hasta que pruebes todas las combinaciones (y cada vez seatools rapido). a mi me fallaba uno nuevo por eso y hasta que di con el fallo me volvi loco

[Kernel1.0]

Sigue teniendo pinta de disco duro. Bájate el BlueScreenView o el WhoCrashed y analiza el directorio C:\Windows\minidump en busca de volcados de memoria, a ver si sacas algo en claro de ellos.

[backfuture]

Es normal que el Seatools tarde eones en hacer el test?

[Mystique]

el largo si, los cortos… no

[backfuture]

Me falta por pasar el dst largo, los demás estan pasados. El Hirens tenia algun programa para comprobar el disco, a la noche probaré

[backfuture]

Los 2 test´s largos pasados

Pongo el reporte del WhoCrashed:

! System Information (local)
–------------------------------------------------------------------------------
! computer name: TRENCK-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon(tm) II X3 450 Processor AMD586, level: 16
3 logical processors, active mask: 7
RAM: 2143453184 total
VM: 2147352576, free: 1989976064
! --------------------------------------------------------------------------------
Crash Dump Analysis

---

! Crash dump directory: C:\Windows\Minidump
! Crash dumps are enabled on your computer.
! On Mon 29/11/2010 12:48:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112910-16395-01.dmp
This was probably caused by the following module: afd.sys (afd+0x28CAF)
Bugcheck code: 0xA (0x4, 0x2, 0x0, 0xFFFFFFFF82AA399F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Sistema operativo Microsoft Windows
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 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 29/11/2010 12:48:28 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: afd.sys (afd+0x28CAF)
Bugcheck code: 0xA (0x4, 0x2, 0x0, 0xFFFFFFFF82AA399F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\afd.sys
product: Sistema operativo Microsoft Windows
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
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 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 Sun 28/11/2010 3:27:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112810-19515-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFC, 0x2, 0x0, 0xFFFFFFFF82A8199F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 28/11/2010 3:25:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112810-14929-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFC, 0x2, 0x0, 0xFFFFFFFF82A8499F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 28/11/2010 3:21:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112810-15038-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFFFC, 0x2, 0x0, 0xFFFFFFFF82A7B99F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 Fri 26/11/2010 12:36:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112610-17425-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0x6, 0x2, 0x0, 0xFFFFFFFF82A6B99F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 23/11/2010 22:56:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112310-18501-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x1BE77)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFFFFF82A74F95)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 23/11/2010 20:23:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112310-20404-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB8E8A)
Bugcheck code: 0xA (0x2A, 0x2, 0x0, 0xFFFFFFFF82AAF99F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft Windows
company: Microsoft Corporation
description: Controlador Win32 multiusuario
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 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 Sun 21/11/2010 14:33:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112110-16988-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x46F6B)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft Windows Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
! On Wed 17/11/2010 3:00:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111710-15771-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xBDD4E)
Bugcheck code: 0x4E (0x99, 0x734D2, 0x2, 0x17C01)
Error: PFN_LIST_CORRUPT
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft Windows
company: Microsoft Corporation
description: Controlador Win32 multiusuario
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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 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 16/11/2010 0:20:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111610-13681-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85903)
Bugcheck code: 0xFC (0xFFFFFFFF92433B3C, 0x12A90963, 0xFFFFFFFF92433AC8, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
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 an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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 31/10/2010 5:10:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103110-15147-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x85903)
Bugcheck code: 0x1A (0x41287, 0x13, 0x0, 0x0)
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 which cannot be identified at this time.
! On Sat 30/10/2010 13:10:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\103010-14367-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xEC9CB)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF82B37B58, 0xFFFFFFFF82B37B58, 0xFFFFFFFF82B37B50)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft Windows
company: Microsoft Corporation
description: Controlador Win32 multiusuario
Bug check description: This indicates that a pool header is corrupt.
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 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 Thu 28/10/2010 23:27:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102910-13962-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x4682B)
Bugcheck code: 0xA (0x13, 0x2, 0x0, 0xFFFFFFFF82A8A99F)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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 17/10/2010 23:06:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101810-17908-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0xCA7B)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF86D1C320, 0x5246704E, 0xFFFFFFFF86D1C320)
Error: BAD_POOL_HEADER
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 that a pool header is corrupt.
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 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.

[Fassou]

Pues si te pasa los largos, entonces drivers, drivers y drivers :mudo:

Pasa de los oficiales de Gigabyte y bájate los últimos drivers de AMD para tu placa y gráfica, los de Realtek para el sonido y red, etc …

Salu2!

PD: si entonces te falla, sólo te quedaría pesar en que la placa esté tocada :nono: aunque una fuente Tacens siempre es candidata en estos casos.

[Kernel1.0]

Que cosa mas rara, cada BSOD parece que apunta a un archivo diferente y hasta a uno de DX, prueba a actualizarlo y a subir un poco el voltaje de las memorias.

[backfuture]

Otro totalmente diferente:

Información adicional del problema:
BCCode: 7f
BCP1: 0000000D
BCP2: 00000000
BCP3: 00000000
BCP4: 00000000

[backfuture]

Voy a meter xp, porque esto es desquiciante.

[backfuture]

Ni un solo pantallazo azul con xp, toco madera.

Gracias por los consejos!

[backfuture]

Me han salido varios (tema drivers, supongo que por no instalar los del chipset) y hoy uno nuevo:

crash dump file: D:\WINDOWS\Minidump\Mini122110-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x22F43)
Bugcheck code: 0x19 (0x20, 0xFFFFFFFF89369FC8, 0xFFFFFFFF89369FC8, 0xA000001)
Error: BAD_POOL_HEADER
file path: D:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft Windows
company: Microsoft Corporation
description: Sistema y núcleo de Windows NT
Bug check description: This indicates that a pool header is corrupt.
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.

Lo más curioso es que me sale al entrar a un chat de un foro

Sumo este tambien, en la misma situación:

crash dump file: D:\WINDOWS\Minidump\Mini121910-03.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x23D53)
Bugcheck code: 0x1000000A (0x0, 0x1C, 0x1, 0xFFFFFFFF804FAD53)
Error: CUSTOM_ERROR
file path: D:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft Windows
company: Microsoft Corporation
description: Sistema y núcleo de Windows NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[backfuture]

Metí windows 7 con los últimos drivers y me sale el mismo pantallazo, dirigido a ntkrpamp.exe

[backfuture]

Voy a dejar de probar software y empezar por pedir una fuente de alimentación

[backfuture]

A ver que me decíis a esto:

El voltaje normal del micro está en 1,367 más o menos, y viendo fotos como esta…

AMD Athlon II X2 265 and X3 450 Processsor Review-Hi Tech Legion-AMD Athlon II X2 265 and X3 450 Processsor Review

Vamos, que la fuente está cascada y entrega más voltaje no??

Alguna fuente con las tres B´s? Hice este test ( http://extreme.outervision.com/psucalculator.jsp ) y con una de 300W me llega, así que con una BUENA de 400W me sobra, pero quiero opiniones antes de comprar, no vaya a ser que me pase como con la Tacens

[backfuture]

Solución: Cambiar de placa base, la ga-880gm-ud2h tenía como voltaje mínimo para la ram 1.6, y las mushkin trabajan a 1.5v