Pantalla azul

[sebastains]

Hola amigos, vengo a pedir su ayuda. Resulta que hace ya un tiempo, que mi computador tira blue screen constantemente.

Uso windows 7 (64 bit), service pack 1.

El error es este:

Información adicional del problema:
BCCode: d1
BCP1: 0000000000000028
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88001D286FD
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

El titulo del error en blue screen es driver irql not less or equal

Ojala alguien me pueda ayudar.

 

EDIT:

Use la herramienta Microsoft Debugging

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff88001d286fd, 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: NETIO

FAULTING_MODULE: fffff80003210000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 5034f6a0

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

CURRENT_IRQL: 0

FAULTING_IP:
NETIO+106fd
fffff880`01d286fd 448b5228 mov r10d,dword ptr [rdx+28h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from fffff80003285169 to fffff80003285bc0

STACK_TEXT:
fffff880`03777648 fffff800`03285169 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt+0x75bc0
fffff880`03777650 00000000`0000000a : 00000000`00000028 00000000`00000002 00000000`00000000 fffff880`01d286fd : nt+0x75169
fffff880`03777658 00000000`00000028 : 00000000`00000002 00000000`00000000 fffff880`01d286fd fffff880`0000000e : 0xa
fffff880`03777660 00000000`00000002 : 00000000`00000000 fffff880`01d286fd fffff880`0000000e 00000000`00000000 : 0x28
fffff880`03777668 00000000`00000000 : fffff880`01d286fd fffff880`0000000e 00000000`00000000 00000000`00000000 : 0x2


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
NETIO+106fd
fffff880`01d286fd 448b5228 mov r10d,dword ptr [rdx+28h]

SYMBOL_NAME: NETIO+106fd

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: NETIO.SYS

BUCKET_ID: WRONG_SYMBOLS

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

Edited June 20, 2014 by sebastains

[neno07]

El error DRIVER_IRQL_NOT_LESS_OR_EQUAL

Indica que un driver está causando conflicto.

Prueba actualizando tus drivers.

[JhazXD]

o también actualizando tu sistema

[tadaotaku]

ram :3

[ExtreemD4t4]

dice que es probablemente causado por un driver ocupando una zona de la memoria que no corresponde :/, asike o son los drivers o es la ram :/

[Varit]

Verificar RAM, si no, actualizar drivers