BSOD memory management problems

[bloodeye28]

I'm getting daily BSOD memory management problems while preforming different actions. (browsing the internet, while gaming, listening to music on youtube and opening a new tab, watching twitch.tv, not really 1 program that I could blame the BSOD on)

Error description after restarting:

______________________________________________
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1043

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000041790
BCP2: FFFFFA80068B5FF0
BCP3: 000000000000FFFF
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\050715-29967-01.dmp
C:\Users\Owner\AppData\Local\Temp\WER-31902-0.sysdata.xml
_______________________________________________

I attached the required .zip file too.

Hopefully you guys can help me out with this!
Cheers,

 

[Boozad]

Welcome to 7F, I've taken a look at your dumps and will see if I can help solve your issues.

 ATI DRIVER

Your ATI driver has been flagged once in one dump, it may be the cause of the memory corruption so replace that driver first.

Download the latest driver for your card from here and save it to your desktop. Download DDU and follow http://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html to remove all traces of your current driver. Reboot and install the downloaded driver.

BugCheck 50, {ffffd8a00fa83018, 0, fffff8800f3ae620, 7}

[COLOR=Red]*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys[/COLOR]
Could not read faulting driver name
Probably caused by : atikmdag.sys ( atikmdag+17c620 )

0: kd> lmvm atikmdag
start             end                 module name
fffff880`0f232000 fffff880`104b6000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=Red]Fri Nov 21 02:30:27 2014[/COLOR] (546EA3C3)
    CheckSum:         0121F198
    ImageSize:        01284000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 MEMTEST86+

Download and run MemTest86+ to test your RAM. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

   Note

Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

BugCheck 3B, {c0000005, fffff800033be9cc, fffff88007b10ca0, 0}

Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+100 )

Followup: Pool_corruption
---------

7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800033be9cc, Address of the instruction which caused the bugcheck
Arg3: fffff88007b10ca0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

BugCheck 1A, {41790, fffffa80068b5cc0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33da4 )

0: kd> !pte fffffa80068b5cc0
                                           VA fffffa80068b5cc0
PXE at FFFFF6FB7DBEDFA8    PPE at FFFFF6FB7DBF5000    PDE at FFFFF6FB7EA001A0    PTE at FFFFF6FD400345A8
Unable to get PXE FFFFF6FB7DBEDFA8
0: kd> !pool fffffa80068b5cc0
GetPointerFromAddress: unable to read from fffff800034b6100
Pool page fffffa80068b5cc0 region is GetUlongFromAddress: unable to read from fffff800034b61c0
Nonpaged pool
GetUlongFromAddress: unable to read from fffff80003424a38
Unable to get pool big page table. Check for valid symbols.
fffffa80068b5000 is not valid pool. Checking for freed (or corrupt) pool
Bad allocation size @fffffa80068b5000, zero is invalid

***
*** An error (or corruption) in the pool was detected;
*** Attempting to diagnose the problem.
***
*** Use !poolval fffffa80068b5000 for more details.


Pool page [ fffffa80068b5000 ] is __inVALID.

Analyzing linked list...
[ fffffa80068b5000 ]: invalid previous size [ 0x69 ] should be [ 0x0 ]
[ fffffa80068b5000 --> fffffa80068b51c0 (size = 0x1c0 bytes)]: Corrupt region


Scanning for single bit errors...

None found

0: kd> !poolval fffffa80068b5000
Pool page fffffa80068b5000 region is Nonpaged pool

Validating Pool headers for pool page: fffffa80068b5000

Pool page [ fffffa80068b5000 ] is __inVALID.

Analyzing linked list...
[ fffffa80068b5000 ]: invalid previous size [ 0x69 ] should be [ 0x0 ]
[ fffffa80068b5000 --> fffffa80068b51c0 (size = 0x1c0 bytes)]: Corrupt region


Scanning for single bit errors...

None found

 DAEMON TOOLS

Uninstall Daemon Tools, a proven cause of BSODs.

1. Uninstall Daemon Tools.
2. Download the SPTD standalone installer and perform the following steps.
3. Double click the executable to open it.
4. Click the button shown below.

   Information

If the button it is grayed out as shown in the image, there is no more SPTD installation on your system and you can just close the window.

 

[bloodeye28]

Thank you very much for your reply Boozad,

I've tried uninstalling Deamon tools as you said, (find it very odd that it would cause BSOD , i've had it on my pc for literally years.)

I also managed to finally get a windows update installed for .NET framework 4.5.2 <something> (i'm not the biggest computer wizard but I think that might have been a cause/problem too?)

Haven't had a bluescreen yet so far. I'll be doing my usual stuff again and see if the BSOD still happens. might take a day. if so, i'll try step 1 and see if that helps.

Thanks man!
-Blood

 

[Boozad]

You're welcome. DaemonTools uses SCSI Pass Thru Direct and has been proven time and again to cause BSODs.

Let us know how it goes.