Constant BSOD IRQL_NOT_LESS_OR_EQUAL

Status
Not open for further replies.
I

imouto

Posts: 14   +0
I really hope someone can help me here since these BSODs are greatly slowing down my work. My computer was working fine till 10/28/06. For work reasons I needed to install the Apache web server and the Coldfusion server onto my computer. It was after this that I started getting BSOD a lot, about every couple of hours while running Dreamweaver, Apache, Coldfusion, and a couple of browsers.

To try to fix the problem I have uninstalled Apache and Coldfusion but still get the BSODs. I also uninstalled and reinstalled my video driver. No luck. I keep getting the same BSOD message: IRQL_NOT_LESS_OR_EQUAL.
In Event Viewer I get the same system error message: Event ID: 1003, Filename: faultrep.dll, Description: Error code 000000d1, parameter1 00000009, parameter2 0000002, parameter3 00000000, parameter4 00000009.

I've tried opening up my computer and cleaning out the dust. I've cleared my pagefile, defragged my hard drive, ran scans using Spybot, Adaware, AVG Antivirus, ewido Anti-spyware, ran memtest, but still no luck. I pretty much can get the BSOD just from using Photoshop for about a 1/2 hr - 1 hour. I also get after surfing the web for a bit.

This is really frustrating since I have work that's due pretty soon. Any help would greatly appreciated. I've attached the last 6 minidumps. Oh, and my PC configuration is:

CPU: Celeron-S, 1300 MHz
Motherboard: AOpen AX34-U
Ram: 384 MB (3 sticks each 128MB)
GPU: ATI Rage Fury
OS: Windows XP Pro
PSU: AOpen ATX-250N

Thanks in advance.
 
I have already tried uninstalling and reinstalling the video card driver but that still hasn't helped. I've tried this three times so far.

I've also run memtest already (as I had mentioned in my original post) and it didn't turn up any errors.

Any other suggestions?
 
xxdanielxx said:
are u using the newest version for your ati if not update
Click to expand...

Yes, it's the latest. I grabbed it from the ATI site. It's the latest they had for such an old video card. Does any of this info from my latest memory.dmp file mean anything?

Code: 
Use !analyze -v to get detailed debugging information.

BugCheck A, {e1852acc, ff, 0, 804f3458}

*** ERROR: Module load completed but symbols could not be loaded for ati2dvaa.dll
Probably caused by : ati2dvaa.dll ( ati2dvaa+4587 )

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

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: e1852acc, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 804f3458, address which referenced memory

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


READ_ADDRESS:  e1852acc Paged pool

CURRENT_IRQL:  ff

FAULTING_IP: 
nt!KeRestoreFloatingPointState+78
804f3458 f60301           test    byte ptr [ebx],0x1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from bf8b5115 to 804f3458

TRAP_FRAME:  effac45c -- (.trap ffffffffeffac45c)
ErrCode = 00000000
eax=824f4020 ebx=e1852acc ecx=00000004 edx=00000000 esi=824f4020 edi=effad920
eip=804f3458 esp=effac4d0 ebp=effac4e4 iopl=0         nv up di pl zr na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010046
nt!KeRestoreFloatingPointState+0x78:
804f3458 f60301           test    byte ptr [ebx],0x1      ds:0023:e1852acc=04
Resetting default scope

STACK_TEXT:  
effac4e4 bf8b5115 824f4020 bf997587 e1852ac8 nt!KeRestoreFloatingPointState+0x78
effac4ec bf997587 e1852ac8 effac538 effad2a4 win32k!EngRestoreFloatingPointState+0x1a
WARNING: Stack unwind information not available. Following frames may be wrong.
effac508 bf994a17 e167eae8 f2427d64 00000858 ati2dvaa+0x4587
effacc10 bf8b4d48 00000858 00000000 effad2ac ati2dvaa+0x1a17
effacc70 bf822e1a e167b010 e2fc9490 00000000 win32k!GreReleaseSemaphore+0xa
effad2f4 bf8bb35e e2fc9490 e1654000 e1afe978 win32k!EngTextOut+0x447
effad340 bf8bf749 bf8229d3 effad3c4 e2fc9490 win32k!OffTextOut+0x6f
effad3d4 bf803bd5 e2fc9490 effad430 e1afe978 win32k!SpTextOut+0x9b
effad65c bf8f55f6 effad854 e149f4dc e149f538 win32k!GreExtTextOutWLocked+0xf5c
effad7bc bf800b16 effad854 7ffde1dc 000000e8 win32k!GreBatchTextOut+0x2c7
effad884 80528783 000000de 0012ea64 0012f6ac win32k!NtGdiFlushUserBatch+0xdd
effad884 7ffe0304 000000de 0012ea64 0012f6ac nt!KiSystemService+0x96
0012ea7c 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4


FOLLOWUP_IP: 
ati2dvaa+4587
bf997587 5f               pop     edi

SYMBOL_STACK_INDEX:  2

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  ati2dvaa+4587

MODULE_NAME:  ati2dvaa

IMAGE_NAME:  ati2dvaa.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  3bb2ac1f

STACK_COMMAND:  .trap ffffffffeffac45c ; kb

FAILURE_BUCKET_ID:  0xA_VRF_ati2dvaa+4587

BUCKET_ID:  0xA_VRF_ati2dvaa+4587

Followup: MachineOwner
 
well u get a bug check of BUGCHECK_STR: 0xA wich is due to antivirus,drive fault and third pary hardware wich we know by the mini dump that it is ati2dvaa.dll. Looking at your mini dump I see this
effac4e4 bf8b5115 824f4020 bf997587 e1852ac8 nt!KeRestoreFloatingPointState+0x78. looking at 0x78 this is what i got. You may receive a STOP 0x00000078 if the NonPagedPoolSize registry setting is more than seven-eighths of physical memory. o work around this problem, change the registry setting so that the NonPagedPoolSize value is less than seven-eighths of physical memory.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

1. Run Registry Editor and open the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control \Session Manager\Memory Manageme

NOTE: The above registry key is one path; it has been wrapped for readability.
2. Change NonPagedPoolSize to less than seven-eighths of the physical memory. To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

http://support.microsoft.com/kb/152734/EN-US/
 
xxdanielxx said:
NOTE: The above registry key is one path; it has been wrapped for readability.
2. Change NonPagedPoolSize to less than seven-eighths of the physical memory. To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Click to expand...

Hmm... that's sounding a little scary there. I'm a bit worried that editing this key might really damage my PC. Also, I don't even know what I'm suppose type in to make it less than seven-eighths of the physical memory. At the moment my PC seems to be able to last a bit longer than before until it BSODs again. I don't know if I want to edit the registry while I still have work to finish up.
 
have u tried to obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

http://support.microsoft.com/kb/152734/EN-US/
 
xxdanielxx said:
have u tried to obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

http://support.microsoft.com/kb/152734/EN-US/
Click to expand...

Not sure why you think I have Windows NT but I'm using Windows XP Professional. And no, I don't exactly have the latest Service Pack for it (let's just say I can't d/l SP2 with my particular copy of Windows XP).
 
nice.. oh sorry about it didnt mean to put NT 4.0

if you have windbg follow the sample i posted below use the bold com... as they are shown then post back results


kd> .bugcheck[Lists bugcheck data.]
Bugcheck code 0000000a
Arguments 00000000 0000001c 00000000 00000000

kd> kb[Lists the stack trace.]
ChildEBP RetAddr Args to Child
8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint
8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194
8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256
8013ed5c 801263ba 00000000 00000000 e12ab000
8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

kd> kv[Lists the trap frames.]
ChildEBP RetAddr Args to Child
8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint (FPO: [0,0,0])
8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194
8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256 (FPO: [0,0] TrapFrame @ 8013eee8)
8013ed5c 801263ba 00000000 00000000 e12ab000
8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

