Windows 10: Win10 SetUnhandledExceptionFilter not allowing enough time

My code runs perfectly in Win7; I create a line of data showing EIP
(which pinpoints the failure to an instruction) and registers. I also
produce a short MiniDump. Windows itself also creates one in
\CrashDumps as well as WER data.

However, in Win10, there is NOTHING! No WER data, no .dmp (there
isn't even a \CrashDumps folder?). Even worse, where I had apx
2 seconds in Win7 to do my stuff, in Win10, I'm only given btx .008
and .044 seconds!!! Most of the time, I don't even get my line of
data B 4 I am rudely killed by something (in PROCMON, my Thread Exit
does NOT point to my ExitThread or a RET, so I was killed!), even
after "optimizing" my code (pre-load LoadLibrary/GetProcAddress,
etc). The only way I can get farther is to run PROCMON, which seems
to help delay the killing. Occasionally, I've gotton as far as the
MiniDump B 4 it gets killed:

23 dbgcore.dll MiniDumpWriteDump + 0x1cd

In my case, the O/P file of this is empty, so it didn't even get a
chance to write a single record (or did, but got lost due to the
killing causing lack of data integrity. PROCMON shows no writes)!

I do see WER stuff in \ProgramData, so it obviously is running for
other things, but not mine. The WER service is Manual/triggered.
An admin 'DIR /s /a /x *.dmp*' from root shows many, but not for
mine at the time of my deliberate crash (xC0000005).

Is there some new timeout setting somewhere? How can I get this
very important feature back for my programs? Or is this just another
reason of many to stay away from Win10? Thankx...

:)

 

BSOD not allowing to update win10

I, with my limited experience, was checking the dump file to see what I could find.

First, and I suppose the answer would be you are trying to upgrade to the newest build but are unable. It may not matter but there are two new updates for the 10586 build you are currently running. Is the problem involved in those also?

But it seems I am seeing comments about dxkrnl.sys, which is the directx driver. I have never seen such a description as I see for yours but it is interesting. Do you have the option of using a different video adapter or possibly putting yours back to
a basic Microsoft adapter to test if the updates will complete? You would not normally expect a Windows component to be responsible so maybe some driver associated with your video card...

Video drivers are involved with power options, such as sleep...

"THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)

The device driver is spinning in an infinite loop, most likely waiting for

hardware to become idle. This usually indicates problem with the hardware

itself or with the device driver programming the hardware incorrectly."

I would also check the Event Viewer to see if you have been getting any error or warning messages consistently which might indicate the source of the issue.

I may be completely off base, so we can wait to see what ZigZag says..

 

BSOD not allowing to update win10

These crashes were related to memory corruption (probably caused by a driver).
Please run these two tests to verify your memory and find which driver is causing the problem. Please run verifier first. You do not need to run memtest yet unless verifier does not find the cause, or you want to.
If you are over-clocking anything reset to default before running these tests.
In other words STOP!!! If you do not know what this means you probably are not
1-Driver verifier (for complete directions see our wiki here)
answers.microsoft.com/en-us/windows/wiki/windows_other-system/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983
2-Memtest. (You can read more about running memtest here)
answers.microsoft.com/en-us/windows/wiki/windows_other-system/bsod-memory-problems-test-easily-and-completely/21c3f63f-f570-4522-b2ef-ecc7b7ff6461

 

So: no one knows how to get crash dumps and WER data from application
programs in Win10, a la Win7?

Well, I wrote my own, and now get my stack output and PSW(EIP)&REGS
at the point of my deliberate crash, whether in shutdown or not, tho I get
killed while trying to do a MiniDump (but see next), which, now, I do last.
ONCE AGAIN, have to race a lousy force-killer that leaves no trail!

At least I figured out how to get back my .dmps like I get in Win7, by
adding the 3 WER LocalDumps registry entries and the \CrashDumps DIR.
This MAY have also nullified that lousy force-killer timeout, as my MiniDump
now completes as well.

As for WER, all I do get now is a Report.wer file; no .h/mdmp, no .xml.