PC reboots regularly with no warning - no BSOD

Page 2 of 3 FirstFirst 123 LastLast

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

    Windows files are not the cause.

    You need to enable driver verifier, there was a memory access violation often caused by drivers



    Diagnostic Test

     DRIVER VERIFIER


    warning   Warning
    Please make a backup of your important files and get your rescue media or create one.
    Please create a restore point.

    Please follow this tutorial to run driver verifier.

    Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

    Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

    If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

    Note   Note
    Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.
      My Computers


  2. Posts : 20
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #12

    I had previous ran the bleepingcomputer driver verifier guide, and that is what was causing my computer to reboot instead of BSOD. When I disabled Driver Verifier it stopped rebooting, now BSOD. Hopefully, since yours has less options checked, it will not reboot. Thank you for helping me.
      My Computer


  3. Posts : 14,901
    Windows 10 Pro
       #13

    Why did you enable driver verifier in the first place?
      My Computers


  4. Posts : 20
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #14

    Because I was getting BSODs.
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #15

    Still the question remains why driver verifier was used, a dump or a few dumps contain in most cases enough for a different step than driver verifier.

    If you indeed had multiple BSOD crashes, I would want you to upload a zip from the DM Log Collector so the dumps can be analyzed, a single dump is than inappropriate to suggest something properly.
      My Computers


  6. Posts : 20
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #16

    Those were all deleted for some reason.
      My Computer


  7. Posts : 20
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #17

    I was getting a ntoskrnl.exe+142780 BSOD and a tcpip.sys bsod.
      My Computer


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

    DId you use any cleanup utility like Ccleaner or disk cleanup?

    What was the BSOD error code of the tcpip.sys?
      My Computers


  9. Posts : 20
    Microsoft Windows 10 Home 64-bit
    Thread Starter
       #19

    Unsure, I was able to find that information by searching my Google search logs. I just got another bluescreen. Running debug right now.
    KMODE_EXCEPTION_NOT_HANDLED
    I attached the minidump.
    I ran the windows memory diagnostic and it found no errors.
      My Computer


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

    Tcpip.sys is a network driver, in many cases it is either of the following that is causing it
    • USB network adapter
    • AV
    • Network driver


    I ran the windows memory diagnostic and it found no errors.
    In 99% of the cases WMD is insufficient to find any errors, for that reason MemTest86+ is recommended.

    The last dump, 0x1E, was caused by driver verifier but no driver flagged. This indicates a different cause than drivers.
    The 0x1E gives a memory access violation result, run MemTest86+ per below instructions.
    Code:
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8036a7d7f67, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception



    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.


    Make a photo of the result and post it.

    Addition:
    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
    If errors show up and you see them a lot later, no problem, the errors don't affect the test.
      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 01:53.
Find Us




Windows 10 Forums