Mad Dad - Several Errors in XP

**NooNoo** · May 5th, 2004, 04:22 AM

Where to start?

I also have had this problem since assembling my first machine a few weeks ago....

XP Pro Service pack 1
Intel 2.5 Ghz
Soyo 845pe Lite motherboard
1 512 stick of RAM and 1 256
Western Digital Caviar 80GB HDD
425 Watt power supply
Nvidia GeForce FX 5600 (AGP)
Sony DVD RW
wacom tablet (my only usb device)
and also a cable modem running through a belkin router

...and when it runs, it runs great. Problem is (seemingly) random reboots. I've been researching my problem using the error codes and dumpchk data and the only thing I've found is small comfort that I'm not alone with this problem. Many threads citing the same errors, curiously most of them seem to be about 1-2 years old. This is the most recent thread I've found, so I registered and am posting.

Let me take a moment to say that I don't have as many "ComputerSmart Points" as others that I see posting, but I'm capable enough, and am always eager to learn whatever I need to to solve a problem.

In all the threads I've read, no one has come to a definitive solution.

This is the best thread I've read so far
http://forums.viaarena.com/messagev...arc&STARTPAGE=1

A lot of people talk about RAM, but when it's changed the problems persist. I've run it with either and both of my sticks and still gotten the BSODS. Haven't run a memtest yet, though. Other people talk about IRQ assignments, and I think that's a possibility. ONly this morning have I started looking into reassigning my IRQs (my USB and VidCard share IRQ 16. IRQ 11 is empty, see this thread: http://www.annoyances.org/exec/forum/winxp/1005541276)

I've checked my voltages, flashed the bios, upgraded to SP1 (the first time it rebooted during the install, -curses!- and I had to reinstall from scratch). I've messed around in BIOS some, but not every corner.

At post I get a message flash by that tells me "no 80 pin conductor cable installed"...which is strange because I'm able to read/write to the HDD no problem (until BSOD, which happens if the machine is idle or busy). Replaced the cable, replugged it, everything, so I'm just going to ignore that problem, because if the cable isn't installed then how could it be working with the HDD, right? I know the diff. between a 40 pin and 80 pin, so I'm sure I've got the right cable installed.

Here's one thing that evryone seems to have in common, a GeForce card. Not everyone, but almost everyone. Mobo, chipset, processor, everything else seems to change (even W2K running instead of XP, but most commonly XP). Through an AGP slo, not PCI.

So, there's some more avenues I want to explore. Questions:
What can you tell me about this, from my Sys. Info screen-

I/O Port 0x00000000-0x00000CF7 PCI bus
I/O Port 0x00000000-0x00000CF7 Direct memory access controller

I/O Port 0x000003C0-0x000003DF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
I/O Port 0x000003C0-0x000003DF NVIDIA GeForce FX 5600SE

Memory Address 0xE8000000-0xE9FFFFFF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
Memory Address 0xE8000000-0xE9FFFFFF NVIDIA GeForce FX 5600SE

IRQ 16 NVIDIA GeForce FX 5600SE
IRQ 16 Intel(R) 82801DB/DBM USB Universal Host Controller - 24C2

Memory Address 0xD0000000-0xDFFFFFFF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
Memory Address 0xD0000000-0xDFFFFFFF NVIDIA GeForce FX 5600SE

Memory Address 0xA0000-0xBFFFF PCI bus
Memory Address 0xA0000-0xBFFFF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
Memory Address 0xA0000-0xBFFFF NVIDIA GeForce FX 5600SE

I/O Port 0x000003B0-0x000003BB Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561
I/O Port 0x000003B0-0x000003BB NVIDIA GeForce FX 5600SE

The error codes I'm getting are mainly the ones listed elsewhere in this thread, 1000007f, x050, x08e, IRQ not less or equal, and some pagefile faults....

Anybody have any ideas, is this thread still alive?

Thanks for anything.

**NooNoo** · May 5th, 2004, 04:25 AM

DSL tech replied:

Well, to over generalize....its either a faulty driver, faulty ram, or a faulty service
http://www.microsoft.com/resources/...md_stp_ccgm.asp

Hudson Smith replied:
Have you installed the Intel INF Update Utility?

Mad Dad replied:

Well, I ran memtest and guess what, my 512 stick came up with all kinds of errors. Why couldn't it have been the 256? Oh well, I'll send it back...

I hope that was the source of my BSODs.

DsLTech, I checked your link. It was the stop code I was getting the least, about paging, and I think it was a result of the bad RAM, a symptom, rather than a cause. Thanks.

hudsonsmith, yes I've installed the INF update, too.

Waiting for another BSOD, fearing it. But you know how it can be sometimes, once you actually verbalize the problem, the solution makes itself apparent. I wonder how many people figure out thier problems because they've posted them in a forum and actually written them out, made them literal and tangible, rather than a jumble of suspiscions and guesses shuffling around in thier head.

**NooNoo** · May 5th, 2004, 04:26 AM

Confus-Ed replied

Originally Posted by Mad Dad

.. But you know how it can be sometimes, once you actually verbalize the problem, the solution makes itself apparent. I wonder how many people figure out thier problems because they've posted them in a forum and actually written them out, made them literal and tangible, rather than a jumble of suspiscions and guesses shuffling around in thier head.

That's the one ! So glad your issue is sorted or at least explained now onto the next one ...

So problem solved I think. I have pm'd this link to Mad Dad for confirmation.

**NooNoo** · May 5th, 2004, 04:41 AM

wmicro offered this general advice:

To user: Qerr, Mad Dad and whoisKeel
Here is what you need to fix your problem, which we all hope, sees these articles.

When you install Microsoft Windows XP, you may receive a STOP error message similar to one of the following during Setup:
STOP 0x0000008e or STOP 0x00000050 PAGE_FAULT_IN_NON_PAGED_AREA sees this
http://support.microsoft.com/default.aspx?kbid=315335

834450 - "Stop 0x0000008E" error message in Win32k.sys when you use the keyboard to access a program menu in Windows XP Fixes an issue in Windows XP where, if you use the keyboard to access a program menu, you may receive a Stop error message. Requires that you install Windows XP Service Pack 1 and a hotfix to resolve the problem.
http://search.microsoft.com/search/....sys+windows+xp
==
Qerr 04-06-2004, 08:40 AM
0x0000008E win32k.sys Page_fault_in_nonpaged_area 0x00000050 navex15.sys

======
whoisKeel Yesterday, 05:46 PM 5-4-04
0x50 PAGE_FAULT_IN_NONPAGED_AREA problem caused by win32k.sys
===================
Mad Dad 04-26-2004, 06:04 AM
Memory Address 0xE8000000-0xE9FFFFFF Intel(R) 82845G/GL/GE/PE/GV Processor to AGP Controller - 2561 Memory Address 0xE8000000-0xE9FFFFFF NVIDIA GeForce FX 5600SE

**peterpam** · May 5th, 2004, 10:30 AM

Have you ried to disconect your CD ou DVD drives? Lots ofRam problems are generated by 'floating' IRQ problems.. Just disconect you DVD and CD drives and run the test again: is it still pointing to errors? Mayby not. Hope I was usefull.

Greetings from thr country of Sun

**jamal_x712** · August 2nd, 2004, 09:52 PM

For those suffering with this malady which has a very long and continous history throughout multiple versions of Windows NT, inclucing 2k xp and 2k3 server. However you must contact MS to get the fix, and their description is not neccessarily the easiest to replicate unless you have intamate knowledge of how every piece of software on your box works.

Here is the link to the KB article:

http://support.microsoft.com/default...b;en-us;834450

Wish you the best.

**NooNoo** · August 3rd, 2004, 04:24 AM

Welcome to Windrivers jamal and thanks for the info

**Spork** · August 3rd, 2004, 01:05 PM

Another thing to test would be the processor. I've seen faulty processors cause all sorts of weird problems. From distorted graphics, random lockups, reboots, shutdowns, BSODs, and even sometimes the systems would only get to the post screen once every 10 tries.

Hell, I had a problem with an Athlon XP where the only time I could get the system to run stable was if I ran the processor at a slower speed than what it was supposed to run at (was rated for 1.8GHz, but would only run stable at 1.6GHz). But once I replaced the processor, my computer ran perfectly.

Just another idea to ponder over...