ERROR IRQL_NOT_LESS_OR_EQUAL

23/11/2005 - 21:30 por el rubio | Informe spam
Hola he instalado XP con service pack 1 en mi ordenador y me ha saltado
varias veces el pantallazo azul dado varias veces con el citado error durante
la instalacion.
Cambie el lector de CD que ya sabia que estaba estropeado por otro que
funciona perfectamente y me dejo instalar XP sin problemas pero cuando fui a
instalar el Office 2003 me ha vuelto a saltar el pantallazao azul y se ha
vuelto a reiniciar. De momento he cambiado la configuracion para que no se
reinicie automaticamente y he instalado ademas del Office otros programas sin
problema.
Os posteo el analisis del Windbg para que por favor le echeis un ojo aver
que os parece.



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


Loading Dump File [C:\WINDOWS\Minidump\Mini112305-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Wed Nov 23 19:19:36.757 2005 (GMT+1)
System Uptime: 0 days 0:01:42.337
Loading Kernel Symbols
.
Loading unloaded module list

Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, 804fceca}

Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+28 )

Followup: MachineOwner


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: 00000028, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804fceca, address which referenced memory

Debugging Details:



READ_ADDRESS: 00000028

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReleasePageFileSpace+28
804fceca 8b7828 mov edi,[eax+0x28]

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e4f44 to 804fceca

TRAP_FRAME: f452bae0 -- (.trap fffffffff452bae0)
ErrCode = 00000000
eax000000 ebx=c000f0a0 ecx000b2b edx000000 esi000009 edic28000
eip€4fceca esp=f452bb54 ebp=f452bb88 iopl=0 nv up ei pl nz na po nc
cs08 ss10 ds23 es23 fs30 gs00 efl010206
nt!MiReleasePageFileSpace+0x28:
804fceca 8b7828 mov edi,[eax+0x28] ds:0023:00000028=????????
Resetting default scope

STACK_TEXT:
f452bb58 804e4f44 00b2b2b2 03c28000 c030003c nt!MiReleasePageFileSpace+0x28
f452bb88 804f9d38 c000f0a0 03c28000 00000000 nt!MiDeletePte+0x3fe
f452bc48 804f7067 e1be8600 04576fff 00000000 nt!MiDeleteVirtualAddresses+0x149
f452bcf4 80587e82 ffb25020 80dfbcf8 f452bd64 nt!MiRemoveMappedView+0x212
f452bd38 80587f36 ffa5b798 ffb343d0 00000000 nt!MiUnmapViewOfSection+0x12a
f452bd54 804da140 ffffffff ffb25020 61625c74 nt!NtUnmapViewOfSection+0x52
f452bd54 7ffe0304 ffffffff ffb25020 61625c74 nt!KiSystemService+0xc4
0012f644 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


FOLLOWUP_IP:
nt!MiReleasePageFileSpace+28
804fceca 8b7828 mov edi,[eax+0x28]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiReleasePageFileSpace+28

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c

STACK_COMMAND: .trap fffffffff452bae0 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28

BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28

Followup: MachineOwner


Muchisimas gracias por anticipado. Espero vuestras respuestas.

Preguntas similare

Leer las respuestas

#1 Dani
23/11/2005 - 21:40 | Informe spam
Si es una instalacion limpia, prueba a testear la ram con algún programa
como memtest , www.memtest.org



"el rubio" <el rubio @discussions.microsoft.com> escribió en el mensaje
news:
Hola he instalado XP con service pack 1 en mi ordenador y me ha saltado
varias veces el pantallazo azul dado varias veces con el citado error


durante
la instalacion.
Cambie el lector de CD que ya sabia que estaba estropeado por otro que
funciona perfectamente y me dejo instalar XP sin problemas pero cuando fui


a
instalar el Office 2003 me ha vuelto a saltar el pantallazao azul y se ha
vuelto a reiniciar. De momento he cambiado la configuracion para que no se
reinicie automaticamente y he instalado ademas del Office otros programas


sin
problema.
Os posteo el analisis del Windbg para que por favor le echeis un ojo aver
que os parece.



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


