Windows 10 won't generate mini dumps on ongoing issue

A

Aureai

Hello everyone,

I have a problem with this laptop... An HP OMEN 15-ax010tx (full specs here), about 4 years old; performance is alright, doesn't heat up, used a lot for gaming with CoD, Destiny 2, etc.

So far everything is okay except that ever since approximately a year ago it's crashing in very random instances intermittently exchanging the BSOD message from "CRITICAL PROCESS DIED" to "UNEXPECTED STORE EXCEPTION". Before crashing, the screen freezes for a couple of seconds before finally giving out the error message. More recently, whenever booting up, the computer wouldn't recognize any OS installed until rebooting several times again to access Windows.

What did we do:

  • We've tried to do several hardware tests to check; MemTest86, the tools from HP, and probably other testing tools that we don't even remember the name anymore, all of them said that everything is okay.

  • We've tried reinstalling Windows several times without success, the issue always returned.


  • Then our last alternative was to check the mini-dumps so it can be analyzed more thoroughly the problem since at the moment we have no clue. Unfortunately, for some reason Windows is not generating them whenever we access to the dump folders (SystemRoot%\MEMORY.DMP); we do have access to see hidden files.

We tried activating dumps and received this message:


Windows might not be able to record details that could help identify system errors because your current paging file is disabled or less 800 megabytes. Click OK to return to the Virtual Memory settings window, enable the paging file, and set the size to a value over 800 megabytes, or click cancel to change your memory dump selection.



We tried to go to the Virtual Memory settings, enabled "Custom Size" and we've put a maximum size of 1000MB. Also didn't work and provoked issues later on the computer (software would crash due of lack of memory).

We tried using this line code on the CMD on administrator mode:


wmic RECOVEROS get DebugInfoType

And it returned the value "1", which means a complete memory dump is activated but still we can't see anything...

If anyone could help us in this issue, we would be forever grateful. Thank you!

Continue reading...
 
Back
Top Bottom