New
#1
BSOD random - ntoskrnl.exe and ntkrnlmp.exe errors
Intel Core i7-2600K CPU @3.40 GHZ
12 GB RAM - OCZ Agility 3 120GB SSD
Hello,
Over the course of the past few weeks I've been getting all kinds of random BSOD's. At first they mainly started when accessing netflix but slowly escalated to just randomly when I'm using photoshop to do my client work. Sometimes they'll just happen when I let the computer idle for too long and it goes into sleep mode. Usually after the BSOD I'll restart it but it wont read the hard drive but after another shutdown it'll read again.
Whenever I run chkdsk /r the computer starts running great again but slowly goes back to the BSOD. Also, whenever I run chkdsk /r after having used the computer (BSOD or not) it always cleans through everything as opposed to saying its already clean.
Is this a bad SSD drive? I have no idea whats going on . Any help would be greatly appreciated!
Heres my Crash dump analysis(it doesn't always catch the crashes, they happen daily)
On Thu 4/26/2012 3:36:52 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042512-27471-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800AC29B30, 0xFFFFFA800AC29E10, 0xFFFFF800035928B0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 4/26/2012 3:36:52 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, 0xFFFFFA800AC29B30, 0xFFFFFA800AC29E10, 0xFFFFF800035928B0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 4/23/2012 7:35:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042312-30045-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B3DA060, 0xFFFFFA800B3DA340, 0xFFFFF800035908B0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 4/15/2012 3:11:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041412-29421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA800B334060, 0xFFFFFA800B334340, 0xFFFFF800035E18B0)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.