My Pc has crashed & the blue screen of death gave me the following info.
IRQL_NOT_LESS_OR_EQUAL
Tecinal Info: 0x 000 000 0A (0X 979 4A2B 8, 0X 000 000 02, 0X 000 000 01, 0X8201 DC2E)
Do anyone has a idea what in the name of everything that's holy it means?
The pc is running vista (not for much longer thou).
Thx

Please give us more detailed info :

Full machine specs?
What you were doing on the pc at the time it bluescreened?
Does it happen at the same place/time period everytime?

Sure you want to ditch it so soon?

IRQL_NOT_LESS_OR_EQUAL
Tecinal Info: 0x 000 000 0A (0X 979 4A2B 8, 0X 000 000 02, 0X 000 000 01, 0X8201 DC2E)

Could be a hardware conflict.

Have you updated the machines drivers recently?

RAM memory ..

Try reseating your ram.

If you have more than one stick in there remove and test each one seperately.

Let us know.

Except for the dvd drive the system is bout 3 months old, the motherboard was bought earlier this year but
not used until now.
Motherboard: Gigabyte GA-965P-S3
Sound: On board
Display adapters: Nvidia geforce 8600 gt
Ram: 2 x Transcend 1gb ddr2 800 (value ram not high end)
Processor: Core 2 Quad Q6600 Running at 2.4ghz


Vista need some serious work on the graphic drivers, games has a tendency to either crash or freese for a
couple moments after witch vista will inform you that the graphic drivers has stopped working and has recovered. Games like Crysis & Neverwinter Nights 2.
A couple times it even crashed running vista's build in screen savers.

I was playing Diablo 2 lod at the time of the last crash & running free download manager.
I'f run both programs before and sins Single & together with no problems.


The problems is random, it's been almost 1 1/2 months sins the last time.
The problem started a couple days after the system was delivered, some programs is guaranteed to give me a blue screen like a e-book reader from adobe I got with my previous motherboard.
I thought there might be something wrong with the xp installation my pc came with & asked a friend to lend me his copy of vista (he is not using it for some reason) and did a clean install but the problem persisted.
Eliminating problem programs helped a lot but it's still not right.

I'l reseat my ram see what happens.
Thx a lot guys.

Hmmm... i play a lot of LoD on my Vista Machine and don't seem to have a problem. Have you updated the Forceware Drivers for your card. When i got my machine the gtx was giving a hell load of shit, so i updated the driver and that solved the problem

I've had this issue twice before and both times it was the RAM: the first because the two sticks didn't like each other and the second because I didn't seat one stick properly.

Are you overclocking? What are your timings on the RAM?

BTW can we please keep Vista fanboy-ism from taking over yet another thread please?

Has the RAM been removed and tested individually yet?

We've just had this exact problem with a Dell Optiplex 755 here at work. I removed all the RAM, then tested each chip individually, then tested each DIMM in the slots to confirm that it wasn't the RAM slots themselves, then I installed both DIMM's and checked that they were properly seated - problem solved.

Don't ask why but for some reason I don't think it's lod, It was a problem way before lod was even installed.


Overclock no I don't feel I have enough knolige to overclock safely so I generally stay away from it. As for
timings, They are still on the default for the motherboard I haven't even looked where I can adjust it.


I was a bit busy today, will do it and see what hapens it may take some time as the problem is not constantly crashing my pc.
I despise intermittent problems, got them at work also => Got called to a masjine & then watching it run
perfectly for hours on end.
Is there a program that can test ram from inside windows? m skills with dos is just this side from nonexistent.

IN Vista there is a memory diagnostic tool.

Go to Control Panel - Administrative Tools.

You will be required to reboot your machine to let the tool run.

tHX rurounikenshin

Any results from the Diagnostic kaless?

I've found that the Vista tools actually do something, so hopefully you'll get your answer

I reseat my ram (in different slots) & ran the test twice. The windows report vanages to fast for me to catch it but from what I saw looking at it running it found nothing.
As I said it's an intermittent fault, we just wil have to wait & see.

Is the RAM still under warranty by any chance?

Do you have other RAM available for stability testing purposes?

Shoed be the ram came with the system & is less than 3 months old, as for other ram fraid not.
Maby I'l just contack the guy who sold me the system.

Hi Kaless,

I am sorry to hear about your problem. I would recommend using your motherboard's memory checking software (if it has this feature) or a memory testing application that is not dependent on top of Windows Vista - this of course requires you to download a bootable live CD image to test your memory (something that you may deem undesirable).

This could be a physical memory problem, but this is indeed a STOP error message, which is 99% aligned with driver problems.

You could also try disabling memory caching in your BIOS settings and/or placing your memory module (s) in alternative memory banks.

Lastly, you may be like me and want to go to ANY length of finding out why a system behaves the way it does if so, you may do the following:

Download the (very handy) Windows Kernel Debugging Tool, located at:

http://www.microsoft.com/whdc/devtools/deb...ng/default.mspx

What you want to do is open the minidump that was created when this error is created. This can be done by opening windbg, then pressing Control and D.

I then want you to browse to the C:\WINDOWS\Minidump directory and select the most recent .dmp file.

After this ha been done, youwill be presented with a console. In this console, I then need you to type

".symfix"
"reload"
"kb"

From there, there should be a filename that is encoded in hexadecimal form. It is usually the first line present. It would be great for you to say what the output is, but what you then do is take that returned line and add the .sys file extension (or.inf) followed by a quick Google to find out what driver is giving you the headaches.

There is an easier command that does this conversion for you, but I don't know how accurate it is - you would need to type the command "lmv" at the kb# console prompt instead (or after) the instructions in the paragraph above.

I take no responsibility if you decide to follow this methodology

Good luck with this!

Thx for the info RavenServers, I did change the memory slots the pc crashed out 2 times in 2 hours.

Vista won't let me open the .dmp file, say I don't have permission. Do jou know how to change that?
I'm already down as the administrator.

Hi Kaless,

I 'm not sure how to accomplish this by means of the Vista OS - I am definitely not fan of it and won't be for a long time.

I am fairly sure some of the other members know more concerning Vista permissions mechanisms. Sorry I could not help you with this obstacle you are facing with regards to opening the dump file.

Thx again RavenServers I had the guy here that sold me the system, he's a solid oke that will not drop one in
the s***.
Among otherthings my motherbord bios got upgraded from v2 => V12, the old bios did not detect
my cpu for what it is I was losing bout 2ghz & I am running xp again.
The system is more stable but I don't think my problem is gone the next step is to take my pc to the guys at rectron, as my whole pc is still under warranty.