Skip to main content
Participant
May 27, 2018
Question

Warp Stabilizer: Step 2 freeze/crash Windows 10 - HELP/URGENT!!

  • May 27, 2018
  • 13 replies
  • 8640 views

I desperately need help fixing the warp stabilizer freeze/crash on step 2(during stabilization). I use premiere pro to provide a living for my family and I heavily depend on using warp stabilizer! Its a hard screen freeze that it wont come back from. A few times it will show a BSOD whea uncorrectable error.

I have two computers I have been swapping hardware on, trying to determine what the problem is. I made a fresh install of Windows 10 on a separate ssd and installed latest version of Premiere Pro. I have two testing stations, my workstation and another PC(we will call this PC2). I used this Windows 10 ssd with premiere in both computers. Warp stabilizer works on PC2 and will freeze/crash on my workstation using the SAME Windows 10 ssd. So I transferred devices, one by one. I changed the GPU and RAM on the workstation and same problem on Windows 10 ssd. So it has to be the motherboard/CPU/Driver on the workstation. I ran PC-Doctor to run extensive checks on all my hardware and everything passed. I ran Intel Processor Diagnostic and it passes. There are zero error log files here: C:\Users\Backup\AppData\Roaming\Adobe\Premiere Pro\12.0\logs. I honestly don't know where to go from here. I'm practically at the point of buying some other video editing software because of the crisis this has caused with completing jobs that pays for my family's living.

Every configuration was tested with the same Windows 10 ssd

Workstation: Warp Stabilizer crash/freeze/BSOD

CPU: i9 - 7940x

MB: Asus Rampage VI APEX

RAM: 64gb Tridentz f4-3200c16q-64gtz

GPU: EVGA Geforce GTX 1080 Ti SC2

PS: hx1000 power supply

PC2: Warp Stabilizer works

CPU: i7-6900k

MB: Asus x-99 A-II

RAM: 32gb Tridentz f4-3200c16d-16gtzb

GPU: EVGA Geforce gtx 1050

PS: Corsair CX750

I have tried the following that produces the same warp stabilizer problem:

Test Hardware swap Workstation: Warp Stabilizer crash/freeze/BSOD

CPU: i9 - 7940x

MB: Asus Rampage VI APEX

RAM: 16gb Tridentz f4-3200c16d-16gtzb

GPU: EVGA Geforce gtx 1050

PS: hx1000 power supply

This topic has been closed for replies.

13 replies

Participant
August 23, 2018

I would like to also add that the morph tool in Premiere is crashing my Windows 10. It happens when I apply the morph tool on my system that has a "ASUS X299 TUF Mark 1" motherboard. It happens when I am on bios version 1401. When I downgraded the bios to version 0802 the morph issue was fixed. Adobe please fix this. Thanks

Everything has latest updates and I tried reinstalling Premiere.

My hardware is:

- GTX 970

- ASUS X299 TUF Mark 1

- Intel Core i9-7960X

- Windows 10 Pro

- 32 GB RAM

- M.2 SSD PCI-E for OS drive

- HDD for Project Files

- SSD for Cache

- Nothing is overclocked

R Neil Haugen
Legend
August 23, 2018

This is a user to user forum. You've got a good bit of information to get to the engineers and the system for that is their new UserVoice system linked at the top of the Overview page of this forum.

File a report listing everything in your post please!

Neil

Everyone's mileage always varies ...
Participant
August 23, 2018

OK found it thanks!

juanmario
Participating Frequently
July 9, 2018

Hi.

When the Warp Stabilizer effect is applied to short clips, the RAM requirements are quite low, but the requirements for disk and RAM may increase, and performance problems begin.

If the effect is applied to long clips, for example 10 minutes, and depending on the content of the video, a phase analysis of the Warp Stabilizer effect may require approximately 10 KB of data per frame, or 20 KB per frame.

What should be done, we must segment the clip in short stretches, Ctrl + K, with this we get 2 advantages, the first one reduces the risk of an error, and the second, if we select 2 or more sections depending on the capacity of your team, accelerate the stabilization process since more segments are processed simultaneously.

They are recommendations, there can always be an extra inconvenience.

