Discussion Video editing slower on fresh W7 installl

[videobruce]

Not sure where to put this since there are many areas what/where the problem could be.

I just did a fresh W7 Pro x64 install, loaded my drivers, done some minor tweaks and loaded the video driver package (Nvidea). It was done on SSD's.
Doing video editing & processing, it use to take 1/2 the length of the video running time to process the result.
I could tell when the process is done by the cooling fan(s) slowing down and now, the AC power consumption showing on a Kill-A-Watt like meter. I DON't game!

Now, the process time is almost the same length of the clip itself; 30" clip takes around 25" instead of 15" to process as example.
The fan speed barely changes and the power consumption only increases slightly.
Also, running Passmark's 3d benchmark test (which puts the heaviest load on the system) the fan(s) barely increase in speed and the peak AC wattage is far less than before indicating something is limiting the processing. There are NO strange processes, etc running!

The original setup had a RT7 Lite stripped down W7 Pro installed, this is a original stock O/S .iso that was used. The same M$ tweaks for Performance and Appearance were done favoring performance. Clear Type is enabled, all the others are unchecked.

Other than the above, the only other difference is the Nvidea driver version that I loaded, but I'm not sure how or if that would affect program processing time. I don't know what the older driver version was.

I have another streamlined W7 iso that used RTLite I'm going to try on spare SSD.

 

[bba_tcg]

Possibly different video editing parameters?

 

[videobruce]

Nope, all basically the same, I tried to use similar files and especially resolutions.

Can/does a GPU driver have anything to do with processing videos as in editing or is it all visual (monitor)?

 

[bba_tcg]

Nope, all basically the same, I tried to use similar files and especially resolutions.

Can/does a GPU driver have anything to do with processing videos as in editing or is it all visual (monitor)?

If you're doing the work on the GPU, certainly the driver is involved. If you're doing the work on the CPU, the GPU driver wouldn't be significant.

 

[videobruce]

I always use the option of using the GPU over software processing.

FWIW;
I decided to swap GPU drivers.
BTW, I usually install these via Device Manager in spite of NVidea and their insistence of welding the unnecessary bloat/fluff in with the actual drivers. I even tried to 'hide' the three .exe's from DM that are in the SAME folder with the drivers, but it wouldn't let me install the drivers with them 'hidden' (I add the word 'old' to the extension instead of actually deleting the files to 'hide' them. It does work!)

NVidea v391.35 from 3-2018 seems to of solved the problem. I tried numerous files and the process time is less than before which I wasn't expecting and the 'Processor' strain (my term) isn't there. Really at a loss here since it was a actually a apparent improvement.
NVidea v375.70, 10-2016 was the oldest which was 1/2 the size of v472.12 from 9-2021 which I believe is the last that will work with a GTX 1060 card if I got my versions correct.

I don't know what was in there originally due to numerous other events and related changes unfortunately.

 

[bba_tcg]

I always use the option of using the GPU over software processing.

FWIW;
I decided to swap GPU drivers.
BTW, I usually install these via Device Manager in spite of NVidea and their insistence of welding the unnecessary bloat/fluff in with the actual drivers. I even tried to 'hide' the three .exe's from DM that are in the SAME folder with the drivers, but it wouldn't let me install the drivers with them 'hidden' (I add the word 'old' to the extension instead of actually deleting the files to 'hide' them. It does work!)

NVidea v391.35 from 3-2018 seems to of solved the problem. I tried numerous files and the process time is less than before which I wasn't expecting and the 'Processor' strain (my term) isn't there. Really at a loss here since it was a actually a apparent improvement.
NVidea v375.70, 10-2016 was the oldest which was 1/2 the size of v472.12 from 9-2021 which I believe is the last that will work with a GTX 1060 card if I got my versions correct.

I don't know what was in there originally due to numerous other events and related changes unfortunately.

Glad you got it sorted!

 

[videobruce]

Now, if I could get the GPT boot issue w/ W7 'sorted'..................

 

[bba_tcg]

It's not hard to do, but trying to explain it is very verbose. I have an explanation in a thread that I believe is in the Windows forum that explains how to fix a boot issue with Win 10. The same explanation would apply to Win 7.

 

[videobruce]

W10 has the same issue??? Are we talking about the same thing??

 

[bba_tcg]

If you're talking about how to get Win 7 to boot in a UEFI configuration on a GPT partitioned disk, yes.

 

