Page 1 of 1
MBR corrupt and windows destroyed
Posted: Sat Feb 13, 2016 9:13 am
by franziscko
Hi everybody! Sorry for my bad English, I hope I can explain all...
I have a very strange problem. Sometimes, very random, (one day after another or one time in 6 months), HD does'nt boot,
I get message MBR CORRUPT.
Need to reinstall BOOTITBM, but, after this, Windows 7 64bit doesn't exist, there are only 2 directories in HD,
$Windows.~bt and $Windows.~ls and a file WinPge.sys long 536.870.912 bytes.
Mainboard is Asrock H77 Pro 4 with Uefi Bios, Hard Disk is a WD Caviar Blue 1TB and i've tested many times with HDD Regenerato
and is ok.
Please help me, I don't know what to do!!!
Regards.
Re: MBR corrupt and windows destroyed
Posted: Sat Feb 13, 2016 6:10 pm
by TeraByte Support
sounds like something is wrapping around and overwriting part of the disk
causing it to corrupt BIBM and part of your windows os.
you may want to run memtest86+ from memtest.org on the system overnight to
see if that is throwing something off.
"franziscko" wrote in message news:11078@public.bootitbm...
Hi everybody! Sorry for my bad English, I hope I can explain all...
I have a very strange problem. Sometimes, very random, (one day after
another or one time in 6 months), HD does'nt boot,
I get message MBR CORRUPT.
Need to reinstall BOOTITBM, but, after this, Windows 7 64bit doesn't exist,
there are only 2 directories in HD,
$Windows.~bt and $Windows.~ls and a file WinPge.sys long 536.870.912
bytes.
Mainboard is Asrock H77 Pro 4 with Uefi Bios, Hard Disk is a WD Caviar Blue
1TB and i've tested many times with HDD Regenerato
and is ok.
Please help me, I don't know what to do!!!
Regards.
Re: MBR corrupt and windows destroyed
Posted: Tue Feb 16, 2016 4:25 pm
by franziscko
Hi, thank you for your reply.
PC is ok, i've used Memtest, HDD Regenerator, Orthos, ecc...
Re: MBR corrupt and windows destroyed
Posted: Sun Mar 13, 2016 2:45 am
by gpsmikey
Two things - TB support - why does your post date indicate "Saturday Feb 13, 2016 11:10 am" - did something forget leap year???
[edit - brain dead ... it is March now. I think more coffee is required!! ]
I ran into a similar situation some years back (when we partitioned disks by specifying start/end track/sector for partitions. I had managed to create one partition that extended into the second one by some number of MB and when the first one would get over about 90% full or so, it would start trashing the front of the following partition. Took a while to figure that one out - this sounds like the same sort of issue.
mikey