BSOD! ayuda plss

[toretore]

Hola a tod@s! a veces me saltan los stop y suelen ser diferentes, casi nunca iguales, aunque se repiten a veces. Tengo 2gb de ram en ddr3 kingston 1333. No hace mucho que lo tuve en overclock y me da miedo que tenga algo que ver porque se me murio en la bios. En una ocasion me canse y le deje en stock pero con el unlock porque tengo el phenom ii 545, ahora b45, le hice un par de bench con el prime y todo bien y nose q puede ser, si tengo q formatear lo hare pero si es de software y me podeis ayudar mucho mejor ;)
si necesitan algo pidanlo. espero puedan ayudarme y muchas gracias de antemano!!

[LinCys]

una imagen del error que te manda ,de la nada te salen los mensajes ? :arrow:

[toretore]

analice con windbg de uno de los dumps que tengo, nose si sera normal tener mas de uno en la carpeta.

 

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\051610-17971-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
************************************************** **************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
************************************************** **************************
Executable search path is:
************************************************** *******************
* 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+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`0365e000 PsLoadedModuleList = 0xfffff800`0389be50
Debug session time: Sun May 16 23:33:33.359 2010 (GMT+2)
System Uptime: 0 days 7:45:26.577
************************************************** *******************
* 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+ *
************************************************** *******************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...................................
Loading User Symbols
Loading unloaded module list
........
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff88002f45208, 2, 0, fffff800036d5690}

***** 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 ***
*** ***
************************************************** ***********************
************************************************** *******************
* 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+ *
************************************************** *******************
Probably caused by : ntoskrnl.exe ( nt+77690 )

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

2: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff88002f45208, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800036d5690, 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 ***
*** ***
************************************************** ***********************
************************************************** *******************
* 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.

MODULE_NAME: nt

FAULTING_MODULE: fffff8000365e000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffff88002f45208

CURRENT_IRQL: 0

FAULTING_IP:
nt+77690
fffff800`036d5690 488baf88200000 mov rbp,qword ptr [rdi+2088h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from fffff800036cdb69 to fffff800036ce600

STACK_TEXT:
fffff880`08bde898 fffff800`036cdb69 : 00000000`0000000a fffff880`02f45208 00000000`00000002 00000000`00000000 : nt+0x70600
fffff880`08bde8a0 00000000`0000000a : fffff880`02f45208 00000000`00000002 00000000`00000000 fffff800`036d5690 : nt+0x6fb69
fffff880`08bde8a8 fffff880`02f45208 : 00000000`00000002 00000000`00000000 fffff800`036d5690 fffffa80`0513f828 : 0xa
fffff880`08bde8b0 00000000`00000002 : 00000000`00000000 fffff800`036d5690 fffffa80`0513f828 61007600`6c00c100 : 0xfffff880`02f45208
fffff880`08bde8b8 00000000`00000000 : fffff800`036d5690 fffffa80`0513f828 61007600`6c00c100 16000000`6f007200 : 0x2


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt+77690
fffff800`036d5690 488baf88200000 mov rbp,qword ptr [rdi+2088h]

SYMBOL_NAME: nt+77690

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

y con el bluescreen el ultimo de ellos.

==================================================
Dump File : 090310-18548-01.dmp
Crash Time : 03/09/2010 23:31:50
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041284
Parameter 2 : fffff980`10a83001
Parameter 3 : 00000000`000027f2
Parameter 4 : fffff780`c0000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+1b52
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\090310-18548-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600

==================================================
gracias de nuevo!

[Knives]

Tienes Windows XP 64 bits o que sistema operativo tienes?

Es que en la red hay varios con tu mismo problema, alguno lo han resuelto formateando :), es problema de drivers

http://www.bleepingcomputer.com/forums/topic328680.html

http://www.sevenforums.com/graphic-c...ng-bsod-_.html

http://support.microsoft.com/kb/955087/es

[toretore]

Tengo w7 y hace ya bastante que lo instale, los primeros stops fueron al principio pero ahora son mas reiterados. os dejo una lista con todos ellos por si se puede solucionar sin formatear. a proposito, le hice un sfc scannow y algunos de los errores no pudieron repararse, si tiene algo q ver...

==================================================

 

