Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSoD While Scanning PS With Avast, Possibly Caused by Atikmdag.sys

21 Dec 2010   #1
Dellius

Windows 7 Ultimate x64
 
 
BSoD While Scanning PS With Avast, Possibly Caused by Atikmdag.sys

Today, as I was scanning my computer with Avast IS, like five minutes into the scan the screen flickered, some crazy colors appeared, followed by a BSoD, which disappeared fast. Then the system restarted itself and I received a "No boot device" error.

I waited a few minutes, I restarted again, and Windows froze. I restarted a third time and this time it started fine. I tried to examine the memory dump myself, but since I had no idea what I was doing, I am not sure I have actually done it properly.

WindBG suggested the culprit might be Atikmdag.sys so I repaired my video card driver using Uninstal a Program > Ati Install Manager > Repair.

I ran Avast IS again and no BSoD this time, but I am totally not sure whether this was the cause, what caused the other freezes, why, and what this memory dump really contained. I want to be sure I have taken care of the problem so it doesn't happen again.

Here is my Memory.DMP file.

Help me, please.


My System SpecsSystem Spec
.
22 Dec 2010   #2
Jonathan_King

Windows 7 Professional x64
 
 

The dump clearly pointed to your ATI drivers as the cause; since you updated them, though, try to forget about it, unless it happens again.

It's fully possible the problem has nothing to do with those drivers, that's just where the system was when it crashed. Perhaps it was a coincidence that Avast was scanning at the time, or perhaps Avast changed something that caused the system to crash once.

Let's just wait to see what happens in the future. If you get any more BSODs, please upload a full jcgriff2 report for us, according to these directions: https://www.sevenforums.com/crashes-d...tructions.html

