Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun.
As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.or read our to learn how to use this site. Well.you don't need Who Crashed to recognize the letters 'ATI' in the Caused By Driver caption. ATI makes graphics chipsets, so it's obviously the ATI driver which should be the first suspect, IMO.I would uninstall all ATI software/drivers (including CCC), using Add/Remove Programs AND Device Manager.then reboot and reinstall the ATI package.If that doesn't resolve it.that would be the time to try to dig deeper, IMO.LouisThank you for your respond Louis!After I realized it was related to the GFX card (googled the atikmdag.sys error) I tried updating to the newest drivers from the official site. It stopped 90% of the crashes. If I start a game or anything that takes up a lot of CPU, it will still crash (Didn't do this a month ago)I'll try to remove everything ATI related, and then re-install the newest updates as you suggest, and will tell you how it went.
Basic usage Make sure that Steam is running. Place the targa image to be converted inside the SteamApps/common/gamefolder/materialsrc/ folder. If necessary, write a text (.txt) file containing a set of Vtex compile parameters. The Vtex executable ( Vtex.exe) is located in the.
Your mention of 'cleaning the Registry' brings bad thoughts to mind. I hope that you are not using a registry cleaner/optimizer application.The registry doesn't need 'cleaning'.that's just hype promoted by those who develop 'registry cleaners'.-See commnets by quietman 7 re registry cleaners.at.LouisI used 'regedit' and searched for 'ATI'. I hope I haven't messed anything up though - I will check out your links once I'm done with this post.So since my last post I've only had one BSoD (Just now) even though I've tried to provoke a crash multiple times throughout the day by forcing high CPU usage as well as GPU usage.The one I just had seemed to be completely random, all I did was watch a video on youtube, and had another tab open with Facebook.This is the Bluescreen connected to the crash. You should be fine using regedit.I do the same when I have problems with ATI chipsets.Take a read,. My personal experience with ATI chipsets is that such errors relate to the driver package installed.but I suppose that a hardware failure could occur.Looking at your Speccy data.I see that are running Spybot and have the TeaTimer function enabled. I suggest uninstalling Spybot (better alternatives available today) and killing the TeaTimer service (at the very least) since it is known to cause unforeseen system issues.See comments by quietman7,.Louis. Thank you once again for your reply Louis!I read something similar to your first link earlier.
I decided to keep digging, and did some searches on similar problems caused by virus. I found several websites that suggested it could be a rootkit.
I just finished running Malwarebytes anti-toolkit, which found 2 malware problems. I am doing a second scan now just to be on the safeside. The toolkit must have slipped under my protection, do you have any suggestions for something more permanent? - Would the tool that quietman7 suggest work for that?I uninstalled Spybot S&D, as you and quietman7 both suggests, it's seems outdated and irrelevant.I'll make some stress tests on my GPU and CPU when the second scan is done, and we'll see what happens. Hopefully it was just the rootkit that caused the error.Edit: Nope, just crashed again - Before my scan had finishedEdited by Jondk, 12 January 2014 - 02:00 PM.
I just finished running Malwarebytes anti-toolkit, which found 2 malware problemsHello -Do you still have the logs with the infections included, and can you paste them here??Please download Rkill (courtesy of BleepingComputer.com) to your desktop.There are 2 different versions. If one of them won't run then download and try to run the other one.You only need to get one of these to run, not all of them. You may get warnings from your antivirus about this tool, ignore them or shutdown your antivirus.rKill.exe:iExplore.exe (renamed rKill.exe):. Double-click on the Rkill desktop icon to run the tool. If using Vista or Windows 7 right-click on it and choose Run As Administrator. A black DOS box will briefly flash and then disappear.
This is normal and indicates the tool ran successfully. If not, delete the file, then download and use the one provided in Link 2. Do not reboot until instructed.
If the tool does not run from any of the links provided, please let me know.NOTE - If normal mode still doesn't work, run the tool from safe mode.When the scan is done Notepad will open with rKill log.Post it in your next reply.NOTE.
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.or read our to learn how to use this site. Well.you don't need Who Crashed to recognize the letters 'ATI' in the Caused By Driver caption. ATI makes graphics chipsets, so it's obviously the ATI driver which should be the first suspect, IMO.I would uninstall all ATI software/drivers (including CCC), using Add/Remove Programs AND Device Manager.then reboot and reinstall the ATI package.If that doesn't resolve it.that would be the time to try to dig deeper, IMO.LouisThank you for your respond Louis!After I realized it was related to the GFX card (googled the atikmdag.sys error) I tried updating to the newest drivers from the official site.
It stopped 90% of the crashes. If I start a game or anything that takes up a lot of CPU, it will still crash (Didn't do this a month ago)I'll try to remove everything ATI related, and then re-install the newest updates as you suggest, and will tell you how it went. Your mention of 'cleaning the Registry' brings bad thoughts to mind. I hope that you are not using a registry cleaner/optimizer application.The registry doesn't need 'cleaning'.that's just hype promoted by those who develop 'registry cleaners'.-See commnets by quietman 7 re registry cleaners.at.LouisI used 'regedit' and searched for 'ATI'. I hope I haven't messed anything up though - I will check out your links once I'm done with this post.So since my last post I've only had one BSoD (Just now) even though I've tried to provoke a crash multiple times throughout the day by forcing high CPU usage as well as GPU usage.The one I just had seemed to be completely random, all I did was watch a video on youtube, and had another tab open with Facebook.This is the Bluescreen connected to the crash. You should be fine using regedit.I do the same when I have problems with ATI chipsets.Take a read,.
![How to use vertex exactimate How to use vertex exactimate](http://dev.wallworm.com/media/1/image/png/page/203_wad_importer.png)
My personal experience with ATI chipsets is that such errors relate to the driver package installed.but I suppose that a hardware failure could occur.Looking at your Speccy data.I see that are running Spybot and have the TeaTimer function enabled. I suggest uninstalling Spybot (better alternatives available today) and killing the TeaTimer service (at the very least) since it is known to cause unforeseen system issues.See comments by quietman7,.Louis. Thank you once again for your reply Louis!I read something similar to your first link earlier. I decided to keep digging, and did some searches on similar problems caused by virus. I found several websites that suggested it could be a rootkit.
I just finished running Malwarebytes anti-toolkit, which found 2 malware problems. I am doing a second scan now just to be on the safeside.
The toolkit must have slipped under my protection, do you have any suggestions for something more permanent? - Would the tool that quietman7 suggest work for that?I uninstalled Spybot S&D, as you and quietman7 both suggests, it's seems outdated and irrelevant.I'll make some stress tests on my GPU and CPU when the second scan is done, and we'll see what happens. Hopefully it was just the rootkit that caused the error.Edit: Nope, just crashed again - Before my scan had finishedEdited by Jondk, 12 January 2014 - 02:00 PM. I just finished running Malwarebytes anti-toolkit, which found 2 malware problemsHello -Do you still have the logs with the infections included, and can you paste them here??Please download Rkill (courtesy of BleepingComputer.com) to your desktop.There are 2 different versions.
If one of them won't run then download and try to run the other one.You only need to get one of these to run, not all of them. You may get warnings from your antivirus about this tool, ignore them or shutdown your antivirus.rKill.exe:iExplore.exe (renamed rKill.exe):.
Double-click on the Rkill desktop icon to run the tool. If using Vista or Windows 7 right-click on it and choose Run As Administrator. A black DOS box will briefly flash and then disappear. This is normal and indicates the tool ran successfully. If not, delete the file, then download and use the one provided in Link 2.
Do not reboot until instructed. If the tool does not run from any of the links provided, please let me know.NOTE - If normal mode still doesn't work, run the tool from safe mode.When the scan is done Notepad will open with rKill log.Post it in your next reply.NOTE.