Buonasera a tutti

Il mio pc è un athlon XP 2800 2.09GHz e 1 GB di ram con Windows XP Professional SP3, da un 15 giorni mi compaiono delle schermate blu con scritto IRQL_NOT_LESS_OR_EQUAL e poi STOP e vari 0x qualcosa senza nulla di più specifico.
Ho utilizzato ripristino conf. di sistema ma non ho risolto cosi cercando in google ho scaricato WindowsDEbug eho aperto l'ultimo file di crash e sostanzialmente ce scritto questo:

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


Loading Dump File [C:\WINDOWS\Minidump\Mini052711-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 ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b240
Debug session time: Fri May 27 08:44:38.656 2011 (UTC + 2:00)
System Uptime: 0 days 12:23:12.216
Unable to load image 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 1000000A, {2, ff, 1, 804de884}

Probably caused by : hardware ( nt!KiServiceExit+87 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000002, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, bitfield :
   bit 0 : value 0 = read operation, 1 = write operation
   bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 804de884, address which referenced memory

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


WRITE_ADDRESS:  00000002

CURRENT_IRQL:  ff

FAULTING_IP:
nt!KiServiceExit+87
804de884 0100            add     dword ptr [eax],eax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  AVSVideoConvert

MISALIGNED_IP:
nt!KiServiceExit+87
804de884 0100            add     dword ptr [eax],eax

LAST_CONTROL_TRANSFER:  from 7c91e514 to 804de884

STACK_TEXT:  
a8e9bd64 7c91e514 badb0d00 0012fec4 00000000 nt!KiServiceExit+0x87
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012feec 00000000 00000000 00000000 00000000 0x7c91e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiServiceExit+87
804de884 0100            add     dword ptr [eax],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!KiServiceExit+87

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

Followup: MachineOwner
---------
Ho controllato anche la ram con memtest più volte e mi da sempre 0 errori.

Cosa devo fare?

Ciao nik87.

Naturalmente l'errore non è connesso con certezza alla memoria centrale, anche se esso può essere un sintomo di rotture hardware della RAM.

Direi di accedere al BIOS del sistema e ripristinare le sue impostazioni predefinite; usa un pò il PC e vedi come risponde.

Se il problema si ripete, e se la RAM in tuo possesso è composta da più moduli, testane uno alla volta.

Più in generale, hai installato nuovo hardware e/o nuovi driver di recente?  


Fammi sapere,


Ciao ciao

il tutto è iniziato quando dopo aver installato allplan 2008 mi usciva l'errore la memoria non poteva essere read e si chiudeva il programma. Cercando in internet trovai questo http://www.azpoint.net/articoli.asp?id=12063 e dopo qualche giorno dopo aver eseguito il passaggio dove dice di aggiornare le dll di windows è comparso questo errore. allplan ora è disinstallato. Un solo banco di ram da 1 GB e 0 errori con memtest

ah dimenticavo ho scaricato anche who crasched e mi da questo:


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

computer name: FORD01
windows version: Windows XP Service Pack 3, 5.1, build: 2600
windows dir: C:\WINDOWS
CPU: AuthenticAMD AMD Athlon(tm) XP 2800+ AMD586, level: 6
1 logical processors, active mask: 1
RAM: 1073201152 total
VM: 2147352576, free: 2064822272



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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Fri 27/05/2011 6.44.38 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini052711-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7884)
Bugcheck code: 0x1000000A (0x2, 0xFF, 0x1, 0xFFFFFFFF804DE884)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\memory.dmp




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

On your computer a total of 2 crash dumps have been found. Only 1 could be analyzed.
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.

nuovo crasch:

On Sun 29/05/2011 7.45.09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini052911-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5353)
Bugcheck code: 0x1000000A (0x4, 0x2, 0x1, 0xFFFFFFFF804DC353)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Sistema e kernel NT
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

OK, è molto probabile che il guasto sia a livello software...per cui puoi lanciare la funzionalità di Ripristino configurazione di sistema, utilizzando come punto di ripristino quello più recente possibile che risulti, ovviamente, precedente all'installazione del programma che hai citato.

Fammi sapere.


Ciao ciao

ciò provato ma non ho più punti di ripristino prima del 20 maggio e non capisco il perchè:que: