Vista - URGENT HELP: Page fault in non paged area

Okay I brought a brand new Packard bell PC Ixtream M3720 and I keep getting BSOD when I game i last for like 20 min before the pc gives me bsod, The BSOD is page fault in non paged area
Send big files the easy way. Files too large for email attachments? No problem!
thats the link to the dump also all packbard bell appilcation apart from recovery manager dont seem to work they say it stop working and it closes this goes for setup my pc and all of them

ohlol wrote:
Brand new computer + problems = return to seller or contact PB's tech
support under the warranty.

If you want to be proactive, back up your data and restore the machine to
factory condition using whatever method was provided by PB. If the problems
are gone, then it was something you installed. Put back your data and move
on. If the problems still exist, it's hardware and warranty-exercising time.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

I want to know what caused the problem, I think it was a graphic driver, if it keeps giving me bsod I will send it to PB

ohlol wrote:
OK, then uninstall the video driver and install ones that you know worked.
If that solves it, great!

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ

Your minidump points to your nvlddmkm,which is probably in
c:\windows\system32\drivers

BugCheck 50, {fffffa6002a24000, 1, fffffa6002c60069, 0}
Could not read faulting driver name
Probably caused by : nvlddmkm.sys ( nvlddmkm+59069 )

Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA
The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This
indicates that invalid system memory has been referenced.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 Memory address referenced
2 0: Read operation

1: Write operation


3 Address that referenced memory (if known)
4 Reserved


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.

Cause
Bug check 0x50 usually occurs after 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).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS
volume.

Resolving the Problem
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.

Finally, 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.

Comments
Typically, this address is in freed memory or is simply invalid.

This cannot be protected by a try - except handler — it can only be
protected by a probe.


--
..
--
"ohlol" <guest@newsgroup-email.com> wrote in message
news:4e53af22dd4b1c2af2917b8cf92bbfc8@newsgroup-gateway.com...