BSOD Please help.

[SlothKing]

I'm not new to pc's but i cant figure out why i have had so many blue screens, can someone please help me figure out the problem?
sometimes i get a blue screen if i'm playing games, or even browsing the internet!
i had one today when i tried to update my Windows Experience index.

i have the latest drivers from AMD, have updated my motherboard bios but i still seem to get the blue screen. I understand that there is a good chance its my hardware but i'm not sure.

the latest bluescreen i got was this: PAGE_FAULT_IN_NONPAGED_AREA
STOP: 0X00000050 Then a bunch of letters and numbers (sorry i cant remember them)

Any help would be very much appreciated!

 

[Bluemoon_9]

Run memtest86+ overnight (8 passes) and report the results. And download bluescreenviewer to check which file is causing the BSOD.

 

[SlothKing]

Run memtest86+ overnight (8 passes) and report the results. And download bluescreenviewer to check which file is causing the BSOD.

Ok thank's, i'll see how it goes

 

[SlothKing]

Run memtest86+ overnight (8 passes) and report the results. And download bluescreenviewer to check which file is causing the BSOD.

Got the blue screen viewer and all the blue screens have these files highlighted in red (im assuming thats not good)
i will run the memtest soon and see what happens.
these are the files below.

atikmdag.sys
ntoskrnl.exe
fltmgr.sys
nvlddmkm.sys
win32k.sys
HDAudBus.sys
ataport.SYS
aswSP.SYS
CLASSPNP.SYS
fvevol.sys
Ntfs.sys

 

[Bluemoon_9]

Bunch of things here, all unrelated

I am inclined to say its a hardware problem. How many RAM sticks do you have?

 

[WinOutreach6]

SlothKing,

Blue screen errors can be cause by both hardware and software issues. In your case, 0x00000050 is the value given to the PAGE_FAULT_IN_NONPAGED_AREA bug check which indicates that invalid system memory has been referenced.

The Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA page contains information relating to the blue screen error that you’re receiving. Some of the possible causes it lists for this error include:

• The installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

• The installation of a faulty system service.

• Antivirus software.

• Corrupted NTFS volumes.

Ways to resolve these issues are also mentioned on the page referenced above, such as:

• Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

• Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

• Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

• Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

Another thing to be aware of is that if the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.

You can also check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

Another resource you may find helpful is the Resolving stop (blue screen) errors in Windows 7 page.

Hope this helps!

Mike
Windows Outreach Team – IT Pro
The Springboard Series on TechNet