Memory Corruption while playing WOW

Page 1 of 2 12 LastLast

  1. Posts : 6
    win 7 home 64bit
       #1

    Memory Corruption while playing WOW


    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.
    Last edited by Sauce73; 19 Sep 2013 at 21:13. Reason: File didnt attach
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    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.

    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.
      My Computer


  3. Posts : 6
    win 7 home 64bit
    Thread Starter
       #3

    Already done.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

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


  5. Posts : 6
    win 7 home 64bit
    Thread Starter
       #5

    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.
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    Copy all the files from C:Windows:Minidump
      My Computer


  7. Posts : 6
    win 7 home 64bit
    Thread Starter
       #7

    Figured out how to get it.
      My Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    You missed the dumps again.
      My Computer


  9. Posts : 15,026
    Windows 10 Home 64Bit
       #9

    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 Check Disk (chkdsk) - Read Event Viewer Log

    4. Run SFC /SCANNOW Command - System File Checker 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 RAM - Test with Memtest86+. 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:
    Code:
    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

    Code:
    RtNdPt60.sys        Tue Dec 11 08:49:52 2007
    Realtek NDIS User mode I/O Driver - Ethernet

    Code:
    AsUpIO.sys          Mon Jul  6 08:21:38 2009
    ASUS hardware monitoring software related

    Code:
    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:
    Code:
    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
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer


  10. Posts : 6
    win 7 home 64bit
    Thread Starter
       #10

    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.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About 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 18:19.
Find Us