![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| RAM and Power Supply Support Support forum for memory and power supplies; Kingston, Corsair, PNY |
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Registered User
Join Date: Apr 2009
Posts: 3
OS: WinXP SP2
|
Odd memtest86 results & RAM-related BSOD (stop 0x00000050)
Hi there... My new rig has been suffering from the same BSOD randomly (while gaming, opening the control panel, browsing the internet... etc) (BSOD stop 0x00000050: PAGE_FAULT_IN_NON_PAGED_AREA) and my research has pointed to RAM as a likely culprit, although there are other possibilities.
System Specs:
Eventually I found out that I could consistently reproduce the BSOD by starting a virtual machine in VMware, and some quick testing revealed that the BSOD happens when I have any two or more DIMMs installed, in any order. I tested this the following way: As per my motherboard's instructions, I used slots 1, 3 and 5 for my RAM. The serial numbers of my three DIMMs ended in 1, 2 and 3, so when I say (1,2,x) I mean that I had DIMM 1 in slot 1, DIMM 2 in slot 3, and nothing in slot 5. Tests: (3,2,1): BSOD on VMware virtual machine startup (1,2,3): BSOD on VMware virtual machine startup (3,2,x): BSOD on VMware virtual machine startup (3,1,x): BSOD on VMware virtual machine startup (1,2,x): BSOD on VMware virtual machine startup (3,x,x): No BSOD - runs fine (2,x,x): No BSOD - runs fine (1,x,x): No BSOD - runs fine As you can see, the BSOD seems dependent upon how many DIMMs are installed, but not on the order or _which_ DIMMs are installed. Because of this I was tempted to say that faulty memory wasn't the problem, but I had to run memtest to be sure. When I ran memtest86 v3.5 (with DIMMs 3,2,1), it stopped after 3 seconds with the following result: Test #0, 5%: [Address test, walking ones, no cache]I've never played around much with memtest, so I'm not sure why it stopped. But, since I thought faulty memory was probably the cause, I reconfigured to (1,3,2) and ran memtest again. I got the same result, including the same error addresses, even though the DIMMs were in different slots. I got the same result for (1,3,x) and (1,2,x). However, when I ran memtest86 with only one DIMM (1,x,x) (2,x,x) and (3,x,x) it ran fine and for each found no errors. I ran memtest86 v3.4 with the configuration (3,2,1) and received no errors. I also ran memtest86+ v2.11 for several passes with (3,2,1) and it reported no errors. Some random facts that may help:
I'm pretty clueless about what's going on here. If it weren't for memtest86 3.5 reporting the errors, I'd say it wasn't a memory problem at all... The fact that memtest 86 v3.5 reports no errors for individual DIMMs and that I don't get any BSODs while using only a single DIMM makes me think... motherboard, possibly? It could also be WinXP 64bit. But if the problem is simply the OS, would memtest86 v3.5 report any errors? Thanks for taking the time to read (or skim!) all this. Any help with this is _greatly_ appreciated. Last edited by Kerek; 04-11-2009 at 07:30 PM. |
|
|
|
| Important Information |
|
Join the #1 Tech Support Forum Today - It's Totally Free!
TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free. Join TechSupportforum.com Today - Click Here |
|
|
#5 (permalink) |
|
Moderator, Hardware Team
Join Date: May 2008
Location: S.E. Pennsylvania
Posts: 18,459
OS: Win7
|
Re: Odd memtest86 results & RAM-related BSOD (stop 0x00000050)
I think it's a memory mismatch the i920 doesn't support PC3 16000, OCZ does not list any EVGA boards in their configuration utility, and Crucial only lists slower speeds the ram should be defaulting to PC3 10600 or 1333Mhz,
http://www.crucial.com/store/listpar...132-BL-E758-A1) http://conf.ocztechnology.com/index....08&mfrid=11611 Corsair does list 16000 Speed but that would be for the i7 965. http://www.corsair.com/configurator/...aspx?id=767751 Have you updated to the latest Bios? There have been a lot of Ram related Bios updates for the X58 series in general, Can't say for sure about EVGA boards. |
|
|
|
|
|
#6 (permalink) |
|
Registered User
Join Date: Apr 2009
Posts: 3
OS: WinXP SP2
|
Re: Odd memtest86 results & RAM-related BSOD (stop 0x00000050)
Well, with a bit of googling I came up with this:
http://communities.vmware.com/threa... Apparently the BSOD is standard given my vmware version under XP 64bit. The random BSOD's I had gotten while doing other things (the ones mentioning disk.sys) vanished as soon as I disconnected my old 400gb seagate barracuda. Random, yes. Hopefully this will help anyone else looking for a solution. Thanks for all your answers! |
|
|
|
![]() |
| Thread Tools | |
|
|