Random BSOD Erorr Messages

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff803b08d117e, Address of the instruction which caused the bugcheck
Arg3: ffffd000f7d6bc30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
PRIMARY_PROBLEM_CLASS:  0x3B_nt!IoRemoveIoCompletion

IO is inn Out usually referring to the hard drive Read/Write operations

Code:

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff803b08d117e, Address of the instruction which caused the bugcheck
Arg3: ffffd000f7d6bc30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Later in the dump were several references to FLTRMGR Which is Microsoft Filesystem Filter Manager from Windows Update and also
0x3B_nt!IoRemoveIoCompletion.

Both storage related. Next please right click on the start icon and select Command prompt administrator, give admin permissions and copy/paste this into the window that opens and press enter sfc /scannow . If you decide to type it in, please notice the space between the sfc and the /. We want it to say no integrity violations were found. If it says there where corrupt files that could not be repaired, please reboot and run it again. You may have to run it 3 times with reboots in between each time.

Please make sure you have run all Windows Updates including SP1, before running the sfc scan.

HappyMan, I have to go back to Post #7 where you ran memtest86+ and received ram errors. Memtest86+ is the best test there is by far and the only test I will use. It will not read my chipset. I have DDR4 like you, but a different chipset. This is your test

Attachment 56755

I would like to point a couple of things out. Notice the wall time. you ran it for 3 hours and 33 min. with SMP enabled (multi cores). You did not complete 1 pass yet. I have the same amount and type of ram as you. Here is a screenshot of mine. I ran it for an hour less than you and did not enable SMP which means I was running on 1 core and finished almost 2 passes with no errors.

Attachment 56759

You're right about the time, I just looked at it wrong. Did you ever run Prime95 or AIDA stress test? I saw you ran IBT.

Try going to task manager, and click on the startup tab. Disable everything you can. The only thing that is necessary is your AV. See if that makes a difference. Are you using a Wi-Fi Dongle of any kind? If so, see if you can change to a wired connection or use a wired keyboard and mouse.

When you run any of the stress tests, and really at all times, make sure you keep a close watch on your temps. I like either Core Temp or Real Temp but there are some other programs out that will keep track of them. I don't know what CPU cooler you are using.

If you are crashing on a bare install of Windows, with nothing else added, I am going to assume a Hardware problem. Does that sound reasonable to you?

Have you ever bench tested before? I usually bench test mine. Pull it out of the case and strip it down to bare essentials. Remove the graphics card, 1 hard drive, no DVD, 1 stick of ram and try it that way. Remove everything that is not necessary to just run. Use 1 stick of ram. If it continues to do the same thing, swap ram sticks, still using just 1. You can do the same thing inside the case, but it is just easier to get to everything on the bench.

You can have a hairline crack in anything from ram, motherboard to PSU that errors when cold. After the first startup, it generates enough heat to make everything expand and the crack closes. I know that sounds like a stretch, but I have seen situations like yours before where that was the only reasonable explanation. Nothing I have seen in your system specs should make your system incompatible with Windows 10. You list nothing unusual. The wireless dongle, I know 10 seems to have issues with some types. So, it seems you have some defective piece of hardware that once running will do fine, but on startup has serious problems. My system was the same way when I first built it. At times I had to try 25 times to get it to start. Once it did, I could do anything in the world with it. It was stable as a rock. I even left it running 24/7 for 2 weeks. It turned out to be the PSU. Once I swapped the PSU, I have had no problems since, not even 1. But, that's what I did. I benched it and started swapping parts 1 at a time until I found the defective one.

BTW, when you try different things, do them 1 at a time so you will know which one is causing the problem.