1.1K Posts

July 1st, 2004 18:00

This error is normally related to software and drivers of the system. Not the hardware specifically. You would probably get better help in the software board for your version of windows. In the mean time if you suspect that the hardware of the system could be a problem you should test the system with the Dell customer diagnostics that came with the system. Boot the system to the drivers and utilities CD that came with your system to run the tests. You will need to have media in each of the drives for the tests to run properly.

2 Intern

 • 

3K Posts

July 1st, 2004 23:00



@LittleAdvice wrote:
This error is normally related to software and drivers of the system. Not the hardware specifically.

Actually, this error is quite specifically related to certain hardware problems, but it would help if you could include the complete error message(s) you're getting, including any reference to STOP details (0x0000...).  There are a number of troubleshooting steps you can review here:

http://support.microsoft.com/?kbid=315266

Regarding your statement about your NAV application, the fact that you have it installed doesn't necessarily mean that it's catching everything that might be going on.  You should run a complete system scan for virus activity regularly, in addition to having the program installed.  If you have any reason to doubt the effectiveness of your AV application, there are a number of free online scanners available for you to get a "second opinion" from.

You need to review your system documentation for instructions on running the Dell Diagnostics application, which will check for hardware failures. Detailed instructions are in your User Guide under "Solving Problems."  The Dell Knowledge Base has additional instructions/tips, and you can access that via the Solutions tab above.

You may find some additional troubleshooting material here:

http://www.google.com/search?hl=en&ie=UTF-8&q=+Kernel_Stack_Inpage_Error&btnG=Google+Search

9 Posts

July 2nd, 2004 04:00

I have run the Dell Diags. 10 iterations of the quick tests and 1 iteration of all tests. All tests passed. Not sure about the Software or drivers since the system was running for  a  year without blue screens.

Dell support came back with Windows XP is not designed to run 24 x 7 and suggested I reboot every so often to clear the memory...

9 Posts

July 2nd, 2004 04:00

I have followed each one of Microsofts suggestions. I run Norton AV 2004 - full system scan every night. Which FREE online virus scan do you like...I have run the dell diags all tests passed. Guess I will have to wait until it crashes again to get the full error stop message string.

2 Intern

 • 

3K Posts

July 2nd, 2004 10:00



@skrome wrote:

Dell support came back with Windows XP is not designed to run 24 x 7 and suggested I reboot every so often to clear the memory...


This is one of the more ridiculous things I've heard out of the "award winning support" department in some time.  Whomever told you that is simply incorrect.  Windows XP is the first operating system MS has come up with that can run for days or weeks without any problem, and any tech support person who isn't aware of this is either lazy or in the wrong line of work.  Absolute drivel.

If the system has passed the Diags test, I would power it down and remove/reseat the memory modules and PCI cards.  Upon restart, I'd reset the default system configuration via System Setup, then let it run and see if there has been any change.  If that doesn't work, run the hardware diagnostics again, and depending on the outcome of those tests, you can either try reinstalling Windows to a formatted drive (according to the instructions in the Reinstall Guide available via the Solutions tab above), or call Dell and hope that you get someone more knowledgeable than the last person with whom you spoke.  I think I'd probably try the reinstallation of Windows, simply because that frequently seems to work when things have gotten to the point where one is having to use System Restore, but that's just an opinion.  I still think you have some sort of hardware problem, though.

Message Edited by Flooby on 07-02-2004 07:38 AM

9 Posts

July 2nd, 2004 18:00

I totally agree Dell support is pretty worthless. It is a mere shadow of itself. Back in the boom years, 96, 97,. 98 their support was award winning. Today it is absolutely amazing how much energy effort and time it takes to get NO results from Dell.

Back to my issue: I read that perhaps I might have a heat/overheating problem. I am thinking about adding a CPU cooling fan? or a second fan somewhere in the chasis.

Any thoughts on this? Any fans you like?

For the moment, my system is up and running okay. Really the only changes I made was to disable Hyperthreading. Lets see how long this lasts till the next random BSOD.

THanks for your time.

Message Edited by skrome on 07-02-2004 02:12 PM

Message Edited by skrome on 07-02-2004 02:12 PM

2 Intern

 • 

3K Posts

July 2nd, 2004 22:00

