Question / Help OBS Crash with message Error: Texture->Map failed: 0x887a0005 0x887a0005 while playing The Witcher 3

[TheGwardian]

OBS Crash with message Error: Texture->Map failed: 0x887a0005 0x887a0005 while playing The Witcher 3.

Full error message is:
"Texture-> Map Failed: 0x887a0005 0x887a0005. Your video card disappeared from the system. Please check for possible hardware / driver issues. This error can also occur if you have enabled opencl in x264 custom settings."

Was playing The Witcher 3 today and had this occur. Am using the latest NVIDIA drivers. System specs below.

First time I've encountered this particular issue.

At the time, I was using Open Broadcaster Software (OBS) to record gameplay locally to one of my drives. For quality, I set the bitrate to 12,000 kb/s because I am not using OBS to stream. I am using it to record locally.

The Witcher is installed on my SSD. The only other programs I had open at the time were Skype and Steam.

I have also attached the log file to this post, below.

Thank you.

**Specs:**

PC:

* Windows 8.1 Pro 64-bit
* Rosewill THOR V2 Case
* EVGA GeForce GTX 970 FTW Edition GPU
* Thermaltake NiC C5 CPU Cooler
* Rosewill SSD/HDD Mountaing Kit with 60mm Fan
* CORSAIR Vengeance 16GB RAM
* CORSAIR HX850i 850W Power Supply
* Intel i7-4790k CPU
* MSI Z97-Gaming 7 Motherboard
* Samsung 840 EVO 120GB SSD
* Western Digital Blue 1TB Drive x 3

Audio:

* Blue Yeti Mic
* Rode PSA1 Mic Boom Arm
* Audio-Technica ATH-M30 Headphones

Networking:

* Cisco Linksys EA4500
* Motorola SURFBoard SB6121
* CAT 6 Ethernet Cables

Peripherals & Misc:

* PS4 Controller
* Razer Naga 2014
* ASUS VS278Q-P 27" 1ms Monitor x 2
* HP 23" S2331 x1
* Logitech C920 Webcam

 

[dping]

OBS Crash with message Error: Texture->Map failed: 0x887a0005 0x887a0005 while playing The Witcher 3.

Full error message is:
"Texture-> Map Failed: 0x887a0005 0x887a0005. Your video card disappeared from the system. Please check for possible hardware / driver issues. This error can also occur if you have enabled opencl in x264 custom settings."

Was playing The Witcher 3 today and had this occur. Am using the latest NVIDIA drivers. System specs below.

First time I've encountered this particular issue.

At the time, I was using Open Broadcaster Software (OBS) to record gameplay locally to one of my drives. For quality, I set the bitrate to 12,000 kb/s because I am not using OBS to stream. I am using it to record locally.

The Witcher is installed on my SSD. The only other programs I had open at the time were Skype and Steam.

I have also attached the log file to this post, below.

Thank you.

**Specs:**

PC:

* Windows 8.1 Pro 64-bit
* Rosewill THOR V2 Case
* EVGA GeForce GTX 970 FTW Edition GPU
* Thermaltake NiC C5 CPU Cooler
* Rosewill SSD/HDD Mountaing Kit with 60mm Fan
* CORSAIR Vengeance 16GB RAM
* CORSAIR HX850i 850W Power Supply
* Intel i7-4790k CPU
* MSI Z97-Gaming 7 Motherboard
* Samsung 840 EVO 120GB SSD
* Western Digital Blue 1TB Drive x 3

Audio:

* Blue Yeti Mic
* Rode PSA1 Mic Boom Arm
* Audio-Technica ATH-M30 Headphones

Networking:

* Cisco Linksys EA4500
* Motorola SURFBoard SB6121
* CAT 6 Ethernet Cables

Peripherals & Misc:

* PS4 Controller
* Razer Naga 2014
* ASUS VS278Q-P 27" 1ms Monitor x 2
* HP 23" S2331 x1
* Logitech C920 Webcam

