BSOD but system doesn't restart after dump

Page 1 of 2 12 LastLast
  1. Almighty1's Avatar
    Posts : 1,047
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
       #1

    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?
      My Computer

  2. axe0's Avatar
    Posts : 14,792
    Windows 10 Pro
       #2

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

  3. Almighty1's Avatar
    Posts : 1,047
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
    Thread Starter
       #3

    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.
      My Computer

  4. axe0's Avatar
    Posts : 14,792
    Windows 10 Pro
       #4

    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.
      My Computers


  5. Posts : 18
    Windows 10
       #5

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

  6. Almighty1's Avatar
    Posts : 1,047
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
    Thread Starter
       #6

    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.
      My Computer


  7. Posts : 18
    Windows 10
       #7

    I just press reset
      My Computer

  8. axe0's Avatar
    Posts : 14,792
    Windows 10 Pro
       #8

    Almighty1 said:
    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
    Kernel memory dump
    A kernel dump contains only the kernel-mode read / write pages present in physical memory at the time of the crash. Since this is a kernel-mode only dump, there are no pages belonging to user-mode processes. However, it is unlikely that the user-mode process pages would be required since a system crash (bugcheck) is usually caused by kernel-mode code. The list of running processes, state of the current thread and list of loaded drivers are stored in nonpaged memory that saves in a kernel memory dump. The size of a kernel memory dump will vary based on the amount of kernel-mode memory allocated by Windows and the drivers that are present on the system.

    If a second crash occurs and another kernel memory dump (or complete memory dump) file is created, the previous contents of the C:\Windows\MEMORY.DMP file are overwritten.

    Small memory dump
    A small memory dump (Minidump) is a C:\Windows\Minidump dump file that contains the stop code, parameters, list of loaded device drivers, information about the current process and thread, and the kernel stack for the thread that caused the crash.
    This option is standard checked with memory.dmp files, thats why they'll be overwritten.
    Attachment 35936
      My Computers

  9. Almighty1's Avatar
    Posts : 1,047
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
    Thread Starter
       #9

    SpecChum said:
    I just press reset
    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.
      My Computer

  10. Almighty1's Avatar
    Posts : 1,047
    Windows XP/7/8/8.1/10, Linux, Android, FreeBSD Unix
    Thread Starter
       #10

    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.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 21:48.
Find Us




Windows 10 Forums