My Computer Blew up!

[Nanook]

I was just sittin here and this happened, a blue screen appeared saying this...

__________________________________________________ ___________

Page_Failt_In_Nonpaged_Area

Techinical information

xxxSTOP. 0X00000050 (0XFD000A48,0x00000000,
0XF924A0C7,0X00000000

AmosNt.SYS-Zddress F924A0c7 base at F92350000, datestamp 3b5eec3d

Beginning dump of physical memory
Physical dump of memory complete

Contact your system admin or tech support group for further information

__________________________________________________ _____

EEK, wha dat??? [img]/forums/images/graemlins/shocked.gif[/img]

[7777]

Re: My Computer Blew up!

hey...sorry to hear bout it (((S)))
curious doe..
how u writing??

[Dr.Dudd]

Re: My Computer Blew up!

Bugchecks Explained: PAGE_FAULT_IN_NONPAGED_AREA
OSR Staff | Published: 24-Aug-04| Modified: 24-Aug-04

What Happened?

To understand this bugcheck code, it’s first necessary to understand what a "page fault" is. If you’re not completely sure you understand this concept, read the article So, Exactly What Is A Page Fault here at OSR Online.

The Windows Memory Manager reserves pre-defined ranges of kernel virtual address space for specific uses. Because the Windows operating system utilizes virtual memory, the Memory Manager does not necessarily assign physical memory to every possible kernel virtual address within its pre-defined ranges. The Memory Manager knows that some of its kernel virtual address ranges are used for pageable memory, and other ranges are used for non-pageable memory. For example, the kernel virtual address space that is reserved for use by the non-paged pool is (obviously) part of one of the Memory Manager’s non-pageable address spaces.

Whenever the Memory Manager detects a page fault (that is, a failure to translate a kernel virtual address to a physical address) in one of its pre-assigned address ranges in which the memory is supposed to be non-pageable, it halts system execution with a PAGE_FAULT_IN_NONPAGED_AREA bugcheck.

The only thing that can cause one of these page faults is an inadvertent reference by a kernel mode component to an invalid memory address that just happens to correspond to one of the Memory Manager’s pre-assigned non-pageable address ranges. The most common reason for this bugcheck is a driver de-referencing a bad pointer.

There are basically innumerable things that can happen that can lead to an invalid memory access, so tracking down these bugchecks can sometimes be particularly difficult. Some of the most common reasons for these bugchecks are buffer overruns and underruns, or accessing of a completely bogus address.

Who Did It?

When analyzing these crash dumps, it is either immediately obvious who caused the problem or it can take some serious detective work. The bugcheck parameters for this particular code are the invalid address that was accessed, whether the access was a read or a write, and the address of the instruction that caused the invalid access. Here are some things to think about when analyzing these dumps:

1) Why is the address bad?

a) Was it previously freed? The !pool WinDBG command can be helpful in determining this.

b) Is this potentially a buffer underrun? A buffer overrun? To determine this, you will need to look at how the address is being used. If, for example, the address is being used in a copy operation, starting your analysis believing it to be a buffer overrun might not be a bad assumption (but just don’t forget that it might not be the right assumption!).

c) Is the address just completely bogus? The !pool command is also useful here, as is the !pte command

2) Where did the address being accessed come from?

3) At which point did the address become bad? Was it previously used successfully by another component?

Using the information gathered from the above steps you can usually begin to get a better idea as to where things went wrong.

How Should I Fix It?

Using Driver Verifier and the checked build of Windows should allow you to better pinpoint the offending driver in the system. If the driver is not a driver that you have any control over, the only available option is disabling the driver until a fixed version is available.

Related WinDBG CommandsDriver update information
This page is designed to help customers troubleshoot video and/or sound problems associated with old or faulty drivers.

If you are planning on updating DirectX as well as the drivers for your sound and video hardware, we suggest installing the update for DirectX first, then the updates for your sound and video hardware.


