I have been getting BSODs for a few months off and on. I do not know a lot but I have 4 mini dumps. I have set in Advanced Settings for "Complete MEMORY Dump. I got a BSOD last night and when I restarted the PC after the BSOD was finished at 100%, (waiting a minute before restart). I did not find a Complete Memory Dump (%SystemRoot%\MEMORY.DMP). How would this Memory Dump disappear or not be created?
Please check your recovery configurations and pagefile configurations, there are numberous events about pagefile configuration failure
Log Name: System
Event ID: 49
User Name: N/A
Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
Standard it is already on the boot partition, maintained by Windows.
- Go to Control Panel > System > Advanced system settings > tab 'Advanced' > Performance settings > Advanced > Change.
'Automatically manage paging file size for all drives' is normally checked.
I have set in Advanced Settings for "Complete MEMORY Dump. I got a BSOD last night ... I did not find a Complete Memory Dump (%SystemRoot%\MEMORY.DMP). How would this Memory Dump disappear or not be created?
Was there a file there at all (meaning an older one) -- in (%systemroot%\memory.dmp)?
I found this entry in the Event Viewer log and it says that a dump from May 29, 2017, was written to/saved in %systemroot%\memory.dmp
From Event Viewer:
Log Name: System
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000208,
0x0000000000000007, 0x0000000000000000, 0xfffff80ac273690b). A dump was saved in:
C:\WINDOWS\MEMORY.DMP. Report Id: e17dcd83-711e-4e5c-9736-c23ec50be72a.
Do you use CCleaner or similar app that may have deleted the dump?
Not only does the Event Viewer indicate that a dump was written on 5/29/17 -- the dump is not included in the Sysnative/jcgriff2 zip file that you attached. So either these dumps are not being written or some app is coming along and deleting them. This fits the pattern of the BSOD/dump from yesterday. There may be many more dumps that are missing from BDODs that actually occurred.
The 5 dumps provided to us in the most recent Sysnative/jcgriff2 output zip file -
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
Volume in drive C is Windows 8.1 x64
Volume Serial Number is C8D9-F1EF
Directory of C:\Users\PalmDesert\_jcgriff2_\dbug\1
10/06/2017 09:34 PM <DIR> .
10/06/2017 09:34 PM <DIR> ..
01/01/1980 12:00 AM 1,384,224 082217-8781-01.dmp
01/01/1980 12:00 AM 1,377,440 082517-9562-01.dmp
01/01/1980 12:00 AM 1,365,792 082917-10000-01.dmp
01/01/1980 12:00 AM 1,369,888 083017-10046-01.dmp
01/01/1980 12:00 AM 1,379,232 092717-10359-01.dmp
5 File(s) 6,876,576 bytes
2 Dir(s) 91,107,069,952 bytes free
Windows 10 dump file dates have left all BSOD Analysts shaking their heads in disbelief as often THE FILE DATE associated with the dump file is just plain wrong. Looking up at the list of your 5 dumps, you can see that the timestamp is wrong as they all say that all 5 BSODs occurred on January 1, 1980 at midnight. To obtain the correct timestamp, look at the filr name or run the dump. I usually do both.
If you look at the column to the right of the file size is the file name. The file name column for Windows' minidumps is partially made up of
Anyway, full physical memory dumps are not of any use to us. We need kernel dumps. Change crash control settings either to "Automatic" or "Full Kernel Dump". Doing so should leave you with a full kernel dump (%systemroot%\memory.dmp) + a minidump (%systemroot%\minidump).
A problem with the page file may be responsible for the lack of your full physical memory dump being written as all dump info is written to the page file first, then re-written to either %systemroot%\memory.dmp +/or %systemroot%\minidump.
If you have any other questions, just ask and we'll do our best to get it/them answered.
I noticed most of the times (in windows 8.1 and 10, can't remember previous OSes) the pagefile.sys is deleted by windows itself, after a reboot.
Or at least, that happens on this machine.
I'm not sure if it depends on the pagefile.sys size.
I usually set it to a fixed size, between 1GB and 4GB.
I've got three ram configurations in these years: 4gb, 6gb, 8gb.
When I reset it (set it to "no paging file"), it disappears at reboot.
Just today, I tried to set it to 30GB (30720MB).
I didn't reboot and the pagefile was there.
Then I reset it to 0 (and this time the reboot was mandatory).
After the reboot, it was still there, and I had to remove it manually (with the delete key).
Maybe when the pagefile.sys size is lower than the ram size, does windows delete it on its own?
That's why you can't find it.
By the way, the msinfo log shows the pagefile was present: 34GB.
Syslist shows a negative size for it (-2147483648).
"Windows 10 dump file dates have left all BSOD Analysts shaking their heads in disbelief as often THE FILE DATE associated with the dump file is just plain wrong. Looking up at the list of your 5 dumps, you can see that the timestamp is wrong as they all say that all 5 BSODs occurred on January 1, 1980 at midnight. To obtain the correct timestamp, look at the filr name or run the dump. I usually do both."
BIOS seems to be already updated.
But I can see you didn't update other things present in your manufacturer website (like softwaremaniac showed in the first reply).
Could it be you are using two antiviruses? Webroot and voodooshield?
Could you specify what antivirus/antimalware/antispyware/firewall software are you using?
It could be this is the cause of your BSODs.
Create a new system restore point.
Create a backup of your important files: they should be put in another location (not in your machine).
Update aomei backupper to the latest version (aomei backupper standard 4.0.6, is free).
Not sure why you are using the 2012 version of it.
Are you using another software to create system images?
By the way, after you updated aomei backupper (or your preferred program for system images: OVERWOLF?) create a new system image of your system: it should be put in another location (not in your machine).
Make also sure you have the usb drive, or the cd, you created with/by aomei backupper at hand.
If you didn't create it, create it right now and test if it works (i.e., if it boots up your machine, without using windows).
Start to update the drivers for your laptop, checking Dell.com - Support for Alienware 17 R4 (click).
It could be dell installed a software on your machine that check drivers for you: try that, if you feel more comfortable with it.
* Yes, I am using Webroot and Voodooshield Beta & Hitman Pro.
*Glasswire Elite Firewall (updated)
*AOMEI Backupper Professional has been updated for a couple of days now to 4.0.6
* I am not using another software for creating system images.
* I have tried updating the drivers that, softwaremaniac posted for me. Some will not update like the "intelppm.sys" I cannot find it on Intel.com. The other drivers I believe are updated. Except for Clone DVD.
Thank you and I'll follow the rest of your advise to backup Dell Drivers to the latest. And make a USB with AOMEI. Besides creating a System Restore in the meantime.
I thought it was another antivirus.
Well, after you got your precautions and then updated your drivers, wait for another bsod.
If it won't appear in next two months, problem solved.
If a new bsod will appear, post it here and we will check it.