Huh. Okay.
So, user has program working fine. Updates drivers. Starts getting BSODs right after they update their drivers. Drivers can cause BSODs because they have kernel level access. They're not getting EFB crashes. Their system is fucking crashing. Ishiiruka doesn't cause BSODs.
I think I dislike incredibly stupid users more than stupid drivers. Damn.
EDIT:
I don't hate on AMD because I don't like them. I hate on them because I've SEEN THEIR STUFF BE REALLY BROKEN. You might not. You're an end user. You probably don't follow times when we've seen AMD break in spectacular ways in drivers.
(03-27-2016, 02:42 PM)Panchito Wrote: [ -> ]There is no need to do that, the EFB related crash was introduced in one of the last two or three Ishiiruka revisions, a couple of people and me reported the bug a few pages back in this thread. Roll back a few Ishiiruka revisions and keep the latest 16.3 drivers, they work beautifully. Alternatively just don't use the DX12 backend until Tino fixes this.
I usually don't use DX12 as post processing glitches easy in it anyway. I was just making sure it was known because from what I read originally, it was that it was on NVidia cards only unless I was mistaken.
The freezing was a known thing. The BSOD is on your end because your drivers are doing something Very Silly.
(03-27-2016, 02:48 PM)helios747 Wrote: [ -> ]Huh. Okay.
So, user has program working fine. Updates drivers. Starts getting BSODs right after they update their drivers. Drivers can cause BSODs because they have kernel level access. They're not getting EFB crashes. Their system is fucking crashing. Ishiiruka doesn't cause BSODs.
Actually it went like this>
Updated Dolphin, started getting BSODs>Downgraded drivers for another reason>Coincidentally fixed the problem>Refreshed Windows>installed my already downloaded drivers>notice the problem is still there with the latest build and latest drivers.
(03-27-2016, 02:48 PM)helios747 Wrote: [ -> ]I think I dislike incredibly stupid users more than stupid drivers. Damn.
EDIT:
I don't hate on AMD because I don't like them. I hate on them because I've SEEN THEIR STUFF BE REALLY BROKEN. You might not. You're an end user. You probably don't follow times when we've seen AMD break in spectacular ways in drivers.
I don't recommend saying things like this because it usually causes arguments do to people misunderstanding each other as text has no emotion. Since text has no emotion, the reader will interpret the text based on the emotion set in ones head as the text is processed by the brain.
(03-27-2016, 02:57 PM)helios747 Wrote: [ -> ]The freezing was a known thing. The BSOD is on your end because your drivers are doing something Very Silly.
I understand this, I was just saying what I said before mostly because no one replied. Too be honest this is not always the case, a lot of times BSODs can be caused by either the software or the drivers. Look at this generation games for example, a lot of them have been causing issues like this on GPUs across the board.
-----
(03-18-2016, 02:42 AM)TailsTheGamer Wrote: [ -> ]On EFB Copy locks up my computer with DX12 (funny enough it's the infamous monitor shutoff bug with R9 285s/R9 380s that's unrelated to Dolphin and when it's not it's a BSOD reporting page fault in non page area atikmdag.sys.) I'm on an R9 285.
Specifically in Sunshine right when you hit "Start" on the save selection screen. Works fine in DX11.
(03-18-2016, 07:52 AM)TailsTheGamer Wrote: [ -> ]ok so I've been having trouble with the crimson drivers anyway, (R9 285s and 380s have been having bad PC Crashes), so I went all the way back to 15.7.1 drivers and the problem went away. Must be related to the Crimson driver issue I was having. I was on 16.3.
I would also like to point out that I already said it could be a driver issue.^
I only repeated what I said because no one said anything. Tino is busy and sometimes misses bug reports or help questions, it happened to me before.
Dont worry already looking at your issue, sorry for the delay response but im not feeling well this weekend.
Quote:I don't recommend saying things like this because it usually causes arguments do to people misunderstanding each other as text has no emotion. Since text has no emotion, the reader will interpret the text based on the emotion set in ones head as the text is processed by the brain.
Well, when you accuse someone of lying "again" and hating for no reason…
(03-27-2016, 04:35 PM)TailsTheGamer Wrote: [ -> ]I understand this, I was just saying what I said before mostly because no one replied. Too be honest this is not always the case, a lot of times BSODs can be caused by either the software or the drivers. Look at this generation games for example, a lot of them have been causing issues like this on GPUs across the board.
Userspace software can't make the whole system BSOD or kernel panic… that's only possible with low-level software, for example at the kernel level. And that's precisely where the drivers are.
Although games can't cause BSODs by themselves, if you have buggy drivers, they might cause BSODs
indirectly when they try to do something which triggers a bug in the drivers.
For the record, I was mostly talking to Panchito, TailsTheGamer was already aware of why the crashes were happening, leolam.
(03-27-2016, 11:43 PM)Tino Wrote: [ -> ]Dont worry already looking at your issue, sorry for the delay response but im not feeling well this weekend.
Damnit, Tino, what are you doing in the forums, then? Get into bed, have some hot milk with honey and get better
(03-26-2016, 03:28 PM)Panchito Wrote: [ -> ]That is a really old revision, why don't you try the latest? You can find it here:
https://forums.dolphin-emu.org/Thread-unofficial-ishiiruka-dolphin-custom-version?pid=297809#pid297809
Â
I deleted that old version from my system. Â I downloaded the new version. The problem now, the Dolphin icon image which is the executable is not opening the file when I click it? (other words doesn't execute) So I can't open the file. I've attached image below. Â Maybe you or someone here can tell me what I'm doing wrong? Â Thanks.
[attachment=14498]
**UPDATE**
Tried opening it with WinRAR and received the following messages:
Can't start because MSVCP140.dll is missing
Can't start because VCRUNTIME140.dll is missing
Did your anti-virus nab the file or something?