Okay then. I shall do as you wish and put the RAM aside and look at your dumps, starting with the latest one.
----------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8004512010, fffff880061b1f1c, ffffffffc000000d, 3}
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+931f1c )
Followup: MachineOwner
---------
Usual cause: Failing GPU driver.
Driver Reference Table: nvlddmkm.sys.
More info Bug Check 0x116.
----------
Code:
0: kd> lmvm nvlddmkm
start end module name
fffff880`05880000 fffff880`06327000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Fri Jan 18 14:22:15 2013 (50F94C87)
CheckSum: 00A92B69
ImageSize: 00AA7000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please follow this and install the most stable 314.22 WHQL driver;
Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.
- Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed). - Now follow Drivers - Clean Left over Files after Uninstalling
- Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
----------
After changing the driver, please stress test the graphics card using Furmark GPU Stress Test.
Information
During the test please check the screen for
artifacts.
The purpose of this test is to make your machine crash and create dump files so that we can pinpoint the cause of your problem.
Tip
Please run Furmark once when your machine has just started, and once again when your machine has been active for several hours.
----------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: ContextRecord ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
Followup: MachineOwner
---------
Usual cause: Incompatible hardware, faulty drivers.
More info Bug Check 0x1E.
We see that this dump is pointing to ntkrnlmp.exe as probable cause, but since that is a Windows driver, it shouldn't crash on it's own and is most likely not the cause. Let's see what the dps command gives us.
----------
Code:
2: kd> dps fffff88003186000 fffff8800318c000
fffff880`0318aa38 00000000`00000000
fffff880`0318aa40 00000000`00000021
fffff880`0318aa48 fffff880`03c37c9fUnable to load image nvmf6264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvmf6264.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6264.sys
nvmf6264+0xcc9f
.
.
.
fffff880`0318ac30 00001f80`0010001f
fffff880`0318ac38 0053002b`002b0010
fffff880`0318ac40 00210286`0018002b
fffff880`0318ac48 fffff880`05a8ce13Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
nvlddmkm+0x1d6e13
Driver Reference Table: nvmf6264.sys, nvlddmkm.sys.
Your nvidia video driver and your nvidia nForce network driver appear to be failing. This will be solved by following my suggestions from the previous dump file.
----------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8007b33010, fffff88006202f1c, ffffffffc000000d, 3}
Unable to load image nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+931f1c )
Followup: MachineOwner
---------
And there you have it. Three consecutive BSoD's all blaming your GPU driver.
----------
Code:
0: kd> !sysinfo machineid
BiosVendor = American Megatrends Inc.
BiosVersion = 0704
BiosReleaseDate = 05/19/2009
As you previously stated, your BIOS version is indeed very old. I would recommend on updating it, but if you're afraid to do it, then you shouldn't.
But, since you stated this;
...if my problems persist , i will simply throw the damn thing in the bin, and buy a new rig...
I see no harm in trying. If it works, it works, and if it doesn't, do as you stated above.
Whatever option you choose, do note that it's a very good idea to make regular backups in case that something happens.
Good luck and keep us posted,
Nommy