The customer was in the middle of reading some Data from ISO Images mounted with UltraISO. Apparently, in the middle of reading the data he got the BSOD that means "Drive can't be read" (0x000000ED) and could not re-boot. I tried to check the Drive using CHKDSK and that's when I got the Master File Table error.
This was a brand new drive with a fresh install of Windows 7 x64, it had been running perfectly for a month. This error happened in the middle of a windows session.
The only software that might have caused this was Perfect Disk v13, which I assumed would be OK for optimizing SSD's. But I had that scheduled to run only between midnight and 6AM. The machine generally stays on 24/7, maybe shut down during weekends. But this happened in the middle of the week.
I ran Partition Wizard 7.x to try to recover the drive, but it failed to fix the error. I had used that to repair one partition on my main machine about a year ago, but that was not the boot partition.
Is there any tool that can check a disk that has Master File Table errors? Else I just have to re-install Windows. But I need to know what caused this so it does not happen again.
The Machine is an AMD CPU, I'm not sure which one, probably an AM2 CPU like a 4400+. Sorry, I have no logs for it, they are all on the unreadable drive. What would cause a drive to go out like that, could UltraISO cause it when accessing mounted ISO images?
TIA.
This was a brand new drive with a fresh install of Windows 7 x64, it had been running perfectly for a month. This error happened in the middle of a windows session.
The only software that might have caused this was Perfect Disk v13, which I assumed would be OK for optimizing SSD's. But I had that scheduled to run only between midnight and 6AM. The machine generally stays on 24/7, maybe shut down during weekends. But this happened in the middle of the week.
I ran Partition Wizard 7.x to try to recover the drive, but it failed to fix the error. I had used that to repair one partition on my main machine about a year ago, but that was not the boot partition.
Is there any tool that can check a disk that has Master File Table errors? Else I just have to re-install Windows. But I need to know what caused this so it does not happen again.
The Machine is an AMD CPU, I'm not sure which one, probably an AM2 CPU like a 4400+. Sorry, I have no logs for it, they are all on the unreadable drive. What would cause a drive to go out like that, could UltraISO cause it when accessing mounted ISO images?
TIA.
My Computer
At a glance
Windows 10/Windows 7 (My Idea- Virtual PC)Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz16 GBnVidia GeForce GTX 750 Ti (2GB)
- Computer type
- PC/Desktop
- Computer Manufacturer/Model Number
- Lenovo Thinkcenter M92p
- OS
- Windows 10/Windows 7 (My Idea- Virtual PC)
- CPU
- Intel(R) Core(TM) i5-3470 CPU @ 3.20GHz
- Motherboard
- Lenovo MahoBay
- Memory
- 16 GB
- Graphics Card(s)
- nVidia GeForce GTX 750 Ti (2GB)
- Sound Card
- nVidia HD Audio
- Monitor(s) Displays
- RCA 4KTV 50"
- Screen Resolution
- 3840p x 2160p
- Hard Drives
- Onboard:
Seagate ST500DM009-2F110A 500GB
WDC WD4000FYYZ-01UL1B1 (WD-WCC131910831) [3726 GB]
USB 3.0
My Book 1140 (WCAZAD122454) [1862 GB]
Apple MDT MD10EAVS-00D7B0 (0000AB123473) [931 GB]
External:
WD Blue Innostar/Matsunichi (465 GB)
WD
- PSU
- Stock Thinkcenter M92p
- Case
- Stock Thinkcenter M92p
- Cooling
- Active
- Keyboard
- BYTEC BY-GA-KT-100-AC
- Mouse
- BYTEC
- Internet Speed
- 1 GHz Down, 40 Mbps Up
- Antivirus
- Windows Defender
- Browser
- EDGE
- Other Info
- Old Other Info:
I finally have an Intel machine that has more than 8GB of Ram.
My ASUS M2N-SE AMD Windows 7 machine is back to Windows 7. Replaced the AMD 4400+ CPU and maxed out the RAM (4GB).
My Core Duo machine is only 2GB of Ram and it is locked to Windows XP in order to run Pro Tools 6.4, which I have been using since 2004.
I have one other Dell OptiPlex 980 tower, Identical to this one,





