New
#1
BSODs but no longer seem to create dump files
First, let me say that the info on this site is a tremendous resource. You guys are great to run this.
I started getting kernal_data_inpage_error BSODs about a month ago. I found your site and found minidumps were being created in c:\windows\minidump\ just like the site indicated. For the last couple of weeks, I still periodically get the BSODs but no .dmp files are getting created. The BSODs report that the physical memory dump has been completed successfully. I followed your procedure to try to enable the dumps (see attached jpeg) but still no longer see any dump files being produced.
I walked through How to Force a Blue Screen in Windows: 13 Steps - wikiHow so that I can create BSODs at will but still do not see any dmp files actually being created. The three things I did around the time that I stopped getting minidumps were
1) In a non-admin session, I used WinExplorer to navigate to windows\minidump. When I was prompted that I was would not be allowed access, I answered "yes" to grant me (from a non-admin logon) access to the folder.
2) I saw there were some very old .dmp files (2+ years ago) in the folder. I deleted those .dmp files
Would either of these stop minidumps from being taken?
I know there is probably something I have messed up but I cannot see it. Can you help me get back to where minidumps are being created again.
3) I walked through your process to systemadvancedsetup process a couple of times to change the dump type to a full dump and back to a minidump.
FYI - before, I believe that before, a BSOD would roll "percentage xx complete" during the process... now, it just seems to immediately say "dump complete" or something like that.
Any assistance would be greatly appreciated.
Thanks,
John
FYI keyboard-generated BSODs immediately indicate "Collecting data for crash dump", "Initiating disk for crash dump" and "physical memory dump complete"... all show at once.
Last edited by johncros; 18 Jul 2013 at 04:06. Reason: add info about BSOD display