Hi,
I've had a myriad of problems with my new SSD. It's a Samsung 850 EVO which doesn't want to work at all. I purchased it on Jun 1st of this year, installed Windows, and shelved it until the rest of my PC parts got here. It kept giving me a BSOD when I would boot, which was chalked up to just reinstalling W7 to fix it, and it did. But now I get nothing but KERNAL_DATA_INPAGE_ERROR. CRITICAL_OBJECT_TERMINATION, and f4 STOP errors. I tried reinstalling Windows, using a different SATA port, changing AHCI mode to something else then back again, memtests which came up fine, chkdsks which, for some reason, came out fine every time. Now it won't boot at all -- no boot error, no error screen, nothing. It boots up, and automatically boots to my secondary HDD, though it'll still be listed under my drive list and be functional as one.
I've contacted Samsung, but I'd like to avoid dealing with them and instead deal with a person who knows what they're talking about, not reading from a manual or remembering training.
Thanks!
WhoCrashed read outs:
On Fri 7/31/2015 11:54:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073115-5428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80074DEB10, 0xFFFFFA80074DEDF0, 0xFFFFF80002FD6E20)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 7/31/2015 11:54:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80074DEB10, 0xFFFFFA80074DEDF0, 0xFFFFF80002FD6E20)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 7/31/2015 3:34:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073015-4742-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008C57B10, 0xFFFFFA8008C57DF0, 0xFFFFF80002FC3E20)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 7/31/2015 3:07:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073015-5304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x7A (0xFFFFF6FC5002BF88, 0xFFFFFFFFC000000E, 0x13D7DD880, 0xFFFFF8A0057F16D4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
I've had a myriad of problems with my new SSD. It's a Samsung 850 EVO which doesn't want to work at all. I purchased it on Jun 1st of this year, installed Windows, and shelved it until the rest of my PC parts got here. It kept giving me a BSOD when I would boot, which was chalked up to just reinstalling W7 to fix it, and it did. But now I get nothing but KERNAL_DATA_INPAGE_ERROR. CRITICAL_OBJECT_TERMINATION, and f4 STOP errors. I tried reinstalling Windows, using a different SATA port, changing AHCI mode to something else then back again, memtests which came up fine, chkdsks which, for some reason, came out fine every time. Now it won't boot at all -- no boot error, no error screen, nothing. It boots up, and automatically boots to my secondary HDD, though it'll still be listed under my drive list and be functional as one.
I've contacted Samsung, but I'd like to avoid dealing with them and instead deal with a person who knows what they're talking about, not reading from a manual or remembering training.
Thanks!
WhoCrashed read outs:
On Fri 7/31/2015 11:54:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073115-5428-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80074DEB10, 0xFFFFFA80074DEDF0, 0xFFFFF80002FD6E20)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 7/31/2015 11:54:05 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA80074DEB10, 0xFFFFFA80074DEDF0, 0xFFFFF80002FD6E20)
Error: CRITICAL_OBJECT_TERMINATION
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 7/31/2015 3:34:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073015-4742-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8008C57B10, 0xFFFFFA8008C57DF0, 0xFFFFF80002FC3E20)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 7/31/2015 3:07:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\073015-5304-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0x7A (0xFFFFF6FC5002BF88, 0xFFFFFFFFC000000E, 0x13D7DD880, 0xFFFFF8A0057F16D4)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.