0x0000007A Kernal Data Exception

[Viper2497]

The debug files are all that the program processed. Don't know if it was complete.View attachment 355411
Do you need the CBS log too after I tried to detect corruption and fix it?
Blue Screen View isn't showing these recent errors, but I do have older KDE Errors.
Most of the time, while gaming, or starting my computer, it will have a fit and lag alot, then freeze looping sound and crash giving the bluescreen. When I try to reboot sometimes, it will say no boot device found, press any key to continue. I have to keep restarting my computer and eventually it gets through to start window. Its a new hard drive, WD Black. Could it be because the motherboard is bad? Sometimes if I switch SATA ports I can resolve the boot issues. Thanks in advance.

 

[D3LL]

Welcome to the Forums Viper!

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.
Use check disk command for any errors on hard disk -
Warning: Microsoft does not recommend interrupting the CHKDSK process. Microsoft does not guarantee the integrity of the disk if the CHKDSK program is interrupted. For safety you can back up your data before using the check disk command.
Use the check disk commands as follows:
1. Click Start.
2. In search window type 'cmd' and ENTER. Right click and select 'Run as administrator'.
3. Type at the command prompt CHKDSK /P and press ENTER to scan the disk.
4. Then type CHKDSK C: /F /R and press ENTER to repair corrupt sectors, if there are any.
NOTE: The root drive has to be C: and the command may schedule a task at the system startup, if it does, then press Y to schedule a task and restart the computer to perform chkdsk.
Once chkdsk completes, boot to the desktop and then check.

You may refer to the below mentioned link for more details -
Content Removed (Windows)

Hope this helps. Let us know the results.

 

[Viper2497]

I had already run a CHKDSK, as per Microsoft Forum instruction. It didn't say anything was wrong.