New
#11
Well no BSOD's so far. So it might have worked :)
But i will not close thread yet, giving it some more time.
Thanks for the help.
Well no BSOD's so far. So it might have worked :)
But i will not close thread yet, giving it some more time.
Thanks for the help.
46 BSODs / 22 days ~ 2 BSODs every day.
You're doing very well so far, compared to your average, but of course this thread will always remain open, so you can update it if need be.
Happy computing!
Oh noes, back with more BSODs :/
attached zip.
Test your RAM: RAM - Test with Memtest86+
Test your hard drive too, using this tool: | Seagate
I just noticed your Atheros NIC drivers are old:Install these updated ones: Atheros CommunicationsCode:L1C62x64.sys Wed Apr 01 01:09:17 2009 (49D2F6FD)
...Summary of the Dumps:Code:Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Nov 1 16:19:21.609 2010 (UTC - 4:00) System Uptime: 0 days 2:06:01.404 BugCheck 1000007E, {ffffffffc0000005, fffff88014badffb, fffff88002e2f698, fffff88002e2ef00} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+ab ) PROCESS_NAME: System BUGCHECK_STR: 0x7E ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Debug session time: Mon Nov 1 11:40:54.384 2010 (UTC - 4:00) System Uptime: 0 days 0:37:40.179 BugCheck 3B, {c0000005, fffff88001005141, fffff880073fc950, 0} Probably caused by : fltmgr.sys ( fltmgr!TreeUnlinkMulti+51 ) BUGCHECK_STR: 0x3B PROCESS_NAME: svchost.exe ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Sorry for the delay of 127 days O_o
I did a memtest (using memory stick) and used the seagate tool to test my hd. 0 errors.
However i have a bunch of new dumps if you don't mind. (actually only 2)
thanks again.
30 minutes after posting in the forum i got one more, this time while playing "minecraft"
attached the dump.
Hello again, welcome back!
I'll just explain the dumps, that will give you your conclusion. The latest dump blames hardware outright, but mentions that the nVidia display drivers were somehow related. The middle dump blames hardware again, with a specific bugcheck that means hardware failure. The third dump doesn't blame anything of consequence, but shows that dwm.exe (the Windows graphics effects process) was "on top" at the time of the crash.
As you can see, this is most likely a physical hardware issue, specifically video card. Before going out and purchasing new hardware, though, give the drivers an update:New drivers can be found here: NVIDIA DRIVERS 266.58 WHQLCode:nvlddmkm.sys Fri Jul 09 17:15:58 2010 (4C37918E)
If that doesn't help, you might as well just run a couple of diagnostics just to make sure. I recommend the Blend and Small FFTs Prime95 tests, and 7 passes of Memtest86 overnight.
https://www.sevenforums.com/tutorials...t-prime95.html
RAM - Test with Memtest86+
...Summary of the dumps:
Code:Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Tue Mar 8 15:25:13.563 2011 (UTC - 5:00) System Uptime: 0 days 0:42:02.968 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : hardware ( nvlddmkm+f97cd ) DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 PROCESS_NAME: System FAILURE_BUCKET_ID: X64_IP_MISALIGNED_nvlddmkm.sys SystemProductName = MS-7599 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Mon Mar 7 15:24:28.546 2011 (UTC - 5:00) System Uptime: 0 days 0:00:11.341 Probably caused by : hardware BUGCHECK_STR: 0x124_AuthenticAMD DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии`` Built by: 7600.16695.amd64fre.win7_gdr.101026-1503 Debug session time: Mon Mar 7 15:21:30.577 2011 (UTC - 5:00) System Uptime: 0 days 3:09:55.998 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4904 ) BUGCHECK_STR: 0xc4_91 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: dwm.exe FAILURE_BUCKET_ID: X64_0xc4_91_nt!_??_::FNODOBFM::_string_+4904 SystemProductName = MS-7599 ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
You are getting STOP 0x124 error - see this: Stop 0x124 - what it means and what to try
When i download and install those drivers. I see a black box around the actual screen area.
If i change resolution, said box becomes smaller/larger, this forces me to use max resolution. (this is actually why i downgraded the driver again months ago, since some programs run using a specific resolution, thus creating the black border)
It is described here. Don't know if there is a fix?
Low resolution always stretched to full screen - NVIDIA Forums <- specially the last angry post. :)
I suggest you keep the new drivers for a time, until you determine whether they have solved the problem or not. If do, feel free to play around with different versions; there are many driver releases between July 2010 and March 2011!