Soporte analisis pantallazo

Me podeis decir donde esta el fallo del pantallazo???



Microsoft (R) Windows Debugger Version 6.4.0007.2

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C:\Documents and
Settings\Administrador\Escritorio\Mini081905-01.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:

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntoskrnl.exe -

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: Fri Aug 19 11:33:41.879 2005 (GMT+2)

System Uptime: 0 days 19:03:49.656

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntoskrnl.exe -

Loading Kernel Symbols

.

Loading unloaded module list



Loading User Symbols

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {28, 2, 0, 804f22b8}

***** 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 ***

*** ***

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

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: 804f22b8, 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 ***

*** ***

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

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 41108004

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

unable to get nt!MiSessionPoolStart

unable to get nt!MiSessionPoolEnd

00000028

CURRENT_IRQL: 2

FAULTING_IP:

nt!PsGetProcessJob+5c8

804f22b8 8b7828 mov edi,[eax+0x28]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 80500e5f to 804f22b8

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be
wrong.

f6c1ac24 80500e5f 05812163 00000000 81d0f3c0 nt!PsGetProcessJob+0x5c8

f6c1ac4c 804e510e e17df528 00000000 e1209fa8
nt!FsRtlRemovePerStreamContext+0xa98

f6c1ac70 804e3d38 81d0f3c0 00000000 e1751500 nt!KeCancelTimer+0x4f

f6c1ac88 80564045 81d0f3c0 00000001 e1209f80 nt!MmIsAddressValid+0x157

f6c1aca4 80563ff6 81d0f3c0 e1209f90 00000000 nt!SeDeleteAccessState+0x5a7

f6c1acc0 804e3c55 e1209fa8 00000000 000005dc nt!SeDeleteAccessState+0x558

f6c1ace4 80567543 81d09260 e1a04f78 81ddd5d8 nt!MmIsAddressValid+0x74

f6c1acfc 805675ac e1a04f78 e1209fa8 000005dc nt!RtlAddAtomToAtomTable+0x5a6

f6c1ad44 805675f6 000005dc 00000001 00000000 nt!RtlAddAtomToAtomTable+0x60f

f6c1ad58 804df06b 000005dc 0117fc7c 7c91eb94 nt!NtClose+0x1d

f6c1ad64 7c91eb94 badb0d00 0117fc78 f780a54a nt!ZwYieldExecution+0xb96

0117fc7c 00000000 00000000 00000000 00000000 0x7c91eb94



STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_NAME: MachineOwner

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner