Main Forum > General Computer Support

Tweaking set safe mode resolution too high

<< < (7/8) > >>

SFSecurity:
 :tongue: :thinking: :omg: :rolleyes: :teeth: :shocked: :smiley: :cheesy: :wink:

Holy Guacamole!

I finally recovered the system. I went through 

https://www.winhelp.us/repair-your-computer-in-windows-vista-or-7.html

step by step and what seems to have done the trick was this:

Creating a new Boot Configuration Data store in Windows Vista or 7 if the previous bootrec steps failed

If renaming the BCD folder still did not work, the last resort is to look up Windows Boot Manager and Windows Boot Loader drive letters and paths from the bcdedit command output as shown earlier.

In case your device is in UEFI boot mode, the Boot Manager drive letter is still the same Z: you assigned earlier with diskpart.

Check and double-check the Windows Boot Manager drive letter and full path to Windows installation folder. If necessary, just run the bcdedit command again.

Enter the following command: bcdboot <the full Windows installation path> /s <the drive letter for Windows Boot Manager or UEFI partition>: /f ALL , for example: bcdboot E:\Windows /s C: /f ALL (Legacy boot) or bcdboot C:\Windows /s Z: /f ALL (UEFI boot).
Windows 7, Repair your computer, Command Prompt, Legacy boot mode. Create a new boot configuration data entry by running the 'bcdboot e:\windows /s C: /f ALL' command.

However, the directions were not exactly correct. Instead of <the full Windows installation path> I used just <Drive Letter>:\Windows as it did not recognize the path I had.  Also it did not recognize /f ALL so I dropped it.

When I rebooted it came up and did a restore to an earlier date that I thought had not worked. Since I tried several that did not seem to work I went back over two months. Now I have to do some updates. Oh well. Better that than having to totally start from scratch.

In any case, THANKS TO ALL OF YOU for sticking with me while I struggled through the worst crash I've ever had.

Boggin:
Glad to see that you were able to get it fixed, but it doesn't answer why it happened in the first place.

What was the reason you were going to run the repair program ?

SFSecurity:
The reason I was running the program was to see if it would be a good tool for the credit union that I'm President of the Board of Directors. I always test programs and run them for a while before suggesting that anyone use them.

I use Malwarebytes, JV16, Spybot Search & Destroy, CCleaner, and Glarys Utilities but I know that there are always little areas that are missed by every program so having as many that are functional is the best protection in the long run. On the other, older and slower computer, even though I have run each of the tools multiple times, I found a potential hack yesterday that was sitting on it from back in the day when it was owned by one of my clients over 4 years ago!

Well, I thought I had recovered my computer but it turns out there is still a problem, I can't run Safe Mode. Huh??? :angry: It goes into the same "out of range" display when I went to try it again. It starts in Normal Windows just fine, after I fixed a bunch of things, including the clock. It was reset to 2002. Anyway, I'm still struggling with solving that problem and have no clue what to do next.  :undecided:  :sad:  :confused: :shocked:

Boggin:
In that case I don't think it would be a good idea to set safe mode/base video through msconfig as you wouldn't be able to access it to uncheck that option.

Are all of the machines Win 7 ?

I usually create a system image onto an external HDD before running a major program like WR, should I need to restore back.

Is it possible for you to do this and run the program on another Win 7 machine to see if this is Win 7 related or specific to your Win 7 machine.

Can you also post the specs of your machine and I'll pass this back to jpm.

SFSecurity:
When I was cleaning out another hard drive to save files to CHKDSK came up and ran on both drives and, supposedly, fixed things. It sure did by deleting BOOTMGR so it couldn't go into SAFE MODE. After a bunch of fiddling around I got BOOTMGR back and tried SAFE MODE only to have the screen go blank yet again with only the "out of range" message showing.

Both machines are W7, the other one is much slower and has only 4 GB memory. As to creating an image on another drive, I'd gotten too lazy, partly because I've never needed it in the past, and didn't do it so now I'm stuck. This computer boots into NORMAL WINDOWS just fine, but no safe mode.

I've spent many too many hours with this problem and haven't been able  to find where the data is that sets the video monitor rate.

I'm beginning to think that since the computer is at least 6 years old - I don't recall when I built it, could be as much as 9 years old - that rather than waste a lot more time trying to figure out how it got Tweaked, I might just build a new on with a newer CPU and more memory. Not sure if I want to upgrade to W8.1 or W10, given what I've seen with them.

Anyway, I'm happy to try any further suggestions.

Navigation

[0] Message Index

[#] Next page

[*] Previous page