BSOD: irql_not_less_or_equal

Hi Everyone,

I am using a Acer 5920G notebook which was loaded with Vista Home Premium x86. I have format the factory default image/partition and reinstalled Vista Ultimate x64. I am using the drivers which are provided by the notebook manufacturer for 64bit Vista editions. I feel the system is running smooth and stable and I also never notice any errors on the event logs but I have this BSOD (irql_not_less_or_equal) problem which happens 2 times within past 2 weeks. When the first BSOD happens 1 week back I don’t manage to record down the error message or the snap of error BSOD. So I disable the auto restart on BSOD function in advance properties. I encounter the same problem yesterday for second time. I have uploaded the BSOD snap and as well as the minidump. Can someone advise me how I can solve the BSOD problem? Even it’s happen once in a blue moon but I feel uncomfortable with it.

System Specs
===========
Intel C2D T7500 (2.2GHZ)
Nvdia 8600M GT
4GB RAM
250 HDD

BSOD SNAP ( http://www.geocities.com/tamilstrike2k/dsc00031.jpg)
BSOD minidump ( http://www.geocities.com/tamilstrike2k/Mini051408-01.zip)

Thanks in advance guys

 

check out this web page it gives a good explanation of the error as well as the easiest fix:

http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6077.mspx?mfr=true

 

I have the same laptop/os as you and there are some newer drivers which resolve all your problems. I would update all these if I were you. My system is rock solid, I have never had a BSOD with these drivers (running vista ultimate x64)

The turbomemory driver on the acer page has some bugs which could cause bsod's. You can download a newer version from the intel site here.
The same goes for the intel wireless driver. I recommend to get that one from intel as well here

And here are the latest intel chipset drivers

You also want to update your video drivers with these.

Drivers (especialy the 64 bit version) are very outdated on the acer site, lots of newer and much more stable versions are available.

Here are some other drivers you can update:
Ethernet
Bluetooth
Latest Launch Manager
Latest touchpad driver (works fantastic on our system, much better then the ones acer provides)
Realtek HD audio driver

You also want to update your BIOS to the latest version, get that one here

Good luck

M.

 

I did an analasys of your dump file, but it didn't realy help me (maybe someone else has an idea of the cause of the BSOD...)

Code:

Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Mike\Bureaublad\Mini051408-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*d:\symbols\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.amd64fre.longhorn_rtm.080118-1840
Kernel base = 0xfffff800`01c5c000 PsLoadedModuleList = 0xfffff800`01e21db0
Debug session time: Wed May 14 08:49:16.950 2008 (GMT+2)
System Uptime: 0 days 0:49:59.003
Loading Kernel Symbols
...................................................................................................................................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {8, c, 1, fffff80001cb7509}

Probably caused by : win32k.sys ( win32k!SetWakeBit+e6 )

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

1: 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: 0000000000000008, memory referenced
Arg2: 000000000000000c, IRQL
Arg3: 0000000000000001, 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: fffff80001cb7509, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e85080
 0000000000000008 

CURRENT_IRQL:  c

FAULTING_IP: 
nt!KeSetEvent+289
fffff800`01cb7509 48894108        mov     qword ptr [rcx+8],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  taskeng.exe

TRAP_FRAME:  fffffa600d812940 -- (.trap 0xfffffa600d812940)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800a416618 rbx=fffffa600d812a98 rcx=0000000000000000
rdx=fffffa8005f8f8c0 rsi=fffffa8000000000 rdi=2000000070000000
rip=fffff80001cb7509 rsp=fffffa600d812ad0 rbp=fffffa800a7392a8
 r8=0000000000000000  r9=0000000000000000 r10=fffff9600018d364
r11=fffff900c1fad4f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeSetEvent+0x289:
fffff800`01cb7509 48894108        mov     qword ptr [rcx+8],rax ds:00000000`00000008=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001cb112e to fffff80001cb1390

STACK_TEXT:  
fffffa60`0d8127f8 fffff800`01cb112e : 00000000`0000000a 00000000`00000008 00000000`0000000c 00000000`00000001 : nt!KeBugCheckEx
fffffa60`0d812800 fffff800`01cb000b : 00000000`00000001 fffffa80`0a8cf700 fffffa80`0a8cf700 fffffa80`0a7392a0 : nt!KiBugCheckDispatch+0x6e
fffffa60`0d812940 fffff800`01cb7509 : 00000000`00395870 00000000`00000000 fffffa80`0a6fcaf0 00000000`00000000 : nt!KiPageFault+0x20b
fffffa60`0d812ad0 fffff960`0018b7c6 : fffffa80`0a83ec10 00000000`00000000 fffffa80`0a8cf700 fffff800`01f4c5f1 : nt!KeSetEvent+0x289
fffffa60`0d812b40 fffff960`0018d7d9 : 00000000`0000c046 fffff900`c1fad4f0 fffff900`c1fad860 fffff960`00187468 : win32k!SetWakeBit+0xe6
fffffa60`0d812b70 fffff960`0018d5c0 : 00000000`0000c046 00000000`00000000 fffff900`c1fad860 fffff900`c1fad4f0 : win32k!PostThreadMessage+0x151
fffffa60`0d812bd0 fffff800`01cb0e33 : fffffa80`0a8cf700 fffffa60`0d812ca0 00000000`0041c9c0 00000000`0041c9c0 : win32k!NtUserPostThreadMessage+0x25c
fffffa60`0d812c20 00000000`774934ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`038de378 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774934ba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SetWakeBit+e6
fffff960`0018b7c6 488b5c2430      mov     rbx,qword ptr [rsp+30h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  win32k!SetWakeBit+e6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47c78e35

FAILURE_BUCKET_ID:  X64_0xA_W_win32k!SetWakeBit+e6

BUCKET_ID:  X64_0xA_W_win32k!SetWakeBit+e6

Followup: MachineOwner

 

Sounds like drivers to me.

 

That or faulty memory.

 

run prime95 (stress test) and memtest86 overnight to rule out 2 possibilities (CPU and memory).