kd> .trap 8013eee8 [Gets the registers for the trap frame at the time of the fault.]
eax=dec80201 ebx=ffdff420 ecx=8013c71c edx=000003f8 esi=00000000 edi=87038e10
eip=00000000 esp=8013ef5c ebp=8013ef64 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
ErrCode = 00000000
00000000 ??????????????? [The current instruction pointer is NULL.]

kd> kb [Gives the stack trace before the fault.]
ChildEBP RetAddr Args to Child
8013ef68 fe551aa1 ff690268 00000002 fe5620d2 NT!_DbgBreakPoint
8013ef74 fe5620d2 fe5620da ff690268 80404690
NDIS!_EthFilterIndicateReceiveComplete+0x31
8013ef64 00000246 fe551aa1 ff690268 00000002 elnkii!_ElnkiiRcvInterruptDpc+0x1d0
 
Man, I had really thought the BSODs were over since I didn't get any all of yesterday (11/13), but sure enough they came back this morning (11/15). Here are my results:

Code: 
kd> kb
ChildEBP RetAddr  Args to Child              
ef77b2f0 8052b629 0000000a e172707c 000000ff nt!KeBugCheckEx+0x19
ef77b2f0 804f3458 0000000a e172707c 000000ff nt!KiTrap0E+0x219
ef77b394 bf8b5115 824194d8 bf997587 e1727078 nt!KeRestoreFloatingPointState+0x78
ef77b39c bf997587 e1727078 ef77b3e8 ef77b730 win32k!EngRestoreFloatingPointState+0x1a
WARNING: Stack unwind information not available. Following frames may be wrong.
ef77b3b8 bf994a17 f06f7608 bc676610 00001000 ati2dvaa+0x4587
ef77baac bf8bb61c e21afb80 00000000 00000000 ati2dvaa+0x1a17
00000000 00000000 00000000 00000000 00000000 win32k!OffCopyBits+0x7b
kd> kv
ChildEBP RetAddr  Args to Child              
ef77b2f0 8052b629 0000000a e172707c 000000ff nt!KeBugCheckEx+0x19 (FPO: [Non-Fpo])
ef77b2f0 804f3458 0000000a e172707c 000000ff nt!KiTrap0E+0x219 (FPO: [0,0] TrapFrame @ ef77b30c)
ef77b394 bf8b5115 824194d8 bf997587 e1727078 nt!KeRestoreFloatingPointState+0x78 (FPO: [Non-Fpo])
ef77b39c bf997587 e1727078 ef77b3e8 ef77b730 win32k!EngRestoreFloatingPointState+0x1a (FPO: [1,0,0])
WARNING: Stack unwind information not available. Following frames may be wrong.
ef77b3b8 bf994a17 f06f7608 bc676610 00001000 ati2dvaa+0x4587
ef77baac bf8bb61c e21afb80 00000000 00000000 ati2dvaa+0x1a17
00000000 00000000 00000000 00000000 00000000 win32k!OffCopyBits+0x7b (FPO: [Non-Fpo])
kd> .trap ef77b30c
ErrCode = 00000000
eax=824194d8 ebx=e172707c ecx=00000004 edx=00000000 esi=824194d8 edi=ef77bdf0
eip=804f3458 esp=ef77b380 ebp=ef77b394 iopl=0         nv up di pl zr na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010046
nt!KeRestoreFloatingPointState+0x78:
804f3458 f60301           test    byte ptr [ebx],0x1      ds:0023:e172707c=04
kd> kb
  *** Stack trace for last set context - .thread/.cxr resets it
