Sign in with
Sign up | Sign in
Your question
Solved

Installed Gigabyte Radeon HD 4650 AGP and now SC2 crashes

Last response: in Graphics & Displays
Share
March 25, 2011 2:41:00 AM

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 StarCraft 2 (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, 0x0000005 (random 0's, numbers, and letters)

Dump physical memory
Memory Dump complete

Like I said earlier I've swept my computer of ati drivers and successfully installed the new ones (I've done this multiple times) so I'm not sure if this is a driver issue.

I've tried removing the new ram I put in since the error says it's a memory error but it doesn't work.

I think this may be related to a power supply issue but I'm not sure. The card recommends having a 400w power supply and I do only have a 380w supply. However, according to multiple power supply estimators I should only need 340w's to run my current set up. Also, normally when the computer shuts off do to a thermal issue, it usually just shuts itself off without prompting a blue screen.

I'm at a loss here as to what the problem may be. Any help would be much appreciated!
March 25, 2011 4:06:27 PM

Anybody have any ideas??
m
0
l
March 26, 2011 3:14:24 AM

Ok, so 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
---------
m
0
l
Related resources
March 28, 2011 9:41:21 AM

have you check your cpu and gpu temp? also you can run memtest86 to test if your RAM are faulty or not. other than that it might driver related problem. did you get the latest driver for your new card?
m
0
l

Best solution

March 28, 2011 9:49:00 AM

driversweeper, driversweeper, driversweeper. Run that and follow the instructions for using it properly. then download and install the latest ati drivers for your video card.
Share
April 4, 2011 1:01:49 AM

I fixed the problem about a week ago. I needed to upgrade my BIOS and download the latest drivers for my motherboard. Once I did that everything started working correctly. I appreciate all of the responses.
m
0
l
April 4, 2011 12:55:08 PM

good, things are working for you now :) 
m
0
l
April 14, 2011 2:09:07 AM

Best answer selected by eamesj1.
m
0
l
!