OT: Perplexed by System Crash

I've been able to do this at will. I've done this 4 times in a row, even works with different documents. Here's how: I go into MS Word XP to print a document. I use document preview on my Epson 870 settings. I zoom in to see the preview by clicking on the magnifying glass (I zoom in full). I scroll with my mouse wheel to view the document. BAM, system re-boots. Is this a RAM problem or hard drive problem, where accessing this document in memory causes the crash? Here's the error message from XP event logs: Event Type: Information Event Source: Save Dump Date: 11/25/2001 Time: 12:57:38 AM Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xbf8670e1, 0xf2398a90, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini112501-01.dmp. What do these numbers above mean? My System (no o/c, nothing funky): AMD 1600+ 512 MB 2100 Corsair Ram GF3 Ti 500 IBM 60 GB HD ECS K7S5A MOBO Enlight case with 340W PS Win XP Office XP TIA. -- Joe Marques

Like David already said, it shound like a software issue. FYI, XP has this *lovely* feature where it will just reboot when it comes across fatal errors and such. -- - Will DeRivera - http://www.numic.net - http://www.luxt.com Joe Marques <[email hidden]> wrote in message news:4J1M7.181599$[email hidden]... > I've been able to do this at will. I've done this 4 times in a row, even > works > with different documents. > > Here's how: I go into MS Word XP to print a document. I use document > preview on my Epson 870 settings. I zoom in to see the preview by clicking > on the magnifying glass (I zoom in full). I scroll with my mouse wheel to > view the document. BAM, system re-boots. > > Is this a RAM problem or hard drive problem, where accessing this document > in memory causes the crash? > > Here's the error message from XP event logs: > > Event Type: Information > Event Source: Save Dump > Date: 11/25/2001 > Time: 12:57:38 AM > > Description: > The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e > (0xc0000005, 0xbf8670e1, 0xf2398a90, 0x00000000). A dump was saved in: > C:\WINDOWS\Minidump\Mini112501-01.dmp. > > What do these numbers above mean? > > My System (no o/c, nothing funky): > > AMD 1600+ > 512 MB 2100 Corsair Ram > GF3 Ti 500 > IBM 60 GB HD > ECS K7S5A MOBO > Enlight case with 340W PS > Win XP > Office XP > > TIA. > > -- > Joe Marques > > > > >

Sounds like a software problem. Download everything from both Office and Windows Update, see if that helps at all. David I "Joe Marques" <[email hidden]> wrote in message news:4J1M7.181599$[email hidden]... > I've been able to do this at will. I've done this 4 times in a row, even > works > with different documents. > > Here's how: I go into MS Word XP to print a document. I use document > preview on my Epson 870 settings. I zoom in to see the preview byclicking

Quoted text (39 lines)

> on the magnifying glass (I zoom in full). I scroll with my mouse wheel to > view the document. BAM, system re-boots. > > Is this a RAM problem or hard drive problem, where accessing this document > in memory causes the crash? > > Here's the error message from XP event logs: > > Event Type: Information > Event Source: Save Dump > Date: 11/25/2001 > Time: 12:57:38 AM > > Description: > The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e > (0xc0000005, 0xbf8670e1, 0xf2398a90, 0x00000000). A dump was saved in: > C:\WINDOWS\Minidump\Mini112501-01.dmp. > > What do these numbers above mean? > > My System (no o/c, nothing funky): > > AMD 1600+ > 512 MB 2100 Corsair Ram > GF3 Ti 500 > IBM 60 GB HD > ECS K7S5A MOBO > Enlight case with 340W PS > Win XP > Office XP > > TIA. > > -- > Joe Marques > > > >

