Various BSODs happening all of a sudden

[borklaser]

Last two days I've gotten 4 BSODs. No hardware changes recently, nor have there been any software changes. Only recent change is installing a Samsung 850 Evo SSD two months ago, and migrating my Windows installation to it.

Ran Memtest86 for a full pass with no errors.
Ran mutiple 3dMark tests, system was stable no artifacting.
Ran chkdsk, no errors

List of BSODs from BlueScreenView:

1) 10/4/15 - 10:36PM CRITICAL_OBJECT_TERMINATION caused by address ntoskrnl.exe+735c0
2) 10/4/15 - 10:39PM CRITICAL_OBJECT_TERMINATION caused by address ntosrknl.exe+735c0
3) 10/6/15 - 12:14AM KERNAL_DATA_INPAGE_ERROR caused by address ntosrknl.exe+735c0
4) 10/6/15 - 12:09PM IRQL_GT_ZERO_AT_SYSTEM_SERVICE caused by address serscan.sys+22adb60

 

[axe0]

Hi borklaser,

Welcome to the 7forums.

The 0x4A(IRQL_GT_ZERO_AT_SYSTEM_SERVICE) might lately being caused by the Bitdefender as the Bitdefender's main active protection process is active at the time of the crash.
Please uninstall Bitdefender using the appropriate uninstall tool you can find here and use Microsoft Security Essentials as alternative.

IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)
Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.
Arguments:
Arg1: 0000000077a4da2a, Address of system function (system call routine)
Arg2: 0000000000000002, Current IRQL
Arg3: 0000000000000000, 0
Arg4: fffff88006868b60, 0

Debugging Details:
------------------
[COLOR="Red"]PROCESS_NAME:  vsserv.exe[/COLOR]

BUGCHECK_STR:  RAISED_IRQL_FAULT

FAULTING_IP: 
+9df1a20000
00000000`77a4da2a c3              ret

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

The 0xf4(CRITICAL_OBJECT_TERMINATION) seems to be caused by Input/Output errors from 1 of your hard drives.
Please test both your hard drives

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

   Note

Do not run SeaTools on an SSD as the results will be invalid.

Run chkdsk /r http://www.sevenforums.com/tutorials/433-disk-check.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa800f8a4b10, Terminating object
Arg3: fffffa800f8a4df0, Process image file name
Arg4: fffff8000337be70, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----

KERNEL_LOG_FAILING_PROCESS:  

PROCESS_OBJECT: fffffa800f8a4b10

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - De instructie op 0x%p verwijst naar geheugen op 0x%p. De benodigde gegevens zijn niet in het geheugen geplaatst vanwege een I/O-foutstatus van 0x%x.

[COLOR="red"]BUGCHECK_STR:  0xF4_IOERR[/COLOR]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`08d999c8 fffff800`0340dcb2 : 00000000`000000f4 00000000`00000003 fffffa80`0f8a4b10 fffffa80`0f8a4df0 : nt!KeBugCheckEx
fffff880`08d999d0 fffff800`033c4d8b : ffffffff`ffffffff fffffa80`12ceb060 fffffa80`0f8a4b10 fffffa80`0f8a4b10 : nt!PspCatchCriticalBreak+0x92
fffff880`08d99a10 fffff800`0332f484 : ffffffff`ffffffff 00000000`00000001 fffffa80`0f8a4b10 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29ce6
fffff880`08d99a60 fffff800`03076853 : fffffa80`0f8a4b10 00000000`c0000006 fffffa80`12ceb060 00000000`00ebd6c0 : nt!NtTerminateProcess+0xf4
fffff880`08d99ae0 00000000`76d6dc7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00ebd618 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76d6dc7a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

[COLOR="red"]FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe[/COLOR]

[COLOR="red"]BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe[/COLOR]

ANALYSIS_SOURCE:  KM

[COLOR="red"]FAILURE_ID_HASH_STRING:  km:x64_0xf4_ioerr_image_wininit.exe[/COLOR]

FAILURE_ID_HASH:  {7e8d25f6-54c6-2456-f4df-269f2fd35200}

Followup: MachineOwner