BSOD With No DMP Files Available? (Event Viewer Lists Kernal-Power)

Hello again, I was able to fix my previous issue from a year or so ago through some help on this forum. In the last 2 weeks Dell and Windows has installed massive updates to things and all of a sudden I'm getting BSOD and constant "warning" "error" or "critical" on the event viewer.

From the small amount of info I've been able to find, Windows removed the high performance setting for battery in this update and that might be why my Dell XPS 15 9550 may be having the "unexpected_store_exception" (which was connected to the same Kernal-Power Event ID 41 Task Category 63. At the same time there is an "error" listed by volmgr that stated "Dump file creation failed due to error during dump creation."

I then tried to install the DM Log Collector so that I could get the information that this forum needs to trouble shoot and etc, but nothing happens other than a quick screen flash in the powershell or etc. I will attach the screen cap of the image that I was able to get a screen cap just in time to see it.

Attachment 214842

Right now I'm not sure what I should be doing, I've considered just a clean install of Windows from scratch, but I cannot find a list on Dell of the drivers I should pre-download on a thumb drive (chipset would like 18 things so not sure if I really need them all or etc).

For reference my computer stats are below as well.

Dell XPS 15 9550
Windows 10 Home 1809 (OS Build 17763.134)
CPU: i7-6700HQ
Motherboard: Dell Inc. 0N7TVV
Memory: 2x8GB DDR4 2133Mhz
Graphics Cards: GeForce GTX 960M and Intel HD Graphics 530
Hard Drive: Samsung 512 GB (PM951 NVMe Samsung 512GB)

I do see that I have some specs listed on my profile, but I'm not sure how to change them or add or etc (only thing new is the Ver # of Windows and the OS Build)

Thanks in advance for any insights you can throw my way.

Run the new log collector below step 9 in the BSOD posting instructions guide.

Run the Beta Collector then?

I will go ahead and download that and see what happens then.

Here is the Beta Collector zip file, I did get a yellow error or sorts that I'm adding for info in a screen cap just to be safe in case that helps.

Attachment 214852

Also per the older post I had I went ahead and did the disk check and etc through powershell and went ahead and included it as well.


Microsoft Windows [Version 10.0.17763.134](c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannowBeginning system scan. This process will take some time.

Beginning verification phase of system scan. Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool Version: 10.0.17763.1

Image Version: 10.0.17763.134

[==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully.

C:\WINDOWS\system32>

Windows PowerShellCopyright (C) Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername -match "wininit"} | fl timecreated, message

TimeCreated : 11/22/2018 11:17:46 PM

Message :

Checking file system on C: The type of the file system is NTFS. Volume label is OS.

A disk check has been scheduled. Windows will now check the disk.

Stage 1: Examining basic file system structure ... 401408 file records processed.

File verification completed. 17205 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...

1039 reparse records processed.

560428 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered to lost and found.

1039 reparse records processed.

Stage 3: Examining security descriptors ...

Cleaning up 5157 unused index entries from index $SII of file 0x9.
Cleaning up 5157 unused index entries from index $SDH of file 0x9.
Cleaning up 5157 unused security descriptors.
Security descriptor verification completed.
79511 data files processed.

CHKDSK is verifying Usn Journal...
39719920 USN bytes processed.

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
401392 files processed.

File data verification completed.

Stage 5: Looking for bad, free clusters ...
87146392 free clusters processed.

Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

486720827 KB total disk space.
137414928 KB in 267579 files.
186724 KB in 79512 indexes.
0 KB in bad sectors.
533603 KB in use by the system.
65536 KB occupied by the log file.
348585572 KB available on disk.

4096 bytes in each allocation unit.
121680206 total allocation units on disk.
87146393 allocation units available on disk.

Internal Info: 00 20 06 00 a9 4b 05 00 60 91 08 00 00 00 00 00 . ...K..`.......
6a 03 00 00 a5 00 00 00 00 00 00 00 00 00 00 00 j...............

Windows has finished checking your disk.
Please wait while your computer restarts.


Hope this may shed some light, but perhaps not?

I just went through the analysis of a missing MEMORY.DMP file in a thread I recently started on the BSOD crashes and Debugging topic. Go to the Microsoft link below and follow the directions to see how large your C:\pagefile.sys is.

My laptop was set to autosize the page file if a crash dump couldn't be created, and will revert back after four weeks. You can change registry key settings to always do a memory dump and fix the size of the pagefile.sys to be large enough to hold the largest expected dump for a 16GB laptop. The size that was configured is supposedly large enough for most MEMORY.DMP images. I'm waiting for guidance on that, but I think you might be having the same problem where the pagefile.sys was too small to write a crash dump. I just took a look at some Windows 7 memory dumps I had taken from an Asus 8GB laptop and the biggest one was 702Mb in size, so perhaps the autosize is reasonable.

My 16GB Lenovo laptop's pagefile.sys is currently 2432 MB after being sized by the kernel during a hang that would have written a crash dump but failed due to a size issue. I won't know if it works unless I get another hang.

This link shows you how to configure system protection so you won't overwrite a MEMORY.DMP file.

https://docs.microsoft.com/en-us/win...ic-memory-dump

The registry setting is CrashDumpEnabled and will show up in your Beta log bundle file "crash-dump-settings.txt". More info on these settings can be found here:

https://www.itprotoday.com/windows-8...gistry-entries

You might want to take action to ensure you get a crash dump if you are still experiencing issues and not getting a MEMORY.DMP in the system root.

I went ahead and checked the memory creation dump stuff, here is a screen cap below
Attachment 214971

I think I had done this when I had another BSOD issue last year and we still couldn't figure out why I had no dmp files. I did a screencap then of the only dmp files my computer ever had which was only iTunes at the time.

I did notice today that it crashed with the "Event 41, Kernel-Power, Task Category (63)" when I closed the lid. When I tried to reopen it about 10 min later it was a black screen where nothing would happen other than the keyboard lighting up. So I went to the Event VIewer again and did an export of the Admin Events Tab and I will attach the text file as well. I also went ahead and make a new Beta Log file in case this one might be better as it was directly after I restarted the computer.

Not sure what I should try next.

For reference I have also had 1,047 instances of "errors" "warnings" or "critical" on Event Viewer in about 36 hours... it was never that high (usually just bonjour service).

Apparently the massive event viewer spike numbers are a 1809 issue, found this link here in the forum so most of the instances are probably tied to that overall

New 1809 update now shows this in Event Viewer - Windows 10 Forums

There is no evidence of any BSOD event in the logs. If it is still happening can you record the BSOD screen by taking a picture of it so we can see the message it gives.

I don't have a screencap or photo unfortunately, but the BSOD said "UNEXPECTED_STORE_EXCEPTION" when it has popped up.

So far as long as it's plugged in I've had one for a bit, but when it's on battery it will randomly pop that up or stay black if I'm opening the lid. Each time (either crash) I'll check out event viewer and see this particular crash "Kernal-Power Event ID 41 Task Category 63."

I do have my computer set up for dumps and etc per my first post in this forum that was rectified, but if I remember correctly my computer just didn't make them. The "who crashed" and etc didn't seem to have it either.

My other laptop on the other hand creates them with the same exact setting and etc, except it's a different SSD (one installed on the Dell won't even let me run a SMART scan either).