Memory Corruption while playing WOW

[Sauce73]

Two months ago I was playing my computer and it crashed. When I went to reboot it wouldn't even make it to the Bios screen. Eventually I removed a stick of memory and it still woudln't boot so I put one back and and put the other back in. It booted but put me down to 2 gb of memory so I went out and bout a new kit of memory KHX16C9B1RK2/8X and took the old one out. At first I couldn't boot with two sticks of memory so I went and reset the cmos and was eventually able to boot. Since then I have received BSOD numerous times and have drove myself crazy trying to figure it out. I ran memtest 86 and passed with no errors. And as long as I don't play wow it hasn't crashed. So I went and spent six hours today redownloading and reinstalling wow and it crashed as soon as I did. I went and downloaded windowsbugger kit and tried my best to decipher myself with no luck.

 

[koolkat77]

First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.

• Create a Dump File when you get a BSOD

Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.

 

[Sauce73]

Already done.

 

[koolkat77]

can you grab them all like you did in the first post.
That zip did not have the latest dumps.

 

[Sauce73]

The first time I used the SF diagnostic program but those dumps were already on the computer at the time. How do i specify a folder then to use SF diagnostic tool to grab dumps from? I placed my dump folder on my desktop so it would be easier to view.

 

[koolkat77]

Copy all the files from C:Windows:Minidump

 

[Sauce73]

Figured out how to get it.

 

[koolkat77]

You missed the dumps again.

 

[koolkat77]

Based on the bugchecks, I would recommend you follow and complete the steps given below:

1. If you are overclocking any hardware, please stop. Reset any changed values back to default and reset/clear CMOS: Clear CMOS - 3 Ways to Clear the CMOS - Reset BIOS. Uninstall any overclocking tool as these can also be a reason of blue screens.

2. Uninstall your current antivirus software. It can be a cause of BSOD very often. Please remove it with its removal tool and use Microsoft Security Essentials in its place. Malwarebytes is a great combination with it. Go through this thread for more info.

3. Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html

4. Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to check windows for integrity violations. Run it up to three times to fix all errors. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.

5. Make scans with Kaspersky TDSskiller and ESET Online scanner.

6. Perform a Clean Start up, this will help avoid any problematic applications from bugging the system.

7. Use Revo Uninstaller Free to uninstall stubborn software. Opt for Advanced Mode and uninstall the software, delete the leftover registry entries.

8. Use Crystal Disk Info to upload a screenshot of your Hard Drives (s). Test your Hard Drives (s) running a Hard Drive Diag.

9. Test and Diagnose RAM issues with http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html. Pay close attention to Part 3 of the tutorial "If you have errors" Take the test for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.
​

Update/Remove the Drivers below:

AODDriver2.sys      Thu Apr  5 15:23:37 2012

(AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems. Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program. Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page) Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

RtNdPt60.sys        Tue Dec 11 08:49:52 2007

Realtek NDIS User mode I/O Driver - Ethernet

AsUpIO.sys          Mon Jul  6 08:21:38 2009

ASUS hardware monitoring software related

ASACPI.sys          Thu Jul 16 09:31:29 2009

Asus ATK0110 ACPI Utility (a known BSOD maker in Win7 and Win8). Also a part of many Asus utilities (Win8 versions available from Windows Update as an Optional Update - but check Asus first!)

​

BSOD BUGCHECK SUMMARY:

[FONT=Lucida Console]Built by: NOT FOUND
Debug session time: Fri Sep 20 02:46:47.159 2013 (UTC + 6:00)
System Uptime: 0 days 0:53:58.345
BugCheck 7F, {8, 80050031, 6f8, fffff80002ec4fc1}
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff800`02e50000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff800`02e50000
Probably caused by : Unknown_Module_fffff800`02e50000 ( nt+75b80 )
BUGCHECK_STR:  0x7f_8
PROCESS_NAME: NOT FOUND
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Thu Sep 19 16:22:46.774 2013 (UTC + 6:00)
System Uptime: 0 days 23:48:17.319
BugCheck 19, {3, fffff8a0285f43f0, fffff8a0285fb8f0, fffff8a0285f43f0}
*** WARNING: Unable to verify timestamp for Unknown_Module_fffff800`02e50000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffff800`02e50000
Probably caused by : memory_corruption
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  Wow-64.exá
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Wed Sep 18 16:25:26.708 2013 (UTC + 6:00)
System Uptime: 1 days 5:02:51.537
BugCheck 3B, {c0000005, fffff8800418db8c, fffff88007221df0, 0}
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : memory_corruption
BUGCHECK_STR:  0x3B
PROCESS_NAME:  avgnsa.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Debug session time: Tue Sep 17 11:22:01.132 2013 (UTC + 6:00)
System Uptime: 1 days 0:44:47.057
BugCheck D1, {8, 2, 1, fffff88000db9ed2}
*** WARNING: Unable to verify timestamp for avgtdia.sys
*** ERROR: Module load completed but symbols could not be loaded for avgtdia.sys
Probably caused by : ataport.SYS ( ataport!PortListRemoveRequest+22 )
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/FONT]

 

[Sauce73]

Unfortunately when removing video driver computer locked and couldn't get it to reload windows so I reformatted. Hoping that took care of the problem but it crashed again last night. I have the microsoft security essentials on here like posted earlier. I made sure I installed the video driver as directed. I set up debug before I did anything else so that if it crashed I could capture it. Whats do I do next? I am really hoping this isn't hardware related.

 

[koolkat77]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5001, fffff70001080000, 51f0, 530fffffa1fe}

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

Followup: MachineOwner
---------

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005001, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 00000000000051f0
Arg4: 0000530fffffa1fe

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


BUGCHECK_STR:  0x1a_5001

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800028eaf1a to fffff80002882b80

STACK_TEXT:  
fffff880`03bf4958 fffff800`028eaf1a : 00000000`0000001a 00000000`00005001 fffff700`01080000 00000000`000051f0 : nt!KeBugCheckEx
fffff880`03bf4960 fffff800`028a999d : fffffa80`092682c0 00000000`00000000 fffffa80`08f0bec8 fffffa80`092682c0 : nt! ?? ::FNODOBFM::`string'+0x2924c
fffff880`03bf49f0 fffff800`0289028a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x309
fffff880`03bf4ac0 fffff800`02880cae : 00000000`00000000 000007fe`fa62891c 00000000`00001001 000007fe`fa62891c : nt!MmAccessFault+0x146a
fffff880`03bf4c20 000007fe`fa2928e5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`01c0c1b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fa2928e5


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2924c
fffff800`028eaf1a cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2924c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

FAILURE_BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+2924c

BUCKET_ID:  X64_0x1a_5001_nt!_??_::FNODOBFM::_string_+2924c

Followup: MachineOwner
---------

------------------------
Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to Part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

 

[Sauce73]

Slot one passes both sticks separately up to 11 passes. None of the other slots will boot with a stick in there to test rest of slots. If I put sticks in Dimm A1 and Dimm B1 I receive errors. Does this mean the slots have gone bad?

 

[koolkat77]

Does this mean the slots have gone bad?

I'm afraid that yes, the motherboard may be bad/faulty now.
What happens if you don't put any ram in those slots?