Mass crashed/BOOTMGR error...help!?

Associate
Joined
9 Jan 2012
Posts
222
Sorry if this is in the wrong place ..

Basically I was on my computer earlier today and suddenly everything crashed.
It started with my internet page, then when I couldn't close it I clicked skype on the task bar and then that crashed. In the end my exploror.exe stopped (without the error popped up however) I just couldn't click, highlight or even alt,ctrl+del to go into the task manager.

This had never happened before.

Anyway, I shut down my pc and then rebooted it.
Suddenly it popped up with BOOTMGR is missing.

After going through my bio settings i managed to launch my computer through one of the three bootup ways.

I Googled and found some people saying you need the repair disc - my pc didn't ever come with one. However I managed to make one, and after swapping boot order in my bios managed to boot pc up through the DVD and the new disc then clicked the system repair 2/3 times to fix the BOOTMGR problem.

Woo it worked again, along with now having a drive E where it's now partitioned part of my windows too now.
However a hour later, my pc did the same crash again - however this time booted up again. However I thought since it was now working I could change my bios back, so I did and then it wouldn't boot up again. So after faffing around ONCE again I changed it back so it boots from the CD.

I'm getting just stressed now since I don't exactly wish to keep the CD in to boot my PC, I want it how it was before. Just press the button and turn it on. So I'm thinking of just wiping the harddrive and reinstalling Windows 7.

- Again, however the computer came with it automatically on, I just had to activate it with the key.

So what are your guys thoughts? Will I have to buy a new Windows Home Premium disc and new code or could I just find someone that has a windows HP disc and use my code I originally used when first setting up my pc.
OR should I just leave it how it is and deal with keeping the disc in to boot up..

Sorry for that wall of text.. might be a bit hard to understand aswell but yeah.. never seen this message before in all my years of working with computers.
 
There's software that will find your windows key for you,

List your pc parts and are you overclocked or stock?
 
There's software that will find your windows key for you,

List your pc parts and are you overclocked or stock?

(Actually just had another freeze thing again while typing) internet browser just froze followed by everything else - had to restart)

All Stock

Intel Core i5-2700K 3.50GHz Quad Core Processor
Asus P8Z68-V GEN3 Intel Z68 (Socket 1155) DDR3 Motherboard
Seagate Baracuda 7200.12 500GB SATA 6GB/s 16MB Cache
Radeon 7970 Graphics card.
16gb RAM but I don't remember just yet what type it's by.

And I have my windows 7 premium key.
 
Ok try enabling x.m.p profile 1 if your memory supports it

Then set vccio voltage to 1.10v,you might need that much for 16gb,vccio is for the integrated memory controller
 
Was the vccio voltage at 1.05v before? If so then keep it at 1.10v now

You should see x.m.p in the BIOS if you can't then your memory doesn't support it,so you'll have to set the rated speed and dram voltage to what's printed on the ram

Maybe 1.65v dram voltage with 16gb

Pretty sure its memory setting related,esp random freezing,
 
Last edited:
Nope.... It's just crashed again.

This time when I tried to do system repair it came up with this.

P1000684_zpsf2b8a5e2.jpg


followed by a different one that said erm, "missingoslauncher"

finally after restarting it for the third time it repaired a loaded as normal but this is silly.

Do you think, transfering everything I wish to save to another harddrive then wiping my SSD and HDD drives and reinstalling a new windows home premium would fix everything?
 
Yeah downloaded and installed everything last night. Not a crash so far :)
Seems it's only been in the last month it's really picked up again the crashes, or atleast people who have been experiencing it... hopefully it won't start again ... *crosses fingers*
 
I didn't know you had an m4 ssd,i was thinking it was memory related but atleast you fixed it

it will run fine now
 
Back
Top Bottom