Windows 10: Random BSOD Erorr Messages

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.

 

I ran Prime95 once and it crashed.

I am using a wired Ethernet connection but have a wireless mouse so I will swap that over to a wired one and try. I'll try the startup thing but I don't think that will work as I had a bare bones install (nothing but the OS / no drivers installed) and it crashed.

 

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?

 

I'm using the stock cooler that came with the CPU. Yes, I agree its sounds like a hardware program or it could be something isn't compatible with windows 10. I'm thinking of installing Windows 7 and seeing if I can get it to crash seeing how all hardware tests come back fine and the system is stable when I play games / run stress tests (other then potentially that one crash from prime).

Edit: I found someone with a similar issue to me where memtest came back fine and the system only crashed on cold boot (Windows 10 crashing several times at boot) I guess I'll see if I can swap the RAM. Unless you have any other ideas / ways I can prove its the RAM?

 

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.

 

I think the issue may be the wireless mouse... While I still have to do more testing to confirm, but when I swapped to a weird mouse I was able to boot up 3 times without any issues. I have a Logitech MX Master mouse, any ideas on what I can do so that I can keep using the mouse?

 

Hopefully, that is your issue. See if this will help you if this is your mouse MX Master - Logitech Support

 

Their software is to just change the buttons it seems *Sad

I have swapped the dongle to a USB 2.0 port so i'll know in a day or two if that helps.

 

Ok, I don't know about drivers then. Windows 10 seems to me to be picky about wireless drivers.

 

Well, I've been playing with it for a bit now... I pulled out the GPU and it crashed, I go down to one stick of RAM and it still crashes but alot less frequently (same for both sticks).

 

Have you used a wired mouse for any length of time/ if not try it. I notice above you tried it for a short time but it seems you went back with a driver update and switched ports. Try not having the dongle installed at all.

I also still go back to the failed Ram test. You are also saying that with 1 ram stick you crash less. You failed Prime95 which tests the CPU and ram.

 

I think I failed the Prime95 test due to this

Intel Skylake bug causes PCs to freeze during complex workloads | Ars Technica

I tried using a weird mouse for a bit with the wireless dongle unplugged and it crashed...

I have recently updated my BIOS so that issue should now be fixed.

Edit: With one stick I seem to crash before windows starts (BIOS Logo flashes then a few seconds later it reboots)... All the Minidumps from the last few days except today should show that.

 

Here are several of the most recent BSODs

Code: Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80129753e81, ffffd0016b5cebb0, 0} Probably caused by : NETIO.SYS ( NETIO!KfdCommitTransaction+279 ) Followup: MachineOwner --------- Use !analyze -v to get detailed debugging information. BugCheck A, {6d9d0000, 2, 0, fffff800f5b196d5} *** WARNING: Unable to verify timestamp for klif.sys *** ERROR: Module load completed but symbols could not be loaded for klif.sys Probably caused by : klif.sys ( klif+3092b ) Followup: MachineOwner Klif.sys file description Productname:Kaspersky Anti-Virus Description: Klif Mini-Filter fre_wnet_x86 Company:Kaspersky Lab --------- Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff8002befd8d1, ffffd00024a76258, ffffd00024a75a70} Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+61 ) Followup: MachineOwner ffffd000`24a76ac0 fffff800`7f648248Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for snapman.sys *** ERROR: Module load completed but symbols could not be loaded for snapman.sys snapman+0x48248 Acronis True Image Snapshot Manager driver ------- Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff801e61455a6, ffffd000285cf5b0, 0} Probably caused by : NTFS.sys ( NTFS!NtfsMapUserBuffer+26 ) Followup: MachineOwner Code: STACK_TEXT: ffffd000`24d0d5b0 fffff800`21d0cb73 : ffffd000`24d0d700 ffffd000`00000004 00000000`00000000 00000000`00000000 : nt!ExFreePoolWithTag+0x3a ffffd000`24d0d690 fffff800`21c45e56 : ffffc001`d9d4d420 ffffd000`24d0d980 ffffc001`d9d4d010 ffffc001`e2effb40 : NTFS!NtfsFullDeleteLcb+0x153 ffffd000`24d0d6c0 fffff800`21d0cd1c : ffffe000`63c49dc8 ffffe000`5e646180 ffffc001`d9d4d010 ffffc001`d9d4d420 : NTFS!NtfsTeardownFromLcb+0x146 ffffd000`24d0d760 fffff800`21c3ca80 : ffffe000`63c49dc8 ffffd000`24d0d863 00000000`00000000 ffffc001`d9d4d010 : NTFS!NtfsTeardownStructures+0xdc ffffd000`24d0d7e0 fffff800`21cf4b5b : ffffd000`24d0d9b8 ffffd000`24d0d9b8 ffffd000`24d0d980 ffffc001`d9d4d010 : NTFS!NtfsDecrementCloseCounts+0xd0 ffffd000`24d0d820 fffff800`21d30182 : ffffe000`63c49dc8 ffffc001`d9d4d150 ffffc001`d9d4d010 ffffe000`5e646180 : NTFS!NtfsCommonClose+0x40b ffffd000`24d0d8f0 fffff800`020f0b79 : fffff800`02419200 ffffe000`5fd44040 fffff800`00000000 fffff800`02419340 : NTFS!NtfsFspCloseInternal+0x1a6 ffffd000`24d0da80 fffff800`0208f125 : 00200020`00200020 00000000`00000080 ffffe000`5e6b3700 ffffe000`5fd44040 : nt!ExpWorkerThread+0xe9 ffffd000`24d0db10 fffff800`021cd916 : ffffd001`9d18f180 ffffe000`5fd44040 fffff800`0208f0e4 00200020`00200020 : nt!PspSystemThreadStartup+0x41 ffffd000`24d0db60 00000000`00000000 : ffffd000`24d0e000 ffffd000`24d07000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16[/quote] ----------[/quote] NETIO is the Windows Network I/O driver. KILF is Kaspersky internet and by the description looks like the Wireless network driver (fre_wnet_x86) In the very beginning of this thread you were asked to uninstall Kaspersky and use their removal tool. I don't know if you did, but the driver is still there.

Acronis Snapshot driver is listed as a cause too. You are still having the same NTFS (Windows file system) errors.

2 of the dumps have an error code of 0X7E, which in many cases is a hard drive/storage error. 2 of the dumps are Network related, I suspect are wireless problems.

Please uninstall Kaspersky and use their removal tool to completely remove all of it and use the built in Windows Defender.

Error code 0X3B is in many cases bad or corrupted Graphics drivers. Please update your graphics drivers. Download the new drivers from Nvidia, uninstall the old drivers then use Display Driver Uninstaller . Be sure while uninstalling to uninstall all of the Nvidia drivers and make sure to uninstall the Graphics driver last. Reboot and install the new drivers, but this time select Custom Install. Make sure the "Clean Install" box is checked, uncheck all parts of the install package except the Graphics driver and the PhysX driver. Install those 2 only.

 

I thought we ruled out the OS thou... Since it crashed on a brand new install without anything installed