BSOD on a mates machine

Stildawn

Stildawn

New Member
Hi All

My mate has been getting BSOD on his near new machine (a month or two old really)

AMD PII 955 @ stock
Gigabyte GA-880GM USB3
A-RAM 2x2gb DDR3 1600mhz
ATi HD5770 1gb

From what he tells me the two BSOD he gets are:

REGISTRY_ERROR
PAGE_FAULT_IN_NONPAGED_AREA

From my limited understanding of BSOD, the Registry Error is an error occuring when the computer is trying to read the registry and is a software problem... However the page fault one leads me to believe its the ram?

Any suggestions on how to proceed on this? Testing? Theories etc?

Cheers
 
Last edited:
Have him do the following and post the log from it.

Download BlueScreenView
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
 
Im guessing that details the exact BSOD? Ok he is bring his computer around for a lan this weekend so Ill get him to do it then lol

Cheers
 
johnb35 said:
Have him do the following and post the log from it.

Download BlueScreenView
No installation required.
Unzip downloaded file and double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.
Click to expand...
+1.

From personal experience with my BSOD-plagued laptop, the page fault error deals with either a dying hard drive or bad RAM. For me it was the hard drive, although I would think the registry error BSOD would point to bad RAM. Have your friend run an HDTune error scan:
http://www.hdtune.com/download.html
Make sure to run the full scan, not the quick one. Also, try running Memtest86+:
http://memtest.org/#downiso
There are installers for a USB flash drive or a CD, both of which you'll have to boot from to run the program.

Good luck! :)
 
Im suspecting the ram to... The thing is that when I built the damn thing I tested the ram for hours in my rig under memtest... Hours and hours and it passed brilliantly...

The HDD is western digital... And Ive never had a problem with them out the box... But the ram... The ram is a cheap brand (although looks pretty flash with heat sinks etc lol) but still cheap...
 
Stildawn said:
Im suspecting the ram to... The thing is that when I built the damn thing I tested the ram for hours in my rig under memtest... Hours and hours and it passed brilliantly...

The HDD is western digital... And Ive never had a problem with them out the box... But the ram... The ram is a cheap brand (although looks pretty flash with heat sinks etc lol) but still cheap...
Click to expand...
Yeah, WD hard drives usually last quite a long time. I still have a 10 gig drive sitting in my closet from 10 years ago, lol. :) Still, hard drive failures go by the bathtub curve. That means that most drives will die in the first year or so from a defect, and the majority of the rest will go to live on for quite a while.

So, ya never know. Still, good idea running memtest on the computer before you gave it to him. I probably wouldn't have thought of that.
 
I had to try 3 different motherboards in the damn thing til I found one that worked lol thats why... Thats the problem when you are scrapeing the bottom of the barrel trying to cut costs lol.

Two Mobos were boardaline enough for the rest of the components and thus were full of problems (one just didnt post ever and the other would crash as soon as the computer was stressed), and the third one (the one Im using now) I only used cause the shop ****ed me around in the one I wanted and thus offered me this one at cost + gst lol.
 
I havent done what you suggested yet John... He is bringing it round on the weekend so Ill try it all then...

He says it works fine most of the time just that is gets these BSOD every now and again like twice or week or something, but like he games on it fine...

If your refering to when I built it? Yeah I built it and then stress tested it for over 48 hours and it was mint, hence I gave it to him lol. That was maybe a month ago now...
 
Heres the BSOD info:

==================================================
Dump File : Mini072011-01.dmp
Crash Time : 20/07/2011 8:48:00 a.m.
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffa80`6b79303a
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`02e1bd16
Parameter 4 : 00000000`00000005
Caused By Driver : aswSP.SYS
Caused By Address : aswSP.SYS+41db0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini072011-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 271,320
==================================================

==================================================
Dump File : Mini071911-02.dmp
Crash Time : 19/07/2011 7:10:08 p.m.
Bug Check String : REGISTRY_ERROR
Bug Check Code : 0x00000051
Parameter 1 : 00000000`00000001
Parameter 2 : fffff880`0f5694b0
Parameter 3 : 00000000`ffffffff
Parameter 4 : 00000000`000003c1
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini071911-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 271,320
==================================================

==================================================
Dump File : Mini071911-01.dmp
Crash Time : 19/07/2011 7:02:42 p.m.
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffa81`04c1d304
Parameter 2 : 00000000`00000000
Parameter 3 : fffffa60`012e4d24
Parameter 4 : 00000000`00000005
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+5ec20
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini071911-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 262,144
==================================================

==================================================
Dump File : Mini071811-01.dmp
Crash Time : 18/07/2011 5:55:01 p.m.
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffff881`0e3fc688
Parameter 2 : 00000000`00000001
Parameter 3 : fffff800`02b5016b
Parameter 4 : 00000000`00000005
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+19f1
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini071811-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 271,320
==================================================

==================================================
Dump File : Mini071711-01.dmp
Crash Time : 17/07/2011 8:14:01 a.m.
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00000000`77996cba
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`0000fffe
Parameter 4 : fffffa60`0adc5ca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini071711-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 271,320
==================================================

==================================================
Dump File : Mini070111-01.dmp
Crash Time : 1/07/2011 3:46:43 p.m.
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00000000`77926cba
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`0000fffe
Parameter 4 : fffffa60`0a1ceca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini070111-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 271,320
==================================================

==================================================
Dump File : Mini062511-01.dmp
Crash Time : 25/06/2011 5:55:53 a.m.
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00000000`77316cba
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`0000fffe
Parameter 4 : fffffa60`09b67ca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini062511-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 271,320
==================================================

==================================================
Dump File : Mini062311-01.dmp
Crash Time : 23/06/2011 12:44:18 p.m.
Bug Check String : APC_INDEX_MISMATCH
Bug Check Code : 0x00000001
Parameter 1 : 00000000`777c6cba
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`0000fffe
Parameter 4 : fffffa60`01dc1ca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini062311-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 271,320
==================================================

==================================================
Dump File : Mini060611-01.dmp
Crash Time : 6/06/2011 12:36:42 p.m.
Bug Check String : PFN_LIST_CORRUPT
Bug Check Code : 0x0000004e
Parameter 1 : 00000000`00000099
Parameter 2 : 00000000`00156581
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00006a6b
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+5a490
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+5a490
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini060611-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 271,320
==================================================

==================================================
Dump File : Mini060311-01.dmp
Crash Time : 3/06/2011 10:22:31 p.m.
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff980`09066d5c
Parameter 3 : fffff980`0ef6d178
Parameter 4 : fffff980`0ef6cb50
Caused By Driver : atikmdag.sys
Caused By Address : atikmdag.sys+3c64e9
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : atikmdag.sys+39ad5c
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\Mini060311-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6000
Dump File Size : 271,272
==================================================
Click to expand...
 
Is avast installed on the system? All the other errors point to either memory or driver issues.
 
I would definitely run that HDTune scan. I seem to remember ntoskrnl often being the cause of the BSODs on my laptop. It turned out that my drive had a bad sector, which I supposed was in the page file (which would cause the page file BSOD that you were getting). If it is the hard drive, then it's a good thing you caught it in the BSOD stage rather than the mass file corruption stage. I was able to clone my laptop hard drive before it got too corrupted, but I was not as lucky with another one of my drives....
 
You must log in or register to reply here.
Back
Top