Loading Dump File [C:\WINDOWS\Minidump\Mini112305-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Wed Nov 23 19:19:36.757 2005 (GMT+1)
System Uptime: 0 days 0:01:42.337
Loading Kernel Symbols



Loading unloaded module list

Loading User Symbols



****************************************************************************
***
*
*
* Bugcheck Analysis
*
*
*



****************************************************************************
***

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, 804fceca}

Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+28 )

Followup: MachineOwner


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: 00000028, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804fceca, address which referenced memory

Debugging Details:



READ_ADDRESS: 00000028

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReleasePageFileSpace+28
804fceca 8b7828 mov edi,[eax+0x28]

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e4f44 to 804fceca

TRAP_FRAME: f452bae0 -- (.trap fffffffff452bae0)
ErrCode = 00000000
eax000000 ebxÀ00f0a0 ecx000b2b edx000000 esi000009


edic28000
eip€4fceca espô52bb54 ebpô52bb88 iopl=0 nv up ei pl nz na po


nc
cs08 ss10 ds23 es23 fs30 gs00


efl010206
nt!MiReleasePageFileSpace+0x28:
804fceca 8b7828 mov edi,[eax+0x28]


ds:0023:00000028=????????
Resetting default scope

STACK_TEXT:
f452bb58 804e4f44 00b2b2b2 03c28000 c030003c


nt!MiReleasePageFileSpace+0x28
f452bb88 804f9d38 c000f0a0 03c28000 00000000 nt!MiDeletePte+0x3fe
f452bc48 804f7067 e1be8600 04576fff 00000000


nt!MiDeleteVirtualAddresses+0x149
f452bcf4 80587e82 ffb25020 80dfbcf8 f452bd64 nt!MiRemoveMappedView+0x212
f452bd38 80587f36 ffa5b798 ffb343d0 00000000 nt!MiUnmapViewOfSection+0x12a
f452bd54 804da140 ffffffff ffb25020 61625c74 nt!NtUnmapViewOfSection+0x52
f452bd54 7ffe0304 ffffffff ffb25020 61625c74 nt!KiSystemService+0xc4
0012f644 00000000 00000000 00000000 00000000


SharedUserData!SystemCallStub+0x4


FOLLOWUP_IP:
nt!MiReleasePageFileSpace+28
804fceca 8b7828 mov edi,[eax+0x28]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiReleasePageFileSpace+28

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c

STACK_COMMAND: .trap fffffffff452bae0 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28

BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28

Followup: MachineOwner


Muchisimas gracias por anticipado. Espero vuestras respuestas.
Respuesta Responder a este mensaje
#2 el rubio
23/11/2005 - 21:54 | Informe spam
Ok pero que tengo que bajarme de todo lo que hay en la pagina y como lo
utilizo?

"Dani" escribió:

Si es una instalacion limpia, prueba a testear la ram con algún programa
como memtest , www.memtest.org
Respuesta Responder a este mensaje
#3 Marc [MVP Windows]
23/11/2005 - 22:24 | Informe spam
Por lo pronto, podrías actualizar a SP2 ese XP. Y sobre el dump, puedes
hacer un dump completo?

Saludos

Marc
MCP - MVP Windows Shell/User
Oracle9i Certified Associate (OCA)
NOTA. Por favor, las preguntas y comentarios en los grupos, así nos
beneficiamos todos.

Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no
otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.

"el rubio" <el rubio @discussions.microsoft.com> wrote in message
news:
Hola he instalado XP con service pack 1 en mi ordenador y me ha saltado
varias veces el pantallazo azul dado varias veces con el citado error
durante
la instalacion.
Cambie el lector de CD que ya sabia que estaba estropeado por otro que
funciona perfectamente y me dejo instalar XP sin problemas pero cuando fui
a
instalar el Office 2003 me ha vuelto a saltar el pantallazao azul y se ha
vuelto a reiniciar. De momento he cambiado la configuracion para que no se
reinicie automaticamente y he instalado ademas del Office otros programas
sin
problema.
Os posteo el analisis del Windbg para que por favor le echeis un ojo aver
que os parece.



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


Loading Dump File [C:\WINDOWS\Minidump\Mini112305-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp1.020828-1920
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
Debug session time: Wed Nov 23 19:19:36.757 2005 (GMT+1)
System Uptime: 0 days 0:01:42.337
Loading Kernel Symbols

Loading unloaded module list

Loading User Symbols
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {28, 2, 0, 804fceca}

Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+28 )

