Page Fault in Non Paged Area

Status
Not open for further replies.
disisme said:
OK... memtest came up with an awful lot of errors around the 508.9M mark. Time to get some more RAM, I think.

cpc, can you please verify that this is the issue from my minidumps and event logs (attached). Sorry, I used RAR rather than zip. There is a 1001 Event for every time I tried to start the machine, and a corresponding minidump.
Click to expand...

I can't unzip your dumps. Re-zip the files and attach the zip files here.

cpc2004
 
cpc2004 said:
I can't unzip your dumps. Re-zip the files and attach the zip files here.

cpc2004
Click to expand...
As I said, I had to use WINRAR... I've unpacked them and repacked them using winzip (on another puter). See attached.

NOTE: After running memtest, I replaced the second memory Simm (was using 3 x 256M DDR simms), but the problem still occurs.
 
Disisme,

All the crashes are at ntaccess.sys and I have no idea what it is.

Bugcheck 50 (ed65f000, 00000000, f3770ccc, 00000000)
Probably caused by NTACCESS+ccc

cpc2004
 
Anything else I can look at to get some idea on the cause cpc?

what does ntaccess.sys actually do (though that may be a red herring)?
 
dae_amp_ika_dtp said:
k here are the mini dumps.
Click to expand...

It seems it is hardware as the crash occurs at different modules. Your system crashes 18 times on 8th May. Usually hardware error crashes the PC so frequently. Unless I find the solid finding at the dump, like CPU error or 1 bit memory corruption. Otherwise I don't confirm the error. Attach Zip 10 more dumps and attach here. Maybe I can find out more clues.

Mini050805-16.dmp 0A (0004e15a, 00000002, 00000000, 804e4a7a) nt!KeSetEventBoostPriority+2e
Mini050805-17.dmp 0A (00000008, 00000002, 00000000, 804e4a6e) nt!KeSetEventBoostPriority+1d
Mini050805-18.dmp 0A (00000008, 00000002, 00000000, 804e4a6e) nt!KeSetEventBoostPriority+1d
Mini050805-15.dmp 7F (c0000005, f83cc3bf, f8965bf4, f89658f0) Ntfs!NtfsReleaseAllResources+23
Mini051105-01.dmp 4E (00000099, 00000000, 00000000, 00000000) nt!MiDeletePte+3e8

cpc2004
 
disisme said:
Anything else I can look at to get some idea on the cause cpc?

what does ntaccess.sys actually do (though that may be a red herring)?
Click to expand...
In my latest post, I mentioned that I don't know what is ntaccess.sys. I've searhed google and I have no finding. Use windows search utility to search the folder holds ntaccess.sys or scan the registry.

cpc2004
 
cpc, the crashes on 8th May are a known issue, caused by our wireless network and cordless phones being very close to the same frequency and the phone being used while I am in one particular internet program (phone rings, system crashes).

I will go out and clear out my minidumps folder, then let the machine do its BSOD loop for an hour or so and zip up the contents for you. I am thinking that there must be a single cause for these problems, because it is so frightfully consistant. Get back to you in an hour or so.

Thanks heaps for your assistance!
 
cpc, I found ntaccess.sys in the registry under HKLM/SYSTEM/ControlSet001/NTACCESS
HKLM/SYSTEM/ControlSet002/NTACCESS
HKLM/SYSTEM/ControlSet002/WEBNTACCESS
HKLM/SYSTEM/CurrentControlSet/NTACCESS
all 3 are related to 'imagepath'.

Windows search found the file in WINDOWS\SYSTEM32.

I have attached a zip file that has 2 minidumps in it...fresh ones...and ntaccess.sys.

Disturbing thing.... after 2 days of endless startup BSOD's, this morning it started up after only 2 minidumps were created. I didnt change any hardware or software....
 
update. NTaccess.sys is the security component of windows that looks after password, specifically the Administrator password. At present I dont USE a password on my XP Pro SP2 installation (thought I do get the logon window). Since I am an Admin, this may be affecting ntaccess.sys, however thats very unlikely. I think ntaccess.sys is a red herring / victim.
 
cpc2004 said:
It seems it is hardware as the crash occurs at different modules. Your system crashes 18 times on 8th May. Usually hardware error crashes the PC so frequently. Unless I find the solid finding at the dump, like CPU error or 1 bit memory corruption. Otherwise I don't confirm the error. Attach Zip 10 more dumps and attach here. Maybe I can find out more clues.

