0x0000008E, 0xC0000005 BSOD after graphics card + mem upgrade, dump report inside

By eamesj1
Mar 26, 2011
Post New Reply
  1. System specs:

    Asus K8N-E Deluxe motherboard
    athalon 64 3200 processor
    3 gb pc3200 ram
    gigabyte radeon hd 4650 agp
    cooler master 380 w power supply
    windows xp service pack 3
    (Everything's ancient, I know.)

    I recently upgraded my graphics card from a radeon x1650 to the hd 4650 and I replaced 2 256 mb kingston ram sticks with 2 1gb pny ram sticks.

    I removed all of the ati drivers on my computer using the add/remove function in the control panel, uninstalled the current driver from the device manager, rebooted the computer in safe mode and ran "Driver Sweeper" to remove any remaining ATI drivers in the registry. Then I successfully applied ati's latest agp hotfix drivers to my card and everything seemed to be working alright.

    I can play the AoE online beta, Napoleon Total War, and Civilization V without any problems. I can also stream Netflix Movies in HD, watch divx movies online with their web player, and I can watch downloaded movies through the VLC player with no problems....

    However, whenever I try to play SC2 (SC2 launches and works fine up until a map is 99% loaded and then it crashes), watch a youtube video, or any flash video for that matter---- my computer crashes to a blue screen and I get this error:

    stop: 0x0000008E, 0xC0000005 (random 0's, numbers, and letters)

    Dump physical memory
    Memory Dump complete

    I downloaded the Windows debugger tool and debugged the last error report. I'm not really sure what all of this means but it looks like there is an issue with some of the new drivers that were installed with the new graphics card. Can someone please read this report and tell me what I need to do to fix this?


    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini032511-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x805540c0
    Debug session time: Fri Mar 25 23:37:01.312 2011 (GMT-4)
    System Uptime: 0 days 11:42:46.910
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..............
    Loading User Symbols
    Loading unloaded module list
    .........................
    Unable to load image atikvmag.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikvmag.dll
    *** ERROR: Module load completed but symbols could not be loaded for atikvmag.dll
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 0, ab8ac530, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** Your debugger is not using the correct symbols ***
    *** ***
    *** In order for this command to work properly, your symbol path ***
    *** must point to .pdb files that have full type information. ***
    *** ***
    *** Certain .pdb files (such as the public OS symbols) do not ***
    *** contain the required information. Contact the group that ***
    *** provided you with these symbols if you need this command to ***
    *** work. ***
    *** ***
    *** Type referenced: nt!_KPRCB ***
    *** ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : atikvmag.dll ( atikvmag+d7c7 )

    Followup: MachineOwner
    ---------
  2. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    Please follow this to post your minidumps, the one above has a problem with it. Was the code 5 not actuially 50, error 5 relates to XP SP2.

  3. eamesj1

    eamesj1 Newcomer, in training Topic Starter

    I've uploaded the minidump files for the last 3 errors.

    Attached Files:

  4. eamesj1

    eamesj1 Newcomer, in training Topic Starter

    Bump. Also, I'm uploading my latest BSOD dump report.

    Attached Files:

  5. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    I have checked the four minidumps and they all point to your ATI drivers, ativvaxx.dll which is a Radeon driver and atikvmag.dll (Virtual Command And Memory Manager) is a component from the software Virtual Command And Memory Manager ATI.

    There is likely to be a compatability issue causing this problem. You should check you have the correct drivers for Windows XP and that you are not using ones for later versions of windows.
  6. eamesj1

    eamesj1 Newcomer, in training Topic Starter

    Thank you for responding.

    I am currently using this driver for my graphics card:

    AMD Catalyst 11.2 Hotfix for Windows XP Professional and Home Edition
    (I'd post a link but I'm not allowed to but I downloaded this driver from the amd website.)


    The drivers successfully installed and the only issues I have are with viewing flash vidoes (like youtube) and playing Star Craft 2. Everything else works. Whenever I uninstall the drivers and have no driver assigned to the video card I am able to watch flash videos. It's weird.

    How do you check which version of windows drivers your computer is using? I know that I have Windows XP with service pack 3 installed. I don't know if SP3 has had any updates to it that I may have missed.

    Also, a part of me is really thinking this problem is being caused due to my power supply not being good enough. Is it possible that when using a program like star craft 2 that requires a lot of system resources (and power) the graphics card fails to get enough power and causes the video memory error?
  7. eamesj1

    eamesj1 Newcomer, in training Topic Starter

    Put a new psu in and I'm still getting the BSOD whenever I try and play SC2 or watch youtube videos so the problem definitely has something to do with the drivers. I'm just not really sure what I should be doing at this point to try and fix this. Any suggestions would be much appreciated.
  8. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    Sorry not to have got back here but been away for a while.

    Obviously we can now cross the power supply off the list.

    Two suggestions, first try and see if using an older version of the driver will work. You could also try running the PC with just one memory stick installed and then swap them around to see if the error only occurs with one of the sticks.

    What is the configuration of your memory, do you have the same amount of memory in each channel. Also check that the recommended voltage for the sticks is set correctly in your bios.
  9. eamesj1

    eamesj1 Newcomer, in training Topic Starter

    I fixed the problem a couple weeks ago. The issue was resolved when I upgraded my BIOS and motherboard chipset. Once I did that everything started to work correctly. I appreciate everyone's responses.
  10. Mark56

    Mark56 TechSpot Paladin Posts: 2,271

    Glad to hear you got it fixed.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.