Steps to identify your DirectX version:
Click on the Start button and select Run.
In the Open: field type in dxdiag and click the OK button.
When the DirectX Diagnostic Tool loads up you will see information about your computer. Near the bottom of the information should be the following field: DirectX Version: which will list what version you are currently running.
Check http://www.microsoft.com/directx/hom...ds/default.asp for the latest version of DirectX and update if necessary*.

*Note: Make sure you have drivers for your sound and video hardware that support the version of DirectX you are going to install. If you are not sure the drivers support the version of DirectX you are going to install consult with the company that built the sound and video hardware for more information. If the hardware came with a computer you bought then contact the computer manufacturer. Check our list of hardware manufactures for contact information Hardware Vendor List.

Steps to identify your video card and driver version:
Click on the Start button and select Run.
Type in dxdiag and click OK.
After the DirectX Diagnostic Tool loads click on the Display tab.
Your video card Name and Manufacturer will be listed in the Device section.
The version of the driver you have installed should be listed under the Driver box next to the word Version.
Visit our Manufacturer Links page to visit the manufacturer page and obtain updated drivers for your specific video card.

*Note: Please make sure you follow all the instructions on the manufacturer's website concerning the removal of current drivers and installation of updated software. For example, Nvidia recommends using the Windows Add and Remove programs utility to remove their drivers, while ATI has a driver removal utility which you can download.

Steps to identify your sound card and driver version:
Click on the Start button and select Run.
Type in dxdiag and click OK.
After the DirectX Diagnostic Tool loads, click on the Sound tab.
The version of the driver you have installed should be listed under the Driver box next to the word Version.

Steps to identify your network card and driver version:
Click Start.
Click Control Panel. If there is an option in the upper left to 'Switch to classic view', then do so.
Click System.
Click the Hardware tab, then click the Device Manager button near the middle.
Expand the Network Adapters category. Make note of the network card name and model listed.
Double click on the network card listed.
Click the Driver tab and make note of the driver Date and Version.
Visit the network card manufacturer's website using the above information to find updated network card drivers.
You can find a list of hardware manufacturers available on our Hardware Vendor List. Your hardware manufacturer should be able to provide you with the latest device driver and troubleshoot any driver installation problems. Blizzard technical support cannot assist directly with driver updates or installation.





Navigation Options: If this guide did not resolve your issue, please visit our online email webform to contact us.


Options: Print the entire solution.

Email the entire solution to yourself.

Report an issue or bug with this web page.

[Nanook]

Re: My Computer Blew up!

Thank you for such a detailed answer Dr. Dudd!

7's! Everything seems to be fine but when this thing happened it was not a pretty sight, it looked like something real bad was happening...

[j-kid]

Re: My Computer Blew up!

Did your PC start to go into standby mode and you moved the mouse or tap the keyboard?

If it is idle while you are say reading a long article, depending on the settings you have, on some computers with Windows SP2 you will experience this problem. Windows SP2 does Standby and Hibernate very poorly and when dealing with some BIOS with the newer ACPI (Advanced Configuration Power Interface) power management support will go wacky. Under the older APM (Advanced Power Management) windows handled things differently and did not experience all these various issues with some PC systems when going into or coming out of sleep or hibernate mode.

[Nanook]

Re: My Computer Blew up!

Hmmm, it's had a slow recovery from "sleep mode" a few times but I can usually get it right back by cntrl+alt+delete and then I just close the task manager window after it wakes up, heheh...

When this happened I had just clicked on a link to one of those electronic christmas cards on American Greetings site, but I'm afraid to go back and try it again. Well, it's been fine since then so it must not have been fatal, lol. I've been having a run of bad luck with just about every single thing I own breaking these days!!!

(((J-Kind))) [img]/forums/images/graemlins/70390-shhh.gif[/img]

[img]/forums/images/graemlins/notworthy.gif[/img]

[Afrocentriclady]

Re: My Computer Blew up!

Hmm look like every ting here is covered. [img]/forums/images/graemlins/70409-waytogo.gif[/img] At least I got a post out of it. [img]/forums/images/graemlins/smirk.gif[/img]