So here I go, finally posting about this issue I've been experiencing for a year now.
Short : Whenever I play a game (whatever it is, being GC or Wii, tried over 20 different games) it works (well, Soul Calibur II wouldn't even boot but it's been fixed with 4.02) for a duration that goes from 10 to 30 minutes most of the time (but sometimes more than an hour) and then Dolphin freezes and I get that stupid message "Dolphin has stopped working". Of course, each time that happens, it's as if I had shutdown the GC or Wii without saving, so I lose everything, which, you will certainly agree, isn't really nice.
Now more information about my software and harware :
I've been running Dolphin 3.0, 3.5, 4.0, 4.01, 4.02 (x64) (and the latest development version never fixed the problem) on Windows 7 x64, Windows 8 x64 and now Windows 8.1 x64.
Some pretty well-known games I've been playing : Zelda The Wind Waker, Mario Kart : Double-Dash, Super Smash Bros Melee, Super Smash Bros Brawl, Fire Emblem : Path of Radiance, Fire Emblem : Radiant Dawn, Soul Calibur II, and way more.
As for my specs, I've gotten a new rig during that period so here are both builds (If you need more details, feel free to ask) :
Intel Core I7 950 (tried at stock (3.06 Ghz) and at 4.2 Ghz) - 12 GB DDR3 (same here, 1600 Mhz stock - also tried at 18... Mhz) - Nvidia GeForce GTX 570 (and again, tried at stock and OC'd, can't remember how much) - Samsung Spinpoint F3 1 TB - Samsung SSD 830 256 GB.
Intel Core I7 4770K (@stock for now) - 16 GB DDR3 (same) - Intel HD 4600 (for now, AMD R9 290 joining the team as soon as custom models are released) - Seagate Barracuda 7200.14 1TB - Samsung SSD 840 120 GB.
As for the settings, I've tried many many settings on each build I've been using. I've tried at least playing with the defaults and putting everything to the minimum with each build.
Thanks in advance.
Oh, I forgot, yes, Windows is always up to date as well as the drivers, DirectX and Visual C++.
EDIT : So I just quickly went through this forum (which I should have done before posting, I know...) and it seems a lot of people are getting this error. Looks it would help people if I posted the complete Windows error report, which I will do tomorrow when I get up. I've also found someone who said it was an option in the BIOS that caused the problem for him, so I'll take a look there too and report back here.
Short : Whenever I play a game (whatever it is, being GC or Wii, tried over 20 different games) it works (well, Soul Calibur II wouldn't even boot but it's been fixed with 4.02) for a duration that goes from 10 to 30 minutes most of the time (but sometimes more than an hour) and then Dolphin freezes and I get that stupid message "Dolphin has stopped working". Of course, each time that happens, it's as if I had shutdown the GC or Wii without saving, so I lose everything, which, you will certainly agree, isn't really nice.
Now more information about my software and harware :
I've been running Dolphin 3.0, 3.5, 4.0, 4.01, 4.02 (x64) (and the latest development version never fixed the problem) on Windows 7 x64, Windows 8 x64 and now Windows 8.1 x64.
Some pretty well-known games I've been playing : Zelda The Wind Waker, Mario Kart : Double-Dash, Super Smash Bros Melee, Super Smash Bros Brawl, Fire Emblem : Path of Radiance, Fire Emblem : Radiant Dawn, Soul Calibur II, and way more.
As for my specs, I've gotten a new rig during that period so here are both builds (If you need more details, feel free to ask) :
Intel Core I7 950 (tried at stock (3.06 Ghz) and at 4.2 Ghz) - 12 GB DDR3 (same here, 1600 Mhz stock - also tried at 18... Mhz) - Nvidia GeForce GTX 570 (and again, tried at stock and OC'd, can't remember how much) - Samsung Spinpoint F3 1 TB - Samsung SSD 830 256 GB.
Intel Core I7 4770K (@stock for now) - 16 GB DDR3 (same) - Intel HD 4600 (for now, AMD R9 290 joining the team as soon as custom models are released) - Seagate Barracuda 7200.14 1TB - Samsung SSD 840 120 GB.
As for the settings, I've tried many many settings on each build I've been using. I've tried at least playing with the defaults and putting everything to the minimum with each build.
Thanks in advance.
Oh, I forgot, yes, Windows is always up to date as well as the drivers, DirectX and Visual C++.
EDIT : So I just quickly went through this forum (which I should have done before posting, I know...) and it seems a lot of people are getting this error. Looks it would help people if I posted the complete Windows error report, which I will do tomorrow when I get up. I've also found someone who said it was an option in the BIOS that caused the problem for him, so I'll take a look there too and report back here.