BSOD caused by adress ''ntoskrnl.exe+ee2cb''

Gandza · 16 Sep 2015

Hi good people,

Can somebody help me with my bsod-s.. It's caused by adress ''ntoskrnl.exe+ee2cb'' and repeted several times this day. Even though, some days passed without this problem.

Here are .zip file made by DM Log Collector.

Attachment 371660

Gandza · 19 Sep 2015

Anybody??

Laith · 27 Sep 2015

Hiya and welcome to SevenForums!

Code:

BugCheck A, {fffffa7fffffffe0, 2, 1, fffff80002ea9ad0}

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

Code:

BugCheck A, {1, 2, 1, fffff80002eff002}

Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

Code:

BugCheck 3B, {c0000005, fffff96000090878, fffff88002944d50, 0}

Probably caused by : win32k.sys ( win32k!HMChangeOwnerThread+2c )

Code:

BugCheck A, {fffffa7fffffffe0, 2, 1, fffff80002eebad0}

Probably caused by : cng.sys ( cng!SHA256Transform+65 )

Code:

BugCheck A, {10, 2, 1, fffff80002eefad0}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )

Run sfc /scannow and chkdsk /r.
Install the latest updates from Windows Update.

Do the exact same steps for chkdsk /r but instead of typing in sfc /scannow type chkdsk /r.

Remove Avira and install Microsoft Security Essentials, for testing purposes.

Run MemTest86+, It must be MemTest86+. RAM - Test with Memtest86+

Gandza · 27 Sep 2015

Thanks for your reply

I have run chkdsk /r like 1 month ago, cause I read it helped some people, and didn't find any errors. I'll try with sfc /scannow.
I had Avira on my old XP hard drive with no troubles, and when I inserted new drive with Win. 7 (Ultimate, 64-bit), BSODs started to restart system with counting Physical Memory to 100. All other components are the same. I'll run MemTest86+ too when grab some time. Can ''dying'' graphic card be the reason, cause I had troubles with it (aguess it's bad MBO's slot)? (btw. sorry for my bad English

)
Big regards.

**axe0** · 27 Sep 2015

The 4 most recent dumps are blaming the AMD drivers
The drivers of your GPU are a little old.
Please check AMD for driver updates.

Code:

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

0: kd> lmvm atikmdag
start             end                 module name
fffff880`0f066000 fffff880`0fd56000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Fri Dec 06 22:19:43 2013 (52A23F6F)
    CheckSum:         00CA856E
    ImageSize:        00CF0000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

Uninstall Daemon Tools
Download the SPTD standalone installer and follow these steps:
- Double click the executable to open it
- Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window