Strange XP pro BSOD

[Force Flow]

Here's what I get:

PAGE_FAULT_IN_NONPAGED_AREA

Stop: 0x00000050 (0xFFFF0000, 0x00000000, 0xF16778C8, 0x00000000)

kmixer.sys - address F16778C8 base at F1669000, Datestamp 3b7d85fd

Specs are:
Asus A7N8X Deluxe
Athlon 2500
2 sticks of Samsung PC3200 256MB
MSI GF4 Ti-series video card
Z-MAX KY-450ATX

I'm guessing one cause may be the PSU, but if the problem lies in the software, it would be easier to fix that.

This is a recent installation of the XP pro. The previous installation of XP Pro gave the same BSOD.

[Doobie]

http://forums.winxpcentral.com/showt...2625#post22625

apperently its a problem with drivers but it doesnt say what drivers.

[Doobie]

this was the anwer to the problem on another post on another site.

http://www.experts-exchange.com/Oper..._20776622.html


http://msdn.microsoft.com/library/de...codes_0ug7.asp

Cause
Bug check 0x7F usually occurs after the installation of faulty or mismatched hardware (especially memory) or in the event that installed hardware fails.

A double fault can occur when the kernel stack overflows. This can happen if multiple drivers are attached to the same stack. For example, two file system filter drivers can be attached to the same stack and then the file system can recurse back in, overflowing the stack.

Resolving the Problem
Debugging: Always begin with the !analyze debugger extension.

If this is not sufficient, use the KV (Display Stack Backtrace) debugger command.

If KV shows a taskGate, then use the .tss (Display Task State Segment) command on the part before the colon.
If KV shows a trap frame, then use the .trap (Display Trap Frame) command to format the frame.
Otherwise, use the .trap (Display Trap Frame) command on the appropriate frame. (On x86 platforms, this frame is associated with the procedure NT!KiTrap.)
After this, use KV again to display the new stack.

Troubleshooting: If hardware was recently added to the system, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run hardware diagnostics supplied by the system manufacturer, to determine which hardware component has failed. The memory scanner is especially important; faulty or mismatched memory can cause this bug check. For details on these procedures, see the owner's manual for your computer. Check that all adapter cards in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure adapter card contacts are clean.

If the error appears on a newly installed system, check the availability of updates for the BIOS, the SCSI controller or network cards. Updates of this kind are typically available on the Web site or BBS of the hardware manufacturer.

Confirm that all hard disks, hard disk controllers, and SCSI adapters are listed on the Microsoft Windows Hardware Compatibility List (HCL).

If the error occurred after the installation of a new or updated device driver, the driver should be removed or replaced. If, under this circumstance, the error occurs during the startup sequence and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer using the Recovery Console in order to access the file. Also try restarting your computer, and press F8 at the character-based 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.

Overclocking (setting the CPU to run at speeds above the rated specification) can cause this error. If this has been done to the computer experiencing the error, return the CPU to the default clock speed setting.

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.

If you encountered this error while upgrading to a new version of Windows, it might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version. If possible, remove all third-party device drivers and system services and disable any virus scanners prior to upgrading. Contact the software manufacturer to obtain updates of these tools. Also make sure that you have installed the latest Windows Service Pack.

Finally, if all the above steps fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error.

[KHT]

This might help.

Error Message:
PAGE_FAULT_IN_NONPAGED_AREA

Explanation:
This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find, the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.

User Action:
This Stop message usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, either main memory, L2 RAM cache, or video RAM). 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. Run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer. Another cause of this Stop message is the installation of a buggy system service. Disable the service and determine if 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 2000 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. Antivirus software can also trigger this Stop message. Disable the program and determine if this resolves the error. If it does, contact the manufacturer of the program about a possible update. A corrupted NTFS volume can also generate this Stop message. Run Chkdsk /f /r to detect and repair disk errors. 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 causing the error. Disabling memory caching of the BIOS might also resolve it. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at http://support.microsoft.com/support.

[Force Flow]

Thanks guys, this gives me a few things to check out.

btw, docmem gave the 2 sticks a clean bill of health

[Force Flow]

Oookay, I tried everything I could think of and finally ended up just zero filling the drive, repartitioning, and reformatting.

When I try to install XP, I get a similar BSOD

STOP: 0x0000007E (0xC0000005, 0x807cb820, 0xF9EE5C50, 0xF9EE5950)

Given that I get this durning the start of the installation, I'm guessing it's a hardware issue. Is Samsung a good brand of RAM?

[edit]: these sticks are not on Asus's list as compatable: http://usa.asus.com/prog/spec.asp?m=...eluxe&langs=09

The number on the chips on the RAM in this machine are K4H560838E-TCCC

[Force Flow]

Looks like the problem was that the motherboard didn't like the RAM in dual channel mode.