Blue screen of death

Foro referente al sistema operativo Windows XP
bluescreen
Usuario linuxero
Usuario linuxero
Mensajes: 4
Registrado: 06 Feb 2013, 22:29
Agradecido : 2 veces
Contactar:

Blue screen of death

Mensajepor bluescreen » 06 Feb 2013, 22:34

Ultimamente me aparece la dichosa pantallita azul todo el tiempo o no me arranca el portatil y se queda la pantalla en negro. Ha empezado a pasarme hace unos dias, sin haber instalado ningun programa, driver o hardware.
Gracias ha que tengo configurado el ordenador para hacer dumps de lo sucedido, he conseguido la siguiente informacion:

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


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

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/s...wnload/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Sat Jan 26 18:42:15.787 2013 (UTC + 0:00)
System Uptime: 0 days 1:33:51.357
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000BE, {b877dd24, 32406121, b8775c94, b}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory. The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: b877dd24, Virtual address for the attempted write.
Arg2: 32406121, PTE contents.
Arg3: b8775c94, (reserved)
Arg4: 0000000b, (reserved)

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0xBE

PROCESS_NAME: winamp.exe

LAST_CONTROL_TRANSFER: from 68107536 to 80566212

STACK_TEXT:
b877dd50 68107536 000002d0 77dc0c68 bbe850b8 nt!NtWaitForSingleObject+0x9c
WARNING: Frame IP not in any known module. Following frames may be wrong.
b877dd60 3bfffff4 5fdf75f7 c2c95b5e cccc0004 0x68107536
b877dd64 5fdf75f7 c2c95b5e cccc0004 cccccccc 0x3bfffff4
b877dd68 c2c95b5e cccc0004 cccccccc 8b55ff8b 0x5fdf75f7
b877dd6c cccc0004 cccccccc 8b55ff8b 575653ec 0xc2c95b5e
b877dd70 cccccccc 8b55ff8b 575653ec 0ad415ff 0xcccc0004
b877dd74 8b55ff8b 575653ec 0ad415ff 053bb878 0xcccccccc
b877dd78 575653ec 0ad415ff 053bb878 b8782ac4 0x8b55ff8b
b877dd7c 0ad415ff 053bb878 b8782ac4 00d7850f 0x575653ec
b877dd80 053bb878 b8782ac4 00d7850f 15ff0000 0xad415ff
b877dd84 b8782ac4 00d7850f 15ff0000 b8780a0c 0x53bb878
b877dd88 00d7850f 15ff0000 b8780a0c 850fc084 mrxdav!RxDispatcher+0x4
b877dd8c 15ff0000 b8780a0c 850fc084 000000c9 0xd7850f
b877dd90 b8780a0c 850fc084 000000c9 8d08758b 0x15ff0000
b877dd94 850fc084 000000c9 8d08758b cb8b045e mrxdav!_imp__KeGetCurrentIrql
b8780a0c 00029088 00029072 00000000 000290c0 0x850fc084
b8780a10 00029072 00000000 000290c0 000290a6 0x29088
b8780a14 00000000 000290c0 000290a6 00000000 0x29072


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !mrxdav
b877dd05 - mrxdav!RxTearDownWorkQueue+cf
[ e8:68 ]
1 error : !mrxdav (b877dd05)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------





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


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

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Mon Jan 28 16:32:21.979 2013 (UTC + 0:00)
System Uptime: 0 days 0:05:33.550
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.............
Unable to load image aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b9fbc663, b7aca748, 0}