Followup: MachineOwner


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: 00000028, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804fceca, address which referenced memory

Debugging Details:



READ_ADDRESS: 00000028

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiReleasePageFileSpace+28
804fceca 8b7828 mov edi,[eax+0x28]

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e4f44 to 804fceca

TRAP_FRAME: f452bae0 -- (.trap fffffffff452bae0)
ErrCode = 00000000
eax000000 ebxÀ00f0a0 ecx000b2b edx000000 esi000009
edic28000
eip€4fceca espô52bb54 ebpô52bb88 iopl=0 nv up ei pl nz na po
nc
cs08 ss10 ds23 es23 fs30 gs00
efl010206
nt!MiReleasePageFileSpace+0x28:
804fceca 8b7828 mov edi,[eax+0x28]
ds:0023:00000028=????????
Resetting default scope

STACK_TEXT:
f452bb58 804e4f44 00b2b2b2 03c28000 c030003c
nt!MiReleasePageFileSpace+0x28
f452bb88 804f9d38 c000f0a0 03c28000 00000000 nt!MiDeletePte+0x3fe
f452bc48 804f7067 e1be8600 04576fff 00000000
nt!MiDeleteVirtualAddresses+0x149
f452bcf4 80587e82 ffb25020 80dfbcf8 f452bd64 nt!MiRemoveMappedView+0x212
f452bd38 80587f36 ffa5b798 ffb343d0 00000000 nt!MiUnmapViewOfSection+0x12a
f452bd54 804da140 ffffffff ffb25020 61625c74 nt!NtUnmapViewOfSection+0x52
f452bd54 7ffe0304 ffffffff ffb25020 61625c74 nt!KiSystemService+0xc4
0012f644 00000000 00000000 00000000 00000000
SharedUserData!SystemCallStub+0x4


FOLLOWUP_IP:
nt!MiReleasePageFileSpace+28
804fceca 8b7828 mov edi,[eax+0x28]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!MiReleasePageFileSpace+28

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c

STACK_COMMAND: .trap fffffffff452bae0 ; kb

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28

BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28

Followup: MachineOwner


Muchisimas gracias por anticipado. Espero vuestras respuestas.
Respuesta Responder a este mensaje
#4 el rubio
23/11/2005 - 22:40 | Informe spam
OK, lo actualizaré. El dump ya lo he configurado para que salga completo asi
que el proximo que me dé ya estrá completo. Ahora estoy haciendo el test de
memoria que me recomendo Dani. Ya posteare los resultados y el nuevo dump si
me vuelve a saltar el pantallazo. De momento si a alguien se le ocurre alguna
otra solución por favor que la ponga. Muchas gracias sobre todo a los que ya
os habeis tomado la molestia de leer mi post y proponerme algo.
Saludos

"Marc [MVP Windows]" wrote:

Por lo pronto, podrías actualizar a SP2 ese XP. Y sobre el dump, puedes
hacer un dump completo?

Saludos

Marc
MCP - MVP Windows Shell/User
Oracle9i Certified Associate (OCA)
NOTA. Por favor, las preguntas y comentarios en los grupos, así nos
beneficiamos todos.

Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no
otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.

