Windows 10: BSOD... issues

Thanks for taking a look at my post!

I've been having BSODs for a while now, and I've officially decided I need professional help. With the BSODs, that is. Typically, they're happening while I'm running games (It's pretty much kicked my brother off my computer, which has it's advantages...) but it will occasionally just decide to die. I've been ignoring them because I've been able to get my other work done, but it's crashing while I'm attempting to install the latest version of Unity.

I've ran Memtest86+ several times, the longest of which was a 22 hour test. No issues there. Updated graphics drivers, "refreshed" Windows, and the issues continued. Any help would be appreciated, log .zip attached.

:)

 

Event 3104 Search: "Enumerating user sessions to generate filter pools failed"

With respect to the BSOD have you the eventlog message that occurred - in most BSOD now, Microsoft is writing the issue to the Event Viewer Log (I seem to recall it was the System log)

In my cases to date the 3104 issue does not appear to be related to BSODs

 

I keep getting BSOD, every 5-6 minutes after login. I've attached the dmp files. Help me find whats causing this please.

At the bottom of the BSOD there is a code exp (0x0000001C) and there might be a file name below that code that may tells if a file or something may have cause the BOSD. If so google the code and the file name to see if it leads you to a reason or a solution.

If you can get into safe mode and the BSOD dose not appear you can try this.

If you cannot get into safe mode or if the BSOD comes back in safe mode you will need to reload your systems from recovery or a new installation.

BSOD is often a software driver issue (dll or hardware driver file) but it can be hardware issue. If you can get into safe mode with no BSOD it is probably a software driver issue and not a physical hardware problem and the driver in the message at the bottom
of the BSOD is the issue.

 

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

• Uninstall Daemon Tools
• Download the SPTD standalone installer and follow these steps:
  • Double click the executable to open it
  • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window

Uninstall Avast while troubleshooting
Avast - Uninstall Completely - Windows 7 Help Forums

Marked parts in blue are system drivers for the file system a.k.a. hard drive.
Hardware could usually mean the memory or hard drive.





Diagnostics Test

HDD TEST


Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials...s-how-use.html



Note Do not run SeaTools on an SSD as the results will be invalid.



Run chkdsk http://www.sevenforums.com/tutorials...isk-check.html



