It's pretty confusing since i have been constantly shifting drives around but i think...that drive is my current C drive, the mx500. I think that error resulted from some issues imaging my former OS...
Type: Posts; User: BobLeSaget
It's pretty confusing since i have been constantly shifting drives around but i think...that drive is my current C drive, the mx500. I think that error resulted from some issues imaging my former OS...
The crystaldisk is from earlier today
The F drive is just a drive i have on usb that i'm backing up my C drive into. It's not usually connected to the pc.
I think this should be the same information as hdtune.
I also found "If you own a Crucial MX500 drive (mine is CT4000MX500SSD1) you SHOULD disable TRIM until the firmware is fixed (M3CR045 is...
I'll probably see if i get another crash, and then hope that i can get a log that'll help.
I somewhat recall the 12 kb in bad sectors thing was with my previous ssd that ended up having to be...
I'm not sure how relevant it is but some of the error history is due to having cloned a drive onto another one that turned out to have bad blocks that didn't show on SMART, I think that might have...
It's possible for an issue on a secondary drive to cause this BSOD?
I just got this BSOD after letting my pc idle for about an hour and a half. A couple minutes of use after i got back i noticed that i could move my mouse but i couldn't actually interact with...
I don't have a screenshot of it but i ran HDtune error scan prior to installing the drive and it came up with no errors/damaged blocks.
Bit of a non-issue other than filling up my reliability history but the couple days since i replaced the drive i've gotten some of these errors. I usually only notice when it happens because of a...
What i ended up doing was i used Macrium to image my original drive to my storage drive, and then restore that image to the new drive. For some reason there's a feature for imaging to ignore and log...
Yeah it's the same drive. I ended up replacing it with a Crucial drive that i had ran seatools and a full surface test first before installing windows on it this time. Funnily enough i decided to try...
I've finally moved to a second drive, and can confirm that the original drive in question still has the same bad sectors spotted by hdtune, and that's running off USB, so completely different...
Yeah i'll definitely keep that as an option. I'm going to see if it's possible to fix the drive enough to get past Macrium's Error Code 23 - Data error (cyclic redundancy check) first.
Neither to both. I haven't actually had any noticeable errors other than bad block errors in event log "The device, \Device\Harddisk1\DR1, has a bad block.". Infact, hard drive sentinel and...
Oh i already know my OS drive has some issues despite only having a couple weeks of use as shown by a hdtune error scan i ran recently. I've already had seatools fail on this drive. I just wanted to...
The mounting thing was related to the first post by SIW2 who noted that mounting the image might be more reliable.
- - - Updated - - -
I ran the .bat file and attached the log
I took a screenshot of the error. I was able to successfully mount the install.wim file but attempting to use dism with it still results in the same error.
Unfortunately the online version has the same issue with being unable to find the source file. This is why i tried to fix it via windows image file. I converted the ESD into a WIM and put it on a...
Unfortunately i've tried it without /limitaccess, and also without designating a source and both times the result has been the same where the source file could not be found.
I attempted to export...
I ran SFC and stumbled onto a corrupt file that it could not repair. The log shows "Cannot repair member file [l:7]'ksc.nlp' of mscorlib, version 10.0.19200.595"
I attempted to use DISM to fix...
Yeah i haven't decided on a brand for my next drive but it's probably going to be a different one for certain. I was considering getting a Crucial brand drive to replace this as an OS drive, while...
BTW have you ever seen device manager display the wrong drive? For whatever reason instead of showing my OS SSD as what it is it just shows it as another copy of my HDD.
Sounds like i'm replacing this drive then, pretty tragic seeing as how i've only used it for about 3 weeks.
Tried out seatools short generic test on the drive in question and it seems to abort itself after 9% Wonder if it's running into the exact same damaged blocks hdtune is, i have no idea how that works.
Would windows still report those bad sectors? I also have a couple of these "A corruption was discovered in the file system structure on volume C:." errors logged
Also looking closer at HD...