Tengo problemas con un PC, el error es bastante raro para mi.
Cambie la memoria RAM para ver si eso era el problema, reintale todo 2 veces, tengo los últimos drivers, ultimas actualizacionesy persiste el problema.
Aquí dejo el dump:
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini081909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Aug 19 20:41:50.593 2009 (GMT-4)
System Uptime: 0 days 0:03:12.296
Unable to load image \WINDOWS\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Loading Kernel Symbols
..........................................................................................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {e136d000, 0, 805738ef, 1}
*** WARNING: Unable to verify timestamp for mssmbios.sys
Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiMapViewOfDataSection+311 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e136d000, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 805738ef, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: e136d000
FAULTING_IP:
nt!MiMapViewOfDataSection+311
805738ef ?? ???
MM_INTERNAL_CODE: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 80529170 to 8053767a
STACK_TEXT:
b54ccb50 80529170 00000050 e136d000 00000000 nt!MiRemoveUnusedSegments+0x3e3
b54ccba0 804e0944 00000000 e136d000 00000000 nt!GUID_DOCK_INTERFACE+0x234
b54ccbb8 805738ef badb0d00 e136006c 81e42d98 nt!Dr_kitb_a+0x7
b54ccc48 8058765a e1037b60 e2a2f98c 0136c53c nt!MiMapViewOfDataSection+0x311
b54cccb4 80587758 e2b08be8 00000002 00000001 nt!NtFlushBuffersFile+0x73
b54ccd44 804dd99f 00000194 00000002 00000001 nt!IopSynchronousApiServiceTail+0x23
b54ccd60 01a6ece4 7c91e514 badb0d00 01a6ebbc nt!ZwSetSystemPowerState+0xf
WARNING: Frame IP not in any known module. Following frames may be wrong.
b54ccd64 7c91e514 badb0d00 01a6ebbc b5634d98 0x1a6ece4
b54ccd68 badb0d00 01a6ebbc b5634d98 b5634dcc 0x7c91e514
b54ccd6c 01a6ebbc b5634d98 b5634dcc 00000000 0xbadb0d00
b54ccd70 b5634d98 b5634dcc 00000000 00000000 0x1a6ebbc
b54ccd74 b5634dcc 00000000 00000000 00000000 0xb5634d98
b54ccd78 00000000 00000000 00000000 00000000 0xb5634dcc
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiMapViewOfDataSection+311
805738ef ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!MiMapViewOfDataSection+311
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 498c19b5
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x50_nt!MiMapViewOfDataSection+311
BUCKET_ID: 0x50_nt!MiMapViewOfDataSection+311
Followup: MachineOwner
---------