Run HDTune to scan for errors, health and benchmark.
Let me know what the results are, prefered screenshots.
Code: 5: kd> k Child-SP RetAddr Call Site ffffd000`20923bf8 fffff802`8cb71ea9 nt!KeBugCheckEx ffffd000`20923c00 fffff802`8cb706c8 nt!KiBugCheckDispatch+0x69 ffffd000`20923d40 fffff802`8ca72668 nt!KiPageFault+0x248 ffffd000`20923ed0 fffff802`8ce39279 nt!MmUnmapViewInSystemCache+0x428 ffffd000`209241f0 fffff802`8ca4a3a2 nt!CcUnmapVacb+0xa9 ffffd000`20924230 fffff802`8ca4fd2c nt!CcUnmapVacbArray+0x212 ffffd000`209242a0 fffff802`8ce3b04c nt!CcGetVirtualAddress+0x40c ffffd000`20924350 fffff802`8ca4d28e nt!CcMapAndCopyFromCache+0x7c ffffd000`209243f0 fffff800`042c6917 nt!CcCopyReadEx+0xfe ffffd000`20924460 fffff800`03b058b5 NTFS!NtfsCopyReadA+0x217 ffffd000`209246f0 fffff800`03b02f1d FLTMGR!FltpPerformFastIoCall+0x135 ffffd000`20924750 fffff800`03b14746 FLTMGR!FltpPassThroughFastIo+0xbd ffffd000`209247b0 fffff800`03b14421 FLTMGR!FltReadFileEx+0x316 ffffd000`209248a0 fffff800`06a09316 FLTMGR!FltReadFile+0x51 ffffd000`20924910 ffffe000`00000001 aswMonFlt+0x9316 ffffd000`20924918 fffff802`00000006 0xffffe000`00000001 ffffd000`20924920 00000000`00000000 0xfffff802`00000006[/quote] Code: 4: kd> k Child-SP RetAddr Call Site ffffd000`22c06538 fffff800`119a1bd5 nt!KeBugCheckEx ffffd000`22c06540 fffff800`11826c36 nt! ?? ::FNODOBFM::`string'+0x3dad5 ffffd000`22c06630 fffff800`1195e5bd nt!MmAccessFault+0x696 ffffd000`22c06780 fffff800`495f3655 nt!KiPageFault+0x13d ffffd000`22c06910 fffff800`495f2f3f FLTMGR!FltpPerformPostCallbacks+0x2b5 ffffd000`22c069e0 fffff800`496232d9 FLTMGR!FltpPassThroughFastIo+0xdf ffffd000`22c06a40 fffff800`11c35bf8 FLTMGR!FltpFastIoRead+0x159 ffffd000`22c06ae0 fffff800`1195fb63 nt!NtReadFile+0x418 ffffd000`22c06bd0 00000000`5ec81e52 nt!KiSystemServiceCopyEnd+0x13 00000000`03ebece8 00000000`00000000 0x5ec81e52[/quote] Code: SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: FLTMGR!FltpPerformPostCallbacks+2b5 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 IMAGE_VERSION: 10.0.10240.16384 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED[/quote]

 

Daemon Tools and Avast unistalled, chkdisk ran, no errors. HD Tune results attached.

 

How old is the SSD?
Please also test the HDD

 

I got it in December 2013, it's been in mostly constant use since then. HD Tune results for storage drive included. SeaTest is running now.

 

SeaTest results finished, here they are. Sorry for the delay on these.

 

Do you know how many passes MemTest86+ had?
You need to run at least 8 complete passes to complete it, less gives inconclusive results and thus isn't worth the time.
Normally with 16GB, it could take around 20h to finish, but for some it takes way longer for some unknown reasons.

 

As I recall, it had completed 8 passes, and was on the ninth. However, this was about a month ago, I could be wrong. I'm going to be away from my computer all day Thursday, I could give it 24 hours or so.
Some improvement, actually. I was able to install the latest version of Unity and Visual Studio (which I think was what crashed the system, as that was what was actively installing at the time of the crash) but had three more BSODs today. Log attached. Also, would you like me to prune all of the minidumps older than a week, or something? There's quite a few of them, and we already have them logged...

 

I suggest to run MemTest86+ again, within a month a lot could have changed.

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
Code: Probably caused by : dxgkrnl.sys[/quote]

 

Nvdia drivers reinstalled, that looks like it might have helped, although I've only been on for about an hour. I'll run the mem test and get back to you when they're done Friday. Thanks!

 

Memtest86+ results back- 13 passes and no errors. I was about ready to close it, as it looked like the Nvidia drivers were the problem, but I just had two back to back crashes. One about a minute post start up directly after finishing Memtest, and one immediately after I started up and logged back in after the BSOD. Log attached.
Very weird.

 

Try booting in safe mode and see if the problem still persist.
If the problem persist, it is usually a hardware/hardware driver problem of the first rank (motherboard, PSU, CPU, HDD/SSD, chipset, cabling etc).
If the problem does NOT persist, it is a software problem or hardware driver that isn't loaded in safe mode.

 

So, have not been able to replicate in a BSOD is in safe mode. But, honestly, they're so sporadic, I don't know whether or not that's just because I haven't run into a random one, or it's clear. Actually didn't have any for several days, and then my brother had several in a row today.
I have noticed that it seems *significantly* more likely for me to have another BSOD immediately following an earlier one- in at most 90 seconds after I log in. The pattern seems to continue until either runs fine(more rare) or I do a full shutdown and leave it off for a few seconds.
I'll do some more testing in safe mode. It usually only bsods under load, any suggestions for testing that is safe mode friendly?