memory_management blue screen crash!!

[Naderox]

Hi all,

My computer has been getting the same crash for months now and it's really frustrating!
The crash is completely random.

My system configuration:

Operating System
Windows 7 Ultimate 64-bit SP1
CPU
AMD Phenom II X6 1090T
Thuban 45nm Technology
RAM
8.00GB Dual-Channel DDR3 @ 535MHz (9-9-9-24)
Motherboard
ASUSTeK Computer INC. M4A88T-V EVO/USB3 (AM3)
Graphics
ASUS VE278 (1920x1080@60Hz)
3072MB ATI AMD Radeon HD 7900 Series (Sapphire/PCPartner)
Storage
231GB Samsung SSD 840 Series SCSI Disk Device (RAID)
931GB AMD 2+0 Stripe/RAID0 SCSI Disk Device (RAID)
1397GB Western Digital WD Ext HDD 1021 USB Device (USB (SATA))
Optical Drives
SONY DVD RW DRU-190S SCSI CdRom Device
Audio
ASUS Xonar DGX Audio Device

My motherboard page:
http://www.asus.com/uk/Motherboards/M4A88TV_EVOUSB3/specifications/

My RAM:
http://www.amazon.co.uk/gp/product/B004JO3L40/ref=wms_ohs_product?ie=UTF8&psc=1

My memory is 1600 MHz and my motherboard only supports 1066/1333/2000(O.C.) but I manually set my RAM frequency in the BIOS to 1333 MHz.

Here's the location of the last crash dump:

https://www.dropbox.com/sh/0gu8ls8i0fxkzzj/AAA9Ls8fUtJ6DxZrxmGsZp_Ta?dl=0

Thank you!

 

[kapitalistas]

you wanna try different memory stick.

 

[johnbl]

-run a malwarebytes and rootkit scan, remove gpu overclock software.
several of your system files have been modified and it looks like one of your antivirus files has been modified also. Not good news if you expect your antivirus software to be working.

- it also looks like some system files have been modified or replaced.
run cmd.exe as a admin
sfc.exe /scannow
this will check for corruption and attempt to repair the files.
the file msrpc.sys looks like it did calls right before the bugcheck and may be involved but it does not look correct.
update these drivers also:
\SystemRoot\system32\DRIVERS\nusb3hub.sys Thu Apr 22 18:34:35 2010
\SystemRoot\system32\DRIVERS\nusb3xhc.sys Thu Apr 22 18:34:36 2010

these drivers were on the stack next to the directx driver calls. they are very old nec usb 3.0 drivers and they may be overflowing the stack and corrupting the directx driver. (very likely) look for a updated driver from your motherboard manufacture or the nec website if you can actually find it.

your Ethernet driver is bad also
\SystemRoot\system32\DRIVERS\Rt64win7.sys Thu Jun 09 23:33:15 2011
Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC
pick up a current version from
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false

or your streaming software will have unexplained problems



your bugcheck was in directx code, but you have GPU overclocking software installed
\C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64\AODDriver2.sys Tue Feb 11 03:06:52 2014
I do think the current 14.9 catalyst drivers were broken on the amd website.

So you don't know if it was the actual graphic driver that messed up or the overclocking values that caused the failure, or the buggy release of AMD drivers.
remove the overclocking software to help isolate the problem.

ShadowofMordor.exe was running and making graphics calls, the directx had a problem in its heap, these can be simple bugs in the game, where the game deletes a memory object twice by mistake. The first delete will make directx free the memory to be used again by the program, the second delete corrupts the direct x data structures and causes the crash in directx.
I would look for updated to the actual game also.

-----
this driver is a red flag, just based on the date and the Name
C:\Users\Nader\AppData\Local\Temp\tmpFE1C.tmp Sat Jul 26 06:29:37 2008
it is not in the drivers directory, and it does not have a proper driver name
I would suspect a rootkit or some type of malware something that may even rename the driver on each boot to keep hidden.

-confirm that passthrusvr.exe you have running is not malware.
you might just want to do a quick malwarebytes scan.

you have a good memory dump but did not use verifier.exe to set debugging flags to help isolate problems
after you fix the above problems, if you still have bugchecks, read this to setup the debug flags.
http://www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html