win7 x64 no boot

Hi all, first post here. I have a boot problem. I first noticed that my desktop icons were being moved around on startup. Looked up a solution (changing "grid" choice on screen options). Problem solved. Then today I started and windows "startup" screen came on then went to black screen. Tried several more times with same result. I then got a "repair" screen come up. During repair it said that I had a error code of 0x0 and that repair cannot be done. I created a boot disc on my other computer and have booted from that disc. I am now in the process of backing up all files prior to trying to find and fix the problem. Where do I start? Any help would be great

 

Of course I should have posted that from the get go:
Desktop pc
Win7 pro x64
Mobo: Gigabyte ex58 UD5
Core i7 920@2.67 Ghz
6Gb RAM
C drive: Intel SSD 160Gb
D drive: Samsung s3
E drive: Samsung s3
F drive: Samsung s3
corsair H50 watercooler
Corsair 1000w PSU
GTX 970 GPU
Soundblaster fatality xfi sound card
Windows has been updated as of this morning at 0840
Running service pack 1
Note that nothing is overclocked nor has it ever been.
I noticed the issue of the desktop icons about a month ago but wasn't particularly concerned. Everything worked fine. I changed the graphics cards about 3 weeks ago and installation was fine and it has been running without a hitch. Although the moving icons were still present.
I am currently running via a startup disc but also have access to a second computer if needs be.
I have just looked at the update history and it shows that there are several updates that "failed" ??


Update for Windows 7 for x64-based Systems (KB2978092)
Installation date: ‎23/‎01/‎2015 21:05
Installation status: Failed
Error details: Code 80070308

Update for Windows 7 for x64-based Systems (KB2913152)
Installation date: ‎23/‎01/‎2015 21:11
Installation status: Failed
Error details: Code 80070308

Security Update for Windows 7 for x64-based Systems (KB3013126)
Installation date: ‎23/‎01/‎2015 21:04
Installation status: Failed
Error details: Code 80070308


Update for Windows 7 for x64-based Systems (KB2923545)
Installation date: ‎23/‎01/‎2015 21:03
Installation status: Failed
Error details: Code 80070308

 

ok I've done a full virus scan and all is clear (kaspersky 2014). I've looked at he action center reliability chart and there are problems. These are namely "critical windows error - windows stopped working and they have occurred (without me knowing) since the 20th January. Yesterday the error was "windows failed to start" unknown fault. On the 3rd Feb there was a "video hardware error" I've checked for solutions but none are available. Im running some plenty of games and have had no problems at all with video. Here is the error code:
Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Extra information about the problem
BCCode: 117
BCP1: FFFFFA80058894E0
BCP2: FFFFF8800F9A55C8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Bucket ID: X64_0x117_Tdr:3_TdrVTR:13_IMAGE_nvlddmkm.sys
Server information: d80bf642-3e8b-4ec7-bd7f-96428974fdc0

 

Thanks for the help
Just ran the sfc/scannow and it has come back with "did not find any integrity violations"

 

If your disk was a spinner those progressive symptoms would be consistent with a failing hard drive. However I would still run chkdsk on the SSD. If the drive has problems that will find them and at least attempt to correct them.

Using your boot disk open a command prompt and type chkdsk /r

 

Ok will do. I've done a windows update again and it rebooted fine without the recovery disc. I just tried to check the GPU drivers using Nvidia geforce experience and the program will not open? I went to device manager and found the graphics card and checked for updates but none are found. Could the GPU software be the problem?

 

i just tried to run chkdsk /r but there is an error saying that the "C" drive is already in use ?
it is asking if i want it checked at next boot ??

 

I didn't realise you were now booting again. Normally, if you try to run chkdsk from a command prompt in Windows it offers to schedule the check for the next boot. If that isn't the case run it from a command prompt in your Windows Repair disk. If you don't have one then it's time to create one, unless you have an installation disk. A manufacturer's recovery disk is no use in this situation.

 

I've got the install disc as well as a recovery disc. The recovery disc is the one I made from windows when it offered to make one .. it's not from the manufacturer. Is there any difference between booting and having the chkdsk /r during boot? Also, what exactly will it be checking? Faulty disc/disc errors?
Sorry for the questions, I'm not all that literate with computers .. if I can't get it into my head then I will never understand :-D

 

It makes no difference at all whether you run chkdsk from Windows or from a disk because if you run it from Windows it won't actually run until you reboot. If you are serious about wanting to understand exactly what it does then research it on the web. It is the standard Microsoft tool for discovering and, if necessary, isolating faulty disk sectors and for performing an exhaustive check on every aspect of your disk's ntfs filing system, correcting any errors present. Chkdsk and sfc, which you have already run, are the basic tools for ensuring that both the disk and its contents are fault free.

 

Completed scan of c drive and all is fine. Computer booted into windows without fault. I really want to find out what the causes are though. It appears to be intermittent according to the log files. I'll check out the graphics card angle especially as GFE is not wanting to work .. but the issues were there before the GPU upgrgrade though ..

 

I've been looking at the event logger and resource monitor. I've found a whole bunch of errors and failures that I am starting to work through. The first two are:
1. Symptom: Device is not present, not working properly, or does not have all of its drivers installed.
Cause: A device has a configuration problem that prevents it from working properly.
Details: The device, sptd, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_SPTD\0000.
Resolution: 1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.

2.Symptom: Device is not present, not working properly, or does not have all of its drivers installed.
Cause: A device has a configuration problem that prevents it from working properly.
Details: The device, Kaspersky Anti-Virus NDIS 6 Filter, is reporting "tv_ConfigMgrErr24". This device will not be available until the issue is resolved. The Plug and Play ID for this device is ROOT\LEGACY_KLIM6\0000.
Resolution: 1. Verify the correct driver is installed.
2. Try updating the drivers using Windows Update.
3. Check with the manufacturer for an updated driver.
4. Attempt to uninstall and then reinstall the device using Device Manager.
Any idea what these are?

 

Are there any exclamation marks showing in Device Manager? If so open the device by double clicking it and try updating the driver. If you are able to determine what device it is from the info in Device Manager then you could try first to find the driver on the manufacturer's website as that is usually preferred to letting Windows find it.

You might also want to check in Windows Update to see if there are any hardware driver updates being offered.

From the error description it sounds as if it might be a tv device causing these errors. If you have a decent unmetered internet connection tv adapters are redundant these days so if you don't have any success with drivers then you could consider whether you still want this device and if not disable or physically remove it. But of course it may not be a tv adapter at all.

 

Just wanted to add that every computer has loads of errors in event viewer and finding the one that has caused a problem is highly dependent on having an accurate recollection of exactly when the error occurred. Otherwise it really is the proverbial pin in a haystack.