BSOD when playing game.

Alrighty, so I bought this game (Red Alert 3) about a month ago but my computer didn't meet the requirements so my bro went out and bought a new video card (Geforce 8400 GS for PCI) and more memory.

I installed the game and it loaded perfectly but 2 seconds after actually playing it I got the Blue screen of death and it restarted.

So I did a little research and thought my power supply was the problem. I realized the graphics card min req. was 400W so I went out and bought a new one yesterday (550W), reinstalled the game and was still having the same problem. I uninstalled and reinstalled the graphics driver in safe mode, nothing happened. At this point I really have no idea what the problem could be. sad.gif Could anyone help me figure out whats going on?

Computer Specs:
Compaq Presario,Windows XP SP3
CPU: AMD Athlon XP 2800+, 2.08GHz
MB: ASUS A7V8X-LA
RAM: 1.43GB



This is the BSOD error I got:

STOP:0x0000007F (0x0000000D, 0x00000000, 0x00000000, 0x00000000)

BCCode : 1000007f BCP1 : 0000000D BCP2 : 00000000 BCP3 : 00000000
BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 768_1
C:\DOCUME~1\Owner\LOCALS~1\Temp\WERd37f.dir00\Mini031509-05.dmp
C:\DOCUME~1\Owner\LOCALS~1\Temp\WERd37f.dir00\sysdata.xml

I used WinDbg for the Minidump file and got:

Loading Dump File [C:\WINDOWS\Minidump\Mini031609-05.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 = 0x8055b1c0
Debug session time: Mon Mar 16 17:01:31.406 2009 (GMT-5)
System Uptime: 0 days 2:37:48.164
************************************************************
*********
* 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
.................
************************************************************
*******************
* *
* Bugcheck Analysis *
* *
************************************************************
*******************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007F, {d, 0, 0, 0}

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

*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
************************************************************
*************
*** ***
*** ***
*** 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 : nv4_disp.dll ( nv4_disp+398d30 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000d, EXCEPTION_GP_FAULT
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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

***** 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+ *
************************************************************
*********

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 499c9aa2

BUGCHECK_STR: 0x7f_d

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

LAST_CONTROL_TRANSFER: from e24c0a30 to e5f7fc03

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
b477297c e24c0a30 bf3aad30 e68153c0 e24c092c 0xe5f7fc03
b4772980 bf3aad30 e68153c0 e24c092c e68153c0 0xe24c0a30
b4772984 e68153c0 e24c092c e68153c0 e24c0890 nv4_disp+0x398d30
b4772988 e24c092c e68153c0 e24c0890 e24c0a30 0xe68153c0
b477298c e68153c0 e24c0890 e24c0a30 e24ba800 0xe24c092c
b4772990 e24c0890 e24c0a30 e24ba800 bf3aad30 0xe68153c0
b4772994 e24c0a30 e24ba800 bf3aad30 b4772b0c 0xe24c0890
b4772998 e24ba800 bf3aad30 b4772b0c bf23e997 0xe24c0a30
b477299c bf3aad30 b4772b0c bf23e997 e24c092c 0xe24ba800
b47729a0 b4772b0c bf23e997 e24c092c e24c0a30 nv4_disp+0x398d30
b47729a4 bf23e997 e24c092c e24c0a30 bf3aad30 0xb4772b0c
b4772b0c bf1a6307 e24c0890 000001dc b4772b64 nv4_disp+0x22c997
b4772b10 e24c0890 000001dc b4772b64 b4772b78 nv4_disp+0x194307
b4772b14 00000000 b4772b64 b4772b78 00000001 0xe24c0890


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_disp+398d30
bf3aad30 ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nv4_disp+398d30

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME: nv4_disp.dll

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

^^ That would be a good thing to do,also if u dont know how to do a clean install here is how :
1_Go to control panel and uninstall the driver from there
2_Reboot and go to safemode and open driver sweeper and click on clean(this removes some files which werent deleted)
3_Boot normally and Install the new driver

BSOD sometimes happens in games,dont take it very serious if doesnt happen randomly.

try a motherboard bios update. thats a geforce 8400gs "PCI". it might help.

You posted "RAM: 1.43GB" Does that meet the minimum requirements for the 8400gs? Not sure about Nvidia, but my ATI 3870 w/ 512MB uses system RAM for games.

So does it happen randomly ?

In every game ?

If u have only have the problem with one game,then your card may be fine,maybe downloading new vga drivers and patches may fix it

Its strange,test the card in another PC if possible with the same game and see if it works fine