I have been receiving IRQL_NOT_LESS_OR_EQUAL BSODs sporadically. Ive looked on various forums and no help!

Log Name:      System
Source:        Microsoft-Windows-Kernel-PnP
Date:          7/31/2015 11:54:26 PM
Event ID:      219
Task Category: (212)
Level:         Warning
Keywords:      
User:          SYSTEM
Computer:      harry-pc
Description:
The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&4.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
    <EventID>219</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>212</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2015-08-01T03:54:26.618986500Z" />
    <EventRecordID>9533</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="220" />
    <Channel>System</Channel>
    <Computer>harry-pc</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DriverNameLength">24</Data>
    <Data Name="DriverName">ACPI\PNP0A0A\2&amp;daba3ff&amp;4</Data>
    <Data Name="Status">3221226341</Data>
    <Data Name="FailureNameLength">14</Data>
    <Data Name="FailureName">\Driver\WUDFRd</Data>
    <Data Name="Version">0</Data>
  </EventData>
</Event>

Any help would be appreciated!

  We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask

Thank you for getting back to me so soon!

Here is a one drive link to the .dmp file

https://onedrive.live.com/redir?resid=7162C79B7899CE71!677&authkey=!AFokKipHPqP8raw&ithint=file%2czipZ

As a side note: As soon as I get this BSOD, and the computer reboots, I get the BSOD much more frequently. By this time I usually end up shutting off my computer for the night. I dont believe it is an overheating issue, I use Everest and monitor my GPU ( which gets up to about 120 degrees F [i think this is reasonable?]), SSD drive, and sata drive

Thank you for all your help!

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


If you are over-clocking anything reset to default before running these tests. In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)

Im running the Driver verifier right now and will post as soon as I can can crash my computer.

Unsure if this is relevant, but in my Windows systems logs, every time my computer crashes it always says this driver failed to load:

\Driver\WudfRd

here is an example from the most recent crash:

The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{e0b12a56-ffea-11e4-825b-0862664cff8b}#0000000000008000.

and here is another instance:

The driver \Driver\WUDFRd failed to load for the device ACPI\PNP0A0A\2&daba3ff&4.

always seems to be this same Driver.

Event Code 219.

Thanks

Computer has successfully crashed! Twice!

Here is the link to the new dumps:

https://onedrive.live.com/redir?resid=7162C79B7899CE71!683&authkey=!AKgaJR6-H0Y9nyU&ithint=folder%2c

-One of the dump files have the system crash while running the verifier with normal use ( IRQL BSOD)

-The second crash was interesting. Upon my PC rebooting and getting onto my desktop, my computer crashed immediately. This time with a Memory_management BSOD. I have reciveed this memory_management BSOD before but, it is very rare and it follows multiple crashes with the IRQL BSOD

Thank you. I will run the memory test tonight

Both of the above were verified but verifier did not catch the offending driver.

Good news on memtest but that does not help much here.

In one of these it was Related to MsRPC.sys Kernel Remote Procedure Call Provider from Microsoft Corporation.

If you have not run a system file check please do so.

Please run a system file check (SFC) & DISM (if necessary) if you are on win 8 or higher
All instructions are in our Wiki article below...
Should you have any questions please ask us.

System file check (SFC) Scan and Repair System Files

• Edited by ZigZag3143xMVP, Moderator 6 hours 54 minutes ago

Two different error codes.  Please run verifier to find the underlying issue

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


If you are over-clocking anything reset to default before running these tests. In other words STOP!!!  If you do not know what this means you probably are not

1-Driver verifier (for complete directions see our wiki here)
2-Memtest. (You can read more about running memtest here)

Driver Verifier was running when the first crash happened. In the .dmp file.

Also, here is the result from the memtest86 I ran over night:

https://onedrive.live.com/redir?resid=7162C79B7899CE71!684&authkey=!ABgKvLHZ0Guu_GY&v=3&ithint=photo%2cjpg