-
January 26th, 2017, 07:20 PM
#31
I was pretty sure the buzzing was some kind of alert. So I'm guessing the CPU and RAM voltages look ok now?
The overvolting could have corrupted some Windows files; setting the voltages back to normal wouldn't fix them.
Did you check the BIOS boot order? You may need to put USB boot up at the top again.
I suppose you could try burning UBCD now that the voltages are back to normal. Ideally, you want to create it on a known good computer.
I still find it hard to believe that you don't know anyone with a computer, even at work. All my friends have at least one computer. Of course the downside to that is all my friends ask for help when they have computer problems.
-
January 26th, 2017, 07:29 PM
#32
Midknyte, I forgot to check the boot order after I reset the BIOS. You sure are on the ball. Your friends sure are lucky to have you in their life and as a friend. I am grateful and thankful to have you here in virualdr because you helped me fix many of issues in the past.
I have to run an errand and when I come back I will check the boot sequence and cpu and memory mudule voltage settings, as well as, try to attempt to burn UBCD to cd and post back after doing so.
-
January 26th, 2017, 07:44 PM
#33
NP. BTW, you might want to put the GEIL memory back in now. Again, the overvolting is probably what caused the error LEDs to come on.
-
January 26th, 2017, 07:48 PM
#34
I have seen instances where a power surge or glitch has caused BIOS settings to change without user action. A few years ago one of the servers I work with had this happen, and the memory settings were changed to a value that caused it not to boot.
-
January 26th, 2017, 08:40 PM
#35
I have had bad shutdowns cause weird things to happen in the BIOS.
-
January 26th, 2017, 10:47 PM
#36
Midknyte, I went back into my bios and changed the boot sequence. I checked the memory module voltages and it now says [auto], where before it said [2.300v]. So everything in bios looks fine now. Again, I tried to boot into ubcd and it won't boot into usb-hhd. I, also, tried to boot into my acronis rescue boot media that I have on another flash drive and it would not boot into that either.
I tried burning another cd with UBCD. It gave me an I/O device error with Imgburn and it gave me an error again with Acive ISO burner program. Since I can't really boot into UBCD, can't I just try to repair windows and see what happens? I have really nothing to loose, so I might as well try it. What must I do? Should I first try to do a restore to an earlier date in "safe mode"?
JDC2000 and Train, now that you mentioned that, I believe that it was a power surge that modified my BIOS settings. That is nice to know for future if something like that occurs again.
-
January 26th, 2017, 11:34 PM
#37
Since I can't really boot into UBCD, can't I just try to repair windows and see what happens?
That's your call. I wouldn't waste my time until I knew the hardware was good. You could be chasing your tail trying to repair Windows, when it's actually a hardware problem.
Did your system boot to UBCD before you had problems? What about Acronis? This is why a second system is so important. You can verify if the boot media is good or not.
-
January 26th, 2017, 11:49 PM
#38
Midknyte, I never tried booting to UBCD in the past. I have 2 flash drives with UBCD on them. I doubt both would be bad. My pc did boot into Acronis Rescue boot media in the past because I did a restore on my current drive. I am not sure why my pc won't boot into usb-hhd now. I will be getting a laptop so eventually, I will have 2 systems.
Is is a lot of work to do a windows repair? Would it be best to try doing a windows restore? Can it be done in safe mode?
-
January 27th, 2017, 12:54 AM
#39
If you never tested your UBCD drives, you can't know if they are good or not.
You can try a System Restore first. You can run System Restore from Safe Mode.
https://technet.microsoft.com/en-us/.../bb457025.aspx
-
January 27th, 2017, 04:49 PM
#40
Update: Midknyte, I did a restore from a date about a week and a half ago and it booted into windows and stopped at the win logo screen with just the blue bar moving at the bottom but never completed booting into windows. Then, I rebooted back into safe mode with networking and as soon as I booted into safe mode, a popup screen said my computer has been successfully restored. Then, I performed a restore dated almost a month ago and it booted successfully into windows. I think this whole issue was, most likely, caused by a power surge. I will be retiring this computer soon. I am going to purchase a laptop that I will use as my main pc until I get the time to build a new pc. Thank you for your help, as well as, the others who posted.
-
January 29th, 2017, 11:30 AM
#41
My computer froze again when I was in windows and stopped at the win logo screen again when I tried to reboot. I had to boot into win safe mode to do another system restore to get my computer to boot back into windows again. Like I said I am going to retire this computer as soon as I find the specs I want on the laptop I want, which is, hopefully, in the next few days. I am not sure why this occurred again that I had to do another restore to get my system to boot into windows.
-
January 29th, 2017, 01:30 PM
#42
Again, this is why you should do hard drive and memory tests. If the hardware is bad, no amount of software tweaks or system restores is going to fix it.
-
January 30th, 2017, 01:05 AM
#43
Midknyte, you probably are correct. I am keeping my fingers crossed that I can still use my computer until I pick out a Dell laptop this week. Thanks.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|