I get this error that I didn't have in W7.  If I shut down W10 I get this message once in a while. I have no way of knowing which component is causing this.  It happens when I shutdown and W10 will restart.  It only happens when the machine is left on for a long time.
 
 Would a USB device cause this?  Video card? Hardware in a PCI slot?
 
 My suspicion is my old Terratec EWX2496.  It uses a PCI slot and running on Vista drivers.  The card in use doesn't seem to exhibit problems.  I also have a Guitar Port hooked up and a UR22, these are USB devices.
 
 Is there anywhere in W10 where I can dig up this error report?  It happens on my AMD system. Specs are listed below.

Well - I use a UR22 on Windows 10, so that doesn't seem likely.
 
You could try:
 
Hit Windows Key + R
Type in msinfo32.exe and run it
 
When that launches, expand the Hardware Resources tab, then click on Conflicts/Sharing, and scroll down to see if there are any conflicts
 
You could also download and run LatencyMon, and look to see if there are any drivers performing badly.
 
In any case, if you DO find a conflict or a poorly performing component, look for updates to those and install them, or disable the device or find a replacement for it.
 
Bob Bone

robert_e_bone
Well - I use a UR22 on Windows 10, so that doesn't seem likely.
 
You could try:
 
Hit Windows Key + R
Type in msinfo32.exe and run it
 
When that launches, expand the Hardware Resources tab, then click on Conflicts/Sharing, and scroll down to see if there are any conflicts
 
You could also download and run LatencyMon, and look to see if there are any drivers performing badly.
 
In any case, if you DO find a conflict or a poorly performing component, look for updates to those and install them, or disable the device or find a replacement for it.
 
Bob Bone

 
 Did that and no conflicts. BTW this is the W10 Anniversary Edition and I don't recall this happening before.

google mentions Avast ... do you use Avast AV by chance?

I run Windows 10 with the Anniversary Update, and also run Avast, HOWEVER - I have the Cakewalk folders and sample libraries excluded from Avast.
 
You could try unplugging the USB audio interface, and temporarily disabling a single component of yours at a time, until it quits producing the errors.  It appears from the quick look I did online, that drivers are often a cause of this error condition.
 
There is also a program called Who Crashed, and others like it, that analyze Windows error logs and dump files, and post a report as to what component caused a given issue.
 
Bob Bone
 
 

There are no performance issues other than a needed reboot.  I will ignore it.

MSDN says it points to a buggy driver...
https://msdn.microsoft.com/en-us/library/ms854226.aspx
This seems to point to your video driver:
http://answers.microsoft.com/en-us/windows/forum/all/driver-irql-not-less-or-equal-0x000000d1/3109e65a-38eb-47b5-8227-80b0db5d7025?auth=1

Tracking down this error with Google searches isn't likely to get you anywhere, because it's so common. It's basically an access violation that occurs in kernel mode, meaning a driver or Windows itself. As such, it can originate from many sources. It can be either a hardware or software problem, although the latter is more likely.
 
Troubleshooting starts with a dump analysis. That will pinpoint the driver that's causing the stop. But that entails some expertise and most users are intimidated by dumps. However, there may also be clues in the Event Log. Use the Event Viewer to look for errors or warnings involving hardware devices. 
 
Check that your drivers are up-to-date. You already know you have at least one old driver, and it's for one of your most critical system components. Might be a good excuse for an upgrade. If that's not a step you're already considering, you could try to vindicate the Terratec by removing it, enabling your onboard audio and then do a bunch of reboots as an experiment. If the error still occurs with the interface physically removed, that would tell you that the problem is elsewhere.

Run this. http://www.nirsoft.net/utils/blue_screen_view.html
 
It is a simple dump analyzer that will show you which driver is causing the crash.
 
To ensure minidumps are enabled:
The log file will be %systemroot%\Minidump which is normally C:\windows\Minidump
If the files don't exist then setup your system to record them;
a. Go to Start and type in sysdm.cpl and press Enter
b. Click on the Advanced tab
c. Click on the Startup and Recovery Settings button
d. Ensure that Automatically restart is unchecked
e. Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
f. Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be found later
Click OK twice to exit the dialogs, then reboot for the changes to take effect.
 
I get them occasionally on mafw.sys (M-Audio driver).  But not enough to be a real problem.  The only time it seems to happen is during a warm reboot without shutting down.
 
BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).
For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash.
 
More debugging info here:
http://www.tenforums.com/bsod-crashes-debugging/

The real problem is W10 AU.  It didn't happen before. The only problem so far is the random need for Windows to restart when I want to shut it down.