Several different BSODs the past week, completely random.

There are multiple different bugcheck codes blaming multiple different things, and one of the dumps is totally uncommon in nature. In this situation it would be better to determine the stability of the RAM at first.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. A camera snap of the memtest86+ window before closing the program would be nice.

MnemonicSyntax said:

Alright, I'll get started on this right away. In the meantime, can you tell me what's being blamed?

I'd surely appreciate it! Thanks!

Memory Corruption, mostly; and ntkrnlmp (which means the dump recording mechanism failed to get the crasher rightly, and wrongly blamed the karnel itself on which the crash took place).

Nice!

Then let us check other possibilities .... if there is a failing driver that is passing bad information to the memory, that may result in memory corruption, too. So let us enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Well, it's already BSOD'd again. Included is the new dump. :/

Also, I forgot to mention I was running Driver Verifier! Thanks!

None of the last two crash dumps are verifier enabled.

Code:

3: kd> !verifier
fffff80003093b80: Unable to get verifier list.

If verifier is enabled, it would have displayed the verifier settings. And, the default bucket ID would also display it, which it does not.

Code:

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

Anyway, one is still blaming memory, and the other is IRST. For the IRST issue, you need to get rid of intel rapid/matrix storage. First uninstall it from Control Panel > Programs and Features. Then Uninstall the driver from device manager.

1. Right click on "my computer" icon and click "manage" on the context menu.
2. It will open the "computer management" window.
3. Select "Device Manager" in the left pane, It will list all the existing devices up.
4. Expand "IDE ATA/ATAPI controllers" by clicking on the triangle in front of it.
5. Select one Intel device item under it, right click, uninstall.
6. Continue the process for all Intel items under "IDE ATA/ATAPI controllers"
7. Now restart the computer. At restart, windows will auto configure the appropriate native system driver.