Mini050805-16.dmp 0A (0004e15a, 00000002, 00000000, 804e4a7a) nt!KeSetEventBoostPriority+2e
Mini050805-17.dmp 0A (00000008, 00000002, 00000000, 804e4a6e) nt!KeSetEventBoostPriority+1d
Mini050805-18.dmp 0A (00000008, 00000002, 00000000, 804e4a6e) nt!KeSetEventBoostPriority+1d
Mini050805-15.dmp 7F (c0000005, f83cc3bf, f8965bf4, f89658f0) Ntfs!NtfsReleaseAllResources+23
Mini051105-01.dmp 4E (00000099, 00000000, 00000000, 00000000) nt!MiDeletePte+3e8

cpc2004
Click to expand...

k cpc. here are the mini dumps... i'll be sending all of them that are on my pc. actually it crashed 20 times..i dont understand why it would all the hardware is new.
 
here are my last four...there should be a total of 26.. those were all from may 8th to 11th. what program do you use to open the .dmp files? well yeah. hope this gives you clues. thanks for your help. please not that.. after installing agp to processor drivers(updated) the computer stoped crashing as much. and that crashing occured alot during norton antivirus scan. or right after i was done with a game. thanks...
 
Dae,

I've analysed all of yours dumps and there had 7 different bugcheck codes. The failing modules are different and they are random. Obviously it is the symptom of the hardware error. Most likely it is the ram problem. Reseat your memory to another memory slot and clean the dust inside the computer case. If you have two memory sticks, take one out. If no more crash, the memory stick is the culprit. If it still crashes, swap with another memory stick.

If it is hardware error, you will have a huge Dr Watson with lots of access violation errors.
If you find the following files, attach the following files at any webspace. I will study your log and dumps.
C:\Documents and Settings\All Users\Documents\DrWatson\user.dmp
C:\Documents and Settings\All Users\Documents\DrWatson\drwtsn32.log
 
cpc2004 said:
Dae,

I've analysed all of yours dumps and there had 7 different bugcheck codes. The failing modules are different and they are random. Obviously it is the symptom of the hardware error. Most likely it is the ram problem. Reseat your memory to another memory slot and clean the dust inside the computer case. If you have two memory sticks, take one out. If no more crash, the memory stick is the culprit. If it still crashes, swap with another memory stick.

If it is hardware error, you will have a huge Dr Watson with lots of access violation errors.
If you find the following files, attach the following files at any webspace. I will study your log and dumps.
C:\Documents and Settings\All Users\Documents\DrWatson\user.dmp
C:\Documents and Settings\All Users\Documents\DrWatson\drwtsn32.log
Click to expand...

hi cpc thanks!! it works..i switched the ram from dimm slot 0 and put it into dimm slot 1. and i havent had a crash.. so is the problem memory bank 0?? if so how can it be fixed? or will i need to get a new mainboard? thanks for your help. and can i erase all .dmp files?? cause one called "memory.dmp" takes up half a gig of hard drive memory..thanks cpc
 
DAE,

Erase all the memory.dmp unless you want to study the dump by yourself. For the hardware issue, usually it is bad contact between memory stick and the memory slot due to temperature change or dust.

cpc2004
 
cpc2004 said:
DAE,

Erase all the memory.dmp unless you want to study the dump by yourself. For the hardware issue, usually it is bad contact between memory stick and the memory slot due to temperature change or dust.

cpc2004
Click to expand...

cpc, what would u recommend?my computer has great cooling and my mobo is only 2 months old.
 
dae_amp_ika_dtp said:
cpc, what would u recommend?my computer has great cooling and my mobo is only 2 months old.
Click to expand...
DAE,

No comment. Reseat the RAM fix the problem. The rule of thumb don't make any change to PC if it is stable unless if you have new requirement.

New computer does not mean no hardware problem. Usually new computer takes time to run-in like a new car. Most of the hardware error of a new PC occurs at the first week. Your PC is 2 months old and it should be stable.

cpc2004
 
Status
Not open for further replies.

Similar threads

M
Front Page Cache Issues?
Replies
13
Views
528
BbN48
B
AGenericFool
Help - Valid Windows 10 Licenses deactivate after two days?!
Replies
1
Views
337
Nelson28
N
J
The machine starts with no screen signal
Replies
1
Views
581
bazz2004
B

Latest posts

Back