ChildEBP RetAddr  Args to Child              
ef77b394 bf8b5115 824194d8 bf997587 e1727078 nt!KeRestoreFloatingPointState+0x78
ef77b39c bf997587 e1727078 ef77b3e8 ef77b730 win32k!EngRestoreFloatingPointState+0x1a
WARNING: Stack unwind information not available. Following frames may be wrong.
ef77b3b8 bf994a17 f06f7608 bc676610 00001000 ati2dvaa+0x4587
ef77baac bf8bb61c e21afb80 00000000 00000000 ati2dvaa+0x1a17
00000000 00000000 00000000 00000000 00000000 win32k!OffCopyBits+0x7b

And thanks very much for trying to help me out here xxdanielxx. I really appreciate it.
 
if you look at the post you put the last to stackframs crash at ati2dvaa

ef77b3b8 bf994a17 f06f7608 bc676610 00001000 ati2dvaa+0x4587
ef77baac bf8bb61c e21afb80 00000000 00000000 ati2dvaa+0x1a17

ati2dvaa.exe, or dll. Is the driver for your graphics card.

From safe mode uninstall anything to do with ATI from add remove programmes in control panel.

Reboot your computer into normal mode, and download, and install the latest drivers for your graphics card from the ATI website.

http://www.ati.com/

When you install the new drivers, disable any antivirus program you are running, as this can seriously screw up driver installations.

or first befor uninstalling try to update it
 
hmm... so it's still my video card driver eh? Perhaps I've been uninstalling and reinstalling incorrectly or something. I do have a question about that, the last time I uninstalled it and restarted my computer, Windows XP would do that automatically detect new hardware thing and then it installs whatever driver it has for ATI Rage Fury. Then I would install the latest driver I got on the ATI website. Is that a problem? I didn't really want Windows to install a driver for it but I don't know how to prevent it. Should I do both the uninstallation and installation of the driver in Safe Mode?
 
When you go to Safe Mode, Device Manager, make sure you "Show Hidden Devices" in case you have multiple copies of the driver installed. Sometimes this can hinder your newly installed driver.

Right Click "My Computer" -> Manage -> Device Manager -> View -> Show Hidden Devices -> Display Adapters

you might also want to look for any disabled or problem drivers, in case it is a conflicting driver (i.e. chipset) causing your problems.

You can also try re-seating the video card. Sometimes this will fix issues with driver installs not working properly.

Hope it helps!
 
Ok, I think it's time for me to just give up and do a clean installation of my OS or something. For a couple of days I didn't get a BSOD but I got one last night. The same error message as before. I had tried all the suggestions you guys gave including:

1. Reseating the video card.
2. Disabling my anti-virus program when I installed the new video driver.
3. There were no conflicts when I selected Show Hidden Devices.

BTW, I don't get any pop-up message when Windows detects the new hardware. It just automatically does it on its on. I can't seem to stop it in any way. I tried double-clicking that icon that shows up in the system tray when it detects the new hardware but no window pops up. I have also noticed that when I completely disable all hardware acceleration in my Display settings my computer can last quite a bit longer before it BSODs. Any thoughts on this? Should I just bite the bullet and do a clean installation?

Thanks again for everyone's help and hope you have a nice Thanksgiving!
 
I have been having trouble and everything has been leading to the graphics driver. I found a piece of info that has helped so far, but that is still up for grabs. I unofficially heard from a former nvidia employee (Kinda the don't ask don't tell thing) that having any anti-virus, firewall, spyware, blah blah running while downloading will affect everything as well, not just the install process. I know it seems weird and odd, but he said it was good info. I don't know how true this is, but so far things seem good. I'm not getting any critical error reports being sent off to Microsoft any longer.... I hope this can help you.
 
What you heard was true, well except for the firewall part. Never turn off your firewall while connected to the net.

Regards Howard :)
 
Status
Not open for further replies.

Similar threads

dansharp2014
Win 11 BSOD
Replies
2
Views
1K
dansharp2014
dansharp2014
H
BSOD during youtube video - Windows 7 64 - suspected hardware malfunction
Replies
15
Views
2K
Kshipper
Kshipper
J
Need help with BSOD Event ID 41
Replies
1
Views
1K
Kshipper
Kshipper

Latest posts

Back