*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8006e41b30, fffffa8006e41e10, fffff80002dcf270}
----- ETW minidump data unavailable-----
Probably caused by : wininit.exe
Followup: MachineOwner
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
Go to Start and type in sysdm.cpl and press Enter
Click on the Advanced tab
Click on the Startup and Recovery Settings button
Ensure that Automatically restart is unchecked
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump << where your .dmp files can be
found later.
Click and apply to exit the dialogs, then reboot for the changes to take effect.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa80069a7b30, fffffa80069a7e10, fffff80002dd5270}
Probably caused by : csrss.exe
Followup: MachineOwner
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C9, {23e, fffff8800908c904, fffff980051b2dc0, 0}
*** WARNING: Unable to verify timestamp for SmSerl64.sys
*** ERROR: Module load completed but symbols could not be loaded for SmSerl64.sys
Probably caused by : SmSerl64.sys ( SmSerl64+9904 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 0, fffff800028a2194}
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiOpenPnpRegistryKey+ba )
Followup: MachineOwner