KEPS

Good to know, thanks. Really appreciate your help. Will continue to cast the net out there and try and figure this out. At the least I'm starting to feel like I won't need to buy a new GPU which is a relief.

Sure, just tried it - everything is okay, as far as I can tell. Please see the attached screengrab from HWinfo while I was running the blend test on all cores. How does it look to you?

One more odd detail - I just tried encoding in Handbrake, H264 but WITH Nvidia NVEnc - and it worked perfectly for both H264 and H265. And in task manager I see the "Video Encode" percentage bar fills up to 50% as it's going, and it goes very quickly. So now I'm suspecting maybe the CPU is the culprit? If the GPU can encode fine when forced to - but if the CPU can't - and who knows which Adobe is using (even though it should be a known quantity...) - maybe it's the CPU? Just restarted and dialed back my overclock from 4.4GHz and 1.25V to 4.2GHz and 1.2V and same problem.

Thanks, that's good to know. Will continue to Google it. Checked Win reliability monitor and right before this whole problem began it seems there's a warning about a failed windows update on something called "9WZDNCRFHVN5-MICROSOFT.WINDOWSCALCULATOR." - that can't be it, can it?

Hrm, very interesting. Just tried encoding a random clip with Handbrake. Tried twice using just its standard H.264 export preset and it crashed right away both times. Then tried H.265 and it worked... but it gave me a file that will play but that's full of tons of random blocks of pixels and garbage. Any ideas what this could be? Feels to me like something either deep in the OS has lost its mind or I've got a very odd and unique problem somewhere in my hardware. EDIT: Tried encoding with MPEG-4 (both MP4 and MKV) in Handbrake and both came through perfectly. Whatever my problem is it's unique to H264, H265 - can't tell if that's GPU related or what?

Thanks, that's a good idea! Just put the weird H265 file that Premiere exported on my phone and can confirm I'm getting the same blocky and sandpaper pixelation - says to me that it's been burned into the file while it was encoding. And I believe Premiere uses the GPU to do the encoding - which, agian, leads me to worry that it's a faulty GPU or a hardware glitch caused by the weird electrical storms we've been having. As for measuring voltage, unfortunately I don't have a way to do that - but given that it's a brand new PSU can't I assume it's working fine? Thanks, and let me know if you have any other ideas!

My specs: Intel i7-5820k overclocked to 4.4GHz (stable under stress) Noctua NH15 cooler fan 64GB RAM (8x8 sticks) EVGA GTX 1070 2 HDDs, 2 SSDs, 1 M.2 NVME SSD Corsair RM 650i (formerly EVGA G2 650 which I thought was faulty but apparently is fine) Latest version of Win 10, updated Use Bitdefender Total Security, updated and ran system check Graphical glitch screengrabs (attached to this post and link here): https://drive.google.com/open?id=1jK40aQ8KA4XdF9C0aDt9K4lQqP3BmeiW Hi folks, Yesterday morning when I turned on my computer I got an odd bios message - something like, "Due to a voltage issue the system is not stable" and it was hanging on the American Megatrends boot screen - I rebooted and everything was fine. However, I started noticing a weird graphical glitch in my Chrome tabs at the top. I thought nothing of it and proceeded with my day. I do video editing work and when I opened Premiere and went to export a project it crashed. No problem, I thought - this happens, so I rebooted and tried again. Another crash. Eventually I realized that the problem was happening ONLY when I tried exporting H.264 clips. I tried ProRes and H.265 and it seemed to run through okay. (Tried exporting with software only, no CUDA, and same crash only for H264). However, I noticed that the H.265 file which exported just fine has all sorts of weird graphical glitches in it. I tried opening it up in Premiere as well as VLC to confirm those glitches are burned into the file and not part of VLC/Premiere. So my problems are: Premiere crashes when trying to export H264, then with intermitant crashes (sometimes on startup), only fixed by a full system restart. Weird graphical / pixelated rainbow stuff in Chrome tabs. H265 export came through with all sorts of weird blocky pixels and also small, sandpaper-textured tiny pixels (see top left corner of attached video image) My first instinct was that, paired with the odd power message I got that morning, there was a PSU issue. I live in an old building with crappy wiring and have had PSUs blow out on me once every three years or so. (I finally figured out the outlet I was using had no working ground connection - re-routed with an extension cord immediately to a working ground outlet so hopefully that helps). So I went out today and got a new PSU - installed it and found the same issue. My next suspect was my video card - so I ran FurMark at full load for like 15 minutes and everything was fine (monitoring temps and fan speeds with GPU-Z - all looked normal). Also ran AIDA64 for 20 mins at full CPU load, again, everything fine. Tried updating Premiere, no change. Noticed I was getting similar graphical glitches when looking at BRAW files in Premiere (but not my Sony A7S2 XAVCS MP4s) - tried uninstalling the last video-related plugin I installed (BRAW Studio, which allows you to import BRAW files into Premiere on PC) - no change. Updated my GTX 1070 drivers, no change. Note, all other video files I try to play in VLC (that I exported a few days prior) play just fine - as do YouTube videos. Similarly, for games, I played Mad Max at full settings for an hour last night, was looking for glitches, and didn't spot anything. If this was a GPU issue wouldn't it be popping up in games and all videos? Or maybe it's just something to do with the circuit that encodes and decodes video, and that's why the problem seems specific to Premiere and only certain, limited graphical things (like the see through areas in Chrome tabs). This is driving me nuts! Feels like it's a dumb Adobe issue - and yet, why is it carried through to Chrome (and, it seems, other apps that have some transparency in the windows?). And if it's a hardware issue, why wasn't it revealed during the 100% stress test? Any thoughts or advice - this is driving me nuts and I need to export projects for work ASAP - will to just go out and get a new video card tonight but wanted to check in here for some thoughts before I blow hundreds of dollars on what may be an unnecessary GPU upgrade. Thanks for your time!