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: Return of the BSOD: STOP 0x*00000000000A

19 Jul 2017   #1
IReallyHateBSOD

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 
Return of the BSOD: STOP 0x*00000000000A

UPDATE 8/3/2017 - RESOLVED

Issue seemed to stem solely from Blizzard games. I completely removed all traces of Blizzard products from the system, went into registry and cleaned it out, did fresh install from scratch after defrag, and then updated GPU driver which is always a MAJOR chore because, just like what I did with the Blizzard games, I have to completely wipe all traces of the Radeon drivers and programs with a special removal tool and install from scratch in Safe Mode. This really is the worst GPU I've ever had. But anyway, resolved!



Had severe BSOD issues back in December of 2016. They have returned in force in such a way that I honestly have never seen, nor heard of a PC having issues like this.

The problems started immensely in May of this year. On June 19th, 2017 I began keeping a log. It is now July 19th. Here is the situation report after one month of keeping track.

Total BSOD experienced from 6/19 - 7/19: 284(!!)
Average BSOD per week: 43
Average BSOD per day: 11
Average BSOD per one hour of continuous gameplay: 4.5

Take into account that on many days I just don't have time for games, so the numbers represent the issues experienced any time I have played games for a continuous amount of time, which can be as little as 3 or 4 hours per week.

Interesting to note - I have discovered that the primary cause of ALL of my BSOD seems to stem from ONLY World of Warcraft and/or Blizzard games in general. I have not experienced BSOD with ANY other game that I play, many of which are far more graphically intensive and demanding on my system than World of Warcraft.

It came to a head today - I completely wiped every single trace of Warcraft and Blizzard material from my computer. Uninstalled, then went into the leftover folders and completely obliterated. Did a totally fresh, brand new installation. Issues not only persist, but are now WORSE! Here's the breakdown for today:

Total BSOD experienced: 8
Longest Amount of Time able to stay in-game before BSOD: 7 minutes, 41 seconds
Shortest amount of Time * *: 39 seconds
Average amount of time * *: 1 minute, 45 seconds

BSOD experienced with other games today: 0
Longest Amount of Time played on another game without BSOD: 3.8 hours

Average time is rounded off but about accurate.

File attached...unfortunately the forum wont let me upload pic or .dmp file.


My System SpecsSystem Spec
.
20 Jul 2017   #2
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

Hello and welcome Mike mate did you check the registry for any leftovers for those games I am not sure of who produces them nut you should have a look in the HKEY's LOCAL_MACHINE & CURRENT _USER > Software scroll down the listings and if you find the stuff you are looking for then delete complete entry. See my pic

BEFORE you do anything like that though please do this Registry - Backup and Restore - Windows 7 Help Forums

Now the last dump is referring to the GPU driver

Code:
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff800030b89a9 to fffff800030b9400

