Windows 10: PC reboots regularly with no warning - no BSOD

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.

 

Those were all deleted for some reason.

 

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

 

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

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

 

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.

 

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

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[/quote]




Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



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.

 

I have been avoiding my PC because I haven't had time to run memtest yet. I just downloaded the USB image and will most likely run it tonight. In the meaning, I updated my memory timings. My motherboard had been detecting the timing speeds incorrectly. I wouldn't think that it would cause a crash, but might as well update it. Sorry for the lag in response.

 

I think maybe I got it? I have been gaming, heavy photoshop usage, etc and no crashes since I changed the memory timings. I will keep this open a bit longer just in case.