Windows 10: BSOD but system doesn't restart after dump

On my system, I have Automatically Restart set in the system failure but when it BSOD's, it says that the system will restart after the dump but it appears it just stays at the blue screen without restarting even after an hour on atleast 3 occasions since I've upgraded to Win10 from Win7 Home Premium on August 11, 2015, the system is able to restart and shutdown normally. Any ideas how to fix this?

:)

 

APC Index Mismatch

For some reason, dump doesn't work with my BSOD, I just waited for 15 minutes but there was "0% completed".

Also, sometimes, if I remove webcam in Device Manager and re-install driver again - everything works, but after Windows restart it breaks again and this trick doesn't work each time.

 

sfc logfile shows a folder which doesn't exist? Folder ----"C:\Windows\System32\hi-in\hi-in\" ---------Folder which i can find --"C:\Windows\System32\hi-IN\"

I need the dump files of BSOD. SFC DISM doesn't prove to be quite useful in troubleshooting BSODs.

 

Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial

 

Thanks, had it on Kernel memory dump with 24 gigs of memory. For troubleshooting a BSOD, is only a minidump needed or does it need to be bigger? Is a Kernel memory dump supposed to write to c:\windows\minidump as well because on my system with the Kernel memory dump, I have 2 .dmp files with different date/timestamps in c:\windows\minidump in addition to the c:\windows\memory.dmp file. Also, wouldn't it actually be better to have automatic restart actually disabled since how would someone know the system crashed if the system restarted, seems easier to just actually be at the BSOD screen so one can look into it.

 

We prefer minidumps, because the memory.dmp file will be overwritten everytime you get a bluescreen, this is not the case with minidumps.
Everytime a bluescreen occurs, there are 2 files generated, a minidump with the date and time and the memory.dmp file (which will be overwritten if this already exists.

I would not recommend to disable the restart option, enough people don't know what to do when they see there system has crashed.
With the restart possibility they can find out more about the crash to solve it.
I'm not sure, but I think that if you don't let your system restart that then the minidump file won't be saved.

 

The dump is saved even when you don't restart as that's how mine is set up.

 

Interesting, I thought the dump would still be there since it's similar to kernel panics in Unix OSes where it will just panic without restarting as the dump file is always written from what the BSOD says. What I meant to say is that since I leave my system on 24x7x365, I might not remember it experienced a BSOD so if it stays at the BSOD, all I do is hold the power button for 10 seconds so it turns off and then restart on my own, then the first thing I do will be to try to troubleshoot.

 

The difference between a kernel dump and a small dump

This option is standard checked with memory.dmp files, thats why they'll be overwritten.
Attachment 35936

 

Depends on the system. My desktop being a tower, I would press reset but my notebook has no reset button so the closest thing is holding down the power button. Sometimes on the desktop, it requires a forced power down when reset doesn't do anything. Desktop is still running WinXP Professional SP3.

 

Yes, I read that C:\Windows\memory.dmp gets overwritten on a kernel dump but it seems my system was always on kernel dump but it still produces the minidump files in c:\windows\minidump in addition to the C:\windows\memory.dmp so perhaps the mini dumps will always be there as long as some type of dump is chosen to be written.