Forum Home
Press F1
 
Thread ID: 102052 2009-08-05 10:41:00 Is memtest86 the be all/end all? sammo450 (13626) Press F1
Post ID Timestamp Content User
798483 2009-08-05 10:41:00 Memtest says it's fine, so it is. Is this accurate, or is there a reasonable chance it didn't see something? I have had two PAGE_FAULT_IN_NON_PAGE_AREA BSODs in the past two days, and I found this in eventvwr: The platform firmware has corrupted memory across the previous system power transition. Please check for updated firmware for your system. What is 'platform' firmware? sammo450 (13626)
798484 2009-08-05 10:52:00 Under which OS are you getting the BSOD? Does this only happen when the computer comes out of hibernation? Have you installed any new drivers/hardware recently? Jen (38)
798485 2009-08-05 10:59:00 Memtest has never failed me. How many passes did you run it for? Blam (54)
798486 2009-08-05 10:59:00 Win 7, only seen it once, not sure when it occured(in relation to power cycles), there was a modem, which has since been uninstalled.

Just one I think.
sammo450 (13626)
798487 2009-08-05 11:17:00 Generally speaking that error can mean two things - hardware or a system/ software fault.

As described by MS
This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.

For vista / W7 Click start type in cmd when it shows, right click / run as administrator - type in chkdsk C:/f Y to accept to run on next reboot - reboot PC and allow it to run through.
wainuitech (129)
798488 2009-08-05 11:35:00 Looks like that error message means update the BIOS. And it looks like that error is also common with the RC version of Win7 Speedy Gonzales (78)
798489 2009-08-05 12:46:00 Memtest is not perfect but it's very good. If you ran Memtest for say 48-hours and your PC is still alive after that, then I would say with 99.99% certainty your RAM is OK

But in your case what Speedy said makes more sense, that it's a BIOS or driver issue.
Agent_24 (57)
798490 2009-08-05 19:01:00 There is another memtester "goldmem" But I tend agree with has prevoiusly been said about win 7 rc2. remember win 7 is still a release canidate beama (111)
798491 2009-08-05 21:07:00 Looks like that error message means update the BIOS. 7

As in Wainuitechs post:
a corrupted NTFS volume can all generate this type of error.


Memtest is accurate.
However I prefer to use MS RAM Diagnostic. It's faster.

But if Memtest passed it, then forget RAM, start with the chkdsk and see how you get on.
pctek (84)
798492 2009-08-07 13:19:00 I don't think Chkdsk found any problems. Today I got a BAD_POOL_HEADER, then when I rebooted I got a dxgkrnl.sys BSOD. Could they all be pointing at a particular issue? sammo450 (13626)
1 2 3 4