BSOD random 0xF4, no dumps; stuck on "initializing disk"

Hi All,

I'm getting random BSODs on my new Dell Precision M5510. The BSOD gets stuck on "initializing disk for crash dump", but never actually creates the dump. I have made sure that the page file is on the same disk as the OS (C:\), and that UAC was turned on. I also set the right location for the minidumps, and made sure that windows was configured to create the dumps in the first place. Still no joy.

The crash is often preceeded by a short time (10 seconds?) when explorer becomes somewhat unresponsive, as if a process is stuck on something. The mouse moves, and I was even able to open the start menu once in this state. Strangely, there were *no* programs listed in the start menu... and then I got the 0xF4 BSOD a few seconds later.

There *is* one initial crash dump which is included in the attachments here. However, I'm not sure how much that dump has to do with the BSODs I'm getting regularly now, for which no dumps exist. Maybe it has something to do with them, maybe not.

Any help would be greatly appreciated. I've seen similar issues for a Crucial SSD for which a firmware update was the fix. My NVMe SSD (a Toshiba 1TB thnsn51t02du7) is relatively new, and I can't find any updates for it, or much about it at all for that matter.

I've also put in an unmatched stick of RAM, but I think it shouldn't be a problem; but perhaps I'm wrong about that.

I should also note that I've been having trouble getting the Intel USB 3.1 driver to update. I run it, but the version number doesn't update in device manager. Not sure what's up with that. Tried various things, updating thunderbolt, etc, with no joy.

Finally, the SATA HDD cable I have in there (I have one NVMe and one seagate 2TB HDD) is 3rd party off Amazon. I assume those cables are just connectors and aren't "smart", so don't think it should be a problem, but did want to mention.

Please see SF Tool and DM log output attached here, as well as a few BSOD pics. Note that the 2nd pic shows a 0x7A error, but that's the only time I've seen that one. Everything else has always been a 0xF4. Thanks for any help you might be able to offer!

Best,
Alex

Diagnostics Test

 HDD TEST

   Note

Please run HDTune first, in the order posted!

Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Make a photo of the result and post it.

Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log :arrow: Check Disk (chkdsk) - Read Event Viewer Log

You'll want to run the tests on all drives/partitions.

D was in my previous laptop with no issues.

How are you sure that it doesn't cause problems in the current system?
This is a statement meaning that a previous setup for the moment shouldn't be used as a reason why something may not be a problem.

Please run chkdsk, same command, again on the C partition.

Alright, please let me know if the BSOD occurs again.