BSODs at random, generally with Plex Media Server running

[mrtacoswildride]

My hypothesis is that the BSODs I've been getting have something to do with Plex. They started about a month after I installed Plex, and have been happening irregularly since then. Here's the list of BSODs from the Event Viewer (if that isn't in the thing I uploaded, very nifty tool btw).

Critical 6/13/2015 21:10:34 Kernel-Power 41 (63)
Critical 6/13/2015 11:08:35 Kernel-Power 41 (63)
Critical 6/13/2015 09:58:48 Kernel-Power 41 (63)
Critical 6/11/2015 08:45:30 Kernel-Power 41 (63)
Critical 6/7/2015 14:58:32 Kernel-Power 41 (63)
Critical 5/16/2015 14:46:55 Kernel-Power 41 (63)
Critical 5/15/2015 04:25:55 Kernel-Power 41 (63)
Critical 5/4/2015 18:46:37 Kernel-Power 41 (63)
Critical 5/4/2015 16:55:21 Kernel-Power 41 (63)
Critical 5/4/2015 13:21:37 Kernel-Power 41 (63)
Critical 5/3/2015 22:26:18 Kernel-Power 41 (63)
Critical 5/3/2015 21:22:50 Kernel-Power 41 (63)
Critical 4/25/2015 16:34:47 Kernel-Power 41 (63)
Critical 4/24/2015 17:45:27 Kernel-Power 41 (63)
Critical 4/24/2015 09:41:14 Kernel-Power 41 (63)
Critical 1/7/2015 19:49:53 Kernel-Power 41 (63)
Critical 11/19/2014 16:25:52 Kernel-Power 41 (63)
Critical 11/19/2014 16:13:48 Kernel-Power 41 (63)
Critical 11/19/2014 16:05:35 Kernel-Power 41 (63)
Critical 11/19/2014 16:03:28 Kernel-Power 41 (63)

As you can see it happened three times today, twice while Plex was actively running. I have Plex set to run on startup, but almost always close it if I'm not actively using it. I've had this computer (which I built) since 2011, and this is a complete record of all BSODs while owning it.

Please let me know if I'm right (or not) and what the suggested solution would be, and if any additional information is required.

Thanks, and I hope the above helps!

 

[ICIT2LOL]

Hello and welcome mrta there are some things I don't quite understand about your dumps but I would certainly be doing these for starters


http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/433-disk-check.html< if necessary include the /f and /r in the command line as per Option2
in safe mode if you like and I would be checking out the memory too

MEMTEST

The memtest you will need to make a bootable disk / stick andset the BIOS to boot from the optical or USBand it will take a fair time torun- some leave it overnight. see the attached document.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

But one thing is very important you must let the test run for at least 8passes any less and the findings are no good. Now if errors come upstraight away then you can stop it - see my pics. Now if there are errors andyou have more than one stick of RAM in then you will need to test each stick ieremove the sticks and replace stick 1 in slot 1 and test no errors do thesame in slot 2 with stick 1 no errors then repeat the process with stick 2 -that will show up the faulty stick - the other thing is it could be a faultyslot but most unusual. With more than two sticks the process is even longer asone may realize.

It is a very lengthy and tedious process but worth it if youhave errors.

While you are it and before the memtest



SLOT CLEANING

Now as for the slots toclean them use a strip of old credit card (or any card thin enough some arebetter than others ) about 1/2 inch wide nip the corners off one end - preferably round them off hold a piece of thin lint free cloth over theend dab on some form of alcohol - isopropyl alcohol (what we swab the skin withbefore an injection) is good and GENTLYswipe along the slots.

This can also be done for the GPU slot/s andalso the contacts of the sticks or cards - not the stick but some lint freecloth of course. See my pic for the sick but please be very gentle doing it ifyou are in any doubt - please ask before doing it but I use this all the timeand have yet to damage anything

 

[Pauly]

Just had a scan through your dumps and they are all showing 0xC5 Pool_Corruption errors, it is worth doing a RAM test to verify memory as mentioned above but these are generally caused by driver problems so may be easiest to enable driver verifier to stress your drivers.
Its worth noting that Networx was referenced by one of your dumps so may be worth removing/disabling/updating this to see if it helps but as it was only once this could well be an erroneous entry and can be delayed until later if you want to do memtest and verifier first

 

[ICIT2LOL]

Yep Pauly I saw them too and I did also advise the memtest in my post plus a quick sfc and chkdsk.
I also thought it as well to reseat the hardware and do some cleaning of the slots on everything because those dumps came up with hardware related stuff.