Event Id 1003

Ok, deja que llegue a casa y te comento por el momento atendere algunos
problemillas aqui...

saludos

"Carlos Sánchez" <ctsg#ctsgnetwork.com> wrote in message
news:
Prueba a restaurar el sistema. Tendras realizado un punto de restauracion
realizado por el sistema antes de la instalacion. Quizas ha sido eso, pero
de momento prueba con eso.

Salu2

Carlos Sánchez

http://www.ctsgnetwork.com
Las Palmas




"Alex Romero Q. (ec)" escribió en el mensaje
news:

instale el sabado el windvd para ver DVD en la computadora, todo quedo

bien

hasta hoy en la mañana que quise realizar una impresion de un archivo en
casa...

saludos



"Carlos Sánchez" <ctsg#ctsgnetwork.com> wrote in message
news:
Ayudaria un poco mas si miras en el visor de sucesos. Para llegar hasta

ahi,

ve a Mi PC --> Boton derecho "Propiedades" > Administrar > Visor de
sucesos > Sistema. Doble click sobre el error y pica donde el icono de
copiar y peganos aqui el error ya que solo con el Suceso no podemos saber
cual es especificamente el error, pero recuerdas se hace poco has
actualizado algun drivers o algo?

Salu2

Carlos Sánchez

http://www.ctsgnetwork.com
Las Palmas




"Alex Romero Q. (ec)" escribió en el mensaje
news:
> Gracias por ayudarme, te cuento
> Tengo WinXP Ingles Sp1+ Todos los SP y actualizaciones de los driver de
> acuerdo al WU.
>
> El mensaje me aparecio hoy en la mañana, al momento de encender y me
aparece
> el mensaje erro en el recover system, el visor del evento aparece el

error

> 1003, lo unico que no recuerdo son los numeros que le sigue ya q
> la pc es la de mi casa.
>
>

Aqui estan los codigos restantes...
Date: date
Source: System
Error Time: time
Category: (102)
Type: Error
Event ID: 1003
User: N/A
Computer: computer
Description: Error code 00000050, parameter1 0xffffffe0, parameter2
0x00000001, parameter3 0xf30da010, parameter4 0x00000000. For more
information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20
45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64
65 ror code 0018: 20 30 30 30 30 30 30 35 00000MN 0020: 30 20 20 50 61 72 61
6d 0 Param 0028: 65 74 65 72 73 20 66 66 eters ff 0030: 66 66 66 66 64 31 2c





gracias

Mira esta informacion que te pego e insisto, puede haber sido por el WINDVD. Pero si te sigue dando ya miramos mas:

Fuente de los datos: http://www.eventid.net/display.asp?eventid03&source
Source System
Type Error
Description Error code <error code>, parameter1 <value>, parameter2 <value>, parameter3 <value>, parameter4 <value>.
Comments Adrian Grigorof
Most of the problems leading to this event indicate faulty hardware, bugs in device drivers or incompatible hardware.

A troubleshooting approach from a newsgroup post: "Boot from CD to start the Recovery Console, then read setuplog.txt, and setupapi.log, to see what happens when it boots.

Another newsgroup posts suggests that this error requires the debugger to look at the parameters of the error. Usually this is some hardware driver failure. Running 'verifier' may identify it. Article Q244617 - How to Use Driver Verifier to Troubleshoot Device Drivers in Windows 2000 may help."

Error code 0000000a = "IRQL_NOT_LESS_OR_EQUAL" - The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS. If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Error code 0000009c = "MACHINE_CHECK_EXCEPTION" - This indicates that a fatal machine check exception has occurred. See also Q162363.

Error code 000000ce = "DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS" - This indicates that a driver failed to cancel pending operations before unloading. If the driver responsible for the error can be identified, its name is printed on the blue screen.

Error code 000000ea = "THREAD_STUCK_IN_DEVICE_DRIVER" - A device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. In many cases this is the result of a bad video card or a bad display driver.

Error code 1000007f = "UNEXPECTED_KERNEL_MODE_TRAP_M" - The first parameter displayed on the blue screen specifies the trap number. Trap number 0x00000000, or Divide by Zero Error, may indicate memory corruption. Other hardware problems, or software failures can cause this error. See the the link to Bug Check codes for more explanations about various trap numbers.

Error code 1000008e = "KERNEL_MODE_EXCEPTION_NOT_HANDLED_M" - Most of newsgroup comments about this error point to faulty hardware or drivers. The hardware varies from modems, video cards, USB device to memory or sound cards. Sometimes it proves to be hardware that it is not compatible with Windows XP. Q310740 gives an example of this error occuring when and old Audigy sound card driver is installed.

Error code 100000be = "ATTEMPTED_WRITE_TO_READONLY_MEMORY" - This is issued if a driver attempts to write to a read-only memory segment. If the driver responsible for the error can be identified, its name is printed on the blue screen. A faulty device driver would typically be the cause of that. Also, potential file corruption.

Error code 100000ea = "THREAD_STUCK_IN_DEVICE_DRIVER_M" - This indicates that a thread in a device driver is endlessly spinning. See the information for 000000ea.

Adrian Florin Moisei (Last update 5/15/2003):
Error code 000000d1 = "DRIVER_IRQL_NOT_LESS_OR_EQUAL". A faulty device driver would typically be the cause of that. See also the comments for event id 1001 from "Save Dump".

Error code 000000c2 = "BAD_POOL_CALLER" - See Q265879 link below.
Error code 00000044 = "MULTIPLE_IRP_COMPLETE_REQUESTS" - See Q196022, Q296734 and Q294876.

Birol | AKBAY
In my case, this error for a motherboard using Bus Mastering and a NIC that does not support Bus Mastering. When Bus mastering is disabled from BIOS, this type of error went away.

PaulD
Windows XP SP1 resolve this issue. See Q317277.

Charlton Wang
From the net, someone mentioned setting the Virtual memory to 0 and then reboot, delete the pagefile.sys file. Then set the virtual memory back to normal. It worked for me.

Axton
Turned out to be BlackIce v2.9 causing blue screen.

Anonymous
With error code 100000ea, this occured in my case due to a faulty video card.
Links Q196022 , Q244617 , Q265879 , Q294876 , Q296734 , Q310740 , Q317277 , Interpreting Bug Check Codes
Send comments - Notify me when updated!
Automatic search for "Event 1003 System" at:
Support @ Microsoft - Search @ Microsoft - Google Newsgroups - Google Microsoft

Carlos Sánchez

http://www.ctsgnetwork.com
Las Palmas




"Alex Romero Q. (ec)" escribió en el mensaje news:eQ#iX#

Aqui estan los codigos restantes...
Date: date
Source: System
Error Time: time
Category: (102)
Type: Error
Event ID: 1003
User: N/A
Computer: computer
Description: Error code 00000050, parameter1 0xffffffe0, parameter2
0x00000001, parameter3 0xf30da010, parameter4 0x00000000. For more
information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp. Data: 0000: 53 79 73 74 65 6d 20
45 System E 0008: 72 72 6f 72 20 20 45 72 rror Er 0010: 72 6f 72 20 63 6f 64
65 ror code 0018: 20 30 30 30 30 30 30 35 00000MN 0020: 30 20 20 50 61 72 61
6d 0 Param 0028: 65 74 65 72 73 20 66 66 eters ff 0030: 66 66 66 66 64 31 2c





gracias