|
Hi,
I *highly* doubt that EseDiskFlushConsistency brought the system down... all this function does is flush database modifications to disk.
If you are interested in finding out what brought the system down then download WinDbg and open the minidump. If you setup the symbols... you will get the exact exception and entire callstack... Bugcheck 0x9F is a DRIVER_POWER_STATE_FAILURE meaning that one of the device drivers installed on your laptop improperly handled a power state.
Instructions for debugging a device driver power management error is here:
How to Debug DRIVER_POWER_STATE_FAILURE[^]
Look at your second bugcheck number: 0xffffee8039c5ac40
I think if you open the minidump in WinDbg and do:
!devstack 0xffffee8039c5ac40[^]
You will find exactly which driver caused the bug check. Always remember that Microsoft Windows allows third-party vendors to write device drivers. Don't be surprised if this is a third-party device driver.
Btw, once you learn how to use WinDbg you will probably not ask many questions[^]... because it's faster to just fire up WinDbg and get the answer.
|
|
|
|
|
I'm feeling quite silly, I have always done this in a hex editor. 
|
|
|
|
|
Sheesh.
It was meant to be a discussion. Like mechanics getting together and discussing odd things that happen.
I downloaded the windbg tool.
And here's the thing...
I went to the location where I had previously attempted to open the memory.dmp file with Visual Studio's debugger and when I got there I found that the file was gone!
My machine has not restarted and I didn't delete the memory.dmp file but now it is gone.
Why would Win10 do that?
I tried attrib to see if the file was just hidden or something but it wasn't there.
I checked Recycle bin to see if the OS deleted it and I don't see it there either.
I was very interested in learning the cause of the crash. Oh well. 
|
|
|
|
|
Well,
I've done some more thinking about this. It was most likely a stray cosmic ray... probably a muon that struck one of your sticks of RAM in the state capacitor and flipped a bit. This probably caused notepad (even though it wasn't running) to determine that it needed to flush it's contents to disk. After calling EseDiskFlushConsistency... your hard drives all spun up at the same time... and all of the zero point energy was consumed in your power supply and this resulted in a bugcheck 0x9F - DRIVER_POWER_STATE_FAILURE. This massive consumption of energy opened a miniature black hole and it consumed your minidump... that's why you can't find it.
Trust me, that's exactly how it happened. Happens all the time.
modified 18-Feb-18 12:15pm.
|
|
|
|
|
raddevus wrote: My machine has not restarted and I didn't delete the memory.dmp file but now it is gone.
Why would Win10 do that?
Easy... professional criminals always do it... erase traces, so noone can connect you to the crime  :P 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Nelek wrote: Easy... professional criminals always do it... erase traces, so noone can connect you to the crime
Win10. Microsoft.
Pick your criminal. 
|
|
|
|
|
Hmmm,
Could you execute the following command from powershell as Administrator and paste the output here?
Get-ScheduledTask | ? {$_.Settings.MaintenanceSettings} | Select-String -Pattern "Disk"
Best Wishes,
-David Delaune
|
|
|
|
|
Sure, thanks...
Here's what I saw:
PS C:\WINDOWS\system32> Get-ScheduledTask | ? {$_.Settings.MaintenanceSettings}
| Select-String -Pattern "Disk"
MSFT_ScheduledTask (TaskName = "SilentCleanup", TaskPath =
"\Microsoft\Windows\DiskCleanup\")
MSFT_ScheduledTask (TaskName = "Microsoft-Windows-DiskDiagnosticDataCol...,
TaskPath = "\Microsoft\Windows\DiskDiagnostic\")
MSFT_ScheduledTask (TaskName = "Diagnostics", TaskPath =
"\Microsoft\Windows\DiskFootprint\")
MSFT_ScheduledTask (TaskName = "StorageSense", TaskPath =
"\Microsoft\Windows\DiskFootprint\")
This is the part where you take over my computer now, right? 
|
|
|
|
|
Hi,
raddevus wrote: MSFT_ScheduledTask (TaskName = "SilentCleanup", TaskPath =
"\Microsoft\Windows\DiskCleanup\")
This scheduled task runs daily and silently and has the ability to delete minidumps.
raddevus wrote: This is the part where you take over my computer now, right?
Occam's razor[^]
Best Wishes,
-David Delaune
|
|
|
|
|
Yeah I figured there was a process that did clean-up automatically.
==> I'm a software developer who writes articles and concentrates on the fun and interesting stuff.
Disk clean up after a crash is no fun at all. Seriously boring.
I expect the system to do the right thing all the time -- especially in this age of AI / Machine-Learning.
Crash and cleanup is "need to know basis". I don't want to know until I have to know.
Keep me ignorant and then I can rant about stupid Win10.
Far more fun.
|
|
|
|
|
Hi,
raddevus wrote: I expect the system to do the right thing all the time
Yeah, I understand. People have different expectations... 'The right thing' is relative and while you maybe wanted to keep your minidumps... others may want them cleaned up daily so they don't take up any disk space.
Best Wishes,
-David Delaune
|
|
|
|
|
Randor wrote: while you maybe wanted to keep your minidumps... others may want them cleaned up daily so they don't take up any disk space.
Agreed. 
|
|
|
|
|
I would be very worried that the last thing it did/attempted/was doing was any sort of disk flush,
and as OP mentioned above looked for the memory.dmp file that disappeared itself without message/log/warning
Boy, that win10 really inspires confidence, not!
And yet they still tell people to upgrade to 10 because it's safer than the old [solid] w7 
Have one client using a stock PC running w7 as an app/db server, only been down once in 5 years (2 years ago now) for a scheduled power outage.
w10: no thanks; stick with what actually proven works.
Signature ready for installation. Please Reboot now.
|
|
|
|
|
Win 10 - not in the same league as Windows 7 yet, and it's pretty clear that it's a management problem.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
A reboot just bit me too. I had a dozen+ tabs open in two browsers researching something, 2 instances of VS. I was in the other room eating dinner when I hear the BIOS beep from my computer.
Thanks a lot Windows Update KB4074588. That was absolutely not planned or communicated.
The process c:\windows\system32\svchost.exe (MYNAMEHERE) has initiated the restart of computer MYNAMEHERE on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Service pack (Planned)
Reason Code: 0x80020010
Shutdown Type: restart
Comment:
|
|
|
|
|
4.2 Magnitude apparently, about 20km NNE from Swansea. A quick check on Google maps, and it was about 5 km from us.
The devastation is horrendous.
(The cat was spooked, and nothing even fell off a shelf.)
Send aid money for rebuilding now! Send it to me, and I'll coordinate it...
Still, explains the series of noises a few days ago: about 4am I was woken by a noise like a Parkinson's patient with a tea cup and saucer. Lasted maybe 30 seconds, then stopped. few minutes later, it's back. Could I find what it was? Nope. Now I know - probably a very small series of foreshocks.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
There has been a 4.6 magnitude earthquake near Nantes five days ago. Perhaps it is this one you're talking about.
"I'm neither for nor against, on the contrary." John Middle
|
|
|
|
|
Nantes and Swansea are a hell of along way away!
|
|
|
|
|
I was talking about the one OG felt a few days ago, not the one that took place today.
"I'm neither for nor against, on the contrary." John Middle
|
|
|
|
|
Was Griff in Nantes a few days ago?
|
|
|
|
|
Why are you asking that?
"I'm neither for nor against, on the contrary." John Middle
|
|
|
|
|
Griff: Had a quake in Swansea.
You: Perhaps it was the one in Nantes 5 days ago.
Me: Swansea and Nantes are a long way away.
You: I am talking about the one Griff felt a few days ago.
Me: Was he in Nantes then?
You: What are you talking about.
Me, now:
|
|
|
|
|
Tip: OriginalGriff wrote: Still, explains the series of noises a few days ago...
You know earthquakes can be felt several hundreds kilometers away, don't you?
"I'm neither for nor against, on the contrary." John Middle
|
|
|
|
|
Not a 4.5, and Nantes is a long way from Swansea.
|
|
|
|
|
In 2004, there has been an earthquake in Beaume-les-Dames (5.2 magnitude). I was home in Lyon and could feel it since my bookcase became suddenly shaky. Hence my question.
Now, I checked and indeed Swansea in quite far from Nantes. But on a geologic scale, not that far. I thought both these events, happening in a few days' window, could be somehow related.
"I'm neither for nor against, on the contrary." John Middle
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
