Sudden Screen Tearing after Last Windows Update

Any issues, problems or troubleshooting topics related to the Prepar3D client application.
Post Reply
Doylie22
Posts: 39
Joined: Tue Dec 01, 2015 10:54 am

Sudden Screen Tearing after Last Windows Update

Post by Doylie22 »

Hi All,

I'm having a very weird issue where after the last *Forced* Windows 10 update I now am getting screen tearing at high altitudes. I've noticed it seems to be when my FPS gets above a certain higher threshold away from the departure airport. It also is only happening in the cockpit. I use chaseplane but I've tried with and without chaseplane and same issue persists.

After some research, I tried to turn off the full screen optimizations in the menu which removed the screen tearing but was causing me to CTD sometimes with no report and even one BSOD with a memory error. Turn them back on and the tearing returns but the sim is stable.

I don't think it's the monitor and I'm really trying to avoid V-Sync or Limiting FPS as I never had an issue before the latest Windows update. Any ideas?

Computer Specs:

ASUS 370-A Prime Mobo
32GB RAM
Intel i7-8700K at base clock
EV3A Geforce GTX 1080TI

Nvidia Driver 431.60
Windows 10 Build 1903 18362.295


Last crash error report:
Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad
Faulting module name: D3D10Warp.dll, version: 10.0.18362.1, time stamp: 0xb8cedf06
Exception code: 0xc0000005
Fault offset: 0x00000000000abd80
Faulting process id: 0x2e54
Faulting application start time: 0x01d556ccded87192
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\D3D10Warp.dll
Report Id: e473ad29-6d61-4c9c-abec-62e8581fbe18
Faulting package full name:
Faulting package-relative application ID:
Doylie22
Posts: 39
Joined: Tue Dec 01, 2015 10:54 am

Re: Sudden Screen Tearing after Last Windows Update

Post by Doylie22 »

Update, V-Sync and Triple Buffering doesn't help. The problem gets worse when P3D is not the active window as well.
User avatar
JorgenSA
Posts: 6010
Joined: Sun Mar 11, 2018 7:17 am
Location: 5 NM ENE of EDXF

Re: Sudden Screen Tearing after Last Windows Update

Post by JorgenSA »

By googling this error, I found multiple answers, here's one:

"D3D10Warp.dll errors could indicate a registry problem, dll file corruption and in lesser cases, a malware issue – which can be solved by scanning with an anti-malware application. D3D10Warp.dll is also known as the Direct3D 10 Rasterizer, is mostly used by games for graphics operations".

Here's a link to a possible solution:

https://appuals.com/fix-corrupted-d3d10warp-dll-file/

What I did to find all this was googling "d3d10warp.dll error"

Jorgen
System: i5-12600K@4.9 GHz, ASUS ROG STRIX Z690-I motherboard, 32 GB 4800 MHz DDR5 RAM, Gainward RTX 3060 w/ 12 GB DDR6 VRAM, Windows 10 Pro.

All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
Doylie22
Posts: 39
Joined: Tue Dec 01, 2015 10:54 am

Re: Sudden Screen Tearing after Last Windows Update

Post by Doylie22 »

I saw that same website before asking on here and the malware scan turned out without any results. I suppose I could try and reinstall the client? I’m really trying to avoid a full reinstall as that would literally take a month to do. Was hoping someone from LM has a quick fix I hadn’t tried yet.
User avatar
JorgenSA
Posts: 6010
Joined: Sun Mar 11, 2018 7:17 am
Location: 5 NM ENE of EDXF

Re: Sudden Screen Tearing after Last Windows Update

Post by JorgenSA »

Since the file in question is a Windows System file (an Application Extension, to be exact), I seriously doubt that a P3D client reinstall will fix this issue.

The first thing I personally would try is rerunning Windows Update. If that does not fix the issue, then go with the methods outlined in the link I posted.

Jorgen
System: i5-12600K@4.9 GHz, ASUS ROG STRIX Z690-I motherboard, 32 GB 4800 MHz DDR5 RAM, Gainward RTX 3060 w/ 12 GB DDR6 VRAM, Windows 10 Pro.

All views and opinions expressed here are entirely my own. I am not a Lockheed-Martin employee.
Post Reply