DarkSun

en modo normal no aparece el controlador de mouse es como si no estuviera instalado nunca, eso pasa a veces cuando apago el pc , reinicio en modo aprueba de fallos o reinicio en la ultima configuracion buena conocida pero no es la idea hacerlo siempre jejej saludos.

Hola saludos mi mouse comenzo a fallar no se si sea el mouse o es la tarjeta (la entrada ps2) solo funciona en modo aprueba de fallos en modo normal tengo win7 alguna idea? gracias

cago el link

gracias

gracias

gracias

gracias

cambie el disipador del procesador pero siguenlos pantallazos azules , ahora solo se repite driver irq not lees or equal o algo asi . apenas pueda pongo pasta disipadora en la tarjeta saludos. el pantallazo azul de hoy :invertido: Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 30-07-2013 21:52:51 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown (0x00000000) Bugcheck code: 0x50 (0xFFFFF8803CCC3CF4, 0x0, 0xFFFFF8800416073B, 0x2) Error: PAGE_FAULT_IN_NONPAGED_AREA 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. 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: Unknown . Google query: Unknown PAGE_FAULT_IN_NONPAGED_AREA Conclusion 1 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: unknown 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. aca el de recien Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Tue 30-07-2013 22:56:58 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown () Bugcheck code: 0x4E (0x9A, 0x33627, 0x0, 0x0) Error: PFN_LIST_CORRUPT 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. 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: Unknown . Google query: Unknown PFN_LIST_CORRUPT Conclusion 1 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: unknown 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. CERRAR POR FAVOR EL PROBLEMA ESTA EN UNA RAM O UN SLOT DE LA TARJETA MADRE SAQUE LA RAM TENGO EL PC FUNCIONANDO CON 4 GB Y NO ME HA DADO PANTALLAZO AZUL DESDE QUE SAQUE LA RAM GRACIAS

a la tarjeta nunca le he puesto pasta disipadora , el error no es el unico que dio ese fue el ultimo por ahi voy a buscar el post antiguo y lo pongo aqui .. , ahora estoy jugando wow tengo que minimizar no ver el wow y baja la temperatura , espero que baje y sigo jugando , nose que puedo hacer para solucionar la wea de temperatura. este es el post anterior http://www.chilecomparte.cl/topic/2126949-hola-tengo-pantallazos-azules-denuevo/

los pantallazos azules los he posteado aca varias veces.. ya formatie el pc y sigue lo mismo , los pantallazos azules aparecen cuando juego WoW ,o cuando veo peliculas, y es por que la temperatura sube bastante despues mando un pantallazo azul .. voy a poner los ultimos informes del whocrashed. System Information (local) computer name: KOMOGATOPALAGUA windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel® Core i5-2310 CPU @ 2.90GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 4294967295 total VM: 2147352576, free: 1966710784 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sun 28-07-2013 10:24:11 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown (0x00000000) Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800034D07D5) Error: IRQL_NOT_LESS_OR_EQUAL 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. 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: Unknown . Google query: Unknown IRQL_NOT_LESS_OR_EQUAL Conclusion 1 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: unknown 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. este fue el ultimo saludos.

lo arme yo , puse la pasta disipadora en el procesador , me dicen tambien que puede que la placa este en corte que ponga unas gomas en la base para asilarla de la carcasa.

pasa cuando juego wow , tengo dudas con el disipador y con la pasta, solo puse en el procesador pero ni idea si este bien puesta

Hola tengo pantallazos azules en mi pc , descargue aida para ver las temperaturas , ya habia formateado el pc y seguia con el problema ahora me fijo en las temperaturas y me dan 79°C , 80 °C , no creo que sea normal , se debe a eso los pantallazos azules??. saludos

Saludos en un pc de un amigo se instalo este virus www.delta-search.com lo bajo despues de poner unos codec de HDvid codec 1 le cambia la pagina de inicio hace que el pc seeaaaaaaaaaa muy lento y cosas asi . pase malwares y cccleaner pero no pasa nada alguna idea? saludos

Hola abri el gabinete del pc y lo estoy trabajando sin tapa y no tengo ningun pantallazo azu desde ayer que lo abri . saludos.