"el rubio" <el rubio @discussions.microsoft.com> wrote in message
news:
> Hola he instalado XP con service pack 1 en mi ordenador y me ha saltado
> varias veces el pantallazo azul dado varias veces con el citado error
> durante
> la instalacion.
> Cambie el lector de CD que ya sabia que estaba estropeado por otro que
> funciona perfectamente y me dejo instalar XP sin problemas pero cuando fui
> a
> instalar el Office 2003 me ha vuelto a saltar el pantallazao azul y se ha
> vuelto a reiniciar. De momento he cambiado la configuracion para que no se
> reinicie automaticamente y he instalado ademas del Office otros programas
> sin
> problema.
> Os posteo el analisis del Windbg para que por favor le echeis un ojo aver
> que os parece.
>
>
>
> Microsoft (R) Windows Debugger Version 6.5.0003.7
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini112305-05.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is:
> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 2600.xpsp1.020828-1920
> Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
> Debug session time: Wed Nov 23 19:19:36.757 2005 (GMT+1)
> System Uptime: 0 days 0:01:42.337
> Loading Kernel Symbols
>
> Loading unloaded module list
>
> Loading User Symbols
> *******************************************************************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck A, {28, 2, 0, 804fceca}
>
> Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+28 )
>
> Followup: MachineOwner
>
>
> 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: 00000028, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000000, value 0 = read operation, 1 = write operation
> Arg4: 804fceca, address which referenced memory
>
> Debugging Details:
>
>
>
> READ_ADDRESS: 00000028
>
> CURRENT_IRQL: 2
>
> FAULTING_IP:
> nt!MiReleasePageFileSpace+28
> 804fceca 8b7828 mov edi,[eax+0x28]
>
> CUSTOMER_CRASH_COUNT: 5
>
> DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
>
> BUGCHECK_STR: 0xA
>
> LAST_CONTROL_TRANSFER: from 804e4f44 to 804fceca
>
> TRAP_FRAME: f452bae0 -- (.trap fffffffff452bae0)
> ErrCode = 00000000
> eax000000 ebxÀ00f0a0 ecx000b2b edx000000 esi000009
> edic28000
> eip€4fceca espô52bb54 ebpô52bb88 iopl=0 nv up ei pl nz na po
> nc
> cs08 ss10 ds23 es23 fs30 gs00
> efl010206
> nt!MiReleasePageFileSpace+0x28:
> 804fceca 8b7828 mov edi,[eax+0x28]
> ds:0023:00000028=????????
> Resetting default scope
>
> STACK_TEXT:
> f452bb58 804e4f44 00b2b2b2 03c28000 c030003c
> nt!MiReleasePageFileSpace+0x28
> f452bb88 804f9d38 c000f0a0 03c28000 00000000 nt!MiDeletePte+0x3fe
> f452bc48 804f7067 e1be8600 04576fff 00000000
> nt!MiDeleteVirtualAddresses+0x149
> f452bcf4 80587e82 ffb25020 80dfbcf8 f452bd64 nt!MiRemoveMappedView+0x212
> f452bd38 80587f36 ffa5b798 ffb343d0 00000000 nt!MiUnmapViewOfSection+0x12a
> f452bd54 804da140 ffffffff ffb25020 61625c74 nt!NtUnmapViewOfSection+0x52
> f452bd54 7ffe0304 ffffffff ffb25020 61625c74 nt!KiSystemService+0xc4
> 0012f644 00000000 00000000 00000000 00000000
> SharedUserData!SystemCallStub+0x4
>
>
> FOLLOWUP_IP:
> nt!MiReleasePageFileSpace+28
> 804fceca 8b7828 mov edi,[eax+0x28]
>
> SYMBOL_STACK_INDEX: 0
>
> FOLLOWUP_NAME: MachineOwner
>
> SYMBOL_NAME: nt!MiReleasePageFileSpace+28
>
> MODULE_NAME: nt
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c
>
> STACK_COMMAND: .trap fffffffff452bae0 ; kb
>
> IMAGE_NAME: memory_corruption
>
> FAILURE_BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28
>
> BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28
>
> Followup: MachineOwner
>
>
> Muchisimas gracias por anticipado. Espero vuestras respuestas.



Respuesta Responder a este mensaje
#5 el rubio
24/11/2005 - 00:15 | Informe spam
Ya lo he testeado. Despues de varias pasadas por los 10 test no ha encontrado
ningun error.

"Dani" wrote:

Si es una instalacion limpia, prueba a testear la ram con algún programa
como memtest , www.memtest.org