Dump File : 090610-14851-01.dmp
Crash Time : 06/09/2010 5:50:10
Bug Check String : REFERENCE_BY_POINTER
Bug Check Code : 0x00000018
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04103790
Parameter 3 : 00000000`00000002
Parameter 4 : ffffffff`ffffffff
Caused By Driver : SCSIPORT.SYS
Caused By Address : SCSIPORT.SYS+18
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\090610-14851-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 090310-18548-01.dmp
Crash Time : 03/09/2010 23:31:50
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041284
Parameter 2 : fffff980`10a83001
Parameter 3 : 00000000`000027f2
Parameter 4 : fffff780`c0000000
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+1b52
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\090310-18548-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 090310-14008-01.dmp
Crash Time : 03/09/2010 16:09:14
Bug Check String : INTERRUPT_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000003d
Parameter 1 : fffff880`02ffaf20
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`038799c6
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\090310-14008-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 090310-14991-01.dmp
Crash Time : 03/09/2010 15:51:52
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`021dc3f0
Parameter 3 : fffffa80`023dc3f0
Parameter 4 : fffffa80`021dc3f0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70740
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\090310-14991-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 071310-12854-01.dmp
Crash Time : 13/07/2010 6:29:15
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa80`02c6abba
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\071310-12854-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 071010-13946-01.dmp
Crash Time : 10/07/2010 4:03:18
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffffa80`02cb3bba
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\071010-13946-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 061310-14008-01.dmp
Crash Time : 13/06/2010 20:49:39
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`02b1f748
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5f3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\061310-14008-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052810-12870-01.dmp
Crash Time : 28/05/2010 12:04:27
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`02bbf7b8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5f3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052810-12870-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052310-13603-01.dmp
Crash Time : 23/05/2010 23:28:38
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`02979038
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5f3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052310-13603-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 052110-13806-01.dmp
Crash Time : 21/05/2010 1:21:48
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`02c104f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4a5f3c
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\052110-13806-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 051710-14414-01.dmp
Crash Time : 17/05/2010 16:32:23
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`02b86028
Parameter 3 : 00000000`b6254000
Parameter 4 : 00000000`00000145
Caused By Driver : hal.dll
Caused By Address : hal.dll+12903
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051710-14414-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600
==================================================

==================================================
Dump File : 051610-17971-01.dmp
Crash Time : 16/05/2010 23:35:40
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : fffff880`02f45208
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff800`036d5690
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+70600
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16617 (win7_gdr.100618-1621)
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\051610-17971-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7600

==================================================

SALUDOS Y GRACIAS!

[Knives]

Que tal, bueno he estado revisando este tema, es interesante esto de los BSOD, aunque suelen tener causas diferentes, por ejemplo en este foro hacen un diagnostico bien detallado con muchas herramientas, http://www.pchelpforum.com/blue-scre...death-ugg.html, al final las posibles causas para estos problemas son:

1. Problema de Drivers, por ejemplo de la tarjeta u otro componete instalado, por lo que seria bueno que coloques las especificaciones de tu PC.

2. Que la fuente no proporcione el voltaje necesario o que la placa no trasmita los voltajes correctos, cosa que descartaron ya que era una buena fuente, y verificaron el voltaje con software.

3. Que la placa tenga algun daño debido al tiempo o desgate, por ejemplo capacitadores reventados, etc. Verifica que todo este Ok en tu placa.

4. Que haya habido algun daño de hardware por el overclock o alguna mala configuración, por lo que se verifica con el Spedfan y el CPUZ los voltajes para verificar sus valores y las temperaturas

5. Que haya algun problema de los dispositivos instalados, se saco la tarjeta de video y se la cambio pero siguio dando los mismos problemas.

6. Problemas con el S.O.

Al final se llego a la conlusion de que era un problema de hardware, especificamente del North bridge de la placa ,ya que se verificó que todo lo demas estaba OK, y se recomendarons posibles soluciones como ultimo recurso como resetear totalmente la bios y actualizarla, ya que se habia probado ya todo lo anterior, y al final lo unico que quedaba era cambio de hardware, especificamente la placa y las memorias.

Puedes chequear los parametros que se verifican en ese post para ver en que estado está tu PC.

Seria bueno que coloques mas detalles de tu PC, trata de colocar voltajes temperaturas, especificaciones, etc, varios usuarios del foro hacen overclock , tal vez este algo mal configurado en tu PC y se pueda ajustar.

Tambien revisa el estado de tu hardware, capacitadores, partes oxidadas, polvo, etc

Si quieres probar soluciones generales, prueba reseteando la bios y actualizandola, y/o formateando completamente y reinstalado nuevamente todo el sistema operativo.

Si luego siguen ocurriendo los BSOD, tal vez tengas algun daño en la placa u otro componente, es harta chamba revisar todo :) pero tu PC lo vale.

Slds.

[toretore]

Hola de nuevo. Os dejo las especificaciones del pc. Phenom ii x2 545 unlock b45 (con los voltajes en stock desde los primeros bsod, pero siguen saltando) 3.0 ghz - asus knight II - asus m4a785td v evo - kingston ddr3 1333 1x2gb - xfx hd5770 - seagate 7200 2x500gb - tecnimax atx 600w - win7 64.

Os comento, no hace mucho tuve un problema de la fuente y es que cada vez que encendía la regleta sin darle al power de la torre se encendía el solo, y casualmente, desde que me tira la mayoría de estos errores ya no sucede, puede que tenga algo que ver..? Las temp están bien, aunque las del core no puedo estar del todo seguro, porque tengo un bug por el unlock y me tengo que fiar del sensor del bios. Aún así parece todo correcto, los voltajes ahora están en stock si prefieren dejo un reporte. La placa esta perfecta. Lo que mas miedo me dio fue lo del north bridge, como puedo verificar que está bien? no hace mucho que actualice la bios.. Gracias de nuevo. Saludos!!

[Solidus J2K]

Primero prueba el sistema con la configuración por defecto, sin el unlock (además para estabilizarlo requieres aumentar el voltaje no solo del CPU sino del NB-CPU y del NB). Deja tal cual lo recibiste, y pruebalo así.

En uno de los reportes encontré que apuntaba a este archivo: FLTMGR.SYS, aquí más experiencias al respecto:

http://www.google.com.pe/search?hl=e...=&oq=&gs_rfai=

[toretore]

Ya le quité el unlock, ayer antes de formatear le pase el memtest y me dio en el test 6 casi 400.000 errores asi que le actualice la bios otra vez, lo formatee y hace 1 hora le pase el memtest para ver que sucedía... bueno pues el memtest limpio completamente, le saco el usb reinicio el pc y ya arrancado completamente ocurre esto.

==================================================
Dump File : 090810-14523-01.dmp
Crash Time : 08/09/2010 15:24:10
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff800`028ca992
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff800`028ca992
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\090810-14523-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

alguien que me ayuda a saber que puede causar el error...
gracias de antemano

[Knives]

Si ya formateaste, instalaste nuevamente un sistema operativo limpio actualzaste bios, y aun asi siguen apareciendo los errores, debe ser error de hardware.

Puede ser la temperatura muy alta, o alguna incompatibilidad en el hardware que tienes o errores en él. La BSOD STOP 0x00000124, segun foros y el mismo microsoft es un error por hardware, ya que una vez que el hardware falla el sistema no puede hacer nada mas y manda esa parada. Ahora te toca revisar todo tu hardware, cables de conexiones del disco duro, que esten todo en su lugar, que no haya daño en algun componente, las temperaturas, todo lo que pueda afectar a tu hardware, ya que las BSOD pueden deberse a muchas causas diferentes.

http://www.vistax64.com/crashes-debu...x00000124.html
http://www.sevenforums.com/crash-loc...-what-try.html
http://forums.techarena.in/vista-har...ces/821254.htm
http://social.answers.microsoft.com/...1-13d8021dd05a

Dijiste que tu windows 7 al principio no te daba problemas por lo que supongo que el sistema que instalaste esta bien, pero luego empezaron a fallar, puede ser por el overclok de las memorias, intenta reemplazando por otro banco de memorias, y pasale nuevamente el test, tal vez solo sea la memoria y no otro componente de tu PC el que este fallando.

[Solidus J2K]

Ya le quité el unlock, ayer antes de formatear le pase el memtest y me dio en el test 6 casi 400.000 errores asi que le actualice la bios otra vez, lo formatee y hace 1 hora le pase el memtest para ver que sucedía... bueno pues el memtest limpio completamente, le saco el usb reinicio el pc y ya arrancado completamente ocurre esto.

==================================================
Dump File : 090810-14523-01.dmp
Crash Time : 08/09/2010 15:24:10
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff800`028ca992
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000008
Parameter 4 : fffff800`028ca992
Caused By Driver :
Caused By Address :
File Description :
Product Name :
Company :
File Version :
Processor : x64
Computer Name :
Full Path : C:\Windows\Minidump\090810-14523-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
==================================================

alguien que me ayuda a saber que puede causar el error...
gracias de antemano

Prueba la estabilidad de cada módulo de memoria, si te apareció un error en el MEMTEST es muy probable que un módulo esté defectuoso, eso no se quita flasheando la BIOS.

Ahora solo te queda descartar HW.

[toretore]

Quisiera saber si el controlador del nb, del chipset vaya, podria causar los stops que tiene el pc. Si es la mem no me queda otra que enviar a RMA. Gracias y saludos!

[saito1600]

A mi esa fuente no me da seguridad y menos para tener una 5770 montada... primero saca la video y prueba con la integrada si fuenciona es por fuente o por video... o puede q la fuente halla dañado tu video.