[Techtalk] OT but I'm desperate.... Windows....!

[Poppy]

A casual Google on the BSOD errors shows a handful of causes.

Simply put, it looks like your print driver handed the kernel a bad
command, is what it looks like. And I know, everyone in here with more
experience in coding drivers than I have (none) is going to say "well,
duh"

I'll do some more looking around today, try and respond if I find
anything interesting.

--Poppy
"Once a technician, always a technician."


On Thu, 2002-10-17 at 22:59, Michelle Howson wrote:
> *mutter mutter* "feature" *mutter mutter*
> 
> Ok.  I've not been home a lot in the last 24 hours, hence the sudden 
> silence from the source of all problems.  And I'm about to go again (argh) 
> so can't reply to the numerous messages in my inbox *grin*  but!  here are 
> some error messages for you all to get your teeth into.
> 
> The story: I had a single page to print off from Excel and decided that I'd 
> give the machine one last try, as it normally only crashes on the second 
> page.  And as I'm about to leave anyway, and nothing urgent is going on on 
> the machine, I decided if it crashes it won't be a catastrophy (or at 
> least, won't be risking a catastrophy).  It crashed - with an inch left to 
> print.  Now I have some error messages to share.
> 
> -blue screen-
> ***Stop: 0*000001E (0*c0000005, 0*8049CC50, 0*00000001, 0*629B53E8)
> KMODE_EXCEPTION_NOT_HANDLED
> 
> ***Address 849CC50 base at 80400000, DateStamp 3d366b8b - ntoskrnl.exe
> 
> Beginning dump of physical memory.
> Physical memory dump complete.  Contact your system administrator or 
> technical support group.
> -/blue screen-
> 
> On start up, got the following window pop up called Printers Folder...
> There was an error found when printing the document "contactlist" to LPT1:. 
>  The device is not connected.
> 
> ..given the option to retry or cancel.
> 
> Lastly, here is what I've dug out from the log:
> Event Type:	Information
> Event Source:	Save Dump
> Event Category:	None
> Event ID:	1001
> Date:		18/10/2002
> Time:		3:54:53 PM
> User:		N/A
> Computer:	HONSHU
> Description:
> The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001e 
> (0xc0000005, 0x8049cc50, 0x00000001, 0x629b53e8). Microsoft Windows 2000 
> [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini101802-01.dmp. 
> 
> I've sort of decided that when the exams are over in a month or so, I'm 
> going to go cold turkey.  Save what I have to save, reformat again and 
> force myself to learn linux properly because I won't have windows at all.  
> I will eventually add windows as well, cause at the moment I'm not ready to 
> go completely without it (and I think some of my uni work has to be done 
> under windows) but -- no classes until march next year, so plenty of time 
> to sort myself out *laughs*
> 
> Can.  Not.  Wait.  *sigh*
> 
> Thanks for all the help, dudes...  if any of the above gives any more clues 
> as to what's going on, share away :)  And I will reply to the other 
> messages re. power etc, soon.
> 
> > > "This can be caused by an optional feature of Windows 2000/XP that will
> > > restart the computer if any internal stop errors happen. To disable this
> > > feature, please follow the process below:
> >
> >I still love how they refer to it as a *feature*. It gets me every time.
> >:)
> >
> >Erinn
-- 
Poppy,				  sylph at cyber-dyne.com
Friend of the Penguin
*-------------------------------------------------------------------------*
'If you're so evil, why don't you... EAT THIS KITTEN!' 'mew!' 'No way,
Mister... that's just WRONG!' - The Tick