try to use anticheat hook in the game capture, often new games need this.

 

[TheGwardian]

try to use anticheat hook in the game capture, often new games need this.

Just tried it. Didn't work. Same error, same crash.

 

[dping]

Just tried it. Didn't work. Same error, same crash.

ok, so undo that change for now. try adding your game as a global source and also set your scene prior to switching to the game might help as well. lastly, after you do this, if its still not working post a fresh OBS log.

 

[R1CH]

Try underclocking your GPU also, Witcher 3 is quite stressful and in combination with OBS may be overloading the GPU.

 

[Aviri]

Same exact thing has been happening to me recently, not even sure how to fix it... Although, I did get a good 1 hour of streaming it before it happened again.

I've posted OBS logs as well as two crash dump files (logs are attatched).

I've also posted a picture of the error window below.

Links to the dump files (will not let me upload here - 1MB Max):
https://www.dropbox.com/s/52rq12g4vo017if/OBSCrashDump2015-05-20_1.dmp?dl=0
https://www.dropbox.com/s/frsx1mtrztyw709/OBSCrashDump2015-05-21_1.dmp?dl=0

Thanks for any possible solution!

Specs:
Motherboard: Asus M5A97

CPU: AMD FX 8350 Eight-Core (4.0 GHz)

GPU: EVGA GTX 980 SC (4GB)

RAM: Corsair Vengeance 16GB

OS: Windows 8.1

SSD: Corsair Force GT 120GB

Case: Rosewill Thor V2 (White)

Peripherals
Monitors: BenQ XL2430T, and Samsung 245BW

Headphones + Mic: Sennheiser G4ME ONE

Keyboard: Razer BlackWidow Chroma

Mouse: Razer Taipan

Mousepad: Corsair Gaming

 

[DanteDarkly]

Just ran into the same error myself 3 times in the last 10/15 minutes
https://gist.github.com/6e3ee6804f8cbff10323
Not sure what other information I might be able to get that would assist :/

 

[D2ultima]

Is everybody using vSync and getting 60fps or above here? If not, try lowering some settings until you can for the most part hit 60fps while streaming, so that vsync is working and your GPUs aren't being overstressed.

