Pantallazo azul.

Hola, después de reinstalar windows xp desde cero a causa de los
pantallazos, he comprobado que continúan sucediendo, os pongo el informe
que genera el debbuging de Microsoft después de analizar el archivo dmp
para haber si alguien "me ilumina"

Gracias por la atención prestada.





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


Loading Dump File [F:\MEMORY.DMP]
Kernel Complete Dump File: Full address space is 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Mon Jul 24 13:26:53.024 2006 (GMT+2)
System Uptime: 0 days 0:06:39.605
WARNING: Process directory table base 0C7E0000 doesn't match CR3 00039000
WARNING: Unable to reset page directories
Loading Kernel Symbols
.
Loading User Symbols
WARNING: Process directory table base 0C7E0000 doesn't match CR3 00039000
Unable to get PEB pointer
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80042000, 0, 0}

Probably caused by : ntoskrnl.exe ( nt!KiTrap08+44 )

Followup: MachineOwner


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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

Debugging Details:



BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 28)
eax000000 ebx
9758c0 ecx
975880 edx000077 esi=7d74bf20
edi1294c0
eip=7d502631 esp1293c4 ebp1294c4 iopl=0 nv up ei pl zr na po
nc
cs1b ss23 ds23 es23 fs3b gs00 efl010246
001b:7d502631 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 7d502631 to 804e0fad

STACK_TEXT:
00000000 7d502631 00000000 00000000 00000000 nt!KiTrap08+0x44
WARNING: Frame IP not in any known module. Following frames may be wrong.
001294c4 00000000 00000000 00000000 00000000 0x7d502631


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap08+44
804e0fad ebee jmp nt!KiTrap08+0x34 (804e0f9d)

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap08+44

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+44

BUCKET_ID: 0x7f_8_nt!KiTrap08+44

Followup: MachineOwner

Un Double_Fault es rarisimo. ¿has revisado la memoria?... Usa el programa
DocMemory de www.simmtester.com y tenlo en ejecucion 4 horas (no debe dar
ni un solo "failed" o "error")

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm
news://jmtella.com

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.



"Manel" wrote in message
news:

Hola, después de reinstalar windows xp desde cero a causa de los
pantallazos, he comprobado que continúan sucediendo, os pongo el informe
que genera el debbuging de Microsoft después de analizar el archivo dmp
para haber si alguien "me ilumina"

Gracias por la atención prestada.





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


Loading Dump File [F:\MEMORY.DMP]
Kernel Complete Dump File: Full address space is 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Mon Jul 24 13:26:53.024 2006 (GMT+2)
System Uptime: 0 days 0:06:39.605
WARNING: Process directory table base 0C7E0000 doesn't match CR3 00039000
WARNING: Unable to reset page directories
Loading Kernel Symbols
.
Loading User Symbols
WARNING: Process directory table base 0C7E0000 doesn't match CR3 00039000
Unable to get PEB pointer
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80042000, 0, 0}

Probably caused by : ntoskrnl.exe ( nt!KiTrap08+44 )

Followup: MachineOwner


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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

Debugging Details:



BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 28)
eax000000 ebx
9758c0 ecx
975880 edx000077 esi=7d74bf20
edi1294c0
eip=7d502631 esp1293c4 ebp1294c4 iopl=0 nv up ei pl zr na
po nc
cs1b ss23 ds23 es23 fs3b gs00 efl010246
001b:7d502631 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 7d502631 to 804e0fad

STACK_TEXT:
00000000 7d502631 00000000 00000000 00000000 nt!KiTrap08+0x44
WARNING: Frame IP not in any known module. Following frames may be wrong.
001294c4 00000000 00000000 00000000 00000000 0x7d502631


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap08+44
804e0fad ebee jmp nt!KiTrap08+0x34 (804e0f9d)

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap08+44

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+44

BUCKET_ID: 0x7f_8_nt!KiTrap08+44

Followup: MachineOwner

Gracias por la ayuda, pondré el ordenador a trabajar.



"JM Tella Llop [MVP Windows]" escribió en el mensaje
news:%

Un Double_Fault es rarisimo. ¿has revisado la memoria?... Usa el programa
DocMemory de www.simmtester.com y tenlo en ejecucion 4 horas (no debe dar
ni un solo "failed" o "error")

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm
news://jmtella.com

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.



"Manel" wrote in message
news:

Hola, después de reinstalar windows xp desde cero a causa de los
pantallazos, he comprobado que continúan sucediendo, os pongo el informe
que genera el debbuging de Microsoft después de analizar el archivo dmp
para haber si alguien "me ilumina"

Gracias por la atención prestada.





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


Loading Dump File [F:\MEMORY.DMP]
Kernel Complete Dump File: Full address space is 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 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Mon Jul 24 13:26:53.024 2006 (GMT+2)
System Uptime: 0 days 0:06:39.605
WARNING: Process directory table base 0C7E0000 doesn't match CR3
00039000
WARNING: Unable to reset page directories
Loading Kernel Symbols
.
Loading User Symbols
WARNING: Process directory table base 0C7E0000 doesn't match CR3
00039000
Unable to get PEB pointer
Loading unloaded module list
..
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80042000, 0, 0}

Probably caused by : ntoskrnl.exe ( nt!KiTrap08+44 )

Followup: MachineOwner


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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure
KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 80042000
Arg3: 00000000
Arg4: 00000000

Debugging Details:



BUGCHECK_STR: 0x7f_8

TSS: 00000028 -- (.tss 28)
eax000000 ebx
9758c0 ecx
975880 edx000077 esi=7d74bf20
edi1294c0
eip=7d502631 esp1293c4 ebp1294c4 iopl=0 nv up ei pl zr na
po nc
cs1b ss23 ds23 es23 fs3b gs00 efl010246
001b:7d502631 ?? ???
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 7d502631 to 804e0fad

STACK_TEXT:
00000000 7d502631 00000000 00000000 00000000 nt!KiTrap08+0x44
WARNING: Frame IP not in any known module. Following frames may be
wrong.
001294c4 00000000 00000000 00000000 00000000 0x7d502631


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap08+44
804e0fad ebee jmp nt!KiTrap08+0x34 (804e0f9d)

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap08+44

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

FAILURE_BUCKET_ID: 0x7f_8_nt!KiTrap08+44

BUCKET_ID: 0x7f_8_nt!KiTrap08+44

Followup: MachineOwner