BSOD "Page fault in nonpaged area"

[Milkey]

Hi, my friend has a problem of BSODs randomly coming while using Mozilla, playing games, doing whatever. We checked his CPU using Orthos for about 2 hours, 4 instances of the application and it was all right. He scanned his memory using memtest and it showed some errors, maybe thats the case? BTW, the computer is 2 months old and has a fresh Windows 7 64bit installation.

His comp spec :

ntel Core i5-3330 Ivy Bridge LGA1155 BOX
Goodram DDR3 8GB(2x4GB) 1333MHz CL9

Asrock B75 Pro3 Intel B75 LGA 1155 (2xPCX/VGA/DZW/GLAN/SATA3/USB3/DDR3/CROSSFIRE)

Sapphire ATI Radeon HD7850 1GB DDR5/256bit DVI/HDMI/DP PCI-Express
Seagate Barracuda 500GB SATA3 (ST500DM002)
OCZ Silencer Mk III Series 500W

 

[x BlueRobot]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

One error with MemTest86+ is enough to cause a BSOD, have they considered getting a replacement with their warranty? Have they located the bad RAM module or DIMM slot?

 

[Milkey]

Here's the file.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 50[/COLOR], {fffff88021617424, 8, fffff88021617424, 2}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+437f6 )

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

Have you located the bad RAM module or DIMM slot yet?

Run Driver Verifier for at least 24 hours, to check for any corrupted drivers; Driver Verifier will place stress on the drivers and therefore hopefully cause the faulty driver to crash and produce a BSOD indicating the file.

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

 

[Milkey]

He made the driver test for 24 hours and opened game. The game closed, but he didnt get the blue screen.

 

[x BlueRobot]

Okay, that's good, and what has happened to the bad RAM module?

Scan for any missing or corrupted protected Windows files with System File Checker, and if any errors are found, then attempt repairs by running the same program 3 separate times with reboots in between each attempt.