Error Pant.Azul 0xC4

Desactiva todo lo de creative de la pestaña Inicio del programa MSCONFIG.
Reinicia y prueba.

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

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.



"Ivan" wrote in message
news:

Tengo instalados los drivers bajados de la web, un archivo q es un pack de
drv y soft(LiveDrvUni-Pack(ENG).exe 23MB) y otro q es un patch
actualizacion(LiveDrvPack_Patch.exe 6MB)
Que sera?Saludos

"JM Tella Llop [MVP Windows]" escribió:

¿con los drivers del CD de Creative o los ultimos bajados de su web?

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

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.



"Ivan" wrote in message
news:
> Tengo una Sound Blaster Live! pci
>
>
> "JM Tella Llop [MVP Windows]" escribió:
>
>> ¿que tienes de hardware en el subsistema de audio?
>>
>> Jose Manuel Tella Llop
>> MVP - Windows
>> (quitar XXX)
>> http://www.multingles.net/jmt.htm
>>
>> 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.
>>
>>
>>
>> "Ivan" wrote in message
>> news:
>> > gracias a todos aqui tienen el Dump:
>> >
>> > Microsoft (R) Windows Debugger Version 6.4.0007.2
>> > Copyright (c) Microsoft Corporation. All rights reserved.
>> >
>> >
>> > Loading Dump File [C:\WINDOWS\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) MP (2 procs) Free
>> > x86
>> > compatible
>> > Product: WinNt, suite: TerminalServer SingleUserTS
>> > Built by: 2600.xpsp_sp2_gdr.050301-1519
>> > Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
>> > Debug session time: Fri Jul 1 19:59:31.187 2005 (GMT-3)
>> > System Uptime: 0 days 1:13:57.896
>> > Loading Kernel Symbols
>> > ..
>> > Loading unloaded module list
>> >
>> > Loading User Symbols
>> > .
>> > *******************************************************************************
>> > *
>> > *
>> > * Bugcheck Analysis
>> > *
>> > *
>> > *
>> > *******************************************************************************
>> >
>> > Use !analyze -v to get detailed debugging information.
>> >
>> > BugCheck C4, {90, ffdff120, 0, 0}
>> >
>> > *** WARNING: Unable to verify timestamp for BF2.exe
>> > *** ERROR: Module load completed but symbols could not be loaded for
>> > BF2.exe
>> > Probably caused by : splitter.sys
>> >
>> > Followup: MachineOwner
>> >
>> >
>> > 0: kd> !analyze -v
>> > *******************************************************************************
>> > *
>> > *
>> > * Bugcheck Analysis
>> > *
>> > *
>> > *
>> > *******************************************************************************
>> >
>> > DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
>> > A device driver attempting to corrupt the system has been caught.
>> > This
>> > is
>> > because the driver was specified in the registry as being suspect
>> > (by
>> > the
>> > administrator) and the kernel has enabled substantial checking of
>> > this
>> > driver.
>> > If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1
>> > and
>> > 0xA
>> > will
>> > be among the most commonly seen crashes.
>> > Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error
>> > codes.
>> > Typically the code is 0x1001 (deadlock detected) and
>> > you
>> > can
>> > issue a '!deadlock' KD command to get more
>> > information.
>> > Arguments:
>> > Arg1: 00000090, A driver switched stacks. The current stack is
>> > neither
>> > a
>> > thread
>> > stack nor a DPC stack. Typically the driver doing this should be
>> > on the stack obtained from `kb' command.
>> > Arg2: ffdff120
>> > Arg3: 00000000
>> > Arg4: 00000000
>> >
>> > Debugging Details:
>> >
>> >
>> >
>> > OVERLAPPED_MODULE: rdbss
>> >
>> > BUGCHECK_STR: 0xc4_90
>> >
>> > DEFAULT_BUCKET_ID: DRIVER_FAULT
>> >
>> > LAST_CONTROL_TRANSFER: from 8067a445 to 805371aa
>> >
>> > IRP_ADDRESS: 8374ee90
>> >
>> > DEVICE_OBJECT: f8bfef10
>> >
>> > DRIVER_OBJECT: 8160edf0
>> >
>> > IMAGE_NAME: splitter.sys
>> >
>> > DEBUG_FLR_IMAGE_TIMESTAMP: 41107d32
>> >
>> > MODULE_NAME: splitter
>> >
>> > FAULTING_MODULE: f8a1d000 splitter
>> >
>> > STACK_TEXT:
>> > f8f3a9ec 8067a445 000000c4 00000090 ffdff120 nt!KeBugCheckEx+0x1b
>> > f8f3aa0c 8067a73f f8f3aa38 8067ad32 00000000
>> > nt!ViDeadlockCheckStackLimits+0x6e
>> > f8f3aa14 8067ad32 00000000 00000000 00000000
>> > nt!ViDeadlockCanProceed+0x2a
>> > f8f3aa38 80550e91 818e3478 00000030 818d5b48
>> > nt!VfDeadlockDeleteMemoryRange+0x13
>> > f8f3aa7c 804ecd0f 818e3478 00000000 8374eed0
>> > nt!ExFreePoolWithTag+0xad
>> > f8f3aad4 804ecd6a 8374eed0 f8f3ab20 f8f3ab14
>> > nt!IopCompleteRequest+0xf4
>> > f8f3ab24 80700ef2 00000000 00000000 f8f3ab3c nt!KiDeliverApc+0xb3
>> > f8f3ab24 f8d54008 00000000 00000000 f8f3ab3c
>> > hal!HalpApcInterrupt+0xc6
>> > WARNING: Frame IP not in any known module. Following frames may be
>> > wrong.
>> > f8f3abac 00416000 0010fe00 00001000 00001000 0xf8d54008
>> > 00000287 00000000 00000000 00000000 00000000 BF2+0x16000
>> >
>> >
>> > SYMBOL_STACK_INDEX: 5
>> >
>> > FOLLOWUP_NAME: MachineOwner
>> >
>> > STACK_COMMAND: kb
>> >
>> > FAILURE_BUCKET_ID: 0xc4_90_IMAGE_splitter.sys_DATE_8_4_2004
>> >
>> > BUCKET_ID: 0xc4_90_IMAGE_splitter.sys_DATE_8_4_2004
>> >
>> > Followup: MachineOwner
>> >
>> >
>> > 0: kd> kb
>> > ChildEBP RetAddr Args to Child
>> > f8f3a9ec 8067a445 000000c4 00000090 ffdff120 nt!KeBugCheckEx+0x1b
>> > f8f3aa0c 8067a73f f8f3aa38 8067ad32 00000000
>> > nt!ViDeadlockCheckStackLimits+0x6e
>> > f8f3aa14 8067ad32 00000000 00000000 00000000
>> > nt!ViDeadlockCanProceed+0x2a
>> > f8f3aa38 80550e91 818e3478 00000030 818d5b48
>> > nt!VfDeadlockDeleteMemoryRange+0x13
>> > f8f3aa7c 804ecd0f 818e3478 00000000 8374eed0
>> > nt!ExFreePoolWithTag+0xad
>> > f8f3aad4 804ecd6a 8374eed0 f8f3ab20 f8f3ab14
>> > nt!IopCompleteRequest+0xf4
>> > f8f3ab24 80700ef2 00000000 00000000 f8f3ab3c nt!KiDeliverApc+0xb3
>> > f8f3ab24 f8d54008 00000000 00000000 f8f3ab3c
>> > hal!HalpApcInterrupt+0xc6
>> > WARNING: Frame IP not in any known module. Following frames may be
>> > wrong.
>> > f8f3abac 00416000 0010fe00 00001000 00001000 0xf8d54008
>> > 00000287 00000000 00000000 00000000 00000000 BF2+0x16000
>> >
>> > "JM Tella Llop [MVP Windows]" escribió:
>> >
>> >> Revisa y pon en practica un articulo mio titulado: "BSOD - Pantalla
>> >> azul.
>> >> Cómo analizar el error" que está publicado en:
>> >> http://www.multingles.net/jmt.htm
>> >>
>> >> Si con el analisis del dump, tienes algun problema posterior,
>> >> comentanoslo.
>> >>
>> >> Jose Manuel Tella Llop
>> >> MVP - Windows
>> >> (quitar XXX)
>> >> http://www.multingles.net/jmt.htm
>> >>
>> >> 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.
>> >>
>> >>
>> >>
>> >> "Ivan" wrote in message
>> >> news:
>> >> > me sale este error en una tipica pantalla azul de WinXp Sp2
>> >> > 0x000000C4(0x00000090,0xFFDFF120,0x00000000,0x00000000)
>> >> > el segundo valor varia, los otros tres hasta ahora siempre
>> >> > iguales.
>> >> > Este error me salio una vez y no le preste atencio, ahora me sale
>> >> > siempre
>> >> > q
>> >> > cargo cualquir mision de un juguito q tengo.
>> >> > No se q puede ser, asi q se los dejo para ver si me pueden
>> >> > ayudar,
>> >> > Saludos
>> >> > y
>> >> > gracias desde ya.
>> >>
>> >>
>> >>
>>
>>
>>

Desactive en la ficha Inicio uno q decia ADGJDet,
todo sigue igual,
tambien obtuve este error q supongo debe ser similar
o almenos eso parece en el dump.

0xC4(0xD,0xFE4276D0,0x0,0x0)

Saludos.


"JM Tella Llop [MVP Windows]" escribió:

Desactiva todo lo de creative de la pestaña Inicio del programa MSCONFIG.
Reinicia y prueba.

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

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.



"Ivan" wrote in message
news:
> Tengo instalados los drivers bajados de la web, un archivo q es un pack de
> drv y soft(LiveDrvUni-Pack(ENG).exe 23MB) y otro q es un patch
> actualizacion(LiveDrvPack_Patch.exe 6MB)
> Que sera?Saludos
>
> "JM Tella Llop [MVP Windows]" escribió:
>
>> ¿con los drivers del CD de Creative o los ultimos bajados de su web?
>>
>> Jose Manuel Tella Llop
>> MVP - Windows
>> (quitar XXX)
>> http://www.multingles.net/jmt.htm
>>
>> 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.
>>
>>
>>
>> "Ivan" wrote in message
>> news:
>> > Tengo una Sound Blaster Live! pci
>> >
>> >
>> > "JM Tella Llop [MVP Windows]" escribió:
>> >
>> >> ¿que tienes de hardware en el subsistema de audio?
>> >>
>> >> Jose Manuel Tella Llop
>> >> MVP - Windows
>> >> (quitar XXX)
>> >> http://www.multingles.net/jmt.htm
>> >>
>> >> 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.
>> >>
>> >>
>> >>
>> >> "Ivan" wrote in message
>> >> news:
>> >> > gracias a todos aqui tienen el Dump:
>> >> >
>> >> > Microsoft (R) Windows Debugger Version 6.4.0007.2
>> >> > Copyright (c) Microsoft Corporation. All rights reserved.
>> >> >
>> >> >
>> >> > Loading Dump File [C:\WINDOWS\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) MP (2 procs) Free
>> >> > x86
>> >> > compatible
>> >> > Product: WinNt, suite: TerminalServer SingleUserTS
>> >> > Built by: 2600.xpsp_sp2_gdr.050301-1519
>> >> > Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
>> >> > Debug session time: Fri Jul 1 19:59:31.187 2005 (GMT-3)
>> >> > System Uptime: 0 days 1:13:57.896
>> >> > Loading Kernel Symbols
>> >> > ..
>> >> > Loading unloaded module list
>> >> >
>> >> > Loading User Symbols
>> >> > .
>> >> > *******************************************************************************
>> >> > *
>> >> > *
>> >> > * Bugcheck Analysis
>> >> > *
>> >> > *
>> >> > *
>> >> > *******************************************************************************
>> >> >
>> >> > Use !analyze -v to get detailed debugging information.
>> >> >
>> >> > BugCheck C4, {90, ffdff120, 0, 0}
>> >> >
>> >> > *** WARNING: Unable to verify timestamp for BF2.exe
>> >> > *** ERROR: Module load completed but symbols could not be loaded for
>> >> > BF2.exe
>> >> > Probably caused by : splitter.sys
>> >> >
>> >> > Followup: MachineOwner
>> >> >
>> >> >
>> >> > 0: kd> !analyze -v
>> >> > *******************************************************************************
>> >> > *
>> >> > *
>> >> > * Bugcheck Analysis
>> >> > *
>> >> > *
>> >> > *
>> >> > *******************************************************************************
>> >> >
>> >> > DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
>> >> > A device driver attempting to corrupt the system has been caught.
>> >> > This
>> >> > is
>> >> > because the driver was specified in the registry as being suspect
>> >> > (by
>> >> > the
>> >> > administrator) and the kernel has enabled substantial checking of
>> >> > this
>> >> > driver.
>> >> > If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1
>> >> > and
>> >> > 0xA
>> >> > will
>> >> > be among the most commonly seen crashes.
>> >> > Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error
>> >> > codes.
>> >> > Typically the code is 0x1001 (deadlock detected) and
>> >> > you
>> >> > can
>> >> > issue a '!deadlock' KD command to get more
>> >> > information.
>> >> > Arguments:
>> >> > Arg1: 00000090, A driver switched stacks. The current stack is
>> >> > neither
>> >> > a
>> >> > thread
>> >> > stack nor a DPC stack. Typically the driver doing this should be
>> >> > on the stack obtained from `kb' command.
>> >> > Arg2: ffdff120
>> >> > Arg3: 00000000
>> >> > Arg4: 00000000
>> >> >
>> >> > Debugging Details:
>> >> >
>> >> >
>> >> >
>> >> > OVERLAPPED_MODULE: rdbss
>> >> >
>> >> > BUGCHECK_STR: 0xc4_90
>> >> >
>> >> > DEFAULT_BUCKET_ID: DRIVER_FAULT
>> >> >
>> >> > LAST_CONTROL_TRANSFER: from 8067a445 to 805371aa
>> >> >
>> >> > IRP_ADDRESS: 8374ee90
>> >> >
>> >> > DEVICE_OBJECT: f8bfef10
>> >> >
>> >> > DRIVER_OBJECT: 8160edf0
>> >> >
>> >> > IMAGE_NAME: splitter.sys
>> >> >
>> >> > DEBUG_FLR_IMAGE_TIMESTAMP: 41107d32
>> >> >
>> >> > MODULE_NAME: splitter
>> >> >
>> >> > FAULTING_MODULE: f8a1d000 splitter
>> >> >
>> >> > STACK_TEXT:
>> >> > f8f3a9ec 8067a445 000000c4 00000090 ffdff120 nt!KeBugCheckEx+0x1b
>> >> > f8f3aa0c 8067a73f f8f3aa38 8067ad32 00000000
>> >> > nt!ViDeadlockCheckStackLimits+0x6e
>> >> > f8f3aa14 8067ad32 00000000 00000000 00000000
>> >> > nt!ViDeadlockCanProceed+0x2a
>> >> > f8f3aa38 80550e91 818e3478 00000030 818d5b48
>> >> > nt!VfDeadlockDeleteMemoryRange+0x13
>> >> > f8f3aa7c 804ecd0f 818e3478 00000000 8374eed0
>> >> > nt!ExFreePoolWithTag+0xad
>> >> > f8f3aad4 804ecd6a 8374eed0 f8f3ab20 f8f3ab14
>> >> > nt!IopCompleteRequest+0xf4
>> >> > f8f3ab24 80700ef2 00000000 00000000 f8f3ab3c nt!KiDeliverApc+0xb3
>> >> > f8f3ab24 f8d54008 00000000 00000000 f8f3ab3c
>> >> > hal!HalpApcInterrupt+0xc6
>> >> > WARNING: Frame IP not in any known module. Following frames may be
>> >> > wrong.
>> >> > f8f3abac 00416000 0010fe00 00001000 00001000 0xf8d54008
>> >> > 00000287 00000000 00000000 00000000 00000000 BF2+0x16000
>> >> >
>> >> >
>> >> > SYMBOL_STACK_INDEX: 5
>> >> >
>> >> > FOLLOWUP_NAME: MachineOwner
>> >> >
>> >> > STACK_COMMAND: kb
>> >> >
>> >> > FAILURE_BUCKET_ID: 0xc4_90_IMAGE_splitter.sys_DATE_8_4_2004
>> >> >
>> >> > BUCKET_ID: 0xc4_90_IMAGE_splitter.sys_DATE_8_4_2004
>> >> >
>> >> > Followup: MachineOwner
>> >> >
>> >> >
>> >> > 0: kd> kb
>> >> > ChildEBP RetAddr Args to Child
>> >> > f8f3a9ec 8067a445 000000c4 00000090 ffdff120 nt!KeBugCheckEx+0x1b
>> >> > f8f3aa0c 8067a73f f8f3aa38 8067ad32 00000000
>> >> > nt!ViDeadlockCheckStackLimits+0x6e
>> >> > f8f3aa14 8067ad32 00000000 00000000 00000000
>> >> > nt!ViDeadlockCanProceed+0x2a
>> >> > f8f3aa38 80550e91 818e3478 00000030 818d5b48
>> >> > nt!VfDeadlockDeleteMemoryRange+0x13
>> >> > f8f3aa7c 804ecd0f 818e3478 00000000 8374eed0
>> >> > nt!ExFreePoolWithTag+0xad
>> >> > f8f3aad4 804ecd6a 8374eed0 f8f3ab20 f8f3ab14
>> >> > nt!IopCompleteRequest+0xf4
>> >> > f8f3ab24 80700ef2 00000000 00000000 f8f3ab3c nt!KiDeliverApc+0xb3
>> >> > f8f3ab24 f8d54008 00000000 00000000 f8f3ab3c
>> >> > hal!HalpApcInterrupt+0xc6
>> >> > WARNING: Frame IP not in any known module. Following frames may be
>> >> > wrong.
>> >> > f8f3abac 00416000 0010fe00 00001000 00001000 0xf8d54008
>> >> > 00000287 00000000 00000000 00000000 00000000 BF2+0x16000
>> >> >
>> >> > "JM Tella Llop [MVP Windows]" escribió:
>> >> >
>> >> >> Revisa y pon en practica un articulo mio titulado: "BSOD - Pantalla
>> >> >> azul.
>> >> >> Cómo analizar el error" que está publicado en:
>> >> >> http://www.multingles.net/jmt.htm
>> >> >>
>> >> >> Si con el analisis del dump, tienes algun problema posterior,
>> >> >> comentanoslo.
>> >> >>
>> >> >> Jose Manuel Tella Llop
>> >> >> MVP - Windows
>> >> >> (quitar XXX)
>> >> >> http://www.multingles.net/jmt.htm
>> >> >>
>> >> >> 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.
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Ivan" wrote in message
>> >> >> news:
>> >> >> > me sale este error en una tipica pantalla azul de WinXp Sp2
>> >> >> > 0x000000C4(0x00000090,0xFFDFF120,0x00000000,0x00000000)
>> >> >> > el segundo valor varia, los otros tres hasta ahora siempre
>> >> >> > iguales.
>> >> >> > Este error me salio una vez y no le preste atencio, ahora me sale
>> >> >> > siempre
>> >> >> > q
>> >> >> > cargo cualquir mision de un juguito q tengo.
>> >> >> > No se q puede ser, asi q se los dejo para ver si me pueden
>> >> >> > ayudar,
>> >> >> > Saludos
>> >> >> > y
>> >> >> > gracias desde ya.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

Perdona denuevo, me olvidava,
taambien probe iniciar el juego con un inico limpio de win(una vez vi ese
articulo)
pero bueno eso no funcionno tambien siguio el error.
Te comento por si sirve de algo.
saludos.


"JM Tella Llop [MVP Windows]" escribió:

Desactiva todo lo de creative de la pestaña Inicio del programa MSCONFIG.
Reinicia y prueba.

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

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.



"Ivan" wrote in message
news:
> Tengo instalados los drivers bajados de la web, un archivo q es un pack de
> drv y soft(LiveDrvUni-Pack(ENG).exe 23MB) y otro q es un patch
> actualizacion(LiveDrvPack_Patch.exe 6MB)
> Que sera?Saludos
>
> "JM Tella Llop [MVP Windows]" escribió:
>
>> ¿con los drivers del CD de Creative o los ultimos bajados de su web?
>>
>> Jose Manuel Tella Llop
>> MVP - Windows
>> (quitar XXX)
>> http://www.multingles.net/jmt.htm
>>
>> 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.
>>
>>
>>
>> "Ivan" wrote in message
>> news:
>> > Tengo una Sound Blaster Live! pci
>> >
>> >
>> > "JM Tella Llop [MVP Windows]" escribió:
>> >
>> >> ¿que tienes de hardware en el subsistema de audio?
>> >>
>> >> Jose Manuel Tella Llop
>> >> MVP - Windows
>> >> (quitar XXX)
>> >> http://www.multingles.net/jmt.htm
>> >>
>> >> 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.
>> >>
>> >>
>> >>
>> >> "Ivan" wrote in message
>> >> news:
>> >> > gracias a todos aqui tienen el Dump:
>> >> >
>> >> > Microsoft (R) Windows Debugger Version 6.4.0007.2
>> >> > Copyright (c) Microsoft Corporation. All rights reserved.
>> >> >
>> >> >
>> >> > Loading Dump File [C:\WINDOWS\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) MP (2 procs) Free
>> >> > x86
>> >> > compatible
>> >> > Product: WinNt, suite: TerminalServer SingleUserTS
>> >> > Built by: 2600.xpsp_sp2_gdr.050301-1519
>> >> > Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
>> >> > Debug session time: Fri Jul 1 19:59:31.187 2005 (GMT-3)
>> >> > System Uptime: 0 days 1:13:57.896
>> >> > Loading Kernel Symbols
>> >> > ..
>> >> > Loading unloaded module list
>> >> >
>> >> > Loading User Symbols
>> >> > .
>> >> > *******************************************************************************
>> >> > *
>> >> > *
>> >> > * Bugcheck Analysis
>> >> > *
>> >> > *
>> >> > *
>> >> > *******************************************************************************
>> >> >
>> >> > Use !analyze -v to get detailed debugging information.
>> >> >
>> >> > BugCheck C4, {90, ffdff120, 0, 0}
>> >> >
>> >> > *** WARNING: Unable to verify timestamp for BF2.exe
>> >> > *** ERROR: Module load completed but symbols could not be loaded for
>> >> > BF2.exe
>> >> > Probably caused by : splitter.sys
>> >> >
>> >> > Followup: MachineOwner
>> >> >
>> >> >
>> >> > 0: kd> !analyze -v
>> >> > *******************************************************************************
>> >> > *
>> >> > *
>> >> > * Bugcheck Analysis
>> >> > *
>> >> > *
>> >> > *
>> >> > *******************************************************************************
>> >> >
>> >> > DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
>> >> > A device driver attempting to corrupt the system has been caught.
>> >> > This
>> >> > is
>> >> > because the driver was specified in the registry as being suspect
>> >> > (by
>> >> > the
>> >> > administrator) and the kernel has enabled substantial checking of
>> >> > this
>> >> > driver.
>> >> > If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1
>> >> > and
>> >> > 0xA
>> >> > will
>> >> > be among the most commonly seen crashes.
>> >> > Parameter 1 = 0x1000 .. 0x1020 - deadlock verifier error
>> >> > codes.
>> >> > Typically the code is 0x1001 (deadlock detected) and
>> >> > you
>> >> > can
>> >> > issue a '!deadlock' KD command to get more
>> >> > information.
>> >> > Arguments:
>> >> > Arg1: 00000090, A driver switched stacks. The current stack is
>> >> > neither
>> >> > a
>> >> > thread
>> >> > stack nor a DPC stack. Typically the driver doing this should be
>> >> > on the stack obtained from `kb' command.
>> >> > Arg2: ffdff120
>> >> > Arg3: 00000000
>> >> > Arg4: 00000000
>> >> >
>> >> > Debugging Details:
>> >> >
>> >> >
>> >> >
>> >> > OVERLAPPED_MODULE: rdbss
>> >> >
>> >> > BUGCHECK_STR: 0xc4_90
>> >> >
>> >> > DEFAULT_BUCKET_ID: DRIVER_FAULT
>> >> >
>> >> > LAST_CONTROL_TRANSFER: from 8067a445 to 805371aa
>> >> >
>> >> > IRP_ADDRESS: 8374ee90
>> >> >
>> >> > DEVICE_OBJECT: f8bfef10
>> >> >
>> >> > DRIVER_OBJECT: 8160edf0
>> >> >
>> >> > IMAGE_NAME: splitter.sys
>> >> >
>> >> > DEBUG_FLR_IMAGE_TIMESTAMP: 41107d32
>> >> >
>> >> > MODULE_NAME: splitter
>> >> >
>> >> > FAULTING_MODULE: f8a1d000 splitter
>> >> >
>> >> > STACK_TEXT:
>> >> > f8f3a9ec 8067a445 000000c4 00000090 ffdff120 nt!KeBugCheckEx+0x1b
>> >> > f8f3aa0c 8067a73f f8f3aa38 8067ad32 00000000
>> >> > nt!ViDeadlockCheckStackLimits+0x6e
>> >> > f8f3aa14 8067ad32 00000000 00000000 00000000
>> >> > nt!ViDeadlockCanProceed+0x2a
>> >> > f8f3aa38 80550e91 818e3478 00000030 818d5b48
>> >> > nt!VfDeadlockDeleteMemoryRange+0x13
>> >> > f8f3aa7c 804ecd0f 818e3478 00000000 8374eed0
>> >> > nt!ExFreePoolWithTag+0xad
>> >> > f8f3aad4 804ecd6a 8374eed0 f8f3ab20 f8f3ab14
>> >> > nt!IopCompleteRequest+0xf4
>> >> > f8f3ab24 80700ef2 00000000 00000000 f8f3ab3c nt!KiDeliverApc+0xb3
>> >> > f8f3ab24 f8d54008 00000000 00000000 f8f3ab3c
>> >> > hal!HalpApcInterrupt+0xc6
>> >> > WARNING: Frame IP not in any known module. Following frames may be
>> >> > wrong.
>> >> > f8f3abac 00416000 0010fe00 00001000 00001000 0xf8d54008
>> >> > 00000287 00000000 00000000 00000000 00000000 BF2+0x16000
>> >> >
>> >> >
>> >> > SYMBOL_STACK_INDEX: 5
>> >> >
>> >> > FOLLOWUP_NAME: MachineOwner
>> >> >
>> >> > STACK_COMMAND: kb
>> >> >
>> >> > FAILURE_BUCKET_ID: 0xc4_90_IMAGE_splitter.sys_DATE_8_4_2004
>> >> >
>> >> > BUCKET_ID: 0xc4_90_IMAGE_splitter.sys_DATE_8_4_2004
>> >> >
>> >> > Followup: MachineOwner
>> >> >
>> >> >
>> >> > 0: kd> kb
>> >> > ChildEBP RetAddr Args to Child
>> >> > f8f3a9ec 8067a445 000000c4 00000090 ffdff120 nt!KeBugCheckEx+0x1b
>> >> > f8f3aa0c 8067a73f f8f3aa38 8067ad32 00000000
>> >> > nt!ViDeadlockCheckStackLimits+0x6e
>> >> > f8f3aa14 8067ad32 00000000 00000000 00000000
>> >> > nt!ViDeadlockCanProceed+0x2a
>> >> > f8f3aa38 80550e91 818e3478 00000030 818d5b48
>> >> > nt!VfDeadlockDeleteMemoryRange+0x13
>> >> > f8f3aa7c 804ecd0f 818e3478 00000000 8374eed0
>> >> > nt!ExFreePoolWithTag+0xad
>> >> > f8f3aad4 804ecd6a 8374eed0 f8f3ab20 f8f3ab14
>> >> > nt!IopCompleteRequest+0xf4
>> >> > f8f3ab24 80700ef2 00000000 00000000 f8f3ab3c nt!KiDeliverApc+0xb3
>> >> > f8f3ab24 f8d54008 00000000 00000000 f8f3ab3c
>> >> > hal!HalpApcInterrupt+0xc6
>> >> > WARNING: Frame IP not in any known module. Following frames may be
>> >> > wrong.
>> >> > f8f3abac 00416000 0010fe00 00001000 00001000 0xf8d54008
>> >> > 00000287 00000000 00000000 00000000 00000000 BF2+0x16000
>> >> >
>> >> > "JM Tella Llop [MVP Windows]" escribió:
>> >> >
>> >> >> Revisa y pon en practica un articulo mio titulado: "BSOD - Pantalla
>> >> >> azul.
>> >> >> Cómo analizar el error" que está publicado en:
>> >> >> http://www.multingles.net/jmt.htm
>> >> >>
>> >> >> Si con el analisis del dump, tienes algun problema posterior,
>> >> >> comentanoslo.
>> >> >>
>> >> >> Jose Manuel Tella Llop
>> >> >> MVP - Windows
>> >> >> (quitar XXX)
>> >> >> http://www.multingles.net/jmt.htm
>> >> >>
>> >> >> 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.
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Ivan" wrote in message
>> >> >> news:
>> >> >> > me sale este error en una tipica pantalla azul de WinXp Sp2
>> >> >> > 0x000000C4(0x00000090,0xFFDFF120,0x00000000,0x00000000)
>> >> >> > el segundo valor varia, los otros tres hasta ahora siempre
>> >> >> > iguales.
>> >> >> > Este error me salio una vez y no le preste atencio, ahora me sale
>> >> >> > siempre
>> >> >> > q
>> >> >> > cargo cualquir mision de un juguito q tengo.
>> >> >> > No se q puede ser, asi q se los dejo para ver si me pueden
>> >> >> > ayudar,
>> >> >> > Saludos
>> >> >> > y
>> >> >> > gracias desde ya.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>