Constant BSOD - HELP!

[aok]

DRIVER_IRQ_NOT_LESS_OR_EQUAL

*** STOP: 0x000000D1

(0x00000000000000018, 0x0000000000000002, 0x0000000000000001...

(FFFFFA6000DB384E)

*** ndis.sys

Address.FFFFFA6000DB384E base at FFFFFA60000C0B0000, Datestamp 47919a99

Here is my error on BSOD, I have previously overclocked but put it back to normal clocks (reset CMOS). Although I do have an unkwown device that Device Manager has detected, I just can't figure out what it is though, I have unistalled it, and it came back. The BSOD appears to only come up if my PC is under stress-mode (Prime95, OCCT). I have tried to play games and they seem fine, but I guess they don't stress my PC up to 100%, my rig is on my profile. If you need any further questions, please do ask but keep checking for my replies as most people don't.

 

[zak4994]

ndis=nvidia problem.

New drivers?

 

[Ham]

I'd bet my right ear that the 'unknown device' is the uguru chip.

What are your ram settings?

And do you have all unused onboard devices (COM ports for example) disabled?

 

[TopSecret]

You're a little way off there Zak, NDIS is "Network Driver Interface Specification" and nothing to do with Nvidia drivers. I would try and uninstall the NIC drivers, if you can get into safe mode.

 

[zak4994]

You're a little way off there Zak, NDIS is "Network Driver Interface Specification" and nothing to do with Nvidia drivers. I would try and uninstall the NIC drivers, if you can get into safe mode.

.

I got it mixed up.

I was in the middle of talking about nVidia when I was typing that post.

 

[llwyd]

That message indicates that a driver messed up memory access. Do a proper re-install of any network related drivers changed around the time the issue started and update your bios for good measure

 

[Youngie1337]

I had this error many times mate, the main culprit was RAM. But this is also caused by many driver errors. I remember I used to get it a lot with my firewire card.

I get it now and again still with my capture device on Vista 64, your best bet is test your memory (sorry haven't read much of your original post) stick by stick. This is most likely a small driver problem, just cross your fingers.

Driver_IRQL_not_less_Or_Equal error means that the system tried to access a portion of memory using a kernel process IRQL (Interrupt Request Level - basically a table used by the kernel to manage interrupt sources) that was too high. Often this is caused by a bad device driver that is using an improper address. Other possibilities are faulty or mistmatched ram or a corrupted pagefile

I would suggest turning off your pagefile.

 

[aok]

Thanks bud, it was this, everything works fine now, I don't stress my PC anymore, my memory is like oufheriqwgfui with itself when stressed tbh. I use multiple stress programs to stress my PC, and that has caused this because I am testing (stressing) a >lot< of RAM.

 

[DeMoB]

If something like your RAM has gone bad, wouldn't it be better to run some specific stress testing programs (Im thinking memtest86+ for you RAM), so you can find out what's not working properly, then get that part fixed (Good ram will still be under some warranty so you can send it back to them to get replaced if you can prove there is a problem, like with memtest).

Dan

 

[Brooksie]

Is your RAM overclocked at all?