STACK_TEXT:  
fffff880`13b345f8 fffff800`030b89a9 : 00000000`0000000a 00000000`00000018 00000000`00000009 00000000`00000000 : nt+0x70400
fffff880`13b34600 00000000`0000000a : 00000000`00000018 00000000`00000009 00000000`00000000 fffff880`1123bca0 : nt+0x6f9a9
fffff880`13b34608 00000000`00000018 : 00000000`00000009 00000000`00000000 fffff880`1123bca0 fffffa80`07991480 : 0xa
fffff880`13b34610 00000000`00000009 : 00000000`00000000 fffff880`1123bca0 fffffa80`07991480 00000000`00000000 : 0x18
fffff880`13b34618 00000000`00000000 : fffff880`1123bca0 fffffa80`07991480 00000000`00000000 00000000`00000000 : 0x9


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
atikmdag+16ca0
fffff880`1123bca0 0fb64118        movzx   eax,byte ptr [rcx+18h]

SYMBOL_NAME:  atikmdag+16ca0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME:  atikmdag.sys

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  WRONG_SYMBOLS

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:wrong_symbols

FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
The usual fix suggested for this is to uninstall the Catalytic Control Centre and use the GPU driver on it's own Drivers Tools


Now there are a few suspicions about the RAM too and you may have to run a memtest as well aare you getting more beeps on boot up than usual?? Normally it should be just one



Code:
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800033c35b4, Address of the instruction which caused the bugcheck
Arg3: fffff880094c5a90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
MEMTEST
Now to make absolutely we are on the same page the memtest linked here is the only one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM. RAM - Test with Memtest86+ - Windows 7 Help Forums
(This is pretyped to save time)
My System SpecsSystem Spec
20 Jul 2017   #3
IReallyHateBSOD

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Interesting. The RAM issue is something I've been told may be the primary culprit. It just blows my mind that it is only Blizzard games, and not any other, that cause the problems. I will see if I can dig up one of my USB sticks.

As for beeps on bootup, unfortunately I cannot tell. I lost the internal speaker piece while I was building the computer 3 years ago so I do not get any audible beeps during startup.

As for the Display driver...I will try uninstalling catalytic and then installing the driver myself. Unfortunately, as I had indicated back in December when I first had major BSOD issues, my particular GPU is incredibly problematic when it comes to installing its own display drivers, and extreme lengths often have to be taken in order to get them to install properly. I do say I am NOT looking forward to having to do this yet again, but I will try the GPU first, and if issues persist, I will begin RAM testing.

I'm working from home for the summer so I have plenty of time to do this over the next few days.
My System SpecsSystem Spec
.

20 Jul 2017   #4
IReallyHateBSOD

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

One other thing I should mention, not sure if relevant - the catalyst for my BSOD stems from severe graphical sputtering, accompanied by loud "buzz" noise. When that starts happening I know that a BSOD is typically moments away, and the next time it happens the "buzz" becomes an infinite sound dragout until I reboot.
My System SpecsSystem Spec
20 Jul 2017   #5
IReallyHateBSOD

Microsoft Windows 7 Home Premium 64-bit 7601 Multiprocessor Free Service Pack 1
 
 

Uh...memtest is apparently not compatible with Windows 7? Not sure why I'm getting that error but can't use it.
My System SpecsSystem Spec
22 Jul 2017   #6
ICIT2LOL

Desk1 7 Home Prem / Desk2 10 Pro / Main lap Asus ROG 10 Pro 2 laptop Toshiba 7 Pro Asus P2520 7 & 10
 
 

Mike I don't know what memtest you are using but read this as it has a link to the only memtest we recommend mate the Windows feature is not worth much at all.

MEMTEST
Now to make absolutely we are on the same page the memtest linked here is the only one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM. RAM - Test with Memtest86+ - Windows 7 Help Forums
(This is pretyped to save time)

But to reiterate this it MUST be 8 passes very minimum only if you get errors before then you canshut it down.
My System SpecsSystem Spec
Reply

 Return of the BSOD: STOP 0x*00000000000A




Thread Tools




Similar help and support threads
Thread Forum
BSOD on return from sleep mode
Recently reinstalled Windows 7. Since then have encountered BSOD on two occasions when bring PC out of sleep.
BSOD Help and Support
BSOD upon return from Sleep on new Rig
New rig, put it together a week ago. Getting a BSOD after waking the computer; has happened twice so far. Running windows 7 professional x64. I manually installed it onto a vertex agility 3 SSD (120gb). I've ensure that all my drivers are up to date, to include the SSD's firmware. I've...
BSOD Help and Support
Return of BSOD on my pc.
hi friend, a few months ago my pc was facing a BSOD error and used to happen 3-4 times a day, but it got solved due to all the help i got here. But from today the wicked BSOD has returned on my pc, and it has occured twice today itself, so i would like some help from you guys if possible. i...
BSOD Help and Support
Return of Random BSOD
Three weks ago I performed the recommended updates and thought my BSODs were cured. However, they continue at a lessened frequency. Past recommendation was to update the AE1000 driver. The most recent Win 7 driver is installed. See atttached files for current machine status. The dump files include...
BSOD Help and Support
BSoD Part 2: The Return
Greetings, everyone: The story so far: Back in August I built a PC. O, la, la. It was working great, except for one small problem. If I ever shut the PC down for a few hours (or over night), it would never let me have a clean boot. It will load me to Windows, give me about 5 minutes, then...
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 12:52.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App