BSOD playing assasins creed

[Spriya]

How to read the dmp file? Cause of error?

 

[axe0]

Diagnostics Test

 HDD TEST

Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run following tests

1. Short Drive Self Test
2. Short generic
3. Long generic

If the short generic fails, no need for the long generic.

   Note

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

Run chkdsk
Disk Check - Windows 7 Help Forums

Run HDTune to

• scan for errors, no quick scan but full scan
• check the health,
• benchmark.

It may take some time, but please take the time you need to perform it properly.
Let me know what the results are

• of the error scan,
• make a screenshot of the health of every hard drive and post the screenshots,
• post screenshots with the benchmark of the
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

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

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc5005b620, ffffffffc000000e, 28275880, fffff8a00b6c4000}

*** WARNING: Unable to verify timestamp for SysPlant.sys
*** ERROR: Module load completed but symbols could not be loaded for SysPlant.sys
Probably caused by : SysPlant.sys ( SysPlant+2544 )

Followup:     MachineOwner
---------

Processing initial command '!analyze -v; !sysinfo smbios; !sysinfo machineid; !sysinfo cpuspeed; !thread; .bugcheck; .time;'
1: kd> !analyze -v; !sysinfo smbios; !sysinfo machineid; !sysinfo cpuspeed; !thread; .bugcheck; .time;
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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 [COLOR="red"]0xC000000E[/COLOR], 0xC000009C, 0xC000009D or 0xC0000185,
it [COLOR="red"]means the disk subsystem has experienced a failure[/COLOR].
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fc5005b620, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffff[COLOR="Red"]c000000e[/COLOR], error status (normally i/o status code)
Arg3: 0000000028275880, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00b6c4000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)