[/QUOTE]The actual error messages (and parameter values) are documented in the Windows DDK (which you can download from
www.microsoft.com/ddk (and also accesible via MSDN Library).
Windows maintains a set of IRQ Levels (32 on x86 32 bit, and 16 on x86 64 bit and ia64/Itanium).
Level 0 is always "passive" (i.e. no interrupt). The highest levels (i.e. levels 28->31, or level 13->15, depending on the platform) are reserved for critical system interrupts (e.g. the system clock, or halting the system due to a critical STOP - which results in a Blue Screen of Death).
The lowest two levels: 1 and 2 are used for software interrupts (Level 1 is APC - Asynchronous Procedure Call, and Level 2 is Dispatch/Deferred Procedure Call).
The other levels (Level 3 upwards) are used for hardware interrupts. When an interrupt occurs (hardware or software) the IRQL (IRQ Level) is raised. When the IRQL is raised, all interrupts that occur at a lower level are "masked" (basically, ignored). So, if the IRQL has been raised to Level 10, then any level 8 IRQs are ignored until the current executing thread signals that it is ready to lower the current IRQL (via a kernel routine: KeLowerIRQL). The system then checks to see if there are any other Level 10 interrupts, and if not, any level 9 interrupts, and if not, any level 8 interrupts. At that point, the level 8 interrupt will be processed.
Now, accessing paged memory occurs at the Dispatch/DPC Level (level 2). If a hardware device has generated an interrupt which has raised the IRQL (to 3 or greater), and the device driver (or whatever code is assigned in the IDT to handle the interrupt) then attempts to access paged memory, the operation can not be completed, because accessing paged memory uses a lower IRQL (level 2), but all operations that utilise lower IRQLs lower than the current IRQL are masked out. So, you end up in a deadlock situation. The current thread wants to access paged memory, but that can't happen until the current thread has finished what it's doing and is ready to lower the IRQL. Because there's a deadlock, Windows will halt the system with an 0x0000000A (IRQL_Not_Less_Or_Equal) bug check.[/QUOTE]
Sve u svemu ovde se spominje skidanje najnovijih drajvera za plocu i graficku,a cak sam negde bio i iscackao da i wmp 11 oce da napravi ovu gresku kao i neki codec pakovi.Probaj i sa drugim kodecima.
Takodje jos jedno pitanje> Da li mozda kacis modem na USB? Ako da i ako je moguce okaci ga na lan ili na drugi usb port iako je u svakom slucaju bolje na lan.
I naravno reset biosove liste hardvera.Ne secam se tacno gde je ta opcija u biosu ali se zove "Reset configuration data"
Evo sta i Microsoft kaze oko ovoga
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314063