BSOD browsing the web, two in less than 10 mins..

[Luisit0]

It has been a week since i had a bsod, i honestly thought my pc was finally working as it should.. It used to get bsod's quite frequently, so i updated all the drivers that needed updating with driverupdater free version and cleaned/optimized the whole pc with tuneup utilities 2013 and it ran great that whole week, but a couple of minutes ago a page_fault_in_nonpaged_area bsod and another same error bsod in less than 10 minutes apart from the first one... i have bluescreenview.exe so i opened it and checked the errors, but i dont understand anything so i took the minidump files and uploaded them here. Hopefully someone can help out here, thanks in advanced!

 

[x BlueRobot]

[COLOR="Red"]BugCheck 50[/COLOR], {fffff683ef78fb40, 0, fffff80002fa2170, 2}

Could not read faulting driver name
Probably caused by : [COLOR="red"]memory_corruption[/COLOR] ( nt!MiTrimWorkingSet+c0 )

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: More Help and Information with Driver Verifier - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Upload .NFO file:

Start rb: > Type: msinfo32 > File, Save

 

[Luisit0]

[COLOR="Red"]BugCheck 50[/COLOR], {fffff683ef78fb40, 0, fffff80002fa2170, 2}

Could not read faulting driver name
Probably caused by : [COLOR="red"]memory_corruption[/COLOR] ( nt!MiTrimWorkingSet+c0 )

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

:info: More Help and Information with Driver Verifier - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Upload .NFO file:

Start rb: > Type: msinfo32 > File, Save

Thank you! I'll try the above steps and reply back once done with results..