Random freezes with no BSOD

Is Driver Verifier still on?

Turn it on with normal settings.

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.

OK so Driver Verifier was still on but I changed it over to the settings described in the tutorial. I restarted the computer and immediately got a series of BSODs during boot up (at the stage where the windows icon is gently glowing in the centre of the screen). I got two different BSOD messages: PAGE_FAULT_IN_NONPAGED_AREA and IRQL_NOT_LESS_OR_EQUAL.

The computer got into a cycle of trying to boot, BSODing, trying to boot again, BSODing again etc. After about 5 cycles, I powered the machine off, booted again, and it successfully made it to the desktop. However unfortunately, none of these BSODs seem to have produced any new dump files. The only two dump files seem to be the ones from 27th.

How should I proceed from here? For the time being, I've turned Driver Verifier off, but I'm happy to switch it back on again. However given that I'm only seemingly getting the BSODs during startup, I guess I'd have to keep restarting the machine rather than using it normally if I'm to force another BSOD.

Hi Britton. So the Memtest86 tests were fine. I followed Thedoctor's advice and ran the tests for eight passes, and it passed all eight times without any error. With the Furmark test, I didn't notice any visual artifacts, but the GPU did start overheating after a couple of minutes. I've not done another test of the SSHDs since the original one I did after the problems began, but on that occasion, both drives passed the Seagate Dos Tools long test.

It says in the tutorial if you cannot start up then use safe mode.

Anyway, those bugchecks are generally caused by drivers or memory and if Driver Verifier bugchecks on start up then it looks like a driver issue.

For another lead we need some new dump files.

Currently, the machine is set to the "Kernel memory dump" option. Is this correct or should I set it to "Small memory dump" instead?

Unless necessary we don't need Kernel Memory Dumps, they are much larger in size so you would have to upload it through one drive.

It's only really needed with cases like 0x101 errors where we need more information one the processor for example.
There are more cases but that's one of the main ones.

Small Memory Dump will do fine.

If it was set to Kernel Memory Dump at the time then it will be located:
C:/Windows/memory.dmp

Kernel Memory Dumps are not located in the minidump file.

Look at the "Last modified" date on the memory.dmp and if it's new then upload that to one drive and post the link.
It's too large to upload here.

Thanks for the advice. I've checked the MEMORY.DMP file but unfortunately, it's dated for the same time as the last crash dumps I uploaded, so I don't think it's been created for any of the more recent BSODs.

I've now changed over to the Small memory dump option, and when I get back tonight, I'll have another restarting session with the computer to see if I can trigger some BSODs and get a memory dump.