Results 1 to 4 of 4
  1. #1
    New Lounger
    Join Date
    Mar 2015
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Random BSOD, usually when gaming

    Hello friendly people of this great vault of knowledge.

    I m a gamer and play different types of games all the time. I am cursed with random occurences of BSOD s. They sometimes occur frequently, sometimes not. I dont mind much normally, but these days, I ve been seeing the unwanted BSOD screens once every few hours. it is really annoying. what i did is :

    - I frequently monitor the temperatures, they seem fine.
    - I updated the drivers ( i sometimes see "atikmdag.sys" error on BSOD screens in the past )
    - I did windows mem diag test and shows no errors whatsoever.

    I m attaching a copy of latest dump files as i ve seen it advised by some members.

    I appreciate your time very much, thank you.
    Attached Files Attached Files

  2. #2
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Welcome to the Lounge, mzah.

    Uninstall EasyTune6 and DaemonTools, remove the SPDT.sys driver that came with the latter: http://www.duplexsecure.com/en/faq

    If you get a further BSOD, collect more data on it by using the Sysnative App/methods and attach the files back here, please.

  3. The Following User Says Thank You to satrow For This Useful Post:

    Fascist Nation (2015-03-02)

  4. #3
    New Lounger
    Join Date
    Mar 2015
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by satrow View Post
    Welcome to the Lounge, mzah.

    Uninstall EasyTune6 and DaemonTools, remove the SPDT.sys driver that came with the latter: http://www.duplexsecure.com/en/faq

    If you get a further BSOD, collect more data on it by using the Sysnative App/methods and attach the files back here, please.
    i highly appreciate you, taking the time to look into the problem, satrow. I will do what you offered right now.

    however,

    daemon tools ----> uninstalled long ago.
    easytune6 ---> i dont think it was ever installed. i didnt even know what it was untill i just googled it.

    ^since neither of these programmes dont appear installed and appearently some traces remain, how would you recommend i get rid of those traces?

    edit: i did a sweep with cccleaner, would that suffice??
    Last edited by mzah; 2015-03-02 at 19:04.

  5. #4
    Super Moderator satrow's Avatar
    Join Date
    Dec 2009
    Location
    Cardiff, UK
    Posts
    4,492
    Thanks
    284
    Thanked 577 Times in 480 Posts
    Daemon Tools drivers in the dumps: a*******.SYS (dynamically installed - name changes each time - probably from an older version) and spdt.sys. I suggest you try an update to the latest version and reboot - then uninstall/reboot. It might help.

    Unfortunately, since I last delved into the intricacies of the Duplexsecure site, they seem to have removed a lot of downloads/uninstallers etc. We'll have to do more work on the spdt.sys - or attempt to disable it/block it from starting with Windows (http://www.duplexsecure.com/en/faq).

    AODDriver2.sys is loaded, and is another known contributor to BSODs. It's part of AMD's CCC graphics drivers control panel software (AMD Fuel), also comes with some GigaByte motherboard software (EasyTune6) and might also be available as part of other motherboard/graphics utility/tweaking software. You can use a 'driver's only' approach to removing this: http://www.sysnative.com/forums/wind...procedure.html

    CCleaner is something of a scattergun approach with birdshot loaded, we need to be surgically accurate.

    I suspect that your problem is failing/faulty hardware but until we rule out these two known BSOD contributors, we won't know if it's time and guile that's needed or whether we have to fall back to throwing money at hardware replacements.

    To check what drivers are currently loaded in Windows, use DriverView, set it to hide Windows drivers, ignore any that begin with dump ... Apart from a few that MS forgot to sign, you should then be left with what are essentially 3rd party (aka suspect) drivers. http://www.nirsoft.net/utils/driverview.html

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •