blue screen

[waitman]

I got a question for ya. I got a pc that seems to only blue screen when the printer is hooked up to it. tested the memory, hard drive and it runs fine except when the printer is hooked up The error message is Kernal data inpage error stop: 0x0000007A (0cx03E1220, 0XC000000E, 0XF8488384, 0x0EEE6860 atapi.sys - address F8488384 base at F847B000, date stamp 41107b4d beginning dump of physical memory. Any idea what to do, updated printer driver maybe? I would appreciate any help you can give,

waitman

 

[waitman]

any ideas anyone?

 

[Dahak]

if it is only happening when the printer is hooked up, try removing all the drives for the printer and reboot and then download and re-install the latest drivers for the printer

aslo this Article at ms point more torwards bad hard drive, usually ive seen this before too and was able to correct it with chkdsk /f /r from start -> run -> cmd

 

[montag451]

What printer is it?

Its strange, but 'Atapi' indicates more towards optical drives.

Do what Dahak suggests for the drivers and post back.

 

[waitman]

Thanks for the replies will do and let you know. I tried the chkdsk /f /r from start -> run -> cmd, didn't seem to do the trick.

 

[dclive]

You might also send me the dump files from c:\windows\dumps, and also download and run mpsreports and send me the resulting cabfiles, too. I'll see if I see anything in the dumpfiles.

 

[waitman]

Thanks dclive, i sent you the files you requested. Still no bluscreen as long as the printer isn't hooked up

 

[RadiclDreamer]

Originally posted by: waitman
Thanks dclive, i sent you the files you requested. Still no bluscreen as long as the printer isn't hooked up

Dumb question but have you updated the drivers for your printer?

 

[waitman]

yes, I do

 

[dclive]

Originally posted by: waitman
Thanks dclive, i sent you the files you requested. Still no bluscreen as long as the printer isn't hooked up

You have lots of crashes. Most are old, so I only looked at the most recent dump/crash.

Update your Intel video drivers with the most recent version. You currently have:

Module[311] [C:\WINDOWS\SYSTEM32\IALMDD5.DLL]
Company Name: Intel Corporation
File Description: DirectDraw(R) Driver for Intel(R) Graphics Technology
Product Version: (6.14:10.4342)
File Version: (6.14:10.4342)
File Size (bytes): 879228
File Date: Wed Oct 19 08:59:12 2005
Module TimeDateStamp = 0x42b8acc3 - Tue Jun 21 19:11:47 2005

Do this, confirm they're installed, reboot, confirm the dates match what you just installed on the driver in Device Manager, and then plug in your printer again.

I looked on Intel's site - the latest driver for the 845G is one version _behind_ what you have up there. How did you get it? Anyway, just try grabbing Intel's driver (http://downloadcenter.intel.co...865&OSFullName=Windows*+XP+Professional&lang=eng&strOSs=44&submit=Go%21) and seeing if that changes anything.

That's what caused the crash on 7/18, the most recent crash.

 

[dclive]

Also, you have serious disk issues:

8/8/2007 12:37:40 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort0, did not respond within the timeout period.
8/8/2007 1:12:47 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort0, did not respond within the timeout period.
8/8/2007 1:17:12 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort0, did not respond within the timeout period.

...and that's just the tip of the iceberg, from a 45 minute period in one day.

Here's more:
7/14/2007 3:31:59 PM 1 0 7 Cdrom N/A DELL2400 The device, \Device\CdRom0, has a bad block.
7/14/2007 3:32:08 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort1, did not respond within the timeout period.
7/14/2007 3:32:19 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort1, did not respond within the timeout period.
7/14/2007 3:32:20 PM 1 0 7 Cdrom N/A DELL2400 The device, \Device\CdRom0, has a bad block.
7/14/2007 3:32:30 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort1, did not respond within the timeout period.
7/14/2007 4:07:18 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort1, did not respond within the timeout period.
7/14/2007 4:07:49 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort1, did not respond within the timeout period.
7/14/2007 6:09:11 PM 1 0 9 atapi N/A DELL2400 The device, \Device\Ide\IdePort1, did not respond within the timeout period.

Smart thing to do is probably to remove all disk-based filter drivers, and see if the issue goes away; if not, start thinking about hardware:
Filter Found
Key = HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
Description = DVD/CD-ROM drives
LowerFilters = PxHelp20 drvmcdb sscdbhk5 MxlW2k

(Google everything to the right of "lowerfilters = pxhelp20" and think about uninstalling all of that software.

 

[waitman]

thanks dclive, let me sort through all of this and I will respond back your help is greatly appreciated. Think it would be better to reinstall windows fresh?

 

[dclive]

No, just fix the problem.... there's no reason to reinstall at all.

 

[waitman]

updated the printer drivers and the graphics. It has not blue screened on me yet. I wonder when my friend gets it back if it will. Seems to do it just at his house! Could a power problem at his house cause this?

 

[dclive]

No. The Intel graphics driver caused the most recent crash.

 

[waitman]

Thanks for your help dclive and everyone else, it has been almost 24 hours and no blue screens.

 

[dclive]

So when you connect, disconnect, and reconnect, then disconnect and reconnect the printer, it's always OK, with no crashes?

Have you done that many back-to-back tests?

 

[waitman]

Originally posted by: dclive
So when you connect, disconnect, and reconnect, then disconnect and reconnect the printer, it's always OK, with no crashes?

Have you done that many back-to-back tests?

I have tried it 4 times so far so good

 

[dclive]

Excellent! The memory dump file is the best way to figure out why a machine is crashing - it removes the guessing from the equation (usually - and for someone who's really good at reading them. I'm OK, so I'll admit to some guesswork from time to time if the debugger doesn't have a straight answer.)

 

[dclive]

Did you fix your disk issues as well?

 

[waitman]

it appears to be fixed, I'm not getting the disk errors. Thanks, time will tell. I still don't know how the graphics driver was the version that is was. Thanks so much, this was driving me crazy. I need to learn how to use those tools. Again thanks.

 

[dclive]

Originally posted by: waitman
it appears to be fixed, I'm not getting the disk errors. Thanks, time will tell. I still don't know how the graphics driver was the version that is was. Thanks so much, this was driving me crazy. I need to learn how to use those tools. Again thanks.

How are you ensuring you aren't getting any disk errors?

 

[waitman]

It doesn't show in the event viewer or the the dump files that I looked through. It was showing up in the event viewer. Still no problems as of right now.