Random BSOD throughout the day

I've been getting BSOD's a lot and I've tried clean install of windows twice and i'm stumped on what to do next. It happens at anytime whether I'm watching a YouTube video, playing WoW, doing coursework etc. I've installed Nirsoft bluescreen viewer to see what problems and most of the BSOD came up with ntoskrnl.exe + (random numbers) and atikmdag.sys + (random numbers). I've lost countless pieces of work and i have to be afraid every time i start doing work in case it BSOD and shuts down. I've attached the zip file so hopefully someone out there can help me fix this menace of a problem. Thank you

Hello and welcome SYC mate have seen some mentions of malware in there so for starters run these in this order
https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
https://www.sevenforums.com/tutorials/433-disk-check.html < if necessary include the /f and /r in the command line as per Option2
http://www.superantispyware.com/
http://www.malwarebytes.org/products/malwarebytes_free/
http://www.bleepingcomputer.com/download/adwcleaner/
ADW download from bleeping computer delete any rubbish found with the malware scans
(with ADW if you are running Kaspersky it will throw it up as malware just override Kaspersky by ignoring it or disabling it for the duration of the scan)

Then take a look at this Is csrss.exe a trojan?

Code:

fffff880`09850590  00000000`00000000
fffff880`09850598  00000000`00000000
fffff880`098505a0  fffffa80`07322400
fffff880`098505a8  fffff880`044e9783Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
 atikmpag+0x3a783
fffff880`098505b0  00000000`00000000
fffff880`098505b8  00000000`00000000
fffff880`098505c0  fffff880`09850630
fffff880`098505c8  00000000`00000000
fffff880`098505d0  00000000`00000000
fffff880`098505d8  00000000`00000000
fffff880`098505e0  fffff8a0`01530700
fffff880`098505e8  00000000`0027d7bc
fffff880`098505f0  00000000`00000000
fffff880`098505f8  00000000`00000000
fffff880`09850600  00000000`00000000
fffff880`09850608  fffffa80`05fce060
fffff880`09850610  00000000`00000072
fffff880`09850618  00000000`00000000
fffff880`09850620  00000000`00000000
fffff880`09850628  00000000`00000000
fffff880`09850630  00000000`00000000
fffff880`09850638  fffff880`110b3d87*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
 atikmdag+0xaad87
fffff880`09850640  00000000`00000000
fffff880`09850648  00000000`00000000

Code:

Adapter Description	AMD Radeon HD 7640G

See it there is a recent update for your video card driver. If so, install that, then do this:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

Yep I saw that too now Golden is probably better off than me to answer that one although I have thoroughly checked it out but I am guessing that is a driver issue.


To me there may be a problem with the Chrome browser and to be frank I am not a great lover of the security suite you have on the machine - but your choice.

Last thing what is the model of the machine please because we cannot link the driver/s for you unless we know exactly the model you have.

Now if you look at this VERIFIER_ENABLED_VISTA_MINIDUMP - Microsoft Community

it has a few suggestions re memtest and the chkdsk function so try running these first in safe mode it takes very little time and to eliminate any problems there

https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
https://www.sevenforums.com/tutorials/433-disk-check.html < if necessary include the /f and /r in the command line as per Option2

For the memtest if Golden thinks it is ok
MEMTEST
The memtest you will need to make a bootable disk / stick and set the BIOS to boot from the optical or USB and it will take a fair time to run- some leave it overnight. see the attached document.
But one thing is very important you must let the test run for at least 8 passes any less and the findings are no good. Now if errors come up straight away then you can stop it - see my pics. Now if there are errors and you have more than one stick of RAM in then you will need to test each stick ie remove the sticks and replace stick 1 in slot 1 and test no errors do the same in slot 2 with stick 1 no errors then repeat the process with stick 2 - that will show up the faulty stick - the other thing is it could be a faulty slot but most unusual.
It is a very lengthy and tedious process but worth it if you have errors.
see pics

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa80ff8cce60, 2, 0, fffff88004f699fd}

*** WARNING: Unable to verify timestamp for usbfilter.sys
*** ERROR: Module load completed but symbols could not be loaded for usbfilter.sys
Probably caused by : usbfilter.sys ( usbfilter+21f4 )

Followup: MachineOwner
---------

This driver is actually part of the AMD chipset USB drivers. See if you can update them from here:
Support & Drivers

Try MSE - it never causes BSOD's.