help - Errori di windows!

[ves81]

perdonate il titolo fasullo ma altrimenti nessuno avrebbe letto il mio 3d

Qualcuno sa dirmi come posso risolvere i seguenti errori e dirmi in parole povere cosa significa la pappardella che mi ha rilasciato microsoft??

e soprattutto cosa si può fare per eliminarli?
grazie

ERRORE 1 *******************
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Informazioni tecniche:
***STOP: 0x000000D1 (0xC5DA6018,0x00000002,0x00000000,0Xf81a2126)
***portcls.sys - Address F81A2126 base at F81A1000, DateStamp 3d6de2ca



The Stop 0xD1 message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.

Interpreting the Message
This Stop message has four parameters:

Memory referenced.
IRQL at time of reference.
Type of access (0x00000000 = read operation, 0x00000001 = write operation).
Address that referenced memory.
Resolving the Problem
For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error. If so, contact the manufacturer about a possible update. Using updated software is especially important for backup programs, multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
For more information about Stop 0xD1 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x000000D1, and 0xD1.

ERRORE 2 *******************************************
BAD_POOL_CALLER
Informazioni tecniche:
***STOP: 0x000000C2 (0x00000007, 0x00000CD4,0x45F0800,0x81956C28)




The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:

By allocating a memory pool size of zero bytes.
By allocating a memory pool that does not exist.
By attempting to free a memory pool that is already free.
By allocating or freeing a memory pool at an IRQL that was too high.
This Stop message is typically due to a faulty driver or software.

Interpreting the Message
Table C.5 describes the information provided by Stop 0xC2 messages. The value of the first parameter indicates the type of violation (see the Description column) and determines the meaning of the next three parameters.

Table C.5 Parameter Listing for Stop Message 0xC2

Parameter 1 Parameter 2 Parameter 3 Parameter 4 Description
0x00000000 This value is always 0 The pool type being allocated The pool tag being used The caller is requesting a zero byte pool allocation
0x00000001, 0x00000002, or 0x00000004 Pointer to pool header First part of pool header contents This value is always zero Pool header has been corrupted

0x00000006 Reserved Pointer to pool header Pool header contents Attempt to free a memory pool that was already freed

0x00000007 Reserved Pointer to pool header This value is always zero Attempt to free a memory pool that was already freed

0x00000008 Current IRQL Pool type Size of allocation Attempt to allocate pool at invalid IRQL

0x00000009 Current IRQL Pool type Address of pool Attempt to free pool at invalid IRQL

0x00000040 Starting address Start of system address space This value is always zero Attempt to free usermode address to kernel pool

0x00000041 Starting address Physical page frame Highest physical page frame Attempt to free a non-allocated nonpaged pool address

0x00000042 or 0x00000043 Address being freed This value is always zero This value is always zero Attempt to free a virtual address that was never in any pool

0x00000050 Starting address Start offset in pages from beginning of paged pool Size in bytes of paged pool Attempt to free a non-allocated paged pool address

0x00000099 Address being freed This value is always zero This value is always zero Attempt to free pool with invalid address or corruption in pool header

0x0000009A Pool type Size of allocation in bytes Allocation's pool tag Attempt to allocate must-succeed

Resolving the Problem
The following suggestions are specific to Stop 0xC2 errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

A Stop 0xC2 message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
A Stop 0xC2 message might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.
If you encounter a Stop 0xC2 message while upgrading to Windows XP Professional, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP Professional, contact the hardware manufacturer to obtain compatible updates. For more information about simplifying your system for troubleshooting purposes, see " Troubleshooting Concepts and Strategies" and "Troubleshooting Startup" in this book.
For more information about Stop 0xC2 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x000000C2, and 0xC2.

ERRORE 3 ********************************************
PAGE_FAULT_IN_NONPAGED_AREA
Informazioni tecniche:
***STOP: 0x00000050 (0xC664BC48,0x00000000,0x805A1E20,0x00000000)


The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.

Interpreting the Message
This Stop message has four parameters:

Memory address that caused the fault.
Type of access (0x00000000 = read operation, 0x00000001 = write operation).
If not zero, the instruction address that referenced the address in parameter 0x00000001.
This parameter is reserved (set aside for future use).
Resolving the Problem
The following suggestions are specific to Stop 0x50 errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.
Stop 0x50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.
For more information about Stop 0x50 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x00000050, and 0x50.



configurazione sistema:
Intel® Pentium® 4 CPU 2.80GHz
512 MB Ram
Scheda madre: produttore n/a – P4TSE-D2
Bios: Phoenix – awardBIOS v6.00PG
DirectX 9.0b (4.09.0000.0902)

Maxtor 6Y080L0 80GB
Samsung cdrw/dvd sm-352b
ATI Technologies Inc. - Radon 9200 Series 128 MB (v.6.14.10.6476 data 25/08/2004)
Creative SB Audigity LS (v.5.12.1.255 data 04/02/2003 – no update on www.creative.com)

Microsoft Windows XP Home edition versione 2002 SP1

[K-Line]

a occhio e croce dovrebbero essere i driver della scheda audio...
li hai già aggiornati all'ultima versione?

[K-Line]

sul sito della creative c'è il "AUDLS_PCDRV_LB_1-02-00.exe" che, a quanto pare, fra le altre cose "Risolve i problemi di stallo e di riavvio del sistema associati ai titoli dei giochi selezionati."

[Swos]

bel titolo


ma nn lo fare +, xke le discussioni si leggono lo stesso!

[MaxFun73]

Visto il titolo ingannevole non ti meriteresti una risposta, cmq. visto che una mano non si nega a nessuno... vai sul sito di Microsoft e fai una ricerca sulla Knowledge Base utilizzando i codici di errore che ti ha mostrato Windows:

STOP: 0x000000D1 0xC5DA6018,0x00000002,0x00000000,0Xf81a2126

...mannaggia, stavo già pensando alla biondina..

[Handy]

Originariamente inviato da MaxFun73




...mannaggia, stavo già pensando alla biondina..

Anch'io

[Psiche]

Ho modificato il titolo...

cercate di esser chiari senza ricorrere a trucchetti...