Thanks for the help. It appears to be my GF3 driver. I rolled back to the 21.83's from the 22.80's and I can no longer create the crash. Looking good so far. -- Joe Marques "David Indech" <[email hidden]> wrote in message news:9trifm$5sk$[email hidden]... > Sounds like a software problem. Download everything from both Office and > Windows Update, see if that helps at all. > > David I > > > "Joe Marques" <[email hidden]> wrote in message > news:4J1M7.181599$[email hidden]... > > I've been able to do this at will. I've done this 4 times in a row, even > > works > > with different documents. > > > > Here's how: I go into MS Word XP to print a document. I use document > > preview on my Epson 870 settings. I zoom in to see the preview by > clicking > > on the magnifying glass (I zoom in full). I scroll with my mouse wheel to > > view the document. BAM, system re-boots. > > > > Is this a RAM problem or hard drive problem, where accessing this document > > in memory causes the crash? > > > > Here's the error message from XP event logs: > > > > Event Type: Information > > Event Source: Save Dump > > Date: 11/25/2001 > > Time: 12:57:38 AM > > > > Description: > > The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e > > (0xc0000005, 0xbf8670e1, 0xf2398a90, 0x00000000). A dump was saved in: > > C:\WINDOWS\Minidump\Mini112501-01.dmp. > > > > What do these numbers above mean? > > > > My System (no o/c, nothing funky): > > > > AMD 1600+ > > 512 MB 2100 Corsair Ram > > GF3 Ti 500 > > IBM 60 GB HD > > ECS K7S5A MOBO > > Enlight case with 340W PS > > Win XP > > Office XP > > > > TIA. > > > > -- > > Joe Marques > > > > > > > > > >

Typical NVIDIA Windows crap, Oh yea I great frame rates in games, but they never say anything about the Windows GUI problems.

I don't have XP yet, but I have read in some of the MS newsgroups that " feature" of the system rebooting when it comes across an error, can be disabled. Don Burnette "Will DeRivera" <[email hidden]> wrote in message news:ZVcM7.5109$[email hidden]... > Like David already said, it shound like a software issue. FYI, XP has this > *lovely* feature where it will just reboot when it comes across fatalerrors

Quoted text (9 lines)

> and such. > -- > - Will DeRivera > - http://www.numic.net > - http://www.luxt.com > > Joe Marques <[email hidden]> wrote in message > news:4J1M7.181599$[email hidden]... > > I've been able to do this at will. I've done this 4 times in a row,

even

Quoted text (7 lines)

> > works > > with different documents. > > > > Here's how: I go into MS Word XP to print a document. I use document > > preview on my Epson 870 settings. I zoom in to see the preview by > clicking > > on the magnifying glass (I zoom in full). I scroll with my mouse wheel

to > > view the document. BAM, system re-boots. > > > > Is this a RAM problem or hard drive problem, where accessing thisdocument

Quoted text (38 lines)

> > in memory causes the crash? > > > > Here's the error message from XP event logs: > > > > Event Type: Information > > Event Source: Save Dump > > Date: 11/25/2001 > > Time: 12:57:38 AM > > > > Description: > > The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e > > (0xc0000005, 0xbf8670e1, 0xf2398a90, 0x00000000). A dump was saved in: > > C:\WINDOWS\Minidump\Mini112501-01.dmp. > > > > What do these numbers above mean? > > > > My System (no o/c, nothing funky): > > > > AMD 1600+ > > 512 MB 2100 Corsair Ram > > GF3 Ti 500 > > IBM 60 GB HD > > ECS K7S5A MOBO > > Enlight case with 340W PS > > Win XP > > Office XP > > > > TIA. > > > > -- > > Joe Marques > > > > > > > > > > > >

In windows 2000, that feature can be disabled by unchecking "Automatically reboot" in the startup and recovery section on the advanced tab for the system properties in control panel. Did that make sense?? It's getting to be a long day for me.... Ryan

It's in the same place in XP. Thanks for that info. What happens if I disable this? Error message box? BSOD? System freeze? Varies depending on the type of error? TIA, -- Joe Marques "Ryan" <[email hidden]> wrote in message news:cHkM7.1178$[email hidden]... > In windows 2000, that feature can be disabled by unchecking "Automatically > reboot" in the startup and recovery section on the advanced tab for the > system properties in control panel. Did that make sense?? It's getting to > be a long day for me.... > > Ryan > >

It won't reboot if there's an error, it will just record it in event viewer and move on [as long as it's not critical] :-) (I'm using win2k, don't know if that exists in XP as well) Ryan