Windows 7 BSOD

attaching msinfo32 in zip folder, and have uninstalled Comodo and switched to MSE. :):)

More crashing again today.
This time:

Memory_Management 0x01a
Ntfs.sys Page_fault_in_nonpaged_area 0x50

Now correct me if I am wrong ntfs.sys is part of the file system used by windows add in the Memmory Management eroor could I now be dealing in bad ram/ or poor hard drive.

I'm not seeing much, you are indeed correct about ntfs.sys.
Although I don't think hardware is the case personally, there's always a possibility but I think it's a driver that we can't find...

0x50 bugchecks indicate a page fault has occurred in the non-paged pool. (It's in the name), I could go into detail but that's another matter.

Well you can run some hardware tests to see if your HDD or RAM is failing.

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Afterwards if no errors show up and everything looks good then follow these instructions to set your BSOD dump files to Kernel Memory Dumps.

Dump Files - Configure Windows to Create on BSOD

Afterwards restart your PC and wait for another BSOD, once you get one copy the file created in this directory to the desktop:
C:/Windows/memory.dmp

Upload that file to a website like OneDrive then post the download link.

Thanks, I give them a go.

Thedoctor44 said:

I'm not seeing much, you are indeed correct about ntfs.sys.
Although I don't think hardware is the case personally, there's always a possibility but I think it's a driver that we can't find...

0x50 bugchecks indicate a page fault has occurred in the non-paged pool. (It's in the name), I could go into detail but that's another matter.

Well you can run some hardware tests to see if your HDD or RAM is failing.

Memtest86 will test your RAM

   Information

Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing

Run a Disk Check to scan for errors

   Note

Afterwards go into an Elevated Command Prompt (Run as administrator) and type in sfc /scannow
If it finds errors reboot and run the scan two more times

Run SeaTools to see if your HDD or SSD is failing

Afterwards if no errors show up and everything looks good then follow these instructions to set your BSOD dump files to Kernel Memory Dumps.

Dump Files - Configure Windows to Create on BSOD

Afterwards restart your PC and wait for another BSOD, once you get one copy the file created in this directory to the desktop:
C:/Windows/memory.dmp

Upload that file to a website like OneDrive then post the download link.

memtest86 what a waste of time, formatted a usb stick to boot from with this nothing happened. Tries with a bootable dvd/cd disc nothing. Told BIOS that they were no hard dives and tried booting from both the dvd and usb stick as per instruction, nothing. STILL BOOTED to windows either memtest86 is rubbish or its not on the website correctly.

Did test the hard drive with scan disk and the seatools no issues found, ran SFC/scannow no issues found. Would love to test the ram but despite me trying many times make and re-reformatting a sub and a cd/dvd no luck getting the program to run. Oh well. I am thinking of running the "windows memtest" instead.

What exactly did it say when you tried to run memtest86?

Anyway, proceed with changing your dump files to Kernel Memory Dumps.

Change the dump files. When I tried booting to cd or usb stick nothing happened, which is a shame I did everything it told us too. I going you give version 4 a try, maybe there is an issue with 5.01. Just as I finished writing this it crashed again.

And again it buggered off..... This time it was win32k.sys 0x50a, it would have attached a new dump file but for some reason windows did do one. < Lazy windows. :)

And still no luck booting into version 4.3.1 with either cd or usb stick.