Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

BSOD, Page Fault


  • Please log in to reply

#1
Gabriel1

Gabriel1

    Member

  • Member
  • PipPipPip
  • 156 posts
Last couple of days i've gotten 3 BSOD's, 2 stating 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA, the other said something about MEMORY_MANAGEMENT so i thought of course i must have fault ram, well i ran memtest overnight (12hours) and 0 errors so now im stumped. (although i ran the memtest with all 4 sticks in) i also ran system file checker and nothing wrong.

heres my pc specs;

CPU; AMD phenom x4 955
Mobo; msi g45 870
GPU; amd HD 6670
PSU; coolermaster 500w
ram; 12gb ram 2x 4 and 2x 2 (all crucial same stick models just different amount)

ran bluescreenview and heres the 3 BSOD's;

==================================================
Dump File : 090812-27721-01.dmp
Crash Time : 9/8/2012 8:59:32 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffb8a0`147915d0
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`03374fbb
Parameter 4 : 00000000`00000007
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090812-27721-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,192
==================================================

==================================================
Dump File : 090712-25412-01.dmp
Crash Time : 9/7/2012 10:15:10 PM
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00005003
Parameter 2 : fffff700`01080000
Parameter 3 : 00000000`00005017
Parameter 4 : 00000000`610d6005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090712-25412-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,192
==================================================

