Windows 10: Random BSOD's, doesn't matter what i am doing. Linked to ATIKMDAG.sys

I have been getting random BSOD's. Doesn't matter what I am doing, but I am getting 1 to 2 a day. I have followed as many steps as I have found, and it seems to fix it for a bit, then they come right back.

I believe they are tied to ATIKMDAG.SYS

I have followed the steps to upload my log and hope you all can help me out.

Thanks

:)

 

Multiple BSOD suddenly.

BSOD are more frequent now, seems to be random, doesn't matter what im doing.

 

No matter what I am doing in my system it constantly kicks me back so the ...home screen

Hi Hensley,

Thank you for posting your query on Microsoft Community.

I understand your inconvenience. Don’t worry. We will assist to resolve this issue.

It seems that your computer is infected by virus and malware.



First of all I would suggest you to check the issue if it occurs in Clean boot state:

You can place the computer in clean boot state and check the issue.

Clean boot: To help troubleshoot error messages and other issues, you can start Windows by using a minimal set of drivers and startup programs. This kind of startup is known as a
"clean boot." A clean boot helps eliminate software conflicts.

How to perform a clean boot to troubleshoot a problem in Windows 10, 8, Windows 7, or Windows Vista

http://support.microsoft.com/kb/929135

Note: Please refer to the section: How to reset the computer to start as usual after troubleshooting with clean boot of the Kb article to boot the computer in normal
startup after fixing the issue. Steps applies to Windows 10 as well.

Note: After troubleshooting, refer to this section
"How to reset the computer to start normally after clean boot troubleshooting"

Disclaimer: A clean boot is performed to start Windows by using a minimal set of drivers and startup programs. This helps eliminate software conflicts that occur when you install
a program or an update or when you run a program in Windows. You may also troubleshoot or determine what conflict is causing the problem by performing a clean boot. You must log on to the computer as an administrator to be able to perform a clean boot. Your
computer may temporarily lose some functionality when you perform a clean boot. When you start the computer normally, the functionality returns. However, you may receive the original error message, or experience the original behavior if the problem still exists.
If the computer is connected to a network, network policy settings may prevent you from following these steps.



Also after starting the computer in normal mode after Clean boot I would suggest you to run Full Virus Scan using Windows Defender.

http://windows.microsoft.com/en-us/windows-10/how-to-protect-your-windows-10-pc#v1h=tab01

Let us know the status of the issue. If you need further assistance, please do let us know and we would be happy to help you.

Thank you.

 

ATIKM is directly related to your AMD GPU driver package. Have you updated your GPU driver?

 

Yes, multiple times. I am on the latest drivers.

 

What are your complete system specs?

 

Operating System
Windows 10 Home 64-bit
CPU
AMD FX-4300 Quad-Core Processor Vishera 32nm Technology
RAM
8.00GB Dual-Channel DDR3 @ 799MHz (11-11-11-28)
Motherboard
MSI 760GM-P23(FX) (MS-7641) (CPU1)
Graphics
HP 23bw (1920x1080@60Hz)
HD1700 (1440x900@60Hz)
2048MB ATI AMD Radeon R7 200 Series (ATI AIB)
Storage
931GB TOSHIBA DT01ACA100 (SATA)
Optical Drives
HL-DT-ST BDDVDRW UH12NS30
Audio
Realtek High Definition Audio

 

Windows 10 Home 64-bit
AMD FX-4300 Quad-Core Processor Vishera 32nm Technology
8.00GB Dual-Channel DDR3 @ 799MHz (11-11-11-28)
MSI 760GM-P23(FX) (MS-7641) (CPU1)
2048MB ATI AMD Radeon R7 200 Series (ATI AIB)
931GB TOSHIBA DT01ACA100 (SATA)
HL-DT-ST BDDVDRW UH12NS30
Realtek High Definition Audio

 

Well two days ago I did a clean uninstall and reinstall of just the AMD driver. Everything was fine for a couple days, and this morning I just had a BSOD while just browsing the internet.

Don't know what to do besides canning my AMD and switching to Nvidia.

 

Please run this beta version of the log collector and post a zip into the thread:
log collector v2-beta08.zip

1) Update the system specs in the "My Computer" section:

System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Site Use Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums


Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, etc.)

2) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings >

a) under performance click settings > on performance options click the advanced tab > under virtual memory click change > post an image into the thread of the virtual memory window

b) under startup and recovery click settings > post an image into the thread

3) Open administrative command prompt and copy and paste:
4) sfc /scannow
5) dism /online /cleanup-image /restorhealth
6) chkdsk /scan
7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

8) Backup all files to another drive or to the cloud
9) Make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
10) Place the backup image onto another drive or into the cloud
11) Make a brand new restore point

12) Read these links on Windows driver verifier:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

13) In the above links on windows driver verifier please learn the multiple methods to turn off the tool using the windows advanced troubleshooting menu

14) Do not use windows driver verifier until it is communicated in the thread