BSOD error 0X0000007A

[jayjaypanda]

Hello, I just got my first BSOD today. And now it happens every hour or so. I'm not sure what to do. I have all the necessary files attached, I believe. Thank you for any help you can give.

 

[Arc]

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

Use !analyze -v to get detailed debugging information.

[COLOR=Red]BugCheck 7A[/COLOR], {4, 0, fffffa801202e100, 7feed80e738}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36ad9 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  [COLOR=Red]Typically caused by
a bad block in the paging file or [B]disk controller erro[/B]r.[/COLOR] Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)
Arg2: 0000000000000000, error status (normally i/o status code)
Arg3: fffffa801202e100, current process (virtual address for lock type 3, or PTE)
Arg4: 000007feed80e738, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

We should pay attention to the disc controllers at first. The Disc Controller being used there is Intel(R) Mobile Express Chipset SATA RAID Controller.

We know that Intel RST is crash prone at its own virtue, and RAID is also problematic at its own virtue. But there is only one possible way to revert it back.

Boot into the BIOS. Disable Intel Rapid Storage. Set the SATA controller mode to AHCI. Then perform a http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html

Then report us back how the computer is running. If still it is showing the same results, we need to concentrate on the HDD and some other hardware one by one.

 

[jayjaypanda]

I haven't done anything so far, just sfc /scannow 2 or 3 times and I've had no blue screens so far. The laptop isn't running slow anymore either, so should I still do as you suggested or should I just leave it be until another issue arises?

 

[Arc]

That is totally your decision

 

[jayjaypanda]

So i ran CHKDSK /R in the command prompt and I recorded this log. Not sure if it shows anything, but I see that it made some corrections in the volume bitmap?

 

[Arc]

Yes it says that some bad clusters are repaired