Overclock.net › Forums › Intel › Intel - General › PC Randomly Shuts Off During RAM Intensive Applications
New Posts  All Forums:Forum Nav:

PC Randomly Shuts Off During RAM Intensive Applications - Page 4

post #31 of 155
I should further elaborate on the previous dump you attached to shed more light on the issue at hand.

NOTE: If overclocking, please reset the system to default values while troubleshooting it. This includes CPU, RAM, GPU overclocking. You're more than welcome to put your stocks back to clock after we've diagnosed your issues!!!!!

The first thing I recommend doing if overclocks aren't the issue is fully uninstalling and reinstalling your nVidia video card drivers, as a bad driver installation can cause 116 bugchecks, especially since the culprit is being pointed to nvlddmkm.sys (nVidia video card drivers). If these issues started happening after a driver update, rollback the video card drivers you installed to an earlier version that worked previously without issue.

If drivers do not help, your issue may be heat related, inadequate cooling, dust buildup in the fans or pci-e slot, so make sure your rig is being cooled adequately.

Run Furmark to test your video card to ensure that the card(s) itself is running as intended:
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).
- Click "Quit" to exit

The following hardware issues can cause a TDR event:
- Failing overclock on CPU or GPU (stop overclocking)
- Bad sector in memory resulting in corrupt data being communicated between GPU and the system (either video or system memory) ( MemTest and a video memory stress test: |MG| Video Memory Stress Test 1.7.116 Download )
- Corrupt hard drive/windows install resulting in corruption to the system registry or the page file (Hard drive diagnostics ( HD Diagnostic ), reset your pagefile

Memtest download to test your RAM: http://www.memtest86.com/

^^ Since you've already done this and got new RAM, skip this step.

To "reset" the pagefile, follow these instructions:
Use this technique to "reset" your pagefile:
a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.
-Then click on the Advanced tab,
-then on the Performance Settings Button,
-then on the next Advanced tab,
-then on the Virtual Memory Change button.
b ) In this window, note down the current settings for your pagefile (so you can restore them later on).
-Then click on the "No paging file" radio button, and
- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.
-Click OK to exit the dialogs.
c ) Reboot (this will remove the pagefile from your system)
d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step b ). Follow the steps all the way through (and including) the reboot.
e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"
In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.
Let the program run and post back what it says when it's done.

- Over heating of GPU or CPU again resulting in corrupt data being communicated. (Point a house fan at the video card, take temperature readings from the card with an IR detector (or your finger - but be very, very careful!!!)

- GPU failure due to any sort of issue from insufficient power(VERY common) to heat. (check the power leads, use a multimeter to check the power output, try another, more powerful PSU)

The following software issues can cause a TDR event:
-Incompatible drivers of any sort (either GPU, sound, etc) ( http://www.microsoft.com/windows/com...s/default.aspx )
-Messy registry (I doubt this and don't approve of registry cleaners)
-Known vista issues resounding around multiple displays, aero, dreamscape, and various display drivers. (none known for this OS)
-Known vista issues that sometimes cause corrupt information to be sent to the video card from system memory (will be addressed completely in SP2, has had various fixes applied since vista's release) (none known for this OS)
-Bad direct x files (uninstall, then reinstall DirectX)
-bad system files (System File Checker - was run above)
-Bad driver (some drivers will cause an event due to internal bugs, however these are not nearly as common as many think due to all of the previous things causing the same symptom) - (remove all 3rd party programs and check to be sure drivers aren't loading. Then install only the necessary 3rd party stuff, and ensure it's the latest version and that it's compatible with Windows 7)

In regards to your question as to whether you can see what programs were on at the time, you can only see what DRIVERS were loaded at the time, and you'd have to 1 by 1 go through every driver finding the source and what program uses it, which will take a bit. Regardless, I believe your issue is hardware rather than software, especially after a reformat, so do some hardware testing that I have provided above smile.gif
post #32 of 155
Thread Starter 
Wow... you have really gone above and beyond. Thank you for your time and help on this issue!

I ran sfc /scannow and it failed at 9% as shown below...

CBS.zip 53k .zip file

I have reset pagefile and will double check that nothing is overclocked and run FurMark.

I also created a custom Windows 7 installation using this guide; however, I only removed some unnecessary items. I'm not sure if that caused it or not.

Edit: Ran FurMark... results.
Edited by Cyanide89 - 4/17/12 at 2:53pm
post #33 of 155
My pleasure smile.gif

The CBS log oddly enough isn't showing any "cannot repair" entries, so let's try doing this:

1. Open Elevated Command Prompt (run cmd as admin).

2. Copy & Paste the following command into CMD and press enter:
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

This will place a sfcdetails.txt file on your desktop with only the SFC scan result details from the CBS.LOG in it. In other words, it should make it hopefully easier for us to see what is unrepairable.

Also, Sean's guide is great, so there's no need to worry about any issues with that installation method. As for Furmark, as long as you were able to run Furmark for at least ~20 minutes without seeing any artifacts or receiving crashes, you should be okay.
post #34 of 155
Thread Starter 
VMT Results: GTX590 (Click to show)
Changing video mode to 640x480x16...OK
[4/17/2012 3:04:09 PM] Test started for "Primary Display Driver (NVIDIA GeForce GTX 590)"...
Trying 16bpp RGB:565 mode...OK
Trying 16bpp RGB:555 mode...OK
Trying 16bpp BGR:565 mode...NOT SUPPORTED (Code: 80004001)
Trying 32bpp RGB:888 mode...OK
Trying 32bpp BGR:888 mode...NOT SUPPORTED (Code: 80004001)
[4/17/2012 3:14:59 PM] Pass completed (0 errors found).

It wouldn't let me test over 1024mb of video memory and I don't know how to test all 3gb if possible.

And here are the sfc results:
sfcdetails.zip 7k .zip file
post #35 of 155
The file it's failing to repair is "authui.dll". I find this odd as it's a fresh Windows install as you have said.

Let's try a CHKDSK before we move on with that.
Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click .
post #36 of 155
Thread Starter 
Schedule Disk Check and rebooted... no errors found and then ran SFC again. Stopped at 9% again. Should I attach the report as well?
post #37 of 155
No, not right now, here's what I want you to do first:

Driver Verifier:
Read the following to enable Driver Verifier. Use Driver Second if Memtest finds nothing, as it's likely a software / driver issue, we just aren't being told what it is, and hopefully Driver Verifier will than force a crash if it finds the violating driver.

Before enabling Driver Verifier, my recommendation is to set a backup / restore point as in severe cases Driver Verifier can break your Windows. If you have difficulty getting into Windows, boot into Safe Mode and disable Driver Verifier there.
post #38 of 155
Thread Starter 
Alright, I've enabled driver verifier. What should I be looking for, and what do I do when I find it?
post #39 of 155
Originally Posted by Cyanide89 View Post

Alright, I've enabled driver verifier. What should I be looking for, and what do I do when I find it?

Driver Verifier simply stresses all 3rd party drivers. When and if it finds a culprit, it will force a crash and write a very detailed verifier enabled crash dump which you will then attach here.

If you don't crash within ~24 hours (do not keep it enabled after 24 hours, it's unnecessary as Driver Verifier should definitely find a culprit by then), the issue is likely hardware, and you'll want to disable Driver Verifier.
post #40 of 155
Thread Starter 
I've noticed that my GPU temps have gone up to 50 Celsius when just browsing computer files... could this be a sign?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel - General
Overclock.net › Forums › Intel › Intel - General › PC Randomly Shuts Off During RAM Intensive Applications