Solved BSOD 7f, frequent during loads, not ram

[Phaerius]

Had some very frequent full lock ups for awhile now, just recently after doing some ram testing they've turned into blue screens under the same circumstances. Coming up with the error code 7f each time. These most often occur right at the end of a loading bar for various games as well as randomly within said games when run at the higher graphics settings. The previous lockups would be a full freeze with repeating soundloop requiring a hard restart to do anything.

Just replaced my ram with a new set, saw a blue screen after about five minutes so it hasn't done anything to fix the issue. Will attempt to upload a dumpfile, but wondering if I could get an initial opinion on what is most likely.

Running the SF diagnostic tool left me with this exception:
System.IO.IOException: Could not complete operation on some files and directories. See the Data property of the exception for more details.
at Microsoft.VisualBasic.FileIO.FileSystem.FxCopyOrMoveDirectory(CopyOrMove operation, String sourceDirectoryPath, String targetDirectoryPath, Boolean overwrite)
at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveDirectory(CopyOrMove operation, String sourceDirectoryName, String destinationDirectoryName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyDirectory(String sourceDirectoryName, String destinationDirectoryName, Boolean overwrite)
at SF_Diagnostic_Tool.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

[koolkat77]

Try rolling back to a stable Nvidia driver version: Driver Rollback

 

[Phaerius]

This has been occuring for about five months, over the course of many driver installs. I do experience many display driver crashes, screen goes black, get the error message about the driver recovering. As I said however, I've gone through a bunch of rollbacks and updates over the last few months.

 

[koolkat77]

Please upload new reports, and grab all when you do so.

 

[Phaerius]

It's still returning the exception in the first post, I will attach the folder it is bringing to my desktop however.

 

[koolkat77]

Do you have on board graphics?

Can you test the video card on another PC to see if it gives the same BSOD's?

 

[Phaerius]

I'm using a gtx 460, I don't have a compy here to test, though I could try a swap in a week or so at a friends. I do have onboard, I remember using it to test something not long ago.

Is there any chance a cpu fault could cause similar symptoms? I want to avoid replacing my mobo or cpu, if possible. I was hoping it'd be ram, but a full swap did nothing at all to the issue. I figured an examination and trouble shoot would be a better idea than buying a new graphics card without testing some things.

 

[essenbe]

Phaerius, at this point most things are possible, but it is unlikely it is a CPU error unless something has happened with the CPU you haven't told us yet. Ram is the most likely suspect along with the video card. While it is longer and more tedious, I would like to test the ram first. I know you said you replaced the ram, but new ram can have errors too or it could be a bad dim slot on the board. Just remember during these tests, we are testing both the sticks of ram and the dim slots too. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html is the best test we have but takes a long time to run, but it has to run for a full 8 passes on each stick in each dim slot. Each pass is made up of about 10 tests, and each pass tests something different. If you can complete these tests, we can be relatively assured it is not the ram which, by the way, is the most common of the causes of BSODs. The tests are better run over night while sleeping because they take so much time. I would like to see a full 8 passes on each stick which will take around 6-8 hours each. Believe me I know how tedious it can be, we've all been there before.

EDIT: I also forgot to mention, if you are overclocking the CPU or GPU stop. Reset CMOS to defaults. Make sure the ram is running at the manufacturers timings, frequency and voltage and the GPU is running at stock speed. You may also check and see if there are any bios updates for your board.

 

[Phaerius]

I don't overclock and nothing unusual has happened to my system, other than these beginning. I've run memtests on all of the old ram, and I've swapped through all available slots, I was using 8 gigs in 4 slots, and now I'm using 8 gigs in 2. I ran individual memtests as well as a full one with all sticks inserted.

I've never been good at finding bios updates, would I be going through the premade websites ie, hp in my case?

 

[Phaerius]

Going to do some more ram tests in the coming days.

 

[Phaerius]

Just got done a seven hour ram test, 0 errors reported. Going to be swapping a friends card into my compy and testing it under the conditions that cause my issue. Here are some of the little things that have cropped up recently that may lead to it being graphics card.

My computer sometimes hardlocks when I am alt-tabbed from a full screen program, and I close a tab in chrome, the instant I click to close the tab it locks. My display driver crashes when I zoom-in out from a picture, any picture, in windows photo viewer. Crashes during load are frequent, usually at the very end of the load, possibly when graphics are starting to be rendered. Hardlocks are most frequent in games with graphics turned near max, and have gotten much more frequent in general since I switched to a higher resolution monitor. Things I ran previously fine at a lower resolution are now hard-locking.

 

[essenbe]

Also, run sfc /scannow http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html use option 2. It is to verify and attempt to repair damaged system files. It will not affect any of your other programs. let us know about the other graphics card. Also, what is the wattage and amps on the +12v rail of your PSU. It will be on a sticker on the PSU.

 

[carwiz]

Follow the instruction here: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html
Be sure to click the Grab All on the utility. We need the rest of the files to complete the analysis--Especially MSINFO. The 0x7f is often caused by hardware or two drivers competing for the same hardware.

Also, check to see if you have this update installed: KB2032276

 

[Phaerius]

As I've said in the first post, when I run the program I receive an exception, the progress bar ceases to move further. Also, I've run sfc scannow in the last 2-3 days, no changes to the issue.

I can however grab my own msinfo, one moment.

Also, this is the exact model of my gtx 460, or it should be.

http://www.zotacusa.com/synergy-geforce-gtx-460-zt-40401-10h.html

 

[carwiz]

You're getting double fault memory stack errors from the display driver but I suspect that's just because memory may be corrupted by AVG. It's notorious for walking all over memory. Un-install AVG since you have MSE. You should never run more that one real-time AV. I would also suggest you un-install Adaware and make use of the security features already included in your browser. If you continue getting BSODs, Un-install DAEMON Tools Lite.

Also, in the future, let the BSOD utility run to completion. It will run for quite a while on your system since you have so many processes running. If you're getting an "exception", what is it?

 

[Phaerius]

I don't run avg actively, I know not to run multiples, I was using it for scans a month or so ago to cover a few programs. Same with AdAware, I don't believe I have any AdAware real time security running, so removing those shouldn't be an issue.

"Unhandled exception has occurred in your application. If you click continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Could not complete operation on some files and directories. See the Data property of the exception for more details."

Details: See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: Could not complete operation on some files and directories. See the Data property of the exception for more details.
at Microsoft.VisualBasic.FileIO.FileSystem.FxCopyOrMoveDirectory(CopyOrMove operation, String sourceDirectoryPath, String targetDirectoryPath, Boolean overwrite)
at Microsoft.VisualBasic.FileIO.FileSystem.CopyOrMoveDirectory(CopyOrMove operation, String sourceDirectoryName, String destinationDirectoryName, Boolean overwrite, UIOptionInternal showUI, UICancelOption onUserCancel)
at Microsoft.VisualBasic.MyServices.FileSystemProxy.CopyDirectory(String sourceDirectoryName, String destinationDirectoryName, Boolean overwrite)
at SF_Diagnostic_Tool.Form1.Button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5466 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
SF Diagnostic Tool
Assembly Version: 5.0.0.6
Win32 Version: 5.0.0.6
CodeBase: file:///C:/Users/Phaerius/Desktop/SF_Diagnostic_Tool.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

As per my first post. The progress bar doesn't move despite leaving it for an hour or so.

 

[essenbe]

Have You replaced the PSU in the machine or does it have the original HP PSU? The recommended wattage for your card is 450W, I believe. I seriously doubt HP put that size PSU in your computer. Can you tell us the specs on it?

 

[carwiz]

Good point Steve.

AVG and Adaware had services running unless you didn't provide the most recent MSINFO. I'm done here until we get valid data to work with.

 

[Phaerius]

That was the msinfo I just saved, also, I do have a have a higher wattage psu. I'm currently running a 600w, let me see if I can find the model. It's a thermaltake I switched to a few months back, current lockup issues were occurring with previous psu as well. Still looking for exact model info.

Pretty sure it's this. http://www.thermaltakeusa.com/products-model.aspx?id=C_00002032

Will leave the diagnostic tool running as long as I can, but the last time I tried that it didn't do much of anything.

 

[Phaerius]

Ran the SF diagnostic tool for five hours, no change past 25-30% when the unhandled exception hits. Didn't put together anything other than the dump files.