Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: RobbZero on March 16, 2009, 01:33:06 PM
-
I keep getting the IRQ_NOT_LESS_OR_EQUAL BSOD when playing AH2. I've read on a post on a search I did about the problem saying that it's a fairly vague error but that it has something to do with a card or the motherboard not operating properly. The only card I have installed is my GeForce NX8600GT (SLI) manufactured by MSI. My mobo's a Asus M2N-E SLI with onboard C-Media audio and onboard network. I read somewhere that you can check to see what IRQs the devices on your system are running on and that you could see if any IRQs are shared. How do you check for that?
-
I don't know how do do it in Vista, but in Windows XP do Start, Run, type msinfo32 and hit OK. Open "Hardware Resources" and click Conflicts/Sharing.
-
oh... and I'm running WinXP :P
-
K. Just did the msinfo32 thing. I'm suspecting there's a problem with IRQ 22 which handles some USB and PCI stuff. I figure maybe it's that cuz I use a USB headset. Also there's a shared mem address between my vid card and PCI-to-PCI bridge.
Here's the list of it all:
System Information report written at: 03/16/09 13:53:35
System Name: ROBB-ZERO
[Conflicts/Sharing]
Resource Device
Memory Address 0xFEFFF000-0xFEFFF3FF High precision event timer
Memory Address 0xFEFFF000-0xFEFFF3FF System board
Memory Address 0xFEFFF000-0xFEFFF3FF System board
I/O Port 0x00000000-0x00000CF7 PCI bus
I/O Port 0x00000000-0x00000CF7 Direct memory access controller
I/O Port 0x000003C0-0x000003DF PCI standard PCI-to-PCI bridge
I/O Port 0x000003C0-0x000003DF NVIDIA GeForce 8600 GT
IRQ 22 Standard Enhanced PCI to USB Host Controller
IRQ 22 Standard Dual Channel PCI IDE Controller
IRQ 23 Standard Dual Channel PCI IDE Controller
IRQ 23 NVIDIA Network Bus Enumerator
IRQ 9 Microsoft ACPI-Compliant System
IRQ 9 SCSI/RAID Host Controller
IRQ 9 AXT24LE4 IDE Controller
Memory Address 0xD0000000-0xDFFFFFFF PCI standard PCI-to-PCI bridge
Memory Address 0xD0000000-0xDFFFFFFF NVIDIA GeForce 8600 GT
Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF PCI standard PCI-to-PCI bridge
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce 8600 GT
I/O Port 0x000003B0-0x000003BB PCI standard PCI-to-PCI bridge
I/O Port 0x000003B0-0x000003BB NVIDIA GeForce 8600 GT
Memory Address 0xF8000000-0xFBFFFFFF PCI standard PCI-to-PCI bridge
Memory Address 0xF8000000-0xFBFFFFFF NVIDIA GeForce 8600 GT[/size]
-
I think the shared mem address is normal. The rest someone else will have to help you with. Try playing AH without the USB headset attached and see if that fixes the error. If it does, try plugging the headset into a different USB port (yeah, I know that sounds lame but I've had it work before).
-
I keep getting the IRQ_NOT_LESS_OR_EQUAL BSOD when playing AH2. I've read on a post on a search I did about the problem saying that it's a fairly vague error but that it has something to do with a card or the motherboard not operating properly. The only card I have installed is my GeForce NX8600GT (SLI) manufactured by MSI. My mobo's a Asus M2N-E SLI with onboard C-Media audio and onboard network. I read somewhere that you can check to see what IRQs the devices on your system are running on and that you could see if any IRQs are shared. How do you check for that?
Did you install this card recently?
Did this problem occur after anything hardware was recently installed?
Do you have any ANTISPYWARE or ANTIVIRUS software installed?
More info once you've provided more information.
-
Goto the Windows Debugging Tools web site.
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx
Get Windbg.exe for your operating system. Read the Manual for basic crash dump file debugging. Follow the instructions for setting a path to the free Microsoft public symbols server. Do a basic debug on any of the small dump files in your windows directory that were generated by the BSOD. Under windows XP you will have a minidump directory with .dmp files or search for .dmp files with the bsod timestamp. Or if your system is not setup to give you a file dump at a BSOD, right click on MY Computer, properties, advanced, Startup and Recovery settings.
Turn off automaticly restart and make sure its set to give you a Small Memory dump. On the next BSOD it will create a minidump after which you will have to reboot your machine. If you want really goary details set it to do a Kernal Memory Dump. If you set it for Kernal Memory Dump let the blue screen sit for up to 10 minutes while a huge memory dump is being written. Then reboot and go back into My Computer and recheck automaticly restart and set it back to write a samll memory dump.
Then if you have installed windbg.exe, set the path to the public syumbols server, perform a basic debug and you will be shown in semi-Microsoft legable English what module faulted in memory. At that point you won't be guessing about IRQ conflicts or which driver is faulting.
By the way do you remember the BSOD - IRQ not less or equal or was it mor like - 0xA: IRQL_NOT_LESS_OR_EQUAL 0000000a(something, something, something, something)
There might be a 0000000a along with four other registers or hex addresses. If it is an 0xA yes in general that will be a new driver related to a hardeware device.
But not all BSOD are hardware errors. By default there are about 100 or so BSOD messages possible along with one you can generate with a Hot Key combination you enable for testing your system.
-
Did you install this card recently?
Did this problem occur after anything hardware was recently installed?
Do you have any ANTISPYWARE or ANTIVIRUS software installed?
More info once you've provided more information.
Yo.
So my video card's been in my PC for well over a year now. As for recently added hardware -- I think that somewhere down the line when I'd add on USB devices like my external USB DVD-Burner and maybe replugging other devices into different ports from when I'd unplug everything to clean my PC out that it comes from that. I don't know how Windows likes it when you move a device from one USB port to another from time to time.
So I'm thinking that this whole mess started with the arrival on the scene of my USB Logitech Headset. I don't remember it being much of a problem at first. I remember when I had a headset with the separate audio and mic jack that it never was a problem.
I'm gonna go ahead and change USB ports for my headset and see what that does.
I'll make sure that I jot down the hex address if I see it again. I remember it being 0x000000A (something, something, something, something)
-
Rob
Out of curiosity, do you use FSAutostart? Have you ever asked FSAutostart to defrag your memory?
-
Never heard of FSAutostart so no I don't use it. Defrags your mem? Sounds like it could be useful.
-
0x000000A (something, something, something, something)
Is more often related to a driver for a peice of hardware but can be a canary pointing to a bad peice of hardware.
If you check for a C:\Windows\minidump directory, and that directory exists and there are 64k .dmp files with date stamps of each BSOD. If you have restart the computer checked in Startup and Recovery, there will be no dump files. Try setting up the windows debugger and reading the files if you have them set to be created. Or pasting the faulting module the debugger will show you. You will very likely get the name of the driver involved in the FAULT. You cannot harm your PC installing and running windbg.exe. You can bore yourself to eath reading the manul.
If you run a windgb debug read in the manual down this path in the Contents section:
Crash Dump Files
Kernel Mode dump Files
Analalyzing a Kernel Mode dump file
Analalyzing a Kernel Mode dump file with Windgb
After you run windbg targeting your .dmp file. You will use the basic command !analyze -v to show you a verbose output of the FAULT.
Otherwise, keep pulling hardware and updating or rolling back drivers until you quit BSODing. I'm just trying to help see exactly what is faulting.
-
One night as I entered AH I use FS Autostart to cut down on the processes running in the backround, I saw that option and thought I'd give it a try.
May have been totally unrelated to AH but as soon as I hit start AH and defrag my memory before starting I got the same error message. Tried the windows debugger and every other thing I could think of with no success.
Finally ended up reloading windows. Just thought I'd ask
Edit
Something sharing or trying to share the same memory address? I made no hardware changes, reloaded and everything was fine.
-
I've had "Automatically Restart" unchecked for quite a few months now. I looked into my C:\Windows\Minidump folder but there's no .dmp files in there for some reason. In the "Write debugging infromation" section is set to write "Small memory dump (64KB)". Well... not really. Ain't GOT no mem dumps :eek:
-
Hungry,
Doesent FS Autostart have a reclaim memory from the stack before app run mode you can enable, rather than defragmentation of the stack? If it tried to free a memory segment that was in use by another application and not available to be released at that moment, your PC would hang, maybe a BSOD or a FS Autostart application exception window would pop up.
I get the hint, you guys don't really want to learn to debug your stack faults and BSOD.......... :)
-
I've had "Automatically Restart" unchecked for quite a few months now. I looked into my C:\Windows\Minidump folder but there's no .dmp files in there for some reason. In the "Write debugging infromation" section is set to write "Small memory dump (64KB)". Well... not really. Ain't GOT no mem dumps :eek:
Run a search of your whole C:\. I've found them in C:\ and C:\Windows\system32
This is my path for the minidumps..... %SystemRoot%\Minidump . You can make it explicit C:\Windows\Minidump or go into your Environment Vayriables and add onto the Path after the last entry:
;%SystemRoot%\Minidump
If your BSOD is locking you HARD dead and you are rebooting manualy emidiatly, try setting it to a Kernal Dump and letting your PC sit for 10 min.
-
Hungry,
Doesent FS Autostart have a reclaim memory from the stack before app run mode you can enable, rather than defragmentation of the stack? If it tried to free a memory segment that was in use by another application and not available to be released at that moment, your PC would hang, maybe a BSOD or a FS Autostart application exception window would pop up.
I get the hint, you guys don't really want to learn to debug your stack faults and BSOD.......... :)
I tried Lord knows I tried, in my case I just couldnt get past it. I read about it until I was blue in the face but most of it was miles beyond where I'm at PC repair wise.
One thing about these posts, (Rob) ahem... when you get it fixed please let us know how you did it!!
-
So I just got another BSOD. It was a variant of the other BSOD that I got. It was (something)_IRQ_NOT_LESS_OR_EQUAL
...and it had some of these numbaz to go with it:
0x000000D1 (0X00000018, 0X00000009, 0X00000000, 0XB8D6B926)
nv4_mini.sys - address B8D6B926 base at B8D1A000 Datestamp ?lx*
[/size]
* First character here is a weird right-angled corner that looks like an "r". Not a letter.
So it seems that this time it was whining about my nVidia card. Maybe I fixed part of the problem by moving my headset to a different USB port but this nv4_(blah blah) usually rears its ugly head now and then.
I get the hint, you guys don't really want to learn to debug your stack faults and BSOD.......... Smiley
I most certainly wanna learn how to solve this bunch of BSOD hooplah :D
I'll definitely let you know, Hungry, how I fix this problem if I ever do.
-
Oh Bustr. I did a search for any .dmp files that I might have but the search didn't find anything at all. I'm going to set the Write debugging info to "Kernel mem dump" this time around and see what gives.
-
0x000000D1 (0X00000018, 0X00000009, 0X00000000, 0XB8D6B926)
nv4_mini.sys - address B8D6B926 base at B8D1A000 Datestamp ?lx*
nv4_mini.sys
Its an NVIDIA miniport driver.
Description: nv4_mini.sys is located in the folder C:\Windows\System32\drivers. Known file sizes on Windows XP are 3,650,368 bytes (8% of all occurrence), 1,897,408 bytes, 2,826,944 bytes, 3,198,560 bytes, 3,958,496 bytes, 3,536,768 bytes, 3,530,432 bytes, 891,711 bytes, 3,994,624 bytes, 3,983,680 bytes, 3,994,688 bytes, 2,459,968 bytes, 3,645,600 bytes, 1,312,555 bytes, 3,988,384 bytes, 3,642,784 bytes, 3,454,144 bytes, 1,329,723 bytes, 3,532,928 bytes, 3,198,368 bytes, 2,830,688 bytes, 2,743,840 bytes, 3,199,616 bytes, 1,550,043 bytes, 1,341,339 bytes, 3,662,944 bytes, 2,459,712 bytes, 3,528,000 bytes, 3,493,984 bytes, 3,925,920 bytes, 3,454,656 bytes, 7,435,648 bytes, 1,330,172 bytes, 3,650,336 bytes, 1,618,939 bytes, 7,433,504 bytes, 5,758,432 bytes, 3,329,504 bytes, 6,807,328 bytes, 3,959,712 bytes, 3,210,400 bytes, 3,919,264 bytes, 6,853,088 bytes, 909,501 bytes, 3,528,384 bytes, 7,435,136 bytes, 3,655,712 bytes, 1,897,696 bytes, 818,713 bytes, 1,878,432 bytes, 3,095,680 bytes, 2,738,400 bytes, 3,200,256 bytes, 3,640,608 bytes, 3,958,272 bytes, 3,535,680 bytes, 6,738,432 bytes, 3,992,608 bytes, 3,199,328 bytes, 1,371,740 bytes, 3,580,480 bytes, 6,852,032 bytes.
The driver can be started or stopped from Services in the Control Panel or by other programs. nv4_mini.sys is a Windows core system file. The program is not visible. The service has no detailed description. nv4_mini.sys is a Microsoft signed file. nv4_mini.sys seems to be a compressed file. Therefore the technical security rating is 14% dangerous, however also read the users reviews.
Try getting newer drivers for your NVIDIA video card or rolling back to older drivers. do some reserach at NVIDIA in their tech support area.
-
Might be time to post the top 1/3rd or so of a DxDiag report.
-
And here it is:
(only went up to Sound Devices section)
------------------
System Information
------------------
Time of this report: 3/16/2009, 23:02:13
Machine name: ROBB-ZERO
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_qfe.080814-1242)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 4600+, MMX, 3DNow (2 CPUs), ~2.4GHz
Memory: 2046MB RAM
Page File: 367MB used, 8594MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: No problems found.
Sound Tab 1: No problems found.
Sound Tab 2: No problems found.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce 8600 GT
Manufacturer: NVIDIA
Chip type: GeForce 8600 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0402&SUBSYS_09101462&REV_A1
Display Memory: 256.0 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor: BenQ T904
Monitor Max Res: 1280,1024
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.8120 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 12/26/2008 01:08:00, 6168960 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 12/26/2008 01:08:00, 6301344 bytes
Device Identifier: {D7B71E3E-4742-11CF-6A68-1B2900C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0402
SubSys ID: 0x09101462
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
-------------
Sound Devices
-------------
Description: Logitech USB Headset
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: USB\Vid_046d&Pid_0a01&Rev_1013&MI_00
Manufacturer ID: 65535
Product ID: 65535
Type: WDM
Driver Name: usbaudio.sys
Driver Version: 5.01.2600.2180 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 8/3/2004 18:07:56, 59264 bytes
Other Files:
Driver Provider: Microsoft
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 200000
Static/Strm HW Mix Bufs: 0, 0
Static/Strm HW 3D Bufs: 0, 0
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Description: C-Media CM6501 Like Sound Device
Default Sound Playback: No
Default Voice Playback: No
Hardware ID: USB\Vid_0d8c&Pid_0201&Rev_0010&MI_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: c6501.sys
Driver Version: 5.12.0002.4219 (English)
Driver Attributes: Final Debug
WHQL Logo'd: Yes
Date and Size: 9/5/2006 18:04:38, 1419968 bytes
Other Files:
Driver Provider: C-Media Inc.
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 100, 100000
Static/Strm HW Mix Bufs: 65, 64
Static/Strm HW 3D Bufs: 65, 64
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: Yes, Yes
Sensaura(tm) ZoomFX(tm): Yes
Registry: OK
Sound Test Result: Not run
-
DxDiag report cannot tell you what the faulting module is. Running a Windbg debug against a dump file will. His proper BSOD message:
0x000000D1 (0X00000018, 0X00000009, 0X00000000, 0XB8D6B926)
nv4_mini.sys - address B8D6B926 base at B8D1A000 Datestamp ?lx*
Tells you everything. It is a miniport driver for his video card that is faulting. DXDiag is only a system report of what is installed in it. Not a diagnosis of what is faulting in it. If the NVIDIA vid card is the newest peice of hardware, it is either defective or he needs to roll back its drivers or install newer ones. If he has installed other new hardware, well its still a older or newer driver issue. If he can get a Kernel dump file, it might give him an idea to what drivers are conflicting by looking at earlier calls in the kernal stack before the fault error occured.
As of now non of you internet PC cowboys have a clue why the nv4_mini.sys driver is faulting.
His blue screen as created by Microsoft is telling us what is wrong. DXDiag is not a debug application. A better question for Skyzzy is: Skuzzy do you have access to the MS in house debug plain english symbols that create debug out puts that display the problem in plain english? When I worked at Bank of America for PES(third level problem escalation), David R. Shaw our Lead Sr. Anylist worked with MS at MS and made us aware of those proprietary debug symbols. Public symbols have to be interprited, or you need to know how to setup your debugger to work in real time to catch the fault as it happens. This is facilitated by connecting another PC or laptop to your PC with a crossed cable. You set the external PC or laptop debugger to trigger a dump on a certain stack call pulled from reading the original dump file. You set the boot.ini of the taget PC to go into debugger mode on boot. When the fault occures the target PC goes into dump mode and dumps its kernal stack to the debug PC or laptop.
This is a total pain in the kester, but it works very well. Ive done it to prove that a DB2 gateway dll was the reason the 8th CPU on a MSSQL server was pegging at 100% to a BSOD during Terrabyte file uploads because of the IBM interface gateway between MSSQL and an external DB2 server. It has the downside of telling you alot about the applications running in the kernal stack when it dumps.
So guys, how do you propose to solve his problem without concrete information other than the BSOD message?
-
Run around crying and screaming HELP!!! or back everything up and reload? just kidding don't club me to hard
-
Download this and next time you get a BSOD use it to process the dump file.
DebugView for Windows by Sysinternals.
http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
It will process the debug info to a text file.
-
Rob your up bub, post the text file?
-
Okie dokie.
Robb's Quick Capsule Update
:aok Got power to case fans to avoid reboots due to overheating. CPU/GPU stays well below 70ºC now.
:aok :aok Updated nVidia driver to latest version. So far -- no BSODs.
:aok :aok :aok No random reboots due to overheating or BSODs since today :D :D :D
If, and I hope it never freaking happens again, I get another BSOD I'll be ready for it with all the tips you laid out in your posts Hungry and bustr.
So for now. Everythings awesome! I played AH2 for a good 3 hours straight without incident.
Thanks for the help!
-
Hip Hip Hoorayyy!! way to go Rob, Hats off to Bustr, he's the one with all the brains lol