...Summary of the dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 14 23:54:03.406 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:33.468
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmdag.sys ( atikmdag+38f201 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+38f201
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
22 Dec 2010   #3
Dellius

Windows 7 Ultimate x64
 
 

Quote:
Code:
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+38f201
My debugger didn't tell me this last one bit.

Here is a full jcgriff report together with a perfmon report.

Here is additional information about my system.

Is Windows 7 . . .
- x86 (32-bit) or x64 ? - x64
- the original installed OS on the system? - not really. My system is a custom build.
- an OEM or full retail version? - full version to the best of my knowledge.


- What is the age of system (hardware)? - a couple of years, except for the PSU and GPU. I upgraded my GPU a month ago and then I had to upgrade my PSU twice in order to power up properly the GPU.
- What is the age of OS installation (have you re-installed the OS?) - Old. Maybe over a year. I am a very careful user.
My System SpecsSystem Spec
.

22 Dec 2010   #4
Jonathan_King

Windows 7 Professional x64
 
 

The minidumps, understandably, point to the same thing the full dump did: your ATI drivers. Try completely removing your current drivers, using Driver Sweeper. then download the latest version and install them: Graphics Drivers & Software

I cannot recall SPTD being the cause of dumps this specific before, but it's worth a shot I guess. SPTD has been causing BSODs for a while now, and updated versions are not being fixed. Daemon Tools and a couple other programs use SPTD, so remove them. Then remove SPTD with this tool: http://www.duplexsecure.com/download...t-v174-x86.exe

Install this updated Intel Ethernet driver: http://downloadcenter.intel.com/Deta...=3003&lang=eng

Finally, test the hard drive, using SeaTools.

...Summary of the dumps:
Code:

Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Dec 14 23:54:03.406 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:33.468
Probably caused by : atikmdag.sys ( atikmdag+38f201 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+38f201
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Thu Dec  9 02:16:49.921 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:30.000
Probably caused by : atikmdag.sys ( atikmdag+38f201 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+38f201
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec  4 23:06:21.359 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:31.437
Probably caused by : atikmdag.sys ( atikmdag+38f201 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+38f201
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sat Dec  4 22:56:35.375 2010 (UTC - 5:00)
System Uptime: 0 days 0:00:31.453
Probably caused by : atikmdag.sys ( atikmdag+38f201 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
FAILURE_BUCKET_ID:  X64_0x3B_atikmdag+38f201
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
  
My System SpecsSystem Spec
22 Dec 2010   #5
Dellius

Windows 7 Ultimate x64
 
 

I have already updated the network adapter drivers together with the chipset, sound, storage drivers and BIOS.

My video card drivers are also the latest ones from AMD, and yes I have previously tried different drivers which used to break the computer's sleep or caused other problems. I did remove them with Driver Sweeper every time, so I am sure my system is clean of any previous driver leftovers.

I ran a Long DST Test using SeaTools and my drive failed, but passed the SMART test.

Does that mean I need to replace the drive ?

What's the deal with SPTD ? Why did you decide it was involved ? I don't see it mentioned anywhere in what you have posted. Yes, I do have Alcohol installed, but it has been stable since day one. Maybe the instability for the past month has corrupted the Alcohol installation, so I will try to reinstall it.
My System SpecsSystem Spec
22 Dec 2010   #6
Jonathan_King

Windows 7 Professional x64
 
 

Since the drive failed, it must be replaced. You are probably not in any immediate danger of data loss, but you never know. I recommend you replace the drive immediately; data loss is nothing to be played with. I suspect that is the cause of your BSODs.

SPTD is a strange driver. It runs in Kernel Mode, rather than User Mode; it has a lot of control over the system.

Check out these BSODs; every one was caused by SPTD:You can see SPTD is rarely blamed by the dumps. We find out that it is the cause, by removing it and watching the results.

If the new hard drive does not solve the issue, remove SPTD.

Now Daemon Tools and Alcohol are the programs that use SPTD. Usually, these programs give no signs of trouble. It is SPTD, not Alcohol, that causes these crashes. Even when Daemon Tools or Alcohol is not running, SPTD is.

So, if you don't want to remove SPTD just now, replace the hard drive. That needs to be done anyway, so it won't hurt to wait and see what happens before removing SPTD.
My System SpecsSystem Spec
23 Dec 2010   #7
Dellius

Windows 7 Ultimate x64
 
 

I tried to uninstall Alcohol from Add/Remove Programs, but I can't see it listed there, which means it has definitely taken some damage during the instability period. Luckily, I have it's installer handy, so I will run it and use it to remove it completely, and then I will remove the SPTD driver, too.

Here is another thing that came up.

I scanned the HDD with HDD Regenerator to repair the damaged sectors which caused the Long DST to fail and now it successfully passed it, but the short DST test failed with reason "Electrical Element Failed".

How serious is this and should I replace the drive ? How long do you think it can hold like that ? I can get a HDD ASAP, but it will cost me almost double the price than if I choose to wait for like 2 weeks.
My System SpecsSystem Spec
23 Dec 2010   #8
Jonathan_King

Windows 7 Professional x64
 
 

Wait the two weeks; save the money.

Data is nothing to be toyed with, though. The drive could possible fail next time you fire up your computer, or it could hold out for another three months. If you have important data on it, you don't want to take the chance.

So, backup anything you don't want to lose. If you don't have another hard drive, that's fine. You can create a Skydrive account for free, and get 25GB of storage space online. If 25GB is not enough, just use another email address and create a second account!

Windows Live SkyDrive - Online document storage and file sharing

That way, if the drive does fail before you get the new one, you won't be left without your data.
My System SpecsSystem Spec
28 Dec 2010   #9
Dellius

Windows 7 Ultimate x64
 
 

What an irony. My drive failed on the 23rd when no one was around to help me.

I took it for repairs and they said it was fine, and it has passed all tests without a problem, but when I took it back home it failed the Short DST test time and time again.

I don't know what to do at this point.
My System SpecsSystem Spec
28 Dec 2010   #10
Jonathan_King

Windows 7 Professional x64
 
 

My System SpecsSystem Spec
Reply

 BSoD While Scanning PS With Avast, Possibly Caused by Atikmdag.sys




Thread Tools




Similar help and support threads
Thread Forum
BSOD at random situations caused by atikmdag.sys
Hey! I have recently started getting 0-3 BSODs per day, with a program called WhoCrashed I have managed to figure out it is caused by atikmdag.sys but BlueScreenView says there are always ntoskrnl.exe + random driver causing the crash. I couldn't attach the minidump file because it says I don't...
BSOD Help and Support
BSOD at random situations caused mostly by atikmdag.sys
Hi im not good at this but i get alot of bluescreens mostly every day and it has been like this for a long time. gona try 2 copy the info Whocrashed gave me On Tue 2014-12-02 09:28:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\120214-37128-01.dmp This was probably caused...
BSOD Help and Support
BSOD at random situations caused by atikmdag.sys
Hello, im getting BSOD on our high spec PC's we have 20 Lenovo M92p I7'S with AMD 8570 Graphics Card Using the latest driver from AMD but also i have tried prevoius drivers. I have uploaded a BSOD of event log error. Please could someone assist me please?
BSOD Help and Support
BSOD caused by atikmdag.sys
My computer has been having the BSOD occurring in frequency for the past few weeks. I have run scans and deleted programs that I installed (there were only like 2) and it keeps crashing. It was crashing when I was watching videos so I updated my Flash but the computer again froze afterwards...
BSOD Help and Support
BSOD at random situations caused by atikmdag.sys A01
Hi Guys, Getting random bluescreens (A01) always related to the above file. I have recently bought a new ati card (R9 290, Gigabyte) which may/may not be related to this issue. I have performed a reinstall of windows, which helped this issue for about 24 hours and then it started again. ...
BSOD Help and Support
BSOD caused by the following module: atikmdag.sys (atikmdag+0x19C6D)
I hope anybody can help me....i already have the latest drivers but i still get BSOD's
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

й Designer Media Ltd

All times are GMT -5. The time now is 05:24.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App