0x000000a IRQL_NOT_LESS_OR_EQUAL

[Shayx]

getting this one mostly alongside D1.
after few minutes or few hours from turn on, very randmoly.

the rig is AMD VENICE +3200, 2GB (4X512) twinmos memories
ATI HD4530 card (new and the BS was before it was installed)
and a generic HEC 400W PSU.

here is a screenshot i've taken from Bluescreenview
which suggest the problem is with Hal.dll and ntoskrnl.exe

iv'e tested memories with memtest86 for about 3 hours, nothing.
updated video, network and audio drivers - same.

what else can i do?

 

[Ergonpandilus]

Do you happen to have X-Fi soundcard?

 

[Jonathan_King]

I see your video card and network drivers mentioned, but could we please have your actual dmps? http://www.sevenforums.com/crash-lockup-debug-how/34900-1-novice-how-ask-help-bsod-problem.html

 

[Shayx]

well this little program tells you all the details
but i can supply the dump files if needed.

 

[Jonathan_King]

Yes, we need to actual files. BlueScreenView is very easy to use, but not very accurate. Windows Debugging Tools is a lot more informative.

 

[Shayx]

ok
well after i googled for this issue i found that using the verifier can find bad drivers.
so i turn it on and got several bluescreens, C1 and C4
half of them talked about magiciso SCSI host controller, so i uninstalled it completly with revo software, so all the letfovers and registery keys were deleted too.
also i ran the signed driver check, it scaned 202 drivers and says that 2 are unsigned, one was MCDBUS.SYS (related to magiciso) and TCPIP.SYS but that's a system file so i don't know what to do with it.

here is a zip file with all the BSOD's. for now i stopped the verifier and the computer is turned on, waiting to see if he get a BSOD.

here is the minidump files:
Minidump.rar - File Shared from Box.net - Free Online File Storage

 

[whs]

I assume you saw this but I'll link it just in case: Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

 

[Ergonpandilus]

Minidump strongly suggests that your SCSI driver is bad. What is your motherboard? I recommend to update your BIOS ja mobo drivers if you haven't done it yet. And it might be a good idea to contact your mobo manufacturer, they usually reply quite fast.

 

[Shayx]

i know
it was the Magiciso SCSI host controller
i uninstalled the program including registry entries and currently waiting to see
if it solved the problem.

i will update.

 

[YakSipper]

Netlimiter is the source of issues too, along with the SCSI Host Controller (MagicIso?). Uninstall them.

Unable to load image \??\C:\Windows\system32\drivers\nltdi.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nltdi.sys
*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys
Probably caused by : nltdi.sys ( nltdi+c5be )

I'd also update the NVIDIA network driver to latest:

Unable to load image \SystemRoot\system32\DRIVERS\nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
Probably caused by : nvmf6264.sys ( nvmf6264+69c3 )

 

[Shayx]

ok, if the bluescreens will return i'll uninstall netlimiter too.

 

[Ergonpandilus]

I got the same error. WindDbg says that probably caused by: hardware (nt!PoIdle+4f).

How do I come to know which HW that actually is?

 

[Jonathan_King]

I got the same error. WindDbg says that probably caused by: hardware (nt!PoIdle+4f).

How do I come to know which HW that actually is?

Hardware often means RAM, CPU, motherboard. See this post: http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and run at least 5 passes.

If you are overlocking, stop.

 

[Ergonpandilus]

Can you f*cking believe it! I bought 4x1GB A-DATA DDR3 1333 Rams half year back and one of them broke early this year and I got it back from warranty justtwo months back.

And NOW the memtest failed! This time it was other pair. I'm never ever going to buy A-DATA rams anymore. Luckily the warranty is still valid.

Thanks for the advice, I never thought that it would be RAM again.

 

[Jonathan_King]

Any time Memtest suggests bad RAM, it could also be a bad motherboard slot. If you can borrow some RAM from a friend, and it checks out bad, replace your mobo.

 

[Ergonpandilus]

I have four slots so I tried out different combinations.

All (4) mems SLOTS 1-4 -> Fails
Pair B only in SLOTS 3-4 -> Succeeds
Pair A only in SLOTS 1-2 -> Fails
Pair B only in SLOTS 1-2 -> Succeeds

Outcome, slots (and mobo) is fine and pair A has bad memory.

I'm going to try out tomorrow pair A only in SLOTS 3-4, but I bet the outcome is the same.

 

[zigzag3143]

I have four slots so I tried out different combinations.

All (4) mems SLOTS 1-4 -> Fails
Pair B only in SLOTS 3-4 -> Succeeds
Pair A only in SLOTS 1-2 -> Fails
Pair B only in SLOTS 1-2 -> Succeeds

Outcome, slots (and mobo) is fine and pair B has bad memory. I'm going

I'm going to try out tomorrow pair B only in SLOTS 3-4, but I bet the outcome is the same.

Which pair is bad? In the chart "B" succeeds, and in the text you say "B" has bad?

Ken

 

[Ergonpandilus]

Oops.

I meant Pair A is bad.