Hola tengo los pantallazos azules denuevo formatie , acabo de poner pasta disipadora (me dijeron que podria ser la temperatura).. pasa mas seguido cuando juego WoW , pero hoy no he jugado y ya van como 5 tengo el whocrashed con el ultimo reporte, pero me gustaria saber como revisar problemas en la ram o la tarjeta de video , disco duro , BIOS algo ..nose lo que sea :kicking: datos de mipc segun whocrashed windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel® Core i5-2310 CPU @ 2.90GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 4294967295 total tengo instaladas 8 GB RAM ... VM: 2147352576, free: 1940606976 tarjeta de video NVIDIA Geforce GT 220 1 GB reporte whocrashed On Thu 11-07-2013 0:46:24 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: Unknown (0x00000000) Bugcheck code: 0x1A (0x41287, 0x3002, 0x0, 0x0) Error: MEMORY_MANAGEMENT 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. 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: Unknown . Google query: Unknown MEMORY_MANAGEMENT Conclusion 1 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: unknown 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. saludos.

Eso trate de bajar un plug in de ma-config pero no esta en linea , si alguien tiene algun programa para sacar el archivo de la tarjeta de red que me sirva? par aun pc sin driver de red saludos

el archivo media feria no existe alguien lo tiene por ahi o que lo pueda resubir?

ya desintale el alcohol (daemon tools) voy a probar antes de formatear saludos editado: volvio aparecer pantalla azul , cual win 7 es mejor? Como puedo saber que placa o que drivers necesito tener antes de formatear?? saludos,

Saludos hace tiempo que no salia el pantallazo azul pero estos dias ya a aparecido 4 o 5 veces... incluso cuando reincio despues de pantallazo azul , inicia windows y vuelve otro pantallazo azul , la lista es variada asi que voy a pegar lo que saque de mes drivers... actualize driver de bios y tarjeta de video pero sigue igual IRQL_NOT_LESS_OR_EQUAL SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M CACHE_MANAGER BAD_POOL_HEADER VIDEO_SCHEDULER_INTERNAL_ERROR IRQL_NOT_LESS_OR_EQUAL SYSTEM_SERVICE_EXCEPTION DRIVER_IRQL_NOT_LESS_OR_EQUAL lo que dice whocrashed salen 12 pantallazos azules listados.. System Information (local) computer name: KOMOGATOPALAGUA windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel® Core i5-2310 CPU @ 2.90GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 4294967295 total tengo 8 GB de memoria RAM sera que una ram ta mala??? VM: 2147352576, free: 1932447744 Crash Dump Analysis Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 14-06-2013 4:35:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\061413-40154-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x402C, 0x2, 0x0, 0xFFFFF8000300E977) 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 Fri 14-06-2013 4:35:12 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: sptd.sys (sptd+0x4B5FC) Bugcheck code: 0xA (0x402C, 0x2, 0x0, 0xFFFFF8000300E977) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\sptd.sys product: SCSI Pass Through Direct company: Duplex Secure Ltd. description: SCSI Pass Through Direct Host 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. 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: sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.). Google query: sptd.sys Duplex Secure Ltd. IRQL_NOT_LESS_OR_EQUAL On Fri 14-06-2013 4:33:38 GMT your computer crashed crash dump file: C:\Windows\Minidump\061413-35817-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CF7) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002F61CF7, 0xFFFFF880061B1568, 0xFFFFF880061B0DC0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 a system thread 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 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 Fri 14-06-2013 3:13:56 GMT your computer crashed crash dump file: C:\Windows\Minidump\061313-65380-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x34 (0x50853, 0xFFFFF8800767D5F8, 0xFFFFF8800767CE50, 0xFFFFF80003109AB7) 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 Fri 14-06-2013 2:33:43 GMT your computer crashed crash dump file: C:\Windows\Minidump\061313-30498-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x19 (0x3, 0xFFFFF8000325CAC0, 0xFFFFF8000325B0C0, 0xFFFFF80003250FC0) Error: BAD_POOL_HEADER 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 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. On Fri 14-06-2013 2:30:06 GMT your computer crashed crash dump file: C:\Windows\Minidump\061313-29421-01.dmp This was probably caused by the following module: watchdog.sys (watchdog+0x122F) Bugcheck code: 0x119 (0x7000000, 0xFFFFFA80094DB010, 0xFFFFFA800D4EB010, 0xFFFFFA800C321410) Error: VIDEO_SCHEDULER_INTERNAL_ERROR file path: C:\Windows\system32\drivers\watchdog.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Watchdog Driver Bug check description: This indicates that the video scheduler has detected a fatal violation. 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 13-06-2013 5:09:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\061313-34975-01.dmp This was probably caused by the following module: Unknown (0xFFFFF800030E0FC0) Bugcheck code: 0xA (0x12F8, 0x2, 0x1, 0xFFFFF800030EF468) Error: IRQL_NOT_LESS_OR_EQUAL 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. 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: Unknown . Google query: Unknown IRQL_NOT_LESS_OR_EQUAL On Wed 12-06-2013 16:09:27 GMT your computer crashed crash dump file: C:\Windows\Minidump\061213-33353-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030F5D6C, 0xFFFFF8800BBFCEE0, 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 Wed 12-06-2013 15:27:21 GMT your computer crashed crash dump file: C:\Windows\Minidump\061213-33930-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xD1 (0x830, 0x2, 0x0, 0xFFFFF880047BA01D) Error: DRIVER_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 a kernel-mode driver attempted to access pageable 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. 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 10-06-2013 19:28:06 GMT your computer crashed crash dump file: C:\Windows\Minidump\061013-27440-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033DFD42, 0xFFFFF88008C17EF0, 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 Mon 10-06-2013 3:46:55 GMT your computer crashed crash dump file: C:\Windows\Minidump\060913-27955-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xD1 (0x57FFFB, 0x2, 0x0, 0xFFFFF88001464D14) Error: DRIVER_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 a kernel-mode driver attempted to access pageable 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. 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 10-06-2013 3:40:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\060913-27549-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CF7) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800475FCF7, 0xFFFFF880053CD568, 0xFFFFF880053CCDC0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 a system thread 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 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. Conclusion 12 crash dumps have been found and analyzed. 2 third party drivers have 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: sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.) unknown 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. Ojala me puedan ayudar. saludos. Intente quitar el dirver de sonido otra vez entrando al modo aprueba de fallos pero no existe el driver , que se puede hacer??

hola gracias por las respuestas instale drivers de audio pero los desinstale cuando me empezo a dar el error , fue lo primero que se me ocurrio pero ya no esta instalado no caxo que otra wea pueda ser

Esto dice el whocrashed windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: GenuineIntel Intel® Core i5-2310 CPU @ 2.90GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 4294967295 total (tengo instalados 8 GB) VM: 2147352576, free: 1902882816 On Wed 15-05-2013 20:50:55 GMT your computer crashed crash dump file: C:\Windows\Minidump\051513-24554-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x19 (0x3, 0xFFFFFA800B7DF120, 0xFFFFFA800B7D1220, 0xFFFFFA800B7DF120) Error: BAD_POOL_HEADER 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 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. ?? saludos

Hola no habia salido el famoso pantallazo azul pero recien salio el codigo es BAD_POOL_HEADER. lei por ahi tenia algo que ver con el hardware. como dato siempre sale cuando estoy jugando WoW ayuda porfa

vale gracias pero pero no quiero cambiar windows denuevo pero si voy a deshabilitar lo del reinicio y posteo gracias.

Hola hace 3 o 4 dias que salio por primera vez el pantallazo azul y hoy se volvio a repetir los datos de mi pc win7 ultimate 64 bits intel core i5-2310 2.9 Ghz 8 gb RAM Nvidia GEforce GT 220 500 GB disco duro despues del pantallazo me puse a leer por ahi y se genero un archivo dmp que no se como leerlo y en el caso que lo supiera leer no sabria que buscar :invertido: . el caso es que hace poco mas menos en la fecha de inicio de los pantallazos instale codec para ver una pelicula sera eso ?. como leo ese archivo o como se lo que esta causando el pantallazo azul ?.. gracias.