New
#1
Win 7 x64 and GeForce 7300 LE bsod
Good morning all,
System Specs:
mobo: ASUS M2A-VM
cpu: Athlon 64 x2 3800+
psu: 550w
gfx: GeForce 7300 LE
ram: 4gb ddr2 800mhz Patriot
hdd: (1) 500gb (1) 20gb
media: cd/dvd burner, multi card reader
other: 4 fan controller
I have been going back and forth with this pc and I'm finally almost done... For some history...
I originally had this pc (same specs, except a 1tb hdd before) running the same O/S, Windows 7 64bit Ultimate N and it ran great. Then my son came charging through the living room and hit the computer and ultimately got the hdd needle stuck, effectively breaking the hdd...
So I went and bought a new hdd...
I only had cds at the time, so I burned the xp iso (yes all my windows are legit) and installed xp 64bit. Everything worked as expected. All happy I prepared to install Win 7...utter fail. Setup would crash, stall, I would get BSOD and so on...
After some hard searching, I removed the GeForce 7300 LE card and removed 4gb of memory. I finally was able to install Win 7! After boot up, I powered down and install the remaining 4gb, boot up went fine. Powered down after doing all available updates and reinstalled the GeForce7300 LE, boot up fine.
Now Windows 7 goes and installs it's driver for the card and says I need restart, so I do. BAM, I get the BSOD. Luckily, I am able to boot into safe mode, still using that card. So I go to nVidia, have them detect my settings and I download the most current driver package, install, restart...bsod...
Now I am in safe mode and can't find an answer...
I would also like to stress that this system worked perfect before and during xp. Can anyone help me!? Below is the output from the Memory dump file from bsod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02860000 PsLoadedModuleList = 0xfffff800`02a9de50
Debug session time: Sat Oct 23 01:58:16.129 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:18.345
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
........................................................
Loading User Symbols
Loading unloaded module list
....
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8007083010, fffff88004747d0c, 0, 2}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.sys -
***** 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 ***
*** ***
*************************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvlddmkm.sys -
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+12ed0c )
Followup: MachineOwner
---------