Random BSOD's for the last few days.

[cricktopsy]

A little about the PC - It's mainly used as a Plex server and I also run a VM off the box using VMware workstation 11. The PC has 2 oboard NICs one I use specifically for the VM machine, the other I use for everything else. I believe the BSOD has something to do with the Intel NIC. I've tried updating/reinstalling Drivers. I could really use some help figuring this out as the PC is not rebooting after BSOD's even though I've checked the settings and they're set to restart after system failure.

View attachment 367036

 

[Pauly]

According to a couple of the recent dumps driver verifier has detected the driver 000.fcl as causing the crash which is part of Cyberlink software
Try uninstalling this software to see if it helps the situation but the dumps are quite varied so may be a bit trial and error on this one

There are also a couple dumps pointing at possible memory issues so would be wise to run memtest86+ on the ram overnight
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html test for a minimum of 8 passes

 

[cricktopsy]

I'll run memtest tonight to verify - I uninstalled powerDVD for now.

What do you think the odds of upgrading to 10 fixes these issues?

 

[Arc]

Disable driver verifier.

As the starting point, please follow this post to disable Samsung Rapid mode.

Also take the following tests:

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark
​

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Stress test the CPU.

Hardware - Stress Test With Prime95
​

It saves the result as a .txt file in the prime95's folder. Upload the file for us.

Let us know the results.
___________________________________________________

BugCheck 50, {fffffa7f9896077d, 1, fffff88001d505d5, 7}


Could not read faulting driver name
Probably caused by : hardware ( afd!AfdPoll64+530 )

Followup: MachineOwner
---------

BugCheck 1000007E, {ffffffffc0000005, fffff88000dc7db8, fffff88002f078d8, fffff88002f07130}

Probably caused by : SamsungRapidDiskFltr.sys ( SamsungRapidDiskFltr+15db8 )

Followup: MachineOwner
---------

 

[Pauly]

Given the combination of the dumps I looked at I think it is highly likely that your issue is either faulty ram passing bad info or a corrupt/dodgy driver, either of which can give these types of dumps so if your RAM checks out good then it is possible but given the unique setup you have and the fact you are running Plex & VM over two NICs it is hard to be sure.

 

[cricktopsy]

Tried running SFC as well - probably unrelated, but these came up.

2015-07-26 14:03:27, Info                  CSI    0000033b [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-26 14:03:27, Info                  CSI    0000033d [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-26 14:03:27, Info                  CSI    0000033f [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-26 14:03:27, Info                  CSI    00000340 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-26 14:03:27, Info                  CSI    00000342 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-07-26 14:03:27, Info                  CSI    00000343 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-07-26 14:03:27, Info                  CSI    00000346 [SR] Repair complete

 

[Pauly]

Those sfc errors are part of a bad update patch from MS and nothing to worry about, they have said they will be fixed at some point but haven't been yet and are unrelated to your issue

 

[cricktopsy]

Ran Memtest, CPU/Video Stress Test - everything was fine there.

CPU ran a little hot, but no crashing.

Let's see if disabling Samsung Rapid Mode and uninstalling Power DVD helps.

 

[Arc]

Ran Memtest, .

Which tool you used to run the memory test, and for how many passes?

Also, what about disabling Samsung Rapid mode?

 

[cricktopsy]

Disabled Rapid Mode, Ran Memtest86 for 8 passes. Here are some new dumps from last night. Looks like it happened 3 times while I was sleeping.

View attachment 367117

 

[Arc]

Ran Memtest86 for 8 passes.

Memtest86 is a crap inferior program to test the memory, having a deceptively similar name to memtest86+.

Only memtest86+ can tell you about the health of the RAM.

How to Test and Diagnose RAM Issues with Memtest86+

 

[cricktopsy]

Ran Memtest86 for 8 passes.

Memtest86 is a crap inferior program to test the memory, having a deceptively similar name to memtest86+.

Only memtest86+ can tell you about the health of the RAM.

How to Test and Diagnose RAM Issues with Memtest86+

Sorry it was memtest86+

 

[Arc]

Ran Memtest86 for 8 passes.

Memtest86 is a crap inferior program to test the memory, having a deceptively similar name to memtest86+.

Only memtest86+ can tell you about the health of the RAM.

How to Test and Diagnose RAM Issues with Memtest86+

Sorry it was memtest86+

Are you really sure? Asking again because the difference between them two is as the difference between the hell and the heaven.

And another thing, your RAM is running at 1866 MHz, which is considered as overclocking.

  Speed                         [COLOR=Red]1866MHz[/COLOR]
  Manufacturer                  Kingston

View attachment 367154
​

Load the BIOS to the defaults by clearing CMOS and see how it goes, because overclocking is often unstable.

How To Clear CMOS (Reset BIOS)
​

Let us know the resulting situation.

 

[cricktopsy]

Yes I'm sure, I tried system restore but that didn't complete successfully.

I'm going to try upgrading to Windows 10 tonight - if that doesn't work I'll bite the bullet and go for a clean install of Windows 10 on Launch Day and rebuild the Plex server. The VM is still intact and that does most of the work so I'll just re-add that after rebuilding.