"el rubio" <el rubio @discussions.microsoft.com> escribió en el mensaje
news:
> Hola he instalado XP con service pack 1 en mi ordenador y me ha saltado
> varias veces el pantallazo azul dado varias veces con el citado error
durante
> la instalacion.
> Cambie el lector de CD que ya sabia que estaba estropeado por otro que
> funciona perfectamente y me dejo instalar XP sin problemas pero cuando fui
a
> instalar el Office 2003 me ha vuelto a saltar el pantallazao azul y se ha
> vuelto a reiniciar. De momento he cambiado la configuracion para que no se
> reinicie automaticamente y he instalado ademas del Office otros programas
sin
> problema.
> Os posteo el analisis del Windbg para que por favor le echeis un ojo aver
> que os parece.
>
>
>
> Microsoft (R) Windows Debugger Version 6.5.0003.7
> Copyright (c) Microsoft Corporation. All rights reserved.
>
>
> Loading Dump File [C:\WINDOWS\Minidump\Mini112305-05.dmp]
> Mini Kernel Dump File: Only registers and stack trace are available
>
> Symbol search path is:
> SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
> Executable search path is:
> Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 2600.xpsp1.020828-1920
> Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054be30
> Debug session time: Wed Nov 23 19:19:36.757 2005 (GMT+1)
> System Uptime: 0 days 0:01:42.337
> Loading Kernel Symbols
>
.
.
> Loading unloaded module list
>
> Loading User Symbols
>
****************************************************************************
***
> *
> *
> * Bugcheck Analysis
> *
> *
> *
>
****************************************************************************
***
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck A, {28, 2, 0, 804fceca}
>
> Probably caused by : memory_corruption ( nt!MiReleasePageFileSpace+28 )
>
> Followup: MachineOwner
>
>
> 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: 00000028, memory referenced
> Arg2: 00000002, IRQL
> Arg3: 00000000, value 0 = read operation, 1 = write operation
> Arg4: 804fceca, address which referenced memory
>
> Debugging Details:
>
>
>
> READ_ADDRESS: 00000028
>
> CURRENT_IRQL: 2
>
> FAULTING_IP:
> nt!MiReleasePageFileSpace+28
> 804fceca 8b7828 mov edi,[eax+0x28]
>
> CUSTOMER_CRASH_COUNT: 5
>
> DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
>
> BUGCHECK_STR: 0xA
>
> LAST_CONTROL_TRANSFER: from 804e4f44 to 804fceca
>
> TRAP_FRAME: f452bae0 -- (.trap fffffffff452bae0)
> ErrCode = 00000000
> eax000000 ebxÀ00f0a0 ecx000b2b edx000000 esi000009
edic28000
> eip€4fceca espô52bb54 ebpô52bb88 iopl=0 nv up ei pl nz na po
nc
> cs08 ss10 ds23 es23 fs30 gs00
efl010206
> nt!MiReleasePageFileSpace+0x28:
> 804fceca 8b7828 mov edi,[eax+0x28]
ds:0023:00000028=????????
> Resetting default scope
>
> STACK_TEXT:
> f452bb58 804e4f44 00b2b2b2 03c28000 c030003c
nt!MiReleasePageFileSpace+0x28
> f452bb88 804f9d38 c000f0a0 03c28000 00000000 nt!MiDeletePte+0x3fe
> f452bc48 804f7067 e1be8600 04576fff 00000000
nt!MiDeleteVirtualAddresses+0x149
> f452bcf4 80587e82 ffb25020 80dfbcf8 f452bd64 nt!MiRemoveMappedView+0x212
> f452bd38 80587f36 ffa5b798 ffb343d0 00000000 nt!MiUnmapViewOfSection+0x12a
> f452bd54 804da140 ffffffff ffb25020 61625c74 nt!NtUnmapViewOfSection+0x52
> f452bd54 7ffe0304 ffffffff ffb25020 61625c74 nt!KiSystemService+0xc4
> 0012f644 00000000 00000000 00000000 00000000
SharedUserData!SystemCallStub+0x4
>
>
> FOLLOWUP_IP:
> nt!MiReleasePageFileSpace+28
> 804fceca 8b7828 mov edi,[eax+0x28]
>
> SYMBOL_STACK_INDEX: 0
>
> FOLLOWUP_NAME: MachineOwner
>
> SYMBOL_NAME: nt!MiReleasePageFileSpace+28
>
> MODULE_NAME: nt
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 3d6de35c
>
> STACK_COMMAND: .trap fffffffff452bae0 ; kb
>
> IMAGE_NAME: memory_corruption
>
> FAILURE_BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28
>
> BUCKET_ID: 0xA_nt!MiReleasePageFileSpace+28
>
> Followup: MachineOwner
>
>
> Muchisimas gracias por anticipado. Espero vuestras respuestas.



Respuesta Responder a este mensaje
Ads by Google
Help Hacer una preguntaSiguiente Respuesta Tengo una respuesta
Search Busqueda sugerida