Solved BSOD with various error codes

[Tuamtuam]

Well, there's not much info available about the crashes.
Since the new GPU yesterday afternoon, the system has crashed 3 times.
Twice it just completely locked up, image on screen, sounds garbled and stuck on loop. Reset button/cold boot only way out.
Once just now the system powered off suddenly, and then rebooted itself, which it did normally with no errors.
Windows shows no errror messages on reboot, nor in the maintenance report in Action Center for any of this.
What more info should I try and provide to you now?

 

[Arc]

So it is happening after employing the new GPU? Well, you post if following the BOSD posting instructions. It may be a case as you said that there is no crash dumps .... but the other files will help us to construct an idea about actually what is going on there.

Also let us know the wattage of the PSU.

check dxdiag
​

 

[Tuamtuam]

Hi,
Yes, even after switching to a newer Nvidia graphics card, the same issues remain it seems.
PSU is 950W. Had 2 crashes today, one with system powering off, and then restarting itself, other with complete lockup.
Rebooting after these, everything is "fine".
Temperatures have been great since the new mobo install, and now the new GPU has fantastic cooling too, along with a new case fan so heat is definitely ruled out as an issue for the CPU, GPU etc. Both CPU and GPU idle at about 39C.

By the way, I have noticed that at some point the Windows Experience/Performance Index rating for my RAM has dropped from above 7 to below 6. Not sure if that is accurate, or meaningful, and not sure if that happened immediately when I installed the new mobo, but it was not the case before that. Just something else which is odd at the moment!

I have grabbed whatever minidumps your tool could find, files attached.
Thanks,
Tom

 

[Arc]

Driver File Version: 9.18.0013.2049 (English)
Driver Version: 9.18.13.2049
Driver Date/Size: 6/21/2013 15:06:36, 15144928 bytes

This information means you have installed the 320.49 WHQL display driver, which is known to be a buggy one.

Install the 314.22 WHQL only. It works fine with NVIDIA GeForce GTX 570.

• Uninstall All nvidia items in Control Panel > Programs and features
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results when done.

 

[Tuamtuam]

Last night I performed the uninstall of the 320.49 drivers, and then install of the 314.22 drivers as you described.
Whole of yesterday there had been no crashes before that, and the PC had been on all day almost.
Anyway, today I noticed that Windows Update had kindly gone and updated the nvidia software for me. Nice.
So I again removed and reinstalled as suggested, and made sure WU is no longer set to automatically install anything, ever, like I thought it already was.
After that was all done, I got a lockup in windows, browising the web with ff. :/
Minidumps attached.

Now, after having replaced mobo, graphics card and data HDD, I am looking around for the next culprit, still with no real clue of course, but with the list narrowing down..
How about a faulty PSU? How much do voltages usually vary by? I'm noticing that they are all below what they are supposed to be, but is it enough to cause an issue?
Screenshot attached.
Cheers.

 

[Arc]

No new BSOD, but here is the probable reason behind the network blockage .....

Event[7637]:
  Log Name: System
  Source: Service Control Manager
  Date: 2013-09-23T16:30:44.174
  Event ID: 7001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Thundersloth
  Description: 
[COLOR=Red]The Windows Media Player Network Sharing Service service depends on the Windows Search service which failed to start because of the following error: 
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.[/COLOR]

Event[7635]:
  Log Name: System
  Source: Service Control Manager
  Date: 2013-09-23T16:28:41.120
  Event ID: 7026
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Thundersloth
  Description: 
[COLOR=Red]The following boot-start or system-start driver(s) did not load: 
dam[/COLOR]

dam.sys is a system file. It should not fail.

IMHO either it is a corrupted windows installation, or a bad hardware failure (PSU -CPU -MOBO).

As you want to check the performance of the PSU, Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator

Stress test the CPU.
Hardware - Stress Test With Prime95

Also perform a http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

Let us know the results. Unfortunately we have no way to check the motherboard.

 

[Tuamtuam]

Thanks.
Did the power supply calculator, it came out as 439W recommended PSU, which mine should exceed by over 500W...
I will give Prime95 a go, I have used it before.
I have Windows 8 Pro 64bit now, no longer Windows 7, and although I am willing to do a clean install once more, I wonder if the recommended procedure is the same?

 

[Arc]

If you are using windows 8, you may start in BSOD Crashes and Debugging - Windows 8 Forums.

 

[Tuamtuam]

Thanks for your answer yet again
At this point, I am pretty much ready to point the finger at the PSU and replace that.
I understand it could be a corrupted Windows installation, but I still think this is unlikely, because in the lifetime of this PC I have:
Upgraded from manufacturer-installed Vista to Windows 7 (clean install, keeping nothing on c: drive)
Reinstalled the whole lot (first Vista, then Win7), total clean reinstall.
Upgraded to Windows 8 (again a clean install, removing the existing partion on c: drive)

The issues were happening a before any of this, have happened between these installs, and are still happening now, and now even more often. That's why I'm more inclined to see it as a hardware issue. It is still guesswork, but I think it would make sense that the PSU is getting worse now after a few years. It has been crashing more often during gaming recently, where it just shuts off and then restarts, so that would seem to me to point to power issues.
I will do some prime95 tests, but will be shopping for a PSU I think in the near future. I will update in due course.
Cheers.

 

[Tuamtuam]

An update for anyone who may be interested.
New PSU installed today, a Cooler Master V850.
Unfortunately I have already had crashes, same as ever.
My next step will be changing the RAM.

At least with the components I have changed in recent months, I am actually upgrading the machine, even if it is not stable yet The PSU seems like a great upgrade, with a 5 year warranty and 80+ Gold efficiency, reviews were outstanding and really convinced me to go for this instead of other options. That and immediate availability in a local shop.

I'm still reluctant to go back and reinstall Windows now, hence the RAM next on the list.
However, I am psyching myself up for it, after noticing just recently unrepairable errors on the sfc /scannow command.
I haven't had time to look into those, but I have run that check many times before, with no errors, whilst the machine was still crashing in the same way, so it doesn't seem to be related, but corrupted system files are never a good thing.

 

[Tuamtuam]

Final update, and the solution has been found.
Followed sevenforum's and eightforum's advice on sfc /scannow and repairing unrepairable errors. Fixed the sfc errors using DISM as detailed here. Unfortunately that was still not the cause nor the solution, still had lockups.
Then, almost a week ago, I received new RAM that I ordered. Installed that, and the system has been 100% error free since. Heh. When I got the old RAM out and had time to have a look, I also noticed the part numbers were identical, but the serial numbers were not similar, and the product info stickers were slightly different in layout. So I guess that means what I received in my new system was NOT a tested kit of RAM??? Nice. Unfortunately no point in following that up 4 years down the line, but no bonus points for MESH Computers from this problem causing RAM.
Anyway, I feel great that the issue is fixed, and also that I have an almost new PC at the end of this!
Thanks again to Arc for trying to help me get to the bottom of this mystery, I will now mark this as solved.

 

[Arc]

Its a relieving news. Mismatch RAM can cause any sort of failure, and it remains undetected by memtest.

Hope those odd crashes will not be there anymore