BSOD on Boot, no Dump Files, various different messages

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 14,897
    Windows 10 Pro
       #11

    The last crash was 15th this month.

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


  2. Posts : 81
    Windows 10
    Thread Starter
       #12

    axe0 said:
    Avira uninstall: How do I uninstall my Avira Antivirus product?

    What moment of shutting down does the crash hapen?
    It's only happened a handful of times, but it's the exact moment that you normally got from the Shutting Down message to your screen going blank as the PC shuts down.

    If there is an update waiting to be installed, then you get the update message and the percentage countdown, and it happens right at the moment that the update completes and the machine powers down.

    If I had to guess, I would say that this is the moment that Avira unloads form memory. I had a couple of issues with Avira when I was on Windows 7, and was told that the answer was that Ariva was trying to make sure that it was the last thing in memory so that a virus or malware couldn't sneak in after it unloaded, and something else was locking the registry and not releasing it, so Ariva couldn't unload properly.

    Since then I've installed Windows 10 on a fresh SSD. That problem was fixed before I went over to Windows 10.
      My Computer


  3. Posts : 81
    Windows 10
    Thread Starter
       #13

    Duplicate Post.
      My Computer


  4. Posts : 81
    Windows 10
    Thread Starter
       #14

    Duplicate Post.
      My Computer


  5. Posts : 81
    Windows 10
    Thread Starter
       #15

    axe0 said:
    The last crash was 15th this month.

    Please make sure your pc is configured for small dump files How to configure minidump | Windows 10 tutorial
    I've changed the settings to crate a small dump. But the last BSOD was 30/01/2016. There was another on 28/01/2016 and again on 24/01/2016.

    They don't always create a dump file. It gives you a system event saying "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." when you next power the PC up.
      My Computer


  6. Posts : 14,897
    Windows 10 Pro
       #16

    Some events after that event you see something like below.
    Code:
    Event[6335]:  Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2016-01-30T22:31:26.000
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: MSI
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000139 (0x0000000000000003, 0xffffd000230ad680, 0xffffd000230ad5d8, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 013016-5390-01.
    That dumps aren't always created, could means some of the following options
    • hardware too much damaged
    • configuration wrong
    • system corruption
    • counterfeit Windows

    I have added all possibilities I can think of (real quick), it is possible that 1 or more are not relevant.
    Most occuring is either wrong configuration or corruption.
      My Computers


  7. Posts : 81
    Windows 10
    Thread Starter
       #17

    I know that it's a genuine version of Windows, and I would hesitate to say that there was some form of corruption as it did exactly the same thing on an upgrade from Windows 7 on an old disc, and on a fresh install of Windows 10 on a brand new disc.

    If it was damaged hardware, wouldn't I see issues more often, not just at boot?
      My Computer


  8. Posts : 14,897
    Windows 10 Pro
       #18

    Not always, it is unexplainable why though but it is rare.
    If it was damaged hardware, wouldn't I see issues more often, not just at boot?
    I wouldn't as there are some updates that sometimes causes corruption.
    I would hesitate to say that there was some form of corruption as it did exactly the same thing on an upgrade from Windows 7 on an old disc, and on a fresh install of Windows 10 on a brand new disc.



    Diagnostics Test

     System File Check


    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
      My Computers


  9. Posts : 81
    Windows 10
    Thread Starter
       #19

    I know that I'm a little out of step, as I'm not able to reply as quickly as I'd like due to circumstances outside of my control.

    I uninstalled Avira as requested, and it still did a BSOD in the same place. So, unless something was left on the system after the uninstall, it's probably not Avria that's causing it.

    I've included the latest set of log files:

    Attachment 62672

    I will try to do the SFC today.

    I have a legacy Sound card that wasn't part of the original build. It's pretty old (Windows Vista vintage from an older PC) but it was the cheapest way that I could put a Fibre optic audio in and out on the PC, could that be the cause of the problems? For example, an older driver conflicting, or it conflicting with the built in sound card?

    I don't like going in to the case too often to unplug things, so I haven't taken it out yet.

    It didn't give me any trouble under Vista, or Windows 7.
      My Computer


  10. Posts : 14,897
    Windows 10 Pro
       #20

    I have a legacy Sound card that wasn't part of the original build. It's pretty old (Windows Vista vintage from an older PC) but it was the cheapest way that I could put a Fibre optic audio in and out on the PC, could that be the cause of the problems? For example, an older driver conflicting, or it conflicting with the built in sound card?
    Yes it can, old components could certainly conflict with the drivers and cause problems with the hardware itself.

    Comparing with previous installations isn't really fair and also not helpful, Windows 10 is different than Vista and 7 and 8/8.1, Windows 10 is still quite new while the others are years on the market and more stable.
      My Computers


 

  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 15:55.
Find Us




Windows 10 Forums