Participating Frequently
July 9, 2018

A 14core 64GB DDR4 11GB CUDA machine should handle a 40frame HD H264 clip in its sleep instead of shutting it down, shouldn’t it?

July 9, 2018

And on top of this.... my warp stabilizer was working just fine until April. There was an update somewhere (asus or adobe) and since then, it has the crashes.

July 6, 2018

OH JOY!! I reverted back to BIOS 0802 and tried the warp stabalizer. NO CRASHES!! I'll keep using it .... just to make sure. But I'll definitely pass this along to the engineer at Asus that's working my case. Thank you @Mauerfuchs_film 

July 6, 2018

Asus support has assigned an engineer to my case. Today he had me reinstall the latest BIOS, chipset driver and Intel Turbo Boost drivers. It didn't make any difference. My system is still crashing. I don't get a blue screen. Just crashes to a black screen and I have to manually hold the power button down to do a restart. I reported back to the engineer and now I'm waiting for his response. But I think I'll try that 0802 BIOS in the meantime and see if it helps my system.

Participating Frequently
July 8, 2018

@selenav87508386 I’m still running Bios 0802, because I’m afraid that updating to 1401 will mess up premiere again. Did you try with these changes of @daniePretorius already?

Glad i could help after all those misleading temporary successes that turned up in smoke short time later.

July 9, 2018

No I haven't made any other changes. I'm at 0802 and running stable. Figured I'd leave it there until Adobe has an update.

Grigor Poghosyan
Participating Frequently
July 4, 2018

It's seems like there is not enough RAM for that option on the other laptops, how big and large is the file you trying to stabilize ?

Participating Frequently
July 5, 2018

I have 64GB RAM with HD Clips and 4K Clips between 100MB or 8GB
Doesn't matter. It is crashing the board to black screen.
In CC2017 it works when i use the same clips.

I downgraded my BIOS to a version from before the ASUS Blackscreen reports showed up in the forums. (BIOS: 0802)I have a similar setup as DaniePretorius also with the same board, Processor, and Samsung M.2

contacted Asus Support and they say it’s an adobe or windows problem. And that its only bios related if the program is communicating directly with a bios related CPU configuration. Nobody has a clue what is causing that Problem. I also don’t wanna make changes now that it’s running stable.

Participating Frequently
July 3, 2018

I have the exact same problem!  Warp crashes in Premiere Pro CC2018 and turns off (hangs) PC in the "stabilizing" stage like clockwork!  Running latest drivers on all hardware, Windows 10, etc.

Hardware:

  • ASUS PRIME X299 DELUXE
  • Intel Core i9 7940X 3.1GHz (4.40GHz Turbo)
  • HyperX Furry 32GB (16GB x 2) DDR4 3466MHz Desktop Memory
  • ASUS ROG STRIX ADVANCED GTX 1080 GAMING 8GB GDDR5X Graphics
  • Card / 2560 CUDA Cores / 1835MHz Boost / 10010MHz 256-bit Memory
  • Samsung 850 EVO 250GB SSD 2.5" SATA 6Gbps 32 Layer 3D V-NAND Solid State Drive
  • Samsung 850 EVO 1TB SSD 2.5" SATA 6Gbps 32 Layer 3D V-NAND SSD
  • Samsung 960 EVO 1TB M.2 PCI-e 3.0 x 4 NVMe Solid State Drive (SSD) MZ-V6P512BW / Max Read : 3200 MB/sec / Max Write : 1900 MB/sec
  • EX3Thnderbolt card hooked up to Lacie 5Big TB 2 drive

Pulling my hair out because of the crashes of an expensive product on this brand new system above

Participating Frequently
July 7, 2018

Just to add, Adobe CC2018 crashed by PC completely to a black screen and "reset" by only keeping the power button in before. It crashed only in the "Stabilization" phase of Warp Stabilizer and not during the "Analyzing" phase.  I also learnt that by changing the following settings in the Warp settings, before the analyzing phase has completed, it did not crash:

Change "Result"/Method/Framing" to other values stopped the crash with my default BIOS settings but I needed the settings in Smooth Mode, Subspace Warp and Stablize, Crop, etc.

