Seems like when I go to print something my computor just keeps rebooting, I downloaded the debuging tool you all linked to...ran the program and this is what I got.
Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini091205-03.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32 \drivers
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Mon Sep 12 19:58:23.531 2005 (GMT-7)
System Uptime: 0 days 0:05:59.246
Loading Kernel Symbols
.................................................. .................................................. .................................................. .....
Loading unloaded module list
.........
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 804e02a6, f8b5cbdc, 0}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

1: kd> !analyze -v;r;kv;lmtn;.logclose;q
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: 804e02a6, The address that the exception occurred at
Arg3: f8b5cbdc, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!KiTrap0D+150
804e02a6 8fe3 pop ebx


Hope this isnt to big a file to show you. I thought it may have something to do with memory. 2 year old ram.....

thanks folks

First off that is just the start of a log. You need to scroll the entire log which is quite long. You can add as an attachment.

That being said what you are showing is pointing to RAM although being 2 years old should have nothing to do with a problem.

Try this Mem Test:

http://www.memtest86.com/

Does this problem only occur whilst using the printer?

Any other issues? With the computer or the printer?

I will run that mem test when I can find an old floppy...lol I dont see those much anymore.

I notice the restarts when I go to print on our network...but It just happened again without even trying to print.

I will try to attatch the long file.....if I can figure out how to attatch...Thanks

That log is completely different. Pointing to your hard drive & or the file system.

You will need another floppy

If you know the manufacturer of your hard drive you can find a diagnostic here:

http://www.tacktech.com/display.cfm?ttid=287

If you do not know you can find out with this scan:

http://www.belarc.com/free_download.html

Under Drives.