Win 7 x64 and GeForce 7300 LE bsod

[jasonwilczak]

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

 

[Crispy]

Um if I'm not mistaken 7300 is beta build right?

 

[yowanvista]

Follow these instructions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[jasonwilczak]

doing the bsod utility now, thanks. not sure about the beta build thing, i just know that it worked before. i will attach the output as soon as it finishes, then gotta take daughter to ballet class.

 

[jasonwilczak]

Alright here is the generated files from the utility for bsod, also the perfmon/report had an error, i placed the screen shot of the error inside. time to take daughter ballet, i will have limited email support, looking to resolve this issue as soon as possible, thanks guys.

 

[yowanvista]

Alright here is the generated files from the utility for bsod, also the perfmon/report had an error, i placed the screen shot of the error inside. time to take daughter ballet, i will have limited email support, looking to resolve this issue as soon as possible, thanks guys.

Your BSODs are caused by nvlddmkm.sys, part of your Nvidia drivers

Possible causes:bad RAM/PSU, incorrect RAM timings/voltages, bad Graphics card, overheating, outdated driver

Uninstall your Nvidia drivers then use driver sweeper to remove leftover Nvidia files
Guru3D - Driver Sweeper

Then reinstall your Nvidia drivers: NVIDIA DRIVERS 260.89 WHQL

This was likely caused by the following module: nvlddmkm.sys
Bugcheck code: 0x116 (0xFFFFFA8007083010, 0xFFFFF88004747D0C, 0x0, 0x2)
Error: VIDEO_TDR_ERROR

 

[jasonwilczak]

Another attempt...

ok, so I followed the instructions: Uninstalled the drivers and used the clean sweep. This reinstalled the MS NVidia 7300 driver. (System did an auto hardware install thing). So then I rebooted...bsod, I then did an uninstall and then installed the newest nvidia drivers (that you posted), reboot, bsod... Not sure what to do from here... I've attached the zip containing the two newest bsods...

 

[Crispy]

Try and reset the bios back to default, if you have another graphic card switch it with 7300 and see if it blue screens.

 

[jasonwilczak]

bios..

Bios is at default except for RAM voltage which is 1.90 due to the modules i'm using. The onboard graphics works ok, except it is below par... but win 7 will load. However, I must stress that my settings worked fine before and now all of the sudden, (using the same win7 iso) they will not work, I do not understand.

 

[Crispy]

When you say "modules i'm using" you are using what do you mean by this?

 

[jasonwilczak]

I'm using Patriot ddr2 800mhz dual channel ram, (2) 1gb modules and (2) 2gb modules. With the ASUS m2a-vm that I bought, I didn't realize Patriot wasn't part of the QVL for this board. In order for me to use more than 1 stick of the ram, i need to set the voltage at +1.90v. I found this a long time ago when I first built the pc, if it is set to anything else, the pc won't pass POST test when using more than 1 stick.

I did try using 1 2gb stick with the 7300 le card and I still got the same bsod (keeping the voltage settings at default) so I'm fairly sure the ram voltage setting isn't the issue.

And, as I said, the pc worked with the 6gb at 1.90v using the vid card, psu, mobo, cpu, and all the same settings a couple months ago, which is what i don't understand.

 

[jasonwilczak]

Also, I'm curious as to why the card works perfectly fine in safe mode? Using the driver, that appears, to be causing the issue? This I do not understand either... I know safe mode is stripped down, but still..

 

[Crispy]

Run memtest86 and see how it goes: Memtest86.com - Memory Diagnostic

 

[jasonwilczak]

Running memtest86 now on the machine. Will post results when finished. Also, today I tried booting up in normal mode using the onboard graphics, however after a random amount of time (sometimes 2mins, other times an hour) I'd get the white screen and cursor and would have to reboot... not sure if it's just because the onboard graphics isn't enough to handle win 7 or not... it works fine in safe mode though.

 

[jasonwilczak]

Just an update for anyone reading this:
So ran memtest86, although the "offending gfx card" wasn't installed, and the memtest passed completely fine. I then attempted to reinstall the gfx card (7300 le) and re-run the test, just to ensure accurate results, and the monitor wouldn't even turn on... I do believe I uninstalled the nvidia drivers completely, so that may have something to do with it, but who knows... I'm going to try some more possibly in the next couple of days, but I'm at my wits end and probably going to give up on this adventure soon. If anyone comes across any revolutionary ideas to this issue, please let me know...

 

[Crispy]

If you have access to another graphic card slot that in and see how it reacts to it, also try to only use 2x2gb RAM and if it dose not work try the using 2x1gb RAM, if the other graphic card you used (assuming you have access to one) then the most possible cause is the motherboard is faulty in one way.