I'm sure someone will do a more indepth analysis for you shortly, but early indications I can see from your dump file is the issue might be hardware related to memory or your hard disk.
I would suggest running a memory test, and also doing a check disk on the drive with your paging file on it (probably your C drive).
If both of those come back clean perhaps try running without AVG for a while to see if it is causing the issue (Use Windows Defender for a bit)
Code:
BugCheck 1A, {3f, 1a9cc, 35a4fd59, 35a50559}
Probably caused by : Unknown_Image ( PAGE_HASH_ERRORS_INPAGE )
Followup: MachineOwner
---------
*** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a01f599598e6bc, 0, 65edac050c631be8, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
Hi,
this bugcheck means the kernel detected critical code or data which has been corrupted. The cause of this can be down to faulty RAM, developer issues and drivers. As the analysis is inconclusive you could try running the driver verifier and see what turns up. You'll need to make a recovery key in case the verifier causes a boot loop in which case you can use the recovery key to enter safe mode and turn the verifier off. Link Removed
Link Removed
The culprit will hopefully be caught on a dump file next time you bsod. See you then..
sorry for not replying for sometime anyway got a new hdd and still got a bsod so ive changed my ram to see if that sorts it out also got the mini dump as well, ill see how it goes with the other ram ive put in
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a01f5a4908b58f, 0, 2428b68d94fac121, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
Hi,
this dump is telling us that pooled memory is being corrupted. So far analysis has proved inconclusive as to the probable cause and you need to run the driver verifier.
See post #22 on running the verifier. Do Not Forget About The Recovery Disk/USB.
As you have now changed the RAM only go through with the above if a bsod occurs. I suspect this is more of a driver issue so may find the bsod continues..