Bugcheck IRQL_NOT_LESS_OR_EQUAL has several reasons to be thrown. This
particular instance was caused by a kernel driver dereferencing a null
pointer.
Unfortunately, I don't see an obvious culprit in the crash dump file - as
the binary that dereferenced the pointer is Win32k.sys. In situations
like this, Win3k.sys is most likely the victim of another kernel driver
doing something bad.
To see what kinds of drivers/software you may have recently installed,
you can look at the [%windir%\inf\setupapi.*.log] files.
It appears that you do not have a driver loaded for your display
adapter - but instead are using VGA.sys. Is there a reason for this?
Also, I could not find any information on the kernel driver awgqdlyk.sys,
which is loaded on your machine. You can find this file in your
[%windir%\system32\drivers] folder. You might want to see what that file
is, and where it came from.
Hi Abubakar,
Please upload the crash dump file to the following URL:
https://sftus.one.microsoft.com/choosetransfer.aspx?key=1fa89359-ae3c-444f-8f40-cbd3adb352c8
Please note: This file transfer session will be removed once you upload
the file.
right now i'm on this page:
http://www.microsoft.com/whdc/DevTools/Debugging/symbolpkg.mspx
Hi, Abubakar.
Rick is the expert here, not me. But I think the heart of your
problem is here:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 00000000
BCP2: 0000001B
BCP3: 00000001
BCP4: 83043A7F
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Your "BCCode: a" corresponds to Stop Code 0x0A. My starting point for
researching Stop Codes is:
TROUBLESHOOTING WINDOWS STOP MESSAGES
http://www.aumha.org/a/stop.htm
One of the first listings there is:
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
There are many possible causes and solutions for this error,
"Typically due to a bad driver, or faulty or incompatible hardware or
software."
This should give you some ideas of the kinds of questions Rick will
need you to answer in your next post.
RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP
Windows Live Mail 2009 (14.0.8064.0206) in Win7 Ultimate x64 RC 7100
Hi,
The details of the blue screen are crucial to identifying the
problem. Error codes, parameters, and any modules involved can all
provide clues. Check the event log for details and post them.
The second "crash" sounds more like a hardware freeze, not an
operating system issue but rather a problem component. Could also be
related to overheating.
--
Best of Luck,
Rick Rogers, aka "Nutcase" - Microsoft MVP
Windows help -
www.rickrogers.org
My thoughts
http://rick-mvp.blogspot.com
Hi,
My vista crashed 2 times today. This is probably the first time
since december 2007 when I bought my laptop with Vista. I know the
usual question would be to check if I installed some new drivers or
any hardware device but thats not the case as far as I know. Its a
Vista Ultimate system, with a cor 2 duo 2.ghz, 2gb ram, wifi etc.
The first time it crashed today was with a blue screen with the
usual bsod stuff printed on it (I know it can be different stuff
written there but right now I dont know the exact stuff other than
'check for new hardware installation' msg). i was running visual
studio 2005 doing asp.net development with it. The second time when
it crashed it hanged and the computer made one beep sound, but no
bsod, the computer just didnt reply, and here also I was debugging
something in asp.net in vs 2k5.
Is there any software that that provide me some information that
may help me find out exactly whats wrong? Some internal diagnostic
software that maybe ships with vista?
regards.
event log is so huge, there r enteries about every second ! And
search was taking time. I will search for more, but after the second
crash the following was displayed when i logged in:
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
BCCode: a
BCP1: 00000000
BCP2: 0000001B
BCP3: 00000001
BCP4: 83043A7F
OS Version: 6_0_6001
Service Pack: 1_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\Mini051409-01.dmp
C:\Users\Ab\AppData\Local\Temp\WER-99450-0.sysdata.xml
C:\Users\Ab\AppData\Local\Temp\WER192A.tmp.version.txt
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
The WER* files are not at there mentioned place, but the dump file is
there. I remember reading someone's blog that the dump file can be
opened with windbg ?
In the meanwhile the system crashed one more time with blue screen.
..ab
