Dolphin, the GameCube and Wii emulator - Forums

Full Version: Random Crashes...
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
I want to use the latest version, but can't due to random crashing in just about every game I've tried. On the latest stable 4.0.1 build I am still having this issue. I can't recall when but sometime post v3.0 or so, this problem has been cropping up. It happens in both GC and Wii games and it doesn't seem to matter what games I'm playing. It happens in all of them. I think somewhere in v3.0 it freezes and I have to exit and re-enter fullscreen to get it to going again (thought at some point it will decide to crash completely). v4.0+ It just crashes when the freeze occurs.

I've tried verious different graphics backends/audio back ends and no effect. Though OpenGL video mode works, but with slowdown in many of my games. I think it still crashes out. But had panic handlers disabled at the time, so can't say what the error was that caused it. DX11/09 both crash the same for me so it didn't matter which one it was. The games involved seem to be running well. Game performance doesn't seem to impact whether or not this crash occurs.

Error message that comes up randomly mid-game (no particular action causes it. It comes up whenever it feels like it)

DX11TongueSTextureEncoder::EncodeFailed in Src\PSTextureEncoder.cpp at line 1170: map staging buffer
(the particular game I was playing when this one came up was GoldenEye 007 NTSC for Wii)

After clicking ok on that error, then Dolphin will hard crash. This is the windows error info for it:

Problem Event Name: APPCRASH
Application Name: Dolphin.exe
Application Version: 0.0.0.0
Application Timestamp: 5263d8da
Fault Module Name: Dolphin.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 5263d8da
Exception Code: c0000005
Exception Offset: 00000000005a5300
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 191c
Additional Information 2: 191c4de7cc2ddf8cdc57c067da21016c
Additional Information 3: 8aa7
Additional Information 4: 8aa7cdf292cd74a55e55e24cac698f43


My computer hasn't changed much over the years except for the video card which was upgraded over the years.

My current build:

Motherboard: ASUS P6T (original, not the Second Edition or Deluxe that came out after)
CPU: Intel i7 965 Quad Core at 3.2GHz
RAM: 6GB (2GB per module) Corsair 1333 DDR3
Video Card: Nvidia GeForce GT 240
OS: Windows 7 x64


I have all the latest drivers. In fact just installed the latest Nvidia drivers tonight. No change in Dolphin behavior. I have a CPU/GPU temperature monitoring program and all temps are at safe levels. My rig has been stable since I built it and the other games I play on it run fine.

If I can't get this fixed I will have to start running really old versions of Dolphin to get around this, but really want to avoid that. I recall in old versions I had crash issues when switching to/from fullscreen midgame. But 3.0+ seemed to have fixed that. That will be one issue I'll encounter again if I have to go to a pre 3.0 release. Sad
Check windows update and visual c++ latest version.
As I have said. My drivers and Windows is up to date.
How about DirectX..is that updated?
Yeah, he said that was updated also.
Unfortunately, there goes the easy fix. An exception code of c0000005 signifies a physical problem. Since your system isn't over clocked, there could be a problem with your RAM being bad. You need to test each stick for errors
I've been doing lightmap rendering and other heavy duty work in 3DS Max for a mapping project I'm doing for BF1942. If I had bad ram, I'd be getting blue screens or crashes when attempting that. I don't think my ram is bad.

My DirectX is updated. Perhaps it's my video card. The specs show it supports DirectX 10.1, but doesn't appear to have full support for DX11. I've been wanting to upgrade the video card anyways. Perhaps I'll strike it lucky and find out it was my video card. Tongue

As a matter of fact I think I didn't have the freezing/crash issues with Dolphin when I was on my previous video card. I got worse performance due to the card being older, but don't recall having freezing issues. Tongue

Another thing about the video card. Right now it's on the second PCIE16x slot instead of the first one. This is due to the PCIE 1x slot being right in between the two slots. (bad layout design if you ask me. Tongue ) My video card takes up two slot spaces and I only have one PCI-E 1x slot. Which I have a TV tuner using. So I had to move it to the second slot. I don't know if having the video card on a different PCIE slot would cause issues but it's something to think about. Tongue

EDIT: Did a check with a ram test program and found no errors.

I can see if I can find a program that can test video ram. That's about the only thing I can think of that could be the issue.

EDIT2: Did a video ram test. No errors found there either...
So all the RAM is good.....hmmmmmm......
Being on a different slot should not affect anything. Being on a lower PCI slot only limits the maximum bandwidth for data transfer. For example, if you have a PCI 3 in a PCI 1, then you're limited to the data transfer speeds of PCI 1.

Is your old card still around to try out some testing? Because the code references some sort of physical error, and since you aren't overclocked, and its not the RAM, its hiding somewhere.
Have you run the CPU and GPU through torture tests like Intel Burn Test, Prime95 and Furmark? Of course monitor the temps as they are being run. Although if Dolphin crashes at startup, it likely isnt a stability thing.
I'll run a pre 3.0 Dolphin and see if it runs. If an old version of Dolphin runs the game just fine I would find it hard to believe it's a physical problem with my hardware.
Version 3.0 and older have other issues that causes it to crash, so I don't know how well it will be able to compare....
Pages: 1 2 3