Could use some technical computer help
The Blind Eternities forum
Posted on June 25, 2016, 3:43 p.m. by kyuuri117
So I recently upgraded from Windows 8 to Windows 10, and within a week my computer started BSODing constantly. About a week later, my computer started dying after bios, but before Windows had loaded or blue screening mid boot.
When it would let me into the recovery options, it would fail the recovery and say that "C:\WINDOWS\System32\Logfiles\Srt\SrtTrail.txt" was the issue.
I can only get my computer toBoot properly every 5-6 times I try, and it's random.
However, since it does sometimes load into Windows, I don't think it's the hard drive, and I'm not having any errors with my video card or ram. The blue screens when Windows is actually working have stopped as well.
I did try a partial system restore where it kept some files but deleted most, but that hasn't seemed to work. I just did a chkdsk, and it booted up normally after that was done...but I don't know if that's fixed the issue.
Any help would be appreciated on how to fix this.
Yea I dunno. I try and Google this stuff before I go asking for help but each time I google this technical computer stuff, I get a page full of stuff I don't understand. So then I google that stuff...and each of those are also hard to understand.
June 25, 2016 4:32 p.m.
VampireArmy says... #4
worse come to worse you may need to wipe everything and redo windows itself.
June 25, 2016 4:35 p.m.
I... think I fixed it.
After some random googling, I found out about this thing called the "Event Viewer". And it shows everything your computer does, including the errors. And while I doubt i've fixed everything, I DID manage to find this damn Kernal error that was stopping the bootup.
So I googled it, and got to this
Basically, from what I understand, the bootup process needs a certain amount of memory, and yet it was locked at 20mb. When I bumped it up to allow it access to up to 128 mb, not only does it boot, but it actually does the fast boot it's supposed to (skipping the option to go to bios).
I'm definitely expecting to try and turn it on tomorrow and have it not work again, but if that doesn't happen, it'l be a nice surprise.
June 25, 2016 4:41 p.m.
Epochalyptik says... #7
This thread was moved to a more appropriate forum(auto-generated comment)
VampireArmy says... #2
it sounds like the new windows install got botched somewhere down the line. I'm not entirely the best at the that stuff though.
June 25, 2016 4:16 p.m.