==================================================
Dump File : 090612-26020-01.dmp
Crash Time : 9/6/2012 11:48:45 PM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : ffffb8a0`0e894de8
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`033b8fbb
Parameter 4 : 00000000`00000007
Caused By Driver : Wdf01000.sys
Caused By Address : Wdf01000.sys+35102
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\090612-26020-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 275,192
==================================================



any help would be appreciated thanks. i did notice each one points to ntoskrnl.exe but no clue what to do about it.

Edited by Gabriel1, 08 September 2012 - 07:20 PM.

  • 0

Advertisements


#2
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
I am about to sign off

However to get you started

MEMTEST
*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.


With your ram configuration it is VITAL to test as above.

Having read your last on the other topic re Norton, I feel sure you will know, and thanks for the contribution - However it is easy to become confused.

I would advice that you take out three sticks, leaving one in and place the three on a piece of card - on which are marked SLOT ONE SLOT TWO etc., in their respective positions - against the entry - RUN ONE

Then run Memtest

Now take out the stick that was left in and replace it with the one from slot 2 - IN THE SAME SLOT as originally tested on the first run

THIS is marked RUN TWO

I am sure by now you have the idea.

NOW having tested all four sticks in that slot and of course depending on the motherboard, as to which slots must be populated - you then run two sticks as SINGLE CHANNEL - eg ONE IN EACH COLOUR of slot

TEST and follow the logical pattern

Now if that passes ALL sticks - you proceed to dual channel - TWO sticks same colour alot

ONLY when you have done this can you be assured that the ram OR indeed the configuration of the ram is not to blame. - or indeed a slot.

IF all those test do not show an error and as you say the last couple of days - what has been installed and what updates if any done in that time.

I would run a full chkdsk eg chkdsk /r on the O/S drive.

and I would I think be tempted to exmaine closely what has changed - especially driver updates and as it is only two days and depending on backups of anything in those two days I would restore to a point before. - that of course will not solve a ardware problem, but it may well solve a conflict of a driver or software, or indeed update.
  • 0

#3
Gabriel1

Gabriel1

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 156 posts
thanks macboat, never thought of running memtest with the sticks individually. ill try to get it done today and report back.
  • 0

#4
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
OK will wait t hear from you
Memtest
just so you have extra confirmation than my typing

If you have more then one module in your system, test them one by one, if
one is consistently giving errors and another is consistently showing no
errors it's a pretty good bet that the module giving the errors is simply
defective. To exclude the possibility that a defective slot is throwing
your results, use the same slot to test each different module.

If each module by itself shows no errors, but when you place two or more
modules into the machine at the same time you do get errors, you are most
likely stuck with a compatibility issue and unfortunately there isn't a
whole lot you can do about it. Be sure to check your computer/motherboard
manual to see if the setup you are trying is allowed, some boards require
special restrictions in the sizes of modules, the order of modules, the
placement of double sided and single sides modules and more of such things.

In some cases having more than one memory module in the system also affects
the timing of the memory system, which might just be enough for the system
to start giving error. The question is whether this is just an unfortunate
combination of factors or whether there is actually a defective component in
the system. And in the latter case which component is the problem.
Elimination of factors is the way to diagnose this. If all components are
actually in order you may simply need to relax the memory latencies a little
bit to relieve the problem.

If you have only one module in your system, or all modules are giving
errors, there are only very few options left. The only thing you can do
really is to try the module(s) in another slot. Finally simply try out
different orders of the memory modules, although your manual might not
mention anything on the matter sometimes there simply exist timing or other
issues which can be resolved by changing the order of your modules. And of
course test each slot by putting a single module into that slot and running
memtest on it.


  • 0

#5
Gabriel1

Gabriel1

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 156 posts
alright so i ran memtest (stayed up all day changing sticks)i ran each stick individually in the first dimm, then ran them each on the other 3 dimms, all the dimms are fine and all the sticks are fine i then put in 2 in dual channel, thats where the errors began, i then changed the same two ram sticks into the other 2 dual channel dimms and got same errors.

just to be sure i changed the ram sticks around and got the same errors no matter what sticks were in dual channel so i guess theres something wrong with the configuration or something wrong with my mobo and dual channel, just no clue how to resolve it.
  • 0

#6
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Well I admire your staying power

Have you tried my suggestion of two sticks - one in each of the coloured slots using the 2 - 4GB
in otherwords single channel

Send me please the detailed spec of each of the ram sticks and PLEASE address the point I raised on my last re the couple of day period.

AND
How LONG has that ram been in the computer against how long has it shown a problem

Are ram settings and processor default or tweaked



  • 0

#7
Gabriel1

Gabriel1

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 156 posts

Well I admire your staying power

Have you tried my suggestion of two sticks - one in each of the coloured slots using the 2 - 4GB
in otherwords single channel

Send me please the detailed spec of each of the ram sticks and PLEASE address the point I raised on my last re the couple of day period.

AND
How LONG has that ram been in the computer against how long has it shown a problem

Are ram settings and processor default or tweaked


ram settings are default, i did try that suggestion about the colored slots, i tried basically every configuration i could think of.

Heres the ram sticks im using; i have 2x; http://www.newegg.co...N82E16820148538
and; http://www.newegg.co...N82E16820148541
each running dual channel (the 2gb with 2gb and 4gb with 4gb) for a total of 12gb of ram.

the 2gb sticks have been running in the system since i built it (maybe 6months) the 4gb sticks have been running for maybe 2-3 weeks *note i didnt get any bsods before*

can a wrongly seated CPU fan cause bsod's? thats the only hardware change ive made since the 4gb sticks.

also, to the two days portion the only thing that has changed within the last 2 days since bsod's started has been small downloads, no windows updates, no driver updates nothing.

Since the BSOD's ive started updating drivers... since the extensive memtesting i havent gotten any BSOD's but theres no way for me to tell if it'll happen again.

Edited by Gabriel1, 10 September 2012 - 02:24 PM.

  • 0

#8
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Cheers

Give me time to look will you please - probably be tomorrow now about 1600

There is no need to quote my post, in fact please only quote what you wish to highlight.

For tonight please just confirm that two of the 4 GB or indeed two of the 2GB or indeed 1 4GB and one 2GB do not crash in single channel so we have two sticks - of any combination ONE in each of the coloured slots

I apologise for labouring the point but it is important


and if by the

can a wrongly seated CPU fan cause bsod's? thats the only hardware change ive made since the 4gb sticks.


you mean the cooler as well, as against the FAN ONLY the answer is a positive 100% yes as it may well then have overheated.

HOWEVER had it done so, the system would more than likely have shut down on severe overheat, or gone into minimum mode and if the damage was REAL, as against only an overheat, I would expect you to have MANY crashes, shutdown etc NOW
WHATEVER the ram situation of sticks in slots.
  • 0

#9
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
I have posted separately so yu do not miss it in case you have already read my last

Since the BSOD's ive started updating drivers... since the extensive memtesting i havent gotten any BSOD's but theres no way for me to tell if it'll happen again.


Once I had satisfied myself as far as possible and indeed satisfied you, that we had thoroughly checked the ram, I was moving then onto the changes
and drivers.

DOES this in bold mean please NO BSOD in dual channel now with all installed, if so it may well be a driver update

I am more than prepared to continue, but if the problem appears SOLVED at this time and of course you can come back as you wish, there is no point in my further investigation.
  • 0

#10
Gabriel1

Gabriel1

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 156 posts
well right now all 4 sticks are seated in dual channel, havent had a BSOD in a day but i can't recreate the BSOD so i dont know if it'll happen again...
  • 0

Advertisements


#11
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
OK

It maybe, that a driver update has cured it.

As soon as it occurs post back with the crash and I will resume with further testing for you.

This in the meantime may help you further understand the philosphy of the testing.

http://www.memtest86.com/tech.html

If you feel that there is anything else that can be done now please just ask.

HOWEVER I do not know if I missed it but I have just realised that you never commented

I would run a full chkdsk eg chkdsk /r on the O/S drive

me thinks

I would also run a system file check
cmd with admin rights
sfc /scannow
  • 0

#12
Gabriel1

Gabriel1

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 156 posts
yes ive run both already thanks for your help macboat.
  • 0

#13
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Good and all in order I presume
No violations reported on sfc
No file errors or of course bad sectors on the HDD


I will remain subscribed to your topic, so I will know as soon as you post - when I am online
  • 0

#14
Gabriel1

Gabriel1

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 156 posts
Hey macboat, sorry for bumping up a semi-old thread, got a BSOD this morning... caught me off guard and upset me quite a bit. I took out my older ram because im sure thats not the problem, i ran 8gb of ram (2x4, newer sticks i recently bought) through memtest, at the 4hour mark got errors...

My question is, how do i know if its the ram, ram settings, or the mobo? Right now im running the ram sticks individually to see if they get any errors, but lets say hypothetically there are no errors, what then? or lets say there are errors, what do i do? how do i rule out that it's not the mobo settings.

right now im running on a msi 870 g45 motherboard on stock settings no overclocking, coolermaster extreme 500w PSU, right now the ram sticks im running is this; http://www.newegg.co...N82E16820148538 x2...

maybe its a compatibility issue im not aware of?


edit: also i forgot to mention that the BSOD's are Memory Management and Page fault BSOD's.

Edited by Gabriel1, 01 October 2012 - 08:47 PM.

  • 0

#15
Gabriel1

Gabriel1

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 156 posts
update; first test 9 passes no errors but as soon as i go to shutdown the PC i get a IRQL BSOD so i don't know what to make of it.... right now im running memtest on the other stick to see if it gets any errors but does it even matter since i already got another BSOD with a supposedly good piece of ram?
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP