IRQ_NOT_LESS_OR_EQUAL BSOD

[Hungry]

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!!

[RobbZero]

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

I'll definitely let you know, Hungry, how I fix this problem if I ever do.

[RobbZero]

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.

[bustr]

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.

[fuzeman]

Might be time to post the top 1/3rd or so of a DxDiag report.

[RobbZero]

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

[bustr]

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?

[Hungry]

Run around crying and screaming HELP!!! or back everything up and reload?  just kidding don't club me to hard

[bustr]

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.

[Hungry]

Rob your up bub, post the text file?

[RobbZero]

Okie dokie.

Robb's Quick Capsule Update

Got power to case fans to avoid reboots due to overheating. CPU/GPU stays well below 70ºC now.
Updated nVidia driver to latest version. So far -- no BSODs.
No random reboots due to overheating or BSODs since today 

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!

[Hungry]

Hip Hip Hoorayyy!!  way to go Rob, Hats off to Bustr, he's the one with all the brains   lol