Files are attached per instructions.
I have saved a string of the memory dump files for different occurances. There should be 11 total, but if the program only picked up the one I will post the others.
Windows 7
x64
Original install
System Builder Version
System built May 2010 with all new parts
OS was installed in May 2010
All updates, sans some "recomended" updates, installed
The MSINFO32 file in the uploaded reports is corrupt. Not unusual, but I rely on this report. Please do the following:
All of the BSOD errors are STOP 0x1A - Memory Management errors. Please follow the directions here to run a free memory diagnostic test: Memory Diagnostics (read the details at the link)MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post. Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).
If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type "msinfo32 /nfo C:\Users\Public\Desktop\TEST.NFO" (without the quotes) and press Enter. Then navigate to the C:\Users\Public\Desktop directory to retrieve the TEST.NFO file. If you have difficulties with making this work, please post back.
If the memory test passes, then please run Driver Verifier according to these directions:
BSOD BUGCHECK SUMMARYUsing Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:
More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced usersCode:Delete these registry keys (works in XP, Vista, Win7): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Code:Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060611-29640-01.dmp] Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Mon Jun 6 10:16:52.956 2011 (UTC - 4:00) System Uptime: 0 days 0:00:28.939 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 ) BUGCHECK_STR: 0x1a_41790 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: svchost.exe FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 Bugcheck code 0000001A Arguments 00000000`00041790 fffffa80`0239b920 00000000`0000ffff 00000000`00000000 BiosVersion = FE BiosReleaseDate = 12/23/2010 CPUID: "Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz" MaxSpeed: 2800 CurrentSpeed: 2798 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ`` Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060611-27861-01.dmp] Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Mon Jun 6 09:55:00.355 2011 (UTC - 4:00) System Uptime: 0 days 0:05:31.338 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 ) BUGCHECK_STR: 0x1a_41790 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: avgmfapx.exe FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 Bugcheck code 0000001A Arguments 00000000`00041790 fffffa80`012f9de0 00000000`0000ffff 00000000`00000000 BiosVersion = FE BiosReleaseDate = 12/23/2010 CPUID: "Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz" MaxSpeed: 2800 CurrentSpeed: 2798 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ`` Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052911-22027-01.dmp] Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Mon May 30 00:54:59.271 2011 (UTC - 4:00) System Uptime: 0 days 6:41:03.255 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 ) BUGCHECK_STR: 0x1a_41790 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: nTuneCmd.exe FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 Bugcheck code 0000001A Arguments 00000000`00041790 fffffa80`022df220 00000000`0000ffff 00000000`00000000 BiosVersion = FE BiosReleaseDate = 12/23/2010 CPUID: "Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz" MaxSpeed: 2800 CurrentSpeed: 2798 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ`` Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052811-31527-01.dmp] Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Sat May 28 12:37:31.554 2011 (UTC - 4:00) System Uptime: 0 days 0:05:39.538 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 ) BUGCHECK_STR: 0x1a_41790 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: avgmfapx.exe FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 Bugcheck code 0000001A Arguments 00000000`00041790 fffffa80`01dd8220 00000000`0000ffff 00000000`00000000 BiosVersion = FE BiosReleaseDate = 12/23/2010 CPUID: "Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz" MaxSpeed: 2800 CurrentSpeed: 2798 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ`` Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052411-18798-01.dmp] Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631 Debug session time: Tue May 24 09:26:54.884 2011 (UTC - 4:00) System Uptime: 0 days 0:00:51.868 Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 ) BUGCHECK_STR: 0x1a_41790 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: Skype.exe FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024 Bugcheck code 0000001A Arguments 00000000`00041790 fffffa80`023c06a0 00000000`0000ffff 00000000`00000000 BiosVersion = FE BiosReleaseDate = 12/23/2010 CPUID: "Intel(R) Core(TM) i7 CPU 930 @ 2.80GHz" MaxSpeed: 2800 CurrentSpeed: 2798 จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Here are the sysinfo files. I am currently running the driver verifier. I will follow your instructions when I get a BSOD. Though it has not crashed yet I am getting graphical anomalies on the windows I open and on the taskbar. I will run some games and see if it persists in heavy use of the Vid Card.
Thank you very much for your help!
rwt
Lot's of STOP 0x117 errors in the MSINFO32 report. They are troubleshot the same way as STOP 0x116 errors, so please follow the steps here: STOP 0x116: VIDEO_TDR_ERROR troubleshooting
You may want to try these free video stress tests:
FurMark download site: FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net
FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
NOTE: Set the alarm to go off at 90บC. Then watch the system from that point on. If the system doesn't display a temperature, watch it constantly and turn it off at the first sign of video problems. DO NOT leave it it unmonitored, it can DAMAGE your video card!!!
- Click "Quit" to exitMore Video Stress Tests:
1. Thanks to VirGnarus for finding this test: https://simtk.org/home/memtest
2. Two other video stress tests (may be more stressful than FurMark):
Video Memory stress Test - ะะะ NVIDIA / ะฃัะธะปะธัั / VMT
Artifact Locator - ะะะ NVIDIA / ะฃัะธะปะธัั / Artifact Locator
Sorry, but I don't read the language that this website is made in.
3. Another interesting test that came to my attention: Download - OCCT Website english
USE AT YOUR OWN RISK - the program doesn't have a whole bunch of safety features to protect you from yourself!
I don't believe heat is an issue as the GPU temp rarely goes above 65 C. My understanding is that is a reasonable number for this GPU.
I have also ran memtest for at least 5 passes and encountered no errors.
I will also do the video stress tests and let you know how those go.
rwt
I ment to ask...
are the video tests testing specifically video memory and not system memory?
rwt
In general, yes they are testing video memory rather than system memory. But you've got to read the documentation for each test to see actually what they're stressing. MemTest tests memory by running different standard patterns and looks for problems, stress testing stresses the system/component and looks for failures in that component.
I've got a story to tell about video temps. A couple of years ago we had a new system on the bench for testing. It had video issues. I ran tests on the video card and it showed normal temps (around 75บC). Yet the system still persisted in having video issues.
So, being curious, I started to fuss around inside the case (checking connections, pulling/tugging on parts, etc). When I touched the video card I severely burnt my fingers! (and said several bad words!). We pointed a fan at the video card and the video issues stopped - so we replaced the video card and the customer went home happy!
So, we look for video issues when running stress tests - and that's a clue that there may be something wrong with the video card. When we run FurMark we run it until the GPU temperature stabilizes (usually in the 90บC range) and look for video issues while it's doing this.
Hello,
Thanks again for all your help. There was another crash on the 13th while my wife was using the computer. I have attached the minidump, but the main dump file was too big to upload even zipped.
I tried to run prime95, but seemed to have some problems though I am not sure if they are related to the driver verifier running at the time.
What issues are you having with Prime95? Have you run Furmark?
The memory dump is a Driver Verifier Enabled memory dump blaming nvoclk64.sys -
- Are you overclocking your system/video card? If so, stop and reset the system to default values
- Then, uninstall the nvoclk64.sys driver software (which dates from 2009). This is most likely a component of nVidia System Tools or System Monitor and there is no newer version available. It's most likely a part of one of these program groups:
- Turn off Driver VerifierStart Menu\Programs\NVIDIA Corporation\3D Vision Public:Start Menu\Programs\NVIDIA Corporation\3D Vision Public
Start Menu\Programs\NVIDIA Corporation\NVIDIA Control Panel Public:Start Menu\Programs\NVIDIA Corporation\NVIDIA Control Panel Public
Start Menu\Programs\GIGABYTE\GIGABYTE VGA @BIOS Timmons-PC\Robby:Start Menu\Programs\GIGABYTE\GIGABYTE VGA @BIOS Timmons-PC\Robby
NVIDIA System Monitor "c:\program files (x86)\nvidia corporation\nvidia system monitor\nvmonitor.exe" startup Timmons-PC\Robby Startup
- Test for further BSOD's
My memory speed and timings are the only OC that I have. The MB is 1066 and I OC to the memory spec of 1333. The video card is factory over clocked from Gigabyte. Should I try and set the stock specs on the video card?
I turned off Driver Verifier and reran Prime95. Prime95 worked correctly, as far as I can tell. The CPU temps jumped to over 90 C, in less than a min and I terminated the program. There were no reported errors. I was not comfortable running the test for any length of time with the temps at those levels. Should I do anymore with Prime95?
I have run FurMark a couple of times. Without MSAA the temp would get up to 86 C after about 5 min and then level off. With MSAA the temp was slower to rise but did eventually make it up to about the same temp before stabalizing. The avg FPS were 22 and 14 respectively. The GPU fan speed was 93% at the hottest GPU temps. I never noticed any errors during the tests.
Given some of the randomness of my issues it is possible my sys memory is faulty, but the memtest couldn't pick it up? If you don't think so then could a faulty video card cause these types of issues as many of the errors involve drivers related to the video card?
The reason I am working through all this is because I don't want to do an RMA if I am not really sure which component is the issue. The Nvidia 400/500 series lockup club! - NVIDIA Forums - this thread describes some of the issues I have been having, but often not to the extreme described by other users. If you choose to read through I would value your opinion on my situation in relation to the thread claims.
Kind regards,
rwt
Quote