problems starting up (sfc /scannow)

Hello all, i've come here before and been pushed in the right direction to be saved from my computer problems...
forgot my username though, haha.

anyway, my computer has been BSODing at startup all day, and for some reason on a one off try, it decided to boot properly, so with the chance i had i started a sfc /scannow.

the scan completed and found errors
"corrupt files but was unable to fix them."
a copy of the log is in the windows/logs/cbs/cbs.log... i'd upload it but it says Access Denied.

would you be able to find the source of the bsod through this log? if not, where could you find the problem?
i really need my computer over the weekend, so its essential that i get it fixed, preferably without the hassle of taking it into a computer repair place. :/
running pro 64bit.

Thanks!

fitzalan said:

Hello all, i've come here before and been pushed in the right direction to be saved from my computer problems...
forgot my username though, haha.

anyway, my computer has been BSODing at startup all day, and for some reason on a one off try, it decided to boot properly, so with the chance i had i started a sfc /scannow.

the scan completed and found errors
"corrupt files but was unable to fix them."
a copy of the log is in the windows/logs/cbs/cbs.log... i'd upload it but it says Access Denied.

would you be able to find the source of the bsod through this log? if not, where could you find the problem?
i really need my computer over the weekend, so its essential that i get it fixed, preferably without the hassle of taking it into a computer repair place. :/
running pro 64bit.

Thanks!

If you can boot normally




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

Okay, its been dumping using kernal, but here it is anyway...
as a .dmp file.

Attachment 146613

alright, so i wrote it down,
its a STOP: 0x0000007E, with a message saying watchdog.sys caused it.
so i googled it and its a video driver error (maybe?) which fits into my situation, cause my video driver keeps failing and the screen keeps tearing, freezing, then a message saying its failed.
my video card is a 4890, ati driver is the latest, i rolled back but the system wouldn't start, so i re installed the latest one and it worked for a while, then BSODs again...
also, a lot of other weird stuff is happening, like windows explorer stops working, and on one startup 2 days ago none of the programs would open, saying there was no entry point to be found.



uploaded is the 256kb log.
cheers guys!



Attachment 146768