Hello,
Quoted from my last thread:
"I'm not sure if this is the right section, but a couple of weeks ago I got an error saying something along the lines of "WINDOWS HAS ENCOUNTERED A FATAL ERROR AND WILL RESTART IN ONE MINUTE". I restarted into safe mode and ran chkdsk, and it gave me this error:
"The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
WIndows found problems with the file system.
It asked me to run CHKDSK /F, which I did, and the computer has been running fine since. Except today, which is why I'm making this thread.
I went AFK for a few minutes and came back to my computer off. Just randomly. There was no error so I can't be sure what it is, but I'm guessing it's related to the MFT. Is this a serious issue? How can I fix it?
My specs:
CPU: AMD FX 8150
RAM: 10.0GB Dual-Channel DDR3 @ 1333MHz (9-9-9-24)
Motherboard: Gigabyte 2AC8
GPU: 3072MB ATI AMD Radeon HD 7900 Series (HP)
Hard drive: 1863GB Hitachi HDS723020BLA642 SCSI Disk Device (SATA)
OS: Windows 7 Home Premium 64 Bit
PSU: SeaSonic M12II 620w
Case: NZXT Phantom 630
I just upgraded to the case late last year, and I noticed the SATA cables were a bit short. Could this be an issue?"
Now, I ran another CHKDSK just to be sure. I didn't get the stuff abut the MFT, however it again said that "The Volume Bitmap is incorrect". It suggested I run CHKDSK /F again, and I did. It claimed to have fixed the issues, and so far so good. However, I'm curious what the cause of all these corruptions could be.
More quotes from previous thread that could prove useful:
"Random buzzing on my speakers and headphones (so it's not the audio device or front panel ports), motherboard dying possibly?"
"Forgot to mention, when I was removing all the plugs from the motherboard, (I followed HP's instructions on this, it was an HP prebuilt, they said to pry it off with a screwdriver) the socket broke off the motherboard instead of the plug coming out. It was the front panel hard drive read LED. Did I kill my motherboard?"
"One thing to note is that the computer didn't restart normally (usually it waits a second before starting again and the case LEDs shut off in that time), it just went to the boot screen instantly."
Thanks
Quoted from my last thread:
"I'm not sure if this is the right section, but a couple of weeks ago I got an error saying something along the lines of "WINDOWS HAS ENCOUNTERED A FATAL ERROR AND WILL RESTART IN ONE MINUTE". I restarted into safe mode and ran chkdsk, and it gave me this error:
"The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
WIndows found problems with the file system.
It asked me to run CHKDSK /F, which I did, and the computer has been running fine since. Except today, which is why I'm making this thread.
I went AFK for a few minutes and came back to my computer off. Just randomly. There was no error so I can't be sure what it is, but I'm guessing it's related to the MFT. Is this a serious issue? How can I fix it?
My specs:
CPU: AMD FX 8150
RAM: 10.0GB Dual-Channel DDR3 @ 1333MHz (9-9-9-24)
Motherboard: Gigabyte 2AC8
GPU: 3072MB ATI AMD Radeon HD 7900 Series (HP)
Hard drive: 1863GB Hitachi HDS723020BLA642 SCSI Disk Device (SATA)
OS: Windows 7 Home Premium 64 Bit
PSU: SeaSonic M12II 620w
Case: NZXT Phantom 630
I just upgraded to the case late last year, and I noticed the SATA cables were a bit short. Could this be an issue?"
Now, I ran another CHKDSK just to be sure. I didn't get the stuff abut the MFT, however it again said that "The Volume Bitmap is incorrect". It suggested I run CHKDSK /F again, and I did. It claimed to have fixed the issues, and so far so good. However, I'm curious what the cause of all these corruptions could be.
More quotes from previous thread that could prove useful:
"Random buzzing on my speakers and headphones (so it's not the audio device or front panel ports), motherboard dying possibly?"
"Forgot to mention, when I was removing all the plugs from the motherboard, (I followed HP's instructions on this, it was an HP prebuilt, they said to pry it off with a screwdriver) the socket broke off the motherboard instead of the plug coming out. It was the front panel hard drive read LED. Did I kill my motherboard?"
"One thing to note is that the computer didn't restart normally (usually it waits a second before starting again and the case LEDs shut off in that time), it just went to the boot screen instantly."
Thanks
Facebook
Twitter
Instagram