Wondering whether I killed my computer...

  • Please make sure you are familiar with the forum rules. You can find them here: https://forums.tripwireinteractive.com/index.php?threads/forum-rules.2334636/
  • Weve updated the Tripwire Privacy Notice under our Policies to be clearer about our use of customer information to come in line with the EU General Data Protection Regulation (GDPR) rules that come into force today (25th May 2018). The following are highlights of our changes:


    We've incorporated the relevant concepts from the GDPR including joining the EU and Swiss Privacy Shield framework. We've added explanations for why and how Tripwire processes customer data and the types of data that we process, as well as information about your data protection rights.



    For more information about our privacy practices, please review the new Privacy Policy found here: https://tripwireinteractive.com/#/privacy-notice

Trendkill

FNG / Fresh Meat
Nov 21, 2006
642
4
0
Dorset, UK
This isn't help with RO exactly, it's a question about whether, through lack of patience, I killed my computer...

I'd closed RO in a hurry and it was 'powering down' as it does (I was gonna update my memory later that day to see if it would speed up the process) but because RO takes an age to close properly I turned my PC of at the wall and when I got back my PC would not get past the Windows loading screen before it restart... Could, by my pretty stupid and impatient actions, have fried something in my PC because RO uses a lot of CPU power whilst it was closing?
My guess is probably yes but I'm no computer expert and was hoping if something was fried whehter someone here might know what...
 
Last edited:

sop_Ie

FNG / Fresh Meat
Aug 31, 2007
58
0
0
BaileanChollaig Corcaigh Eire
Did you try booting in at safe mode?,I dont think you fryed anything from your description.
  • Restart the computer.
  • Just after the POST diagnostics and memory count, start pressing the F8 key
  • On the Startup Menu, choose Safe Mode
  • restart pc
 
Last edited:

Peter.Steele

FNG / Fresh Meat
Sep 6, 2006
2,128
779
0
Chambers of the Grand Council
You didn't damage your hardware, probably. You -might- have corrupted some data on the hard drive from now shutting down correctly, but it's not tooooooo terribly likely that you did any physical damage to the hard drive.
 

fiftyone

FNG / Fresh Meat
May 6, 2006
5,453
284
0
Put in Windows boot disk and choose R to repair, let Windows do its thing.
Or if I remember correctly choose DOS prompt/command line only and type CHKDSK.
This is off the top of my head so don't quote me on it.
 

Trendkill

FNG / Fresh Meat
Nov 21, 2006
642
4
0
Dorset, UK
Well I've tried safe mode and I'm pretty sure my brother (who's the computer whiz) tried the repair thing but it wouldn't get past 75%. I'll ask my brother though next time I see him.
 

endorphin

FNG / Fresh Meat
Mar 5, 2006
349
0
0
Before you fdisk, make sure the windows cd is clean (windex)...

and try the repair again.
 

Peter.Steele

FNG / Fresh Meat
Sep 6, 2006
2,128
779
0
Chambers of the Grand Council
Before you fdisk, make sure the windows cd is clean (windex)...

and try the repair again.


True.

There's another option as well that I forgot about. Recovery Console doesn't make it easy to figure out, but you CAN re-install Windows over your current installation ... but keep all your installed programs and such. It's just a little more complicated and the options aren't really clearly laid out to do it.

http://pcworld.about.com/magazine/2109p156id111652.htm
^^^^ Explains the procedure.
 

fiftyone

FNG / Fresh Meat
May 6, 2006
5,453
284
0
True.

There's another option as well that I forgot about. Recovery Console doesn't make it easy to figure out, but you CAN re-install Windows over your current installation ... but keep all your installed programs and such. It's just a little more complicated and the options aren't really clearly laid out to do it.

http://pcworld.about.com/magazine/2109p156id111652.htm
^^^^ Explains the procedure.

True, this could be the way to go !

To add to what I wrote earlier I think CHKDSK \S will do a system check,(I believe).