Main Forum > General Computer Support
Newbie: run-time error
Boggin:
It could run for the 30 day trial and then expire.
What version of Windows is the install disk ?
While I know you can use a Pro disk to run an offboot sfc /scannow on Home Premium, I'm not sure if that can be done with a lower version on a higher version - but you could give it a try.
Change the boot order so that you can boot up with the install disk - press any key to boot from CD/DVD when prompted and that may eventually give you an inverse window with Windows Setup (EMS Enabled) highlighted, or it could take you straight to a splash screen.
If it's the former, press enter and you'll get to the splash screen to click on Repair your Computer.
Change/confirm the language/currency etc. and make a note of the location when it searches for the install.
Select Command Prompt when you get to the Recovery Environment.
To confirm the partition where the OS is, enter -
bcdedit |find "osdevice" and using whichever partition letter it gives, enter (assuming c) -
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
and see what that reports.
That's a Pipe symbol before find which is the upper case of \ which you probably know and there's a space before each forward slash.
Enter exit to close the cmd window when done, remove the disk then hit Restart.
emptypockets:
The install disk is Windows 7 Ultimate 64 bit made from an .ISO at pcsteps.com
The OS is located on partition d:
Ran offboot sfc /scannow and it reports errors it can't repair.
I looked at the CBS.log to see if I could make heads or tails of it on my own, but, once again I don't know where to look or what I'm even supposed to be looking for in there.
Boggin:
It could well be those AMD and ati errors which are CPU related and not Windows files.
Any Windows files can be extracted from an install disk as at the bottom of this article http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html but I don't have an answer for those ati errors as there was nothing in the drivers that would seem to address them.
All I can suggest for those is to see if anything applies in AMD Support and then use Step 2 to submit a ticket, but as it will be out of warranty, I'm not sure what their procedure is.
http://support.amd.com/en-us/contact
I would think the ticket box would be too small to include the CBS log although you could copy & paste a couple as examples, but see what they say, telling them a sfc /scannow is reporting AMD and ati errors for your make and model of computer.
emptypockets:
Thanks Boggin. I'll get started on the 2 suggestions you last posted. You may not hear from me for a couple of days. I get the gist of what I'm supposed to do in the tutorial--it'll just take me awhile to learn the procedure--back to school again. No problem tho because I'm learning as I go.
I already see how I can use the cmd to see and read sfc results from CBS.log. That'll help me a lot (although I'll still probably get lost along the way). I'll check back in here often to see if there's any new info while I'm busy with the rat killing. lol
Boggin:
Been doing a bit more digging and KB3022345 was found to cause sfc /scannow errors, although that was superseded by KB3080149 (I think).
Both of these are Telemetry updates from the MS spying range.
Can you go to Installed Updates to see if you have either installed by typing them into the top right search box and if so, right click on them and select Uninstall, then redo sfc /scannow to see if it reduces the errors.
I hide all Telemetry updates as they tend to help Win 10 onto your computer.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version