Personal computing discussed
Moderators: renee, morphine, SecretSquirrel
Aphasia wrote:I wonder if there is any more hidden differences from the patch-notes between 14.7 RC and RC3. I've had problems with both bluescreens with the rc and the Mantle hangs is still there from the 14.4.
Put in bug reports about it, and also reports for the BF4 CTE environment since the Mantle hang is obviously some form of game dependent thing involved.
Weird thing, during a Mantle hang today, it seemed to have really borked my comp, the hang actually corrupted my windows install so I had to do a system repair. The shell32 among others.
sschaem wrote:And please, remove the Trojan "Gaming evolved" from your driver.. its an HORROR that I should not be forced to install.
Savyg wrote:That would be very unlikely to be related to any graphics API at all.
Aphasia wrote:Which part's, the hangs, which are verified to be Mantle since it's closer to the metal and only happens during Mantle usage, or the corruption of the shell.
Potentially, any really hard hang with files open can have a chance to corrupt things if stuff ends badly, say a hard reset during a cache flushing to disk, etc.
So in some part it was because it hanged at that instant, but I doubt it was the graphics API that caused the corruption, rather the hang at that particular instant during which something else happened.
Torn Writes
In NTFS the file system overwrites metadata and data structures during a modify operation. During this modify operation data is read off the disk and then new data is written on top of the old data, becoming the new data. Torn writes occur when this process can’t complete fully. Think about what could happen if a power failure occurred during the write operation.
Aphasia wrote:you do realize that defrag is automatically disabled for SSD's running under windows, right...
Aphasia wrote:Still running on Win 7 here though. My thought is that the hang coincided with the windows updates that came out, so the updates were done during playing, but the hung came before reboot. Oh well, a reboot and repair back to last restore point and another reboot and the computer works fine again. I'm surprised how well the system protection actually are when you need em. I remember good old XP basically requiring a reformat if something jacked up really badly with it, not to mention the older OS'es like 2000, NT4 and NT3.51.
LoneWolf15 wrote:I've had issues since upgrading recently -my R9 280X cards in crossfire flicker, especially in 2D.
I've tried 14.4 and now 14.7RC3, no fixes. Reloaded Windows 7 from scratch in the event it was a driver issue; didn't fix it.
Just opened a support case with XFX in the event it's a BIOS issue.
Savyg wrote:sschaem wrote:And please, remove the Trojan "Gaming evolved" from your driver.. its an HORROR that I should not be forced to install.
Here's a hint:
You're not forced to install it.
You're not alone in thinking it shouldn't be in the express option, though.
Warsam71 wrote:Savyg wrote:sschaem wrote:And please, remove the Trojan "Gaming evolved" from your driver.. its an HORROR that I should not be forced to install.
Here's a hint:
You're not forced to install it.
You're not alone in thinking it shouldn't be in the express option, though.
Thank you both for your feedback. I will look into this for you...
JustAnEngineer wrote:I had crashes while watching videos in Firefox with my Radeon R9-290 a month and a half ago. The set of updates before this one seems to have fixed it for me.
Warsam71 wrote:Hello everyone,
I'll be more than happy to look into the atikmpag and atikdag files for you. It will take me a few days or so since I may have to ask multiple teams (just setting your expectations )...either way, I will keep you posted. And please, feel free to send me a PM or post here again if you don't hear from me by mid next week (I hope it's okay).
SuperSpy wrote:That sounds like a frightening new type of exploit in the works, if the codec is buggy enough to cause the driver to crash, there's more than a passing chance a properly-malformed video could become a remote-execution exploit, being that it's in kernel land (hence the BSOD) that would allow complete access to the computer bypassing all security.
Does Windows support the NX bit in kernel mode code?