PresentMon icon indicating copy to clipboard operation
PresentMon copied to clipboard

Intel PresentMon Beta v0.5 Corrupted OS Install and Made SSD Temporarily Unusable Following

Open tyger07 opened this issue 2 years ago • 1 comments

After installing PresentMon Beta v0.5 from Intel's page ( https://game.intel.com/story/intel-presentmon/ ), my games started crashing. Then the operating system became slow and everything just wasn't working quite right. I rebooted, and the system wouldn't boot. It gave an error message about the boot partition something something (wish I could tell you exactly, but I didn't write it down). All recovery options were not available to me. Even though the SSD had a recovery partition, it appeared not to function. I installed the Windows install and recovery media on a USB drive, but could not perform a repair. I attempted to delete all the partitions and reinstall Windows, but that also failed. I entered the system BIOS (UEFI), but that froze when I went to the drive section, with an exception error message. I figured that the SSD had failed. Very coincidental that it occured RIGHT after installing PresentMon? I removed the 'failed' SSD and installed a different SSD. Windows successfully installed on it first attempt. Once Windows was installed on this second SSD, I installed Samsung Magician, shut down, reinstalled the 'failed' SSD, booted up, and checked the status of the 'failed' SSD. It was fine. No errors detected. You couldn't boot from it, and you couldn't reinstall Windows from it, and you couldn't view its status in BIOS without BIOS freezing, but it is fine? So I tried copying the new Windows install image from the new SSD to the old SSD. Success. No problem. I am now using the 'old' 'failed' SSD without problem, because it is a faster drive.

Something in PresentMon totally destroyed the beginning of the drive which could not be corrected by any means other than re-imaging the drive.

tyger07 avatar Aug 24 '23 04:08 tyger07

Thank you very much for reporting this issue. We have not observed the described issue. We will setup a system to continuously test Intel PresentMon in an attempt to reproduce the issue. We will update this thread with all updates to progress.

markgalvan-intel avatar Sep 05 '23 17:09 markgalvan-intel