If you replace everything - the original problem will go away.
But you'll have a new problem - much less money!
Driver Verifier is supposed to cause BSOD's. If it doesn't cause a Driver Verifier BSOD in 36 hours of use, we presume that it's not a 3rd party driver problem (because that's what we set it to test for).
In this case, the last memory dump was a Driver Verifier enabled memory dump - and it blamed a Windows driver (dxgmms1 - a DirectX driver). Since we tested for 3rd party drivers, this is either a hardware problem or a Windows problem (since Driver Verifier didn't point out a 3rd party driver when it caused the crash).
Also, the last 3 memory dumps were all different - which usually suggests a hardware issue. BUT, the line blurs a bit here - as these hardware issues also include:
- compatibility issues
- low-level driver problems
- malware
We've checked for the most common of the above issues. I see no sign of compatibility, low-level driver problems, or anything suggestive of malware. So, again, we must suspect hardware.
So, have you run all of the hardware tests that I suggested? I can't recall you posting the results of a CPU stress test. How about the other video tests (other than Furmark and the MemtestG80 and MemtestCL test thingy)
If so, then we've gotta start looking at other things (the cheap keyboard is a good idea for now).
Then try this procedure to start ruling things out:
Hardware Troubleshooting Via System Stripdown
Remember from earlier - if it's video related, and we rule out the video stuff, then we've gotta suspect the motherboard.
Good luck!
Further info on BSOD error messages available at:
http://www.carrona.org/bsodindx.html
The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this.
DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the
older drivers from the device manufacturer's website - or uninstall them from your system.
Reference links are included below.
-
DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.
Code:
[FONT=lucida console]
vmbus.sys Sat Nov 20 04:57:29 2010 (4CE79B89)
winhv.sys Sat Nov 20 04:20:02 2010 (4CE792C2)
nvstor.sys Fri Mar 19 16:45:11 2010 (4BA3E257)
nvstor64.sys Fri Apr 09 05:22:41 2010 (4BBEF1E1)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
dump_nvstor64.sys Fri Apr 09 05:22:41 2010 (4BBEF1E1)
MpFilter.sys Wed Apr 06 16:07:29 2011 (4D9CC801)
atikmpag.sys Mon Dec 05 21:12:14 2011 (4EDD79FE)
nvmf6264.sys Thu Mar 04 20:04:39 2010 (4B9058A7)
atikmdag.sys Mon Dec 05 21:52:23 2011 (4EDD8367)
AtihdW76.sys Tue Oct 18 03:09:49 2011 (4E9D263D)
MpNWMon.sys Wed Apr 06 16:07:23 2011 (4D9CC7FB)
NisDrvWFP.sys Wed Apr 06 16:08:53 2011 (4D9CC855)
mbam.sys Wed Nov 02 09:07:48 2011 (4EB140A4)
ALSysIO64.sys Sat Jul 09 20:27:45 2011 (4E18F201)
[/FONT]
http://www.carrona.org/drivers/driver.php?id=vmbus.sys
http://www.carrona.org/drivers/driver.php?id=winhv.sys
http://www.carrona.org/drivers/driver.php?id=nvstor.sys
http://www.carrona.org/drivers/driver.php?id=nvstor64.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=dump_nvstor64.sys
http://www.carrona.org/drivers/driver.php?id=MpFilter.sys
http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys
http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
http://www.carrona.org/drivers/driver.php?id=AtihdW76.sys
http://www.carrona.org/drivers/driver.php?id=MpNWMon.sys
http://www.carrona.org/drivers/driver.php?id=NisDrvWFP.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=ALSysIO64.sys
BSOD BUGCHECK SUMMARY
Code:
[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\022012-19125-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Feb 20 17:13:52.232 2012 (UTC - 5:00)
System Uptime: 0 days 2:12:40.011
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204 )
BUGCHECK_STR: 0x1a_411
DEFAULT_BUCKET_ID: [COLOR=Red]VERIFIER_ENABLED_VISTA_MINIDUMP[/COLOR]
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0x1a_411_VRF_dxgmms1!VIDMM_SEGMENT::MarkResourcesForEviction+204
Bugcheck code 0000001A
Arguments 00000000`00000411 fffff6fc`5006c100 aea00000`a7c47882 f0000000`f0000001
BiosVersion = F3
BiosReleaseDate = 06/03/2008
CPUID: "Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz"
MaxSpeed: 2200
CurrentSpeed: 2200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\022012-16926-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Feb 20 05:07:20.822 2012 (UTC - 5:00)
System Uptime: 0 days 0:40:11.476
Probably caused by : dxgkrnl.sys ( dxgkrnl!DXGADAPTER::DdiOpenAllocation+4d )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: JagexLauncher.
FAILURE_BUCKET_ID: X64_0x3B_dxgkrnl!DXGADAPTER::DdiOpenAllocation+4d
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff880`0551ccc1 fffff880`0494ca00 00000000`00000000
BiosVersion = F3
BiosReleaseDate = 06/03/2008
CPUID: "Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz"
MaxSpeed: 2200
CurrentSpeed: 2200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021912-15397-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 19 14:58:43.347 2012 (UTC - 5:00)
System Uptime: 0 days 0:20:14.321
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+447c6 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: dwm.exe
FAILURE_BUCKET_ID: X64_0x50_nt!_??_::FNODOBFM::_string_+447c6
Bugcheck code 00000050
Arguments fffff7ff`f2dc73c4 00000000`00000008 fffff7ff`f2dc73c4 00000000`00000002
BiosVersion = F3
BiosReleaseDate = 06/03/2008
CPUID: "Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz"
MaxSpeed: 2200
CurrentSpeed: 2200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/FONT]