[videobruce]

Yes, that's it. the missing bootx64.efi file in one of the two 'boot' folders which I still don't understand.
Link to that post you mentioned?

 

[bba_tcg]

If you already have the required volumes set up, and they have drive letters, you might try using the following (elevated) command:

bcdboot c:\windows /s x: (where x is the drive letter of where the boot files are located) /f UEFI

Hopefully, the output of bcdboot will be "boot files copied successfully" (or something very similar). Note that I disclaim any responsibility if it doesn't work. Google "bcdboot command line" if you want further knowledge concerning the command.

Edit: also, if your Windows drive letter doesn't show as c: substitute the right drive letter.

 

[videobruce]

I'm referring to the install file/files doing a fresh install to a GPT drive.

 

[bba_tcg]

So am I. This installs the boot files if you already have the volumes set up and they have drive letters.

 

[StinkyPinky]

I had to check the date of these posts. Does the PC not support Win 10/11?

 

[dr1337]

I had to check the date of these posts. Does the PC not support Win 10/11?

if I weren't a gamer I would still be using windows 7 on my main PC; most of our computers at work literally run w7 because its faster and less likely to randomly install wrong drivers and do updates during production.

Even with pro licences and group policy, I have still seen windows update features cause issues recently with some video drivers. And just like the thread OP noticed, the sheer amount of background tasks is crazy and the performance difference on older systems and NUCs is pretty significant. Software bloat creep is real and IMO a real problem for the world in general. I shouldn't have to run a bunch of random junk on any operating system if I don't want to, especially when it all degrades performance. (and they definitely do that on purpose just to help sell new PCs like apple crippling iphones with updates or bloatware with OEM laptops)

 

[igor_kavinski]

NVidea v391.35 from 3-2018 seems to of solved the problem.

Must be a regression with newer drivers and since it's Nvidia, they don't care about users of their older cards. I have a Titan card and they dropped support for it in their Studio drivers after a certain driver version. That's an expensive PRO card so imagine how less they care about people owning their gaming cards..

 

[videobruce]

This is slightly OT, but it appears to be the secret, highly cryptic recipe to fix the GPT problem with W7 which no one could give me an answer;

Advanced Windows 7 installation from USB flash (UEFI, USB 3.0 info included)

I've only seen this thread by Yazoo. How to install Windows 7 from a usb flash drive and test that it works. I haven't tried those instructions but I assume they work. I have compiled some alternate instructions using information I have gleaned from around the net. My primary purpose was to...

forums.anandtech.com

 

[bba_tcg]

This is slightly OT, but it appears to be the secret, highly cryptic recipe to fix the GPT problem with W7 which no one could give me an answer;

Advanced Windows 7 installation from USB flash (UEFI, USB 3.0 info included)

I've only seen this thread by Yazoo. How to install Windows 7 from a usb flash drive and test that it works. I haven't tried those instructions but I assume they work. I have compiled some alternate instructions using information I have gleaned from around the net. My primary purpose was to...

forums.anandtech.com

Lol. Someone attempted to give you an answer, but you really haven't been very forthcoming with what your particular situation is.

If you have win 7 installed on an MBR disk, the easiest way would be to use mbr2gpt.exe. If it's not part of the win 7 install, booting from a win 10 or 11 USB drive would do it.

If you already have win 7 on a GPT disk and it won't boot, using the command I listed in a post above will work, if you already have drive letters assigned to the volumes you're using.

If you don't have drive letters assigned, use the search function in the Windows subforum here to find the thread where I helped Markfw get a Windows 10 GPT disk to boot.

 

[videobruce]

Lol. Someone attempted to give you an answer, but you really haven't been very forthcoming with what your particular situation is.

The original issue was apparently solved as I stated, the side note which should of been in a separate thread, is just that. The 'GPT' issue w/ W7 I wasn't aware of until recent. I decided to return to using MBR since that worked w/o the hassle.

 

[bba_tcg]

Yes. I realize you solved the original topic of the thread. I've given you the information you need to take care of the side note, which should have been a separate topic in the Windows subforum, even though you claim no one could give you an answer.

 

[videobruce]

With all the posts, it wasn't clear enough for me.

If you already have the required volumes set up

"Volumes" being drives or partitions?

 

[bba_tcg]

Volumes are formatted partitions, with or without a drive letter assigned. A logical storage area.