Hopefully this will assist an Adobe engineer to pinpoint the issue!

Motherboard: ASUS PRIME X299 DELUXE

BIOS Version: 1401

I then changed some settings in my BIOS and it worked!

Now Warp Stabilizer is working like a dream with the following settings in my BIOS(BIOS screenshots from phone).  Adobe take note to fix Premiere!

X.M.P-->Disabled

Note the BIOS version above.

I have changed the BCLK Frequency:DRAM Frequency Ratio to 100:133

All other settings on Auto

Note the CPU Core ration below:

I can share the rest of the settings as well if need be.  Note that no overclocking was taking place before or with current settings.

No crashes any longer...Warp Stabilization is working like a dream now!

Not sure why, but it works now after a lot of hours spent with settings, etc!

Adobe, please look into it and fix permanently.

Regards

Danie

July 7, 2018

@DaniePretorius That's great info!! Thank you so much for posting.

Participating Frequently
July 2, 2018

I downgraded the ASUS UEFI BIOS from 1401 to 0802, So far it works without any Problems in CC2018 it does everything

mikek72914389
Participant
June 28, 2018

I am having the same issue on my machine, but I think I solved the "Warp Stabilize" crashing. The crashing happens during the "Stabilizing" portion of Warp Stabilize effect. The "Analyze" part completes and then BOOM. Crash. Screens go black. Machine restarts but doesn't reboot. Once in a while I will get a "Whea_Uncorrectable_Error"message from Windows blue screen.

The problem started happening two days ago when I used the Asus EZ-Tune to overclock my machine. (Got 3,738 cb in Cinebench R15 when overclocked, btw :O) I also had XMP on. RAM was overclocked to 3600 Mhz.

The crashing stopped when:

1. I reverted back to older version of BIOS (1301)

2. Ran CPU at stock speeds

3. Ran RAM at stock speeds, XMP turned OFF in BIOS and motherboard (this is what really fixed it, I think)

4. Went to an older NVIDIA GPU driver.

I am going to try overclocking the CPU and RAM again, but manually this time, to see if the crashing persists and compare Asus overclock vs manual overclock with Warp Stabilize. Maybe it's bad RAM sticks? I will also update the GPU driver, since I don't think a GPU driver is an issue.

I'll post an update if I run into any other issues/ fixes.

MK

Participating Frequently
June 29, 2018

I was in Adobe support at least 5 times, no one could help. It worked for renders under 100 frames from time to tim, still it crashes on warp or morph in CC 2018.1 but CC 2017 works fine. It feels like it’s a driver or software problem. I was told my graphi card doesn’t work right... It can’t be, it passed every stress test... Asus X299 Problem? Possible, but CC2017 works like a beast. I just wanna bring my new projects back to CC 2017. Haven’t tried CC2018.0 again because the project is not supported. Any chance to migrate back with my new projects?

Participating Frequently
June 14, 2018

THANKS ADOBE. IT WORKED

A friendly support team worker solved it for me by checking the windows crash log and just set back the Nvidia driver to Version 23.21.13.8813 That worked perfectly. No crash so far.

June 17, 2018

Tech support had me roll back my NVidia driver and it did not help. Did you do anything else besides the driver rollback?

Participating Frequently
June 19, 2018

Had another crash.

My system got really slow and crashed at step 2 again.

Right now i switched back to the earlier version of Premiere 2018. It's slow but stable for now

Participating Frequently
June 14, 2018

Same Problem here.

brand new pc. Proved in hardcore stress tests. Collapsing to black screen, Memory Error at step 2 of warp stabilizer and sometime inbetween different tasks in Premiere Pro CC 2018.

also Intel i9 7940x

Asus Prime X299 Deluxe

64 Gb Ram in 4 slots 1.2V

Zotac Geforce 1080 ti Amp Core edition
Logitech Craft Keyboard via Dongle

Watercooling besilent loop

i thought i’d be prepared to handle warp stabilization now.

when will there be a fix. i love Premiere and I always protected it, so i switched to windows again, but now I feel like I need to simply switch the program after all these years. I don’t like final cut thoug. Please help. So many things collapsing On Mac and Windows since cc2018...

Thanks