Also, question. When does it crash? Does it happen after an unintensive scene? Has anyone without a nVidia maxwell GPU gotten this error? If Kepler GPUs do not get the error and GPUs like the Titan X (because I fixed PCGamer's stream the other day and they ended up with no problems for a long time, and they were using that) do not get the error due to their sheer rendering power, then I might know what the bug is.

For those who don't know, Maxwell GPUs = 900 series and the 750/750Ti and Kepler = 600 and 700 series (excepting 750/750Ti), and most 800M series.

 

[Aviri]

I was reliefed to hear that others were getting the same problem, and maybe it was just a driver error, but maybe all of our GPU's are getting overstressed. :'(

Going to stream it some more tonight, I was running it on ultra with vSync off, so I'll turn it on and see if it happens again. If it does happen again, I'll lower some other settings and hope the best from there. Also, I'll monitor the GPU itself to see if it gets to hot, etc, etc... Will update later tonight.

 

[FitzesLP]

Hey there, i got exact the same error today during capturing GTA V with my new GTX 960. I didnt change the ingame settings with the new card.

Here is the last logfile: https://gist.github.com/8ab07acbf193c997e72c

 

[Aviri]

Is everybody using vSync and getting 60fps or above here? If not, try lowering some settings until you can for the most part hit 60fps while streaming, so that vsync is working and your GPUs aren't being overstressed.

Also, question. When does it crash? Does it happen after an unintensive scene? Has anyone without a nVidia maxwell GPU gotten this error? If Kepler GPUs do not get the error and GPUs like the Titan X (because I fixed PCGamer's stream the other day and they ended up with no problems for a long time, and they were using that) do not get the error due to their sheer rendering power, then I might know what the bug is.

For those who don't know, Maxwell GPUs = 900 series and the 750/750Ti and Kepler = 600 and 700 series (excepting 750/750Ti), and most 800M series.

The crash can come at anytime, I haven't been able to pin point it, but I have had instances to where it crashes within 10 seconds of loading the game and walking around, hitting the action button on something like a torch on a wall, or simply just ridding Roach (Witcher's horse) around...

After the crash happens, either my computer completely froze, and I had to force restart it... Or it froze for a while (1 min or so), OBS's stream preview goes grey, the error I posted above appears, and once you press Ok it closes OBS and makes The Witcher 3 greyed out as well as unplayable. Also a thing to note, before you press Ok and OBS closes, viewers see a frozen picture of where the game crashed and can hear live audio (mostly complaints) Kappa.

It looks like just Maxwell cards are expierencing this crash, but could also be Kepler too, just no that owns one has posted. Hopefully they are fortunate enough to not expierence it though...

UPDATE: I've gotten a good amount of streaming in today, about 3-4 hours worth of The Witcher. Maybe for the first 30 minutes I was having the same exact issue even after turning vSync back on, so I decided to turn the graphics to high instead of ultra. That seemed to work and the crash did not appear for the two and a half hours that I remained streaming for. After vSync and changing to high I was getting around 60 frames/second so D2iltima may be correct that it is putting stress on the GPU, I'll update more if it appears again. I've also attatched my most recent log if it helps anyone.

I also had GPU-Z running while the crash happened (no PC restart) and after playing the game without the crash for 2+ hours. I set it so it shows the max reading of each sensor throughout the gameplay/crash.

This just shows that the GPU is getting pounded by this game while streaming. :'(
Let me know what you guys think about this.

GPU SPECS:



Also, thank you D2 for helping, I really appreciate it as this is quite an annoying problem.

 

[D2ultima]

Okay. To everyone who is getting crashing errors, please try this:

Overvolt your GPUs by 100mV or 0.1v, and set your TDP target to *WELL* over 100%. Try 200% if you can.

Please report back and let me know if it fixes your errors. Also let me know if Vsync (and making sure you get 60fps WITH excess GPU power) fixes the issue(s).

*sigh* having to fix maxwell's bloody voltage issues AGAIN I swear to god nVidia... *grumbles off into distance then goes to sleep for the night aka morning*

 

[Aviri]

Looks like all is still running well, did a 3 hour stream tonight which had no crashes. The only thing I find concerning, is that my GPU is being loaded at 98% in nearly all the categories while ingame. Cutscenes and such it drops down to around 14%. The cards temperature did not reach over 75 C, so I wasn't worried about it that much. Please let me know if the card is meant to handle 98% usage over such great times, I just dropped a good $600 on it, it'd be a nightmare if it were to get damaged.

This time around I did overvolt my GPU, and set the TDP, both as much as EVGA's PrecisionX would allow me...

• +87mV
• +24% Power Target
• No increase in GPU Clock or Memory Clock.

I have yet to try and go back to ultra settings, but I feel like it would only make things worse as my GPU is almost maxed at the high setting.

Anyway, again, thanks for the help D2ultima! You're the best!

 

[D2ultima]

Please let me know if the card is meant to handle 98% usage over such great times, I just dropped a good $600 on it, it'd be a nightmare if it were to get damaged.

Anyway, again, thanks for the help D2ultima! You're the best!

It is, don't worry.

I know I am ;). You're welcome though!

 

[StrangeLuv]

Okay. To everyone who is getting crashing errors, please try this:

Overvolt your GPUs by 100mV or 0.1v, and set your TDP target to *WELL* over 100%. Try 200% if you can.

Please report back and let me know if it fixes your errors. Also let me know if Vsync (and making sure you get 60fps WITH excess GPU power) fixes the issue(s).

*sigh* having to fix maxwell's bloody voltage issues AGAIN I swear to god nVidia... *grumbles off into distance then goes to sleep for the night aka morning*

I would love to try this and see if it works as a solution. However, I am a noob when it comes to these things. Could someone give me some quick steps for how to 'overvolt' my gpu and set a tdp target?

 

[Aviri]

A simple YouTube, or Google search of your GPU with overlock at the end of it should show you. But keep in mind, you aren't really overclocking, just over volting. Usually most overvolt + increase the TDP when overclocking

 

[D2ultima]

I would love to try this and see if it works as a solution. However, I am a noob when it comes to these things. Could someone give me some quick steps for how to 'overvolt' my gpu and set a tdp target?

Download nVidia Inspector.
Run nVidia Inspector.
Click "show overclocking" button at bottom right.
WAIT for it to "load" the current clocks (when "Current Clock" shows numbers for the GPU clock and Est. Max, you're ready).
Raise slider for "Power and Temperature Target" as high as it'll go.
Raise slider for "Voltage Offset" by about 100.0 mV. Hit "Apply Clocks & Voltage" at the bottom right.
Close nVidia Inspector.
Run game and see if it works.

When finished, repeat steps again, and instead of adjusting sliders, simply hit "Apply Defaults" and then "Apply Clocks & Voltage" and you're on your merry way.

Do *NOT* adjust the base clock or memory clock sliders for the experiment.

 

[dping]

Download nVidia Inspector.
Run nVidia Inspector.
Click "show overclocking" button at bottom right.
WAIT for it to "load" the current clocks (when "Current Clock" shows numbers for the GPU clock and Est. Max, you're ready).
Raise slider for "Power and Temperature Target" as high as it'll go.
Raise slider for "Voltage Offset" by about 100.0 mV. Hit "Apply Clocks & Voltage" at the bottom right.
Close nVidia Inspector.
Run game and see if it works.

When finished, repeat steps again, and instead of adjusting sliders, simply hit "Apply Defaults" and then "Apply Clocks & Voltage" and you're on your merry way.

Do *NOT* adjust the base clock or memory clock sliders for the experiment.

All, please take the above steps with caution because depending on the GPU and possibly being already overvolted, this might not have the desired affect and will also raise temps. please do a thorough stress test to ensure stability.

One I recommend is:
OCCT (GPU test) - enable check and run for no less than 5 minutes prior to changing anything.

* If temps are not to high and not throttling and you get errors in OCCT (GPU test), then i would consider what @D2ultima said
* If temps are are high, and throttling and getting errors in OCCT (GPU test), I would actually underclock (but leave voltages) your card slightly

TL;DR, not everyone needs to overvolt their card; this will not work for everyone

 

[Xacius]

UPDATE: Been pretty active on my stream this week. Not one crash. Lock your GPU's vcore and clock speed. I used EVGA Precision's K-Boost to find stable settings. I've tested using both the 0.655 beta and the 0.12 Multiplatform.

Old:
I've been getting this error for the past year on multiple builds and OS's. It happens on the Multiplatform, and the x32 and x64 normal betas.

Disabling the in-obs video preview helped reduce the crash frequency, but it still happened regularly every couple of hours, at least once per every 6 hours of streaming.

The following seems to have fixed the problem:

I locked my GPU's voltage and clock speed.

Out of everything I've tried, this seems to have fixed the problem completely (at least on the 0.655 x64 beta). I'll post back later this week after testing some more.


specs:
Intel i7 4790K at 4.5GHz, 1.235v
2x 8GB DDR3: G.Skill TridentX CL10 2400MHz
Samsung 830 Series 256GB SSD
EVGA GTX 970 04G-P4-2978-KR: locked at 1417MHz and 1.250v
ASUS VS-238 x3 (1080p)
Windows 10 Professional x64

 

[Dianddra]

I was having this issue as well and disabling the preview window seems to have fixed it for me (knock on wood...err I mean bytes)
I am using windows 10 and an asus strix gtx 970 card with obs and this was occuring when I would play skyrim special edition and only this game and nothing else would cause it.