If the system passes the Dell Diagnostics tests (particularly in Extended loop mode, as opposed to one quick test), I doubt that cooling is an issue, but you could certainly pull the cover off the next time the error occurs, restart and see if the increased air circulation helps any.  If it does, that might be an indication that another fan might be needed, but I tend to doubt that this is the problem at this stage.

96 Posts

July 3rd, 2004 14:00



@Flooby wrote:


@skrome wrote:

Dell support came back with Windows XP is not designed to run 24 x 7 and suggested I reboot every so often to clear the memory...


This is one of the more ridiculous things I've heard out of the "award winning support" department in some time.  Whomever told you that is simply incorrect.  Windows XP is the first operating system MS has come up with that can run for days or weeks without any problem, and any tech support person who isn't aware of this is either lazy or in the wrong line of work.  Absolute drivel.



Funny, my Dimension 8100 with Windows 2000 Pro SP4 has an uptime of 62 days without a reboot, and it came out before Windows XP....

2 Intern

 • 

3K Posts

July 3rd, 2004 20:00

Oops...I'll be sure to add "Of the operating systems with which I work on a regular basis" to the front of that testimonial for WinXP in the future.  I guess I'd better include "WinXP has better driver support than Win2k, too," though.   

96 Posts

July 3rd, 2004 20:00



@Flooby wrote:
Oops...I'll be sure to add "Of the operating systems with which I work on a regular basis" to the front of that testimonial for WinXP in the future.  I guess I'd better include "WinXP has better driver support than Win2k, too," though.   

Huh?

I've got a ton of new hardware in my system, never had a problem with drivers - including legacy.  *shrug* I know some people have had some real issues, so I'm not saying it ain't possible, but I've just never seen it (so far).

I've got my in-laws system that I've got to build later this summer, and digging up the chipset drivers for that ought to be interesting...

9 Posts

July 4th, 2004 15:00

First the system profile: Dell 8250;3.05GHz, 1.5 GB RAM, XP Pro SP1, 200 GB HDD, ATI Raedeon 9700 Pro,

To date I have disabled HyperThreading. Ran Dell Diags quick (10 iterations) and compete Diags - all passed, Reset BIOS to factory defaults, ADDED a PCI slot cooler fan and removed the front face plate below the floppy drive and removed the flip up door to open up air flow with the new cooling fan.

Thus far we are stabilized.

If and when it crashes again, I will note the complete error message and note the error message in the system log.

Message Edited by skrome on 07-04-2004 11:13 AM

Message Edited by skrome on 07-04-2004 11:14 AM

9 Posts

July 5th, 2004 00:00

okay happy independence day...home from golf only to see the infamous BSOD. THis time I copied the error down for reference. BTW, there were no errors nor even information entires in the Systems or Application events log. Here is the error string

KERNEL_DATA_INPAGE_ERROR

Stop: 0X0000007A (0XC03DD2F4, 0XC000000E, 0XF74BD558, 0X4A05F860)

and then under all this was a new message I had never seen before

atapi.sys address FF4BD558 base at F74B1000, date stamp 3D6DDB04

I am open to suggestion

 

Thank you for taking the time to respond!!

 

 

Message Edited by skrome on 07-04-2004 08:52 PM

2 Intern

 • 

3K Posts

July 5th, 2004 02:00

http://www.updatexp.com/stop-messages.html  See if you get any more ideas from the suggestions under Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR here.

You might also find some ideas here: http://www.annoyances.org/exec/forum/winxp/t1074443182

9 Posts

July 8th, 2004 18:00

July 11 today,  2 months after the initial BSOD, Dell (Banctech) replaced the motherboard (so much for Next day onsite Service.)

Hopefully this will do it. Many of the references did indeed point hardware specifically to IDE controller issues and/or memory. If this doesnt stop the random BSOD's then the Dell onsite support tech suggested perhaps memory or CPU needs to be replaced.

I will keep you posted.

Thanks for all of your help

2 Intern

 • 

3K Posts

July 9th, 2004 02:00



@skrome wrote:

 If this doesnt stop the random BSOD's then the Dell onsite support tech suggested perhaps memory or CPU needs to be replaced.


Boy, that doesn't seem to be a very cost effective way of fixing a PC.  "We'll just keep adding new parts until something actually works." I'd be out of business tomorrow if I had to work that way.  Hold out long enough, and they'll replace the mouse pad, too. 

Here's hoping that the first fix is the charm...unless you need another mouse pad, that is. 

No Events found!

Top