Hello everybody,

Windows 8 runs quite well here. There is one exception, and that is that there's a roughly 30% chance of it bluescreening when I start Internet Explorer. I don't have to actually do anything in IE: it starts, loads, renders and displays the homepage, and within one second either the system bluescreens, or it doesn't and then I can use IE normally for any length of time.

The bluescreen has *never* occurred under other circumstances or with other programs. I've *only* seen it happen under the circumstances I described above. Since IE is not my default browser I wasn't really bothered by this issue, until now. :)

When looking for similar symptoms online, it turned out the BSOD is a well known one: SYSTEM_SERVICE_EXCEPTION in atikmdag.sys with an access violation error (0xc0000005).

In all the reports I found, this BSOD occurs under different scenario's. I've seen crashdumps mentioning firefox.exe for example, and other programs. What seems to differ in my case is that the BSOD **never** happens, **unless** right after Internet Explorer started. And even then it only happens around 30% of the time.

I've been experiencing this issue for a long time (at least more than 6 months). That means it happened with at least 3 different AMD driver versions and many Windows Update-cycles. My system is all current at the moment.

I have an Ivy Bridge system with 16GiB of RAM, running Win8 64 bit. There were four minidumps on my system, which I zipped (along with the event log entries about the bugcheck), and made them available through the following link:

 [ it won't let me mention a link until my account is verified - the minidumps are on jur.jen.osk.am (yes, that really works - I hope no one minds that I included a link anyway)]

Unfortunately, I don't have that much experience analysing Windows dump files or debugging running systems. Could somebody please provide some guidance of how to proceed?

Thank you,

Jurjen Oskam

1. Analyze minidump (or full dump file - depending on your settings) with WinDBG or at least view it with Nirsoft viewer.

2. I do more disagnostic tests aiming at RAM and HDD.

3. If nothing helps, restore backup or reinstall.

Rgds

Milos

post a link without http or replace http with hxxp

If you are being told you cant post a link, or embed a picture (or any other restriction) you just need to post to one of these threads saying your account has not been validated http://social.msdn.microsoft.com/Forums/en-US/4d9b6981-6fa4-4ad8-b576-2e9241ee8cba/verify-your-account-5

I had a similar problem with atikmpag.sys AMD Driver.  In my troubleshooting I found that sometimes AMD drivers don't extract properly  during installation.  My solution was to....

Locate all atikmdag.sy_ 

Copy the file atikmdag.sy_ to another folder that is shorter e.g. C:\test or C:\Users\username\Desktop

Open the command prompt

Enter C: and hit enter, then enter cd C:\test\ or cd C:\Users\username\Desktop

Now enter the following command Extract.exe atikmdag.sy_ atikmdag.sys

Open C:\Windows\system32\drivers and rename the existing atikmdag.sys to atikmdag.sys.bak

Copy the file atikmdag.sys from your desktop to C:\Windows\system32\drivers

Reboot PC

The original source actually used this method for fixing a BSOD that referenced the same .sys file you are having problems with.  I used it for the atikmpag.sys file and I haven't gotten any BSODs since.  I must however, urge you to make the .bak file as a backup just in case.  Hope everything works out.