New
#21
The pagefile should be on the SSD. SSDs are not nearly as fragile as many people think.
I've read this so I know :) The SSD Endurance Experiment: Two freaking petabytes - The Tech Report - Page 1
Wait a second...If a Short Generic test of SeaTools says 'Fail' at 12% it's bad right?
Here is an extremely long one, but pretty much same results SSD Write Endurance 25nm Vs 34nm - Page 56
Your dump files still say it is your hard drive
Code:KERNEL_DATA_INPAGE_ERROR (7a) The requested page of kernel data could not be read in. Typically caused by a bad block in the paging file or disk controller error. Also see KERNEL_STACK_INPAGE_ERROR. If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185, it means the disk subsystem has experienced a failure. If the error status is 0xC000009A, then it means the request failed because a filesystem failed to make forward progress. Arguments: Arg1: fffff6fc5008c3d0, lock type that was held (value 1,2,3, or PTE address) Arg2: ffffffffc0000185, error status (normally i/o status code) Arg3: 000000008246e880, current process (virtual address for lock type 3, or PTE) Arg4: fffff8a01187a2a8, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address) Debugging Details: ------------------ ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error. DISK_HARDWARE_ERROR: There was error with disk hardware BUGCHECK_STR: 0x7a_c0000185
But can it be the 2TB HDD with the pagefile on it? It fails the short generic test. When I test SMART on it it keeps saying 'SMART' at drive status. CrystalDiskInfo doesn't show info of the HDD.
I think you just answered your own question. If you have another known working hard drive, switch it out and try with the other drive. The dump file said Disk Hardware Error. You told us earlier that Seatools passed. I would suggest you get all your data off the drive as soon as possible.
Well I tried to get the pagefile off it...but then after restart the HDD isn't visible in the explorer. After a second restart the HDD is back, but with the pagefile on it again. Fortunately the data on it isn't too important. I want to do a CHKDSK but then the pagefile has to off it or I have to wait hours until I can do something else again, so as long as I can't remove the pagefile AND see the drive I will do it tonight.
The pagefile isn't the problem, I'm pretty sure. The Dump file said Hardware error, and Seatools failed it, and Crystal Disk Info can't read it, I believe is what you said. If that is the case, then the Hard drive is the problem, not the Page File.
But what does the HDD do other than having the pagefile while I play a game on the other HDD? It seems logical to me that GTA writes stuff to the pagefile and then it crashes because of the HDD failing.
Technically, I can't answer because I don't know. But, I do know that the OS has to have contact with all the Hard drives. Just as an example I had a HD once, used for nothing but backups, which went bad and the computer would not even start because of it. I disconnected that hard drive and the computer started and ran just fine. Almost any time the CPU detects a Hardware error it sends the command for the system to shut down to protect itself.