Unable to load image aswFsBlk.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswFsBlk.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswFsBlk.SYS
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : aswSnx.SYS ( aswSnx+9663 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b9fbc663, The address that the exception occurred at
Arg3: b7aca748, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
aswSnx+9663
b9fbc663 8b4828 mov ecx,dword ptr [eax+28h]

TRAP_FRAME: b7aca748 -- (.trap 0xffffffffb7aca74
ErrCode = 00000000
eax=000000a9 ebx=00000000 ecx=49bb000e edx=49ba000d esi=8536d5c8 edi=00000000
eip=b9fbc663 esp=b7aca7bc ebp=b7aca7ec iopl=0 ov up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a46
aswSnx+0x9663:
b9fbc663 8b4828 mov ecx,dword ptr [eax+28h] ds:0023:000000d1=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: firefox.exe

LAST_CONTROL_TRANSFER: from f7687c3f to b9fbc663

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b7aca7ec f7687c3f 8653b178 85395160 85c8169c aswSnx+0x9663
b7aca81c f768a18e 8536d5c8 00000000 8536d5c8 fltMgr!FltpCallOpenedFileNameHandler+0x45
b7aca838 f768a76b 8536d5c8 00000000 000000fe fltMgr!FltpGetNormalizedFileNameWorker+0xc4
b7aca850 f76882a2 8536d5c8 00000000 8536d5c8 fltMgr!FltpGetNormalizedFileName+0x19
b7aca868 f7680365 80552000 8536d5c8 b7aca8a4 fltMgr!FltpCreateFileNameInformation+0x84
b7aca878 f7678e0a 8536d5c8 85c8169c 00000000 fltMgr!FltEnumerateInstances+0x99
b7aca8a4 f7679366 8536d5c8 b7aca8f4 b7aca938 fltMgr!FltpGetFileNameInformation+0xaa
b7aca8cc b7f58b40 00c8169c 00000101 b7aca8f0 fltMgr!FltGetFileNameInformation+0x114
b7aca914 b7f5875b b7aca964 85c8169c b7aca938 aswFsBlk+0x1b40
b7aca944 f7674888 00120196 b7aca964 b7aca994 aswFsBlk+0x175b
b7aca9a4 f76762a0 00aca9e8 85c81640 8661bfb4 fltMgr!FltpPerformPreCallbacks+0x2d4
b7aca9b8 f7683217 b7aca9e8 f76816aa 00000000 fltMgr!FltpPassThroughInternal+0x32
b7aca9d0 f7683742 b7aca9e8 856a9008 8661bfd8 fltMgr!FltpCreateInternal+0x63
b7acaa04 804e37f7 865b7020 8661be00 8661bffc fltMgr!FltpCreate+0x258
b7acaa14 b7bb6777 00000000 862e84f8 85395160 nt!IopfCallDriver+0x31
b7acaa38 b7bafac7 86258560 8661be00 8661be10 aswMon2+0x7777
b7acaa4c 804e37f7 86258560 8661be00 8661be00 aswMon2+0xac7
b7acaa5c 8056c712 866d6578 85306804 b7acac04 nt!IopfCallDriver+0x31
b7acab3c 80563fec 866d6590 00000000 85306760 nt!IopParseDevice+0xa12
b7acabc4 805684da 00000000 b7acac04 00000040 nt!ObpLookupObjectName+0x56a
b7acac18 8056cbeb 00000000 00000000 00000001 nt!ObOpenObjectByName+0xeb
b7acac94 8056ccba 027ffeac 40100080 027ffe4c nt!IopCreateFile+0x407
b7acacf0 8056cdf0 027ffeac 40100080 027ffe4c nt!IoCreateFile+0x8e
b7acad30 804de7ec 027ffeac 40100080 027ffe4c nt!NtCreateFile+0x30
b7acad30 7c90e4f4 027ffeac 40100080 027ffe4c nt!KiFastCallEntry+0xf8
027ffea4 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
aswSnx+9663
b9fbc663 8b4828 mov ecx,dword ptr [eax+28h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: aswSnx+9663

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswSnx

IMAGE_NAME: aswSnx.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 5090582a

FAILURE_BUCKET_ID: 0x8E_aswSnx+9663

BUCKET_ID: 0x8E_aswSnx+9663

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




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

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Mon Feb 4 13:20:34.075 2013 (UTC + 0:00)
System Uptime: 0 days 0:02:43.645
Loading Kernel Symbols
...............................................................
................................................................
........
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {b7b7ecc0, 0, 804e4090, 3}


Could not read faulting driver name
Probably caused by : ntoskrnl.exe ( nt!KeRemoveQueue+308 )

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

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: b7b7ecc0, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 804e4090, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000003, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: b7b7ecc0

FAULTING_IP:
nt!KeRemoveQueue+308
804e4090 c9 leave

MM_INTERNAL_CODE: 3

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: AvastSvc.exe

LAST_CONTROL_TRANSFER: from 00000000 to 804e4090

STACK_TEXT:
b7b7ecc0 00000000 00000000 00000000 00000000 nt!KeRemoveQueue+0x308


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KeRemoveQueue+308
804e4090 c9 leave

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KeRemoveQueue+308

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

FAILURE_BUCKET_ID: 0x50_nt!KeRemoveQueue+308

BUCKET_ID: 0x50_nt!KeRemoveQueue+308

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

La cosa es que no entiendo bien la informacion y no se como arreglarlo. Sabe alguien que es lo que pasa y como arreglarlo?

Saludos

Avatar de Usuario
Souto
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 10665
Registrado: 25 Feb 2008, 10:21
Ubicación: Galicia
Agradecido : 6 veces
Agradecimiento recibido: 647 veces
Contactar:

Re: Blue screen of death

Mensajepor Souto » 07 Feb 2013, 00:19

Hola, bienvenido
El volcado apunta a que el Avast podría ser el responsable.
Desisnstálalo o actualiza la versión.

Saludos
Qui dove il mare luccica e tira forte il vento

bluescreen
Usuario linuxero
Usuario linuxero
Mensajes: 4
Registrado: 06 Feb 2013, 22:29
Agradecido : 2 veces
Contactar:

Re: Blue screen of death

Mensajepor bluescreen » 09 Feb 2013, 00:02

desintale el avast y algun otro programa pero el problema continua. Alguna otra idea?

bluescreen
Usuario linuxero
Usuario linuxero
Mensajes: 4
Registrado: 06 Feb 2013, 22:29
Agradecido : 2 veces
Contactar:

Re: Blue screen of death

Mensajepor bluescreen » 09 Feb 2013, 00:07

Estos son los ultimos volcados:


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


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

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Thu Feb 7 09:06:24.306 2013 (UTC + 0:00)
System Uptime: 0 days 0:15:29.877
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b7760475, b73abb0c, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: b7760475, The address that the exception occurred at
Arg3: b73abb0c, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
sysaudio!_SEH_epilog+a
b7760475 d95f5e fstp dword ptr [edi+5Eh]

TRAP_FRAME: b73abb0c -- (.trap 0xffffffffb73abb0c)
ErrCode = 00000002
eax=00000000 ebx=ffffffff ecx=b73abc14 edx=00000001 esi=00000000 edi=00000000
eip=b7760475 esp=b73abb80 ebp=b73abbcc iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
sysaudio!_SEH_epilog+0xa:
b7760475 d95f5e fstp dword ptr [edi+5Eh] ds:0023:0000005e=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x8E

PROCESS_NAME: winamp.exe

LAST_CONTROL_TRANSFER: from b77632a2 to b7760475

STACK_TEXT:
b73abbcc b77632a2 8572e628 00000000 e2c02a68 sysaudio!_SEH_epilog+0xa
b73abc24 f6c53f95 853aaf08 8572e628 b73abc58 sysaudio!CPinInstance::PinDispatchIoControl+0x153
b73abc34 804e37f7 853aaf08 8572e628 806ef070 ks!DispatchDeviceIoControl+0x28
b73abc44 80567f81 8572e770 862ce2a8 8572e628 nt!IopfCallDriver+0x31
b73abc58 8057aa9f 853aaf08 8572e628 862ce2a8 nt!IopSynchronousServiceTail+0x70
b73abd00 8058efd7 00000380 00000374 00000000 nt!IopXxxControlFile+0x611
b73abd34 804de7ec 00000380 00000374 00000000 nt!NtDeviceIoControlFile+0x2a
b73abd34 7c90e4f4 00000380 00000374 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
047ffe20 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !sysaudio
2 errors : !sysaudio (b7760475-b776056d)
b7760470 0d 00 00 00 00 *d9 5f 5e 5b c9 51 c3 90 90 90 90 ......_^[.Q.....
...
b7760560 45 fc 8b 45 fc 5f 5e 5b c9 c2 08 00 90 *10 90 90 E..E._^[........

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: STRIDE

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

BUCKET_ID: MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------




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


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

Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Fri Feb 8 00:09:10.864 2013 (UTC + 0:00)
System Uptime: 0 days 0:01:33.434
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 7ca19001, 171a, c0503000}

Probably caused by : memory_corruption ( nt!MiLocateWsle+c0 )

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041284, A PTE or the working set list is corrupt.
Arg2: 7ca19001
Arg3: 0000171a
Arg4: c0503000

Debugging Details:
------------------


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 80525016 to 8053380e

STACK_TEXT:
b7a093cc 80525016 0000001a 00041284 7ca19001 nt!KeBugCheckEx+0x1b
b7a09404 80569566 0000171a 7ca19000 862ea050 nt!MiLocateWsle+0xc0
b7a0941c 8056e5c8 c01f2864 8624bda0 00000000 nt!MiGetPageProtection+0xdf
b7a09448 8056e3c6 7ca19000 862ea050 8624bda0 nt!MiQueryAddressState+0xa6
b7a09504 804de7ec ffffffff 7c9f4518 00000000 nt!NtQueryVirtualMemory+0x477
b7a09504 7c90e4f4 ffffffff 7c9f4518 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
03605340 00000000 00000000 00000000 00000000 0x7c90e4f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiLocateWsle+c0
80525016 006a00 add byte ptr [edx],ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!MiLocateWsle+c0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48025eab

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c0

BUCKET_ID: 0x1a_41284_nt!MiLocateWsle+c0

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

Avatar de Usuario
helheim
Usuario Bill Gates
Usuario Bill Gates
Mensajes: 5001
Registrado: 20 Abr 2008, 11:38
Agradecido : 24 veces
Agradecimiento recibido: 169 veces
Contactar:

Re: Blue screen of death

Mensajepor helheim » 09 Feb 2013, 12:33

Para tener una información un tanto más clara, descarga WHOCRASHED.

Instálalo y espera a que te vuelva a pegar el pantallazo. Luego ejecútalo como Administrador (botón derecho del ratón sobre el archivo). Pulsa en Analyze y cuando termine el proceso, copia el contenido de Analyze y Conclusion en tu próximo mensaje.

A ver si de esta manera simplifica un poco la información.

Un saludo.
La experiencia es una llama que alumbra quemando (Benito Pérez Galdós)

bluescreen
Usuario linuxero
Usuario linuxero
Mensajes: 4
Registrado: 06 Feb 2013, 22:29
Agradecido : 2 veces
Contactar:

Re: Blue screen of death

Mensajepor bluescreen » 11 Feb 2013, 15:18

Vale, hice lo que me dijiste e incluso hice un volcado completo de la memoria y esto fue lo que consegui:


System Information (local)
--------------------------------------------------------------------------------

computer name: COMPUTER_1
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: GenuineIntel Intel(R) Pentium(R) M processor 1600MHz Intel586, level: 6
1 logical processors, active mask: 1
RAM: 1072611328 total
VM: 2147352576, free: 2058665984




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Mon 2/11/2013 1:44:36 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021113-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5C80E)
Bugcheck code: 0x50 (0xFFFFFFFFCF8834BC, 0x0, 0xFFFFFFFF80568B37, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 2/11/2013 1:44:36 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: nt_ll.sys (nt_ll!KiFastSystemCallRet+0x0)
Bugcheck code: 0x50 (0xFFFFFFFFCF8834BC, 0x0, 0xFFFFFFFF80568B37, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_ll.sys .
Google query: nt_ll.sys PAGE_FAULT_IN_NONPAGED_AREA



On Fri 2/8/2013 12:09:10 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini020813-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xEE6B)
Bugcheck code: 0x1A (0x41284, 0x7CA19001, 0x171A, 0xFFFFFFFFC0503000)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nt_ll.sys

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.


Busque en internet informacion, pero no encontre nada que me ayude,hay muchas posibles causas y estoy bastante confuso. No hay actualizaciones para ese driver y tampoco esta claro que sea la causa del problema. Alguien sabe cual es el problema?


Volver a “Windows XP / X64”

¿Quién está conectado?

Usuarios navegando por este Foro: No hay usuarios registrados visitando el Foro y 2 invitados