Win7 BSOD after 5818 attempt

[WhackOBill 8]

I happened to be off today and I was going to take the time to get more familiar with the Emby server. I went into the configure page and noticed there was a 5818 update available. So having done nothing else, I told it to go ahead and download and install. It never came back and simply spun the little color change wheel. So I tried a reboot and got a BSOD. I tried Safe Mode with Networking and also got a BSOD. I eventually made into plain safe mode and used a restore point from last night. Apparently that wasn't the solution either. So I let it attempt some system restore of some kind and I seem to be back up with the prior version of Emby running. However, in the configure page there's a button for me to push to complete the prior install. I'm terrified of this button. I let the thing spin for nearly 10 minutes last time and I consider myself lucky to be back running. About the only thing odd on my box is a 4 tuner Ceton card. Otherwise it's a basic Win7/Media Center box.

 

And advice on this 5818 thing before I push this menacing button?

[Luke 42078]

What button exactly? A BSOD is often indicative of a hardware failure so i would consider running diagnostic programs.

[WhackOBill 8]

Well, I was in the middle of backing up when Emby popped up and restarted 5818. The restart seems to have gone fine. This time, after a few seconds, it asked me to allow the load on some MS runtime components. I had read about this in the recent email about server updates and so I let it install. So far, no faults. My backup continues on.

 

I did notice that my automated backup hadn't run in a while. It apparently failed at some point and set the next run date to the year 1899.

 

Hopefully I'm back to stable. The restore point may have saved me.

[WhackOBill 8]

Seems like I'm good again. I must not have given 5818 enough time to update itself or perhaps it got stuck in a bad spot. I'm on an i3-3225 with 8GB and a Samsung 840 Pro SSD and my Emby updates usually occur in about 30 seconds. Perhaps there was more to this on ... Like converting some existing files to a newer format or something.

 

In any case, apologies for the panic. I've just never had a BSOD (C5) on this box before and when it started to recur I began to panic.

[sh0rty 717]

Seems like I'm good again. I must not have given 5818 enough time to update itself or perhaps it got stuck in a bad spot. I'm on an i3-3225 with 8GB and a Samsung 840 Pro SSD and my Emby updates usually occur in about 30 seconds. Perhaps there was more to this on ... Like converting some existing files to a newer format or something.

 

In any case, apologies for the panic. I've just never had a BSOD (C5) on this box before and when it started to recur I began to panic.

 

I know that. That's why I'm backing up every morning since my first PC Armageddon 

Edited January 26, 2016 by shorty1483

[WhackOBill 8]

What button exactly? A BSOD is often indicative of a hardware failure so i would consider running diagnostic programs.

Well, you were right.  My system was apparently teetering on the edge of failure and now has given up the ghost.  It just happened to pick a time during my 5818 to first show signs of instability.  My system won't even make it through the BIOS now.

 

My board is a Z77, G1.SniperM3, and is unavailable these days.  I've ordered a newer Z97 board and, of course, I had to get a new CPU as well since the socket changed.  I decided to test drive that Broadwell i5 with the 6200 Iris Pro iGPU now that Emby is QuickSync aware.

 

Now I just have to figure out how to swap it in and get things to boot since I was unable to perform a sysprep /generalize before the death of my other board.