Spontaneous Reboot Problem

I have a 2 year old Gateway 700XL (2.2 GHz Pent 4., 1024 Mb RAM, 120 GB HD,
XP Home, ATI Radeon VideoCard with FPD1810 LCD Monitor), which has run
virtually flawlessly. The only glitch has been a rare monitor black-out
lasting a few seconds (without any reboot or other issues), occurring once
every couple of months. I researched this problem, and saw that many others
experienced this with this hardware, with no definitive answer that I could
ever identify.

I keep it well maintained in terms of critical updates, have run AdAware,
NAV 2003, ZoneAlarm, etc.

Out of nowhere it has started spontaneously rebooting. I'll just be doing
the usual - either checking email, browsing the web, and the screen goes
black, and without further intervention, it just completely reboots. I'm
not a gamer, so the system (or video subsystem) is not getting any real
work-out when this occurs.

My daughter reported this happening when she was using it perhaps a month or
two ago. Then it happened once yesterday. Today it happened again, and
kept doing it, running only 5 or 10 minutes before rebooting. Now I have it
turned off, and will let it cool down overnight and see what happens in the
morning.

I took the side cover off and verified that the fan was spinning (it seemed
fairly fast but I don't know how fast it should be). The side of the metal
around the CPU was fairly warm to touch, but it didn't seem excessively hot.
After turning it off completely, I gently vacuumed the fan and surrounding
area, case vents, and left the side off for better ventilation. It still
rebooted.

I downloaded MemTest, and tried running it. It got to around 70%, showed 0
errors, but then rebooted so it couldn't complete.

I'm inclined to think this is a hardware issue, but short of bringing or
sending it in for service, what kind of diagnostics or other methods can I
use to try and define the source of this problem?

Has anyone experienced this with this or similar systems?

I had done some 'googling' yesterday and what I found suggested fan, memory
or other hardware failure, but one person concluded a software problem (I
forget which) was the source.

Any help greatly appreciated. I really depend on this computer for many,
many tasks, on a daily basis!

Thanks!

--
Don
Photo Website at:
www.dlcphotography.net
remove "lens cap" for email reply

Don,

Two possibilities come to mind immediately, one based on experiences with a
client's newly installed home computer years ago:

1. The power supply is failing after two years.
2. Maybe you've connected a home appliance like a refrigerator, washer or dryer
to the same circuit as the computer?

Either way, voltage drops can cause reboots... Ben Myers

On Sat, 24 Jan 2004 22:30:20 -0500, "Don Cohen"
wrote:

I have a 2 year old Gateway 700XL (2.2 GHz Pent 4., 1024 Mb RAM, 120 GB HD,
XP Home, ATI Radeon VideoCard with FPD1810 LCD Monitor), which has run
virtually flawlessly. The only glitch has been a rare monitor black-out
lasting a few seconds (without any reboot or other issues), occurring once
every couple of months. I researched this problem, and saw that many others
experienced this with this hardware, with no definitive answer that I could
ever identify.

I keep it well maintained in terms of critical updates, have run AdAware,
NAV 2003, ZoneAlarm, etc.

Out of nowhere it has started spontaneously rebooting. I'll just be doing
the usual - either checking email, browsing the web, and the screen goes
black, and without further intervention, it just completely reboots. I'm
not a gamer, so the system (or video subsystem) is not getting any real
work-out when this occurs.

My daughter reported this happening when she was using it perhaps a month or
two ago. Then it happened once yesterday. Today it happened again, and
kept doing it, running only 5 or 10 minutes before rebooting. Now I have it
turned off, and will let it cool down overnight and see what happens in the
morning.

I took the side cover off and verified that the fan was spinning (it seemed
fairly fast but I don't know how fast it should be). The side of the metal
around the CPU was fairly warm to touch, but it didn't seem excessively hot.
After turning it off completely, I gently vacuumed the fan and surrounding
area, case vents, and left the side off for better ventilation. It still
rebooted.

I downloaded MemTest, and tried running it. It got to around 70%, showed 0
errors, but then rebooted so it couldn't complete.

I'm inclined to think this is a hardware issue, but short of bringing or
sending it in for service, what kind of diagnostics or other methods can I
use to try and define the source of this problem?

Has anyone experienced this with this or similar systems?

I had done some 'googling' yesterday and what I found suggested fan, memory
or other hardware failure, but one person concluded a software problem (I
forget which) was the source.

Any help greatly appreciated. I really depend on this computer for many,
many tasks, on a daily basis!

Thanks!

--
Don
Photo Website at:
www.dlcphotography.net
remove "lens cap" for email reply

Go into the control panel - system applet - advanced - startup and recovery.
Uncheck the "automatically restart" box. The next time you should see an
error that lets you track the problem.

Also look in the Event Logs to see what's there.

Chances are it's a software issue, not hardware.



"Don Cohen" wrote in message
...
I have a 2 year old Gateway 700XL (2.2 GHz Pent 4., 1024 Mb RAM, 120 GB
HD,
XP Home, ATI Radeon VideoCard with FPD1810 LCD Monitor), which has run
virtually flawlessly. The only glitch has been a rare monitor black-out
lasting a few seconds (without any reboot or other issues), occurring once
every couple of months. I researched this problem, and saw that many
others
experienced this with this hardware, with no definitive answer that I
could
ever identify.

I keep it well maintained in terms of critical updates, have run AdAware,
NAV 2003, ZoneAlarm, etc.

Out of nowhere it has started spontaneously rebooting. I'll just be doing
the usual - either checking email, browsing the web, and the screen goes
black, and without further intervention, it just completely reboots. I'm
not a gamer, so the system (or video subsystem) is not getting any real
work-out when this occurs.

My daughter reported this happening when she was using it perhaps a month
or
two ago. Then it happened once yesterday. Today it happened again, and
kept doing it, running only 5 or 10 minutes before rebooting. Now I have
it
turned off, and will let it cool down overnight and see what happens in
the
morning.

I took the side cover off and verified that the fan was spinning (it
seemed
fairly fast but I don't know how fast it should be). The side of the
metal
around the CPU was fairly warm to touch, but it didn't seem excessively
hot.
After turning it off completely, I gently vacuumed the fan and surrounding
area, case vents, and left the side off for better ventilation. It still
rebooted.

I downloaded MemTest, and tried running it. It got to around 70%, showed
0
errors, but then rebooted so it couldn't complete.

I'm inclined to think this is a hardware issue, but short of bringing or
sending it in for service, what kind of diagnostics or other methods can I
use to try and define the source of this problem?

Has anyone experienced this with this or similar systems?

I had done some 'googling' yesterday and what I found suggested fan,
memory
or other hardware failure, but one person concluded a software problem (I
forget which) was the source.

Any help greatly appreciated. I really depend on this computer for many,
many tasks, on a daily basis!

Thanks!

--
Don
Photo Website at:
www.dlcphotography.net
remove "lens cap" for email reply

Thanks guys.

Further info:

I can't think of any new appliance or other electrical draw in my house. I
have a "APC Back-up Office" UPS for my computer, which is many years old
(perhaps 4-5 years). There is a lot of hardware (Monitor, Network Switch,
USB Printer, Speakers, Cable-Modem, etc.) plugged into it.

I did further reading using my laptop, and did disable the "automatically
restart" box.

I left my computer off overnight. After rebooting this morning, the problem
recurred within minutes, implying that it's not a heat issue. No chance to
look at error logs. But did receive the following blue screen message:

PAGE DEFAULT_IN_NONPAGED_AREA

Followed by some generic troubleshooting instructions that don't seem
particularly helpful, then:

Technical Information:

***STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, 0x00000000)

Beginning dump of physical memory
Physical memory dump complete

Contact your system adminitrator...yada, yada, yada.

I'll be researching this, but hopefully this will help identify the problem.

I have not recently added hardware.
I believe the last system change made was doing a NAV 2003 Live Update.
I can't remember precisely, but after a recent reboot not too long before
this started (but months after my daughter reported this occurring once), I
received a "Windows has recovered from a serious error" message, but
everything seemed to run fine after that.


So where do we go from here?

Thanks!

Don

"Edward J. Neth" wrote in message
. ..
Go into the control panel - system applet - advanced - startup and
recovery.
Uncheck the "automatically restart" box. The next time you should see an
error that lets you track the problem.

Also look in the Event Logs to see what's there.

Chances are it's a software issue, not hardware.



"Don Cohen" wrote in message
...
I have a 2 year old Gateway 700XL (2.2 GHz Pent 4., 1024 Mb RAM, 120 GB
HD,
XP Home, ATI Radeon VideoCard with FPD1810 LCD Monitor), which has run
virtually flawlessly. The only glitch has been a rare monitor black-out
lasting a few seconds (without any reboot or other issues), occurring
once
every couple of months. I researched this problem, and saw that many
others
experienced this with this hardware, with no definitive answer that I
could
ever identify.

I keep it well maintained in terms of critical updates, have run
AdAware,
NAV 2003, ZoneAlarm, etc.

Out of nowhere it has started spontaneously rebooting. I'll just be
doing
the usual - either checking email, browsing the web, and the screen goes
black, and without further intervention, it just completely reboots.
I'm
not a gamer, so the system (or video subsystem) is not getting any real
work-out when this occurs.

My daughter reported this happening when she was using it perhaps a
month
or
two ago. Then it happened once yesterday. Today it happened again, and
kept doing it, running only 5 or 10 minutes before rebooting. Now I
have
it
turned off, and will let it cool down overnight and see what happens in
the
morning.

I took the side cover off and verified that the fan was spinning (it
seemed
fairly fast but I don't know how fast it should be). The side of the
metal
around the CPU was fairly warm to touch, but it didn't seem excessively
hot.
After turning it off completely, I gently vacuumed the fan and
surrounding
area, case vents, and left the side off for better ventilation. It
still
rebooted.

I downloaded MemTest, and tried running it. It got to around 70%,
showed
0
errors, but then rebooted so it couldn't complete.

I'm inclined to think this is a hardware issue, but short of bringing or
sending it in for service, what kind of diagnostics or other methods can
I
use to try and define the source of this problem?

Has anyone experienced this with this or similar systems?

I had done some 'googling' yesterday and what I found suggested fan,
memory
or other hardware failure, but one person concluded a software problem
(I
forget which) was the source.

Any help greatly appreciated. I really depend on this computer for
many,
many tasks, on a daily basis!

Thanks!

--
Don
Photo Website at:
www.dlcphotography.net
remove "lens cap" for email reply

A little further info:

Last night before the final reboot, memtest had gotten over 300% without
detecting any errors.

I just booted into Safe Mode without problem to troubleshoot further, but
the same blue screen came up within 5 minutes.

Don



"Don Cohen" wrote in message
...
Thanks guys.

Further info:

I can't think of any new appliance or other electrical draw in my house.
I
have a "APC Back-up Office" UPS for my computer, which is many years old
(perhaps 4-5 years). There is a lot of hardware (Monitor, Network Switch,
USB Printer, Speakers, Cable-Modem, etc.) plugged into it.

I did further reading using my laptop, and did disable the "automatically
restart" box.

I left my computer off overnight. After rebooting this morning, the
problem
recurred within minutes, implying that it's not a heat issue. No chance
to
look at error logs. But did receive the following blue screen message:

PAGE DEFAULT_IN_NONPAGED_AREA

Followed by some generic troubleshooting instructions that don't seem
particularly helpful, then:

Technical Information:

***STOP: 0x00000050 (0xB7874E5E, 0x00000000, 0xB7874E5E, 0x00000000)

Beginning dump of physical memory
Physical memory dump complete

Contact your system adminitrator...yada, yada, yada.

I'll be researching this, but hopefully this will help identify the
problem.

I have not recently added hardware.
I believe the last system change made was doing a NAV 2003 Live Update.
I can't remember precisely, but after a recent reboot not too long before
this started (but months after my daughter reported this occurring once),
I
received a "Windows has recovered from a serious error" message, but
everything seemed to run fine after that.


So where do we go from here?

Thanks!

Don

"Edward J. Neth" wrote in message
. ..
Go into the control panel - system applet - advanced - startup and
recovery.
Uncheck the "automatically restart" box. The next time you should see
an
error that lets you track the problem.

Also look in the Event Logs to see what's there.

Chances are it's a software issue, not hardware.



"Don Cohen" wrote in message
...
I have a 2 year old Gateway 700XL (2.2 GHz Pent 4., 1024 Mb RAM, 120
GB
HD,
XP Home, ATI Radeon VideoCard with FPD1810 LCD Monitor), which has run
virtually flawlessly. The only glitch has been a rare monitor
black-out
lasting a few seconds (without any reboot or other issues), occurring
once
every couple of months. I researched this problem, and saw that many
others
experienced this with this hardware, with no definitive answer that I
could
ever identify.

I keep it well maintained in terms of critical updates, have run
AdAware,
NAV 2003, ZoneAlarm, etc.

Out of nowhere it has started spontaneously rebooting. I'll just be
doing
the usual - either checking email, browsing the web, and the screen
goes
black, and without further intervention, it just completely reboots.
I'm
not a gamer, so the system (or video subsystem) is not getting any
real
work-out when this occurs.

My daughter reported this happening when she was using it perhaps a
month
or
two ago. Then it happened once yesterday. Today it happened again,
and
kept doing it, running only 5 or 10 minutes before rebooting. Now I
have
it
turned off, and will let it cool down overnight and see what happens
in
the
morning.

I took the side cover off and verified that the fan was spinning (it
seemed
fairly fast but I don't know how fast it should be). The side of the
metal
around the CPU was fairly warm to touch, but it didn't seem
excessively
hot.
After turning it off completely, I gently vacuumed the fan and
surrounding
area, case vents, and left the side off for better ventilation. It
still
rebooted.

I downloaded MemTest, and tried running it. It got to around 70%,
showed
0
errors, but then rebooted so it couldn't complete.

I'm inclined to think this is a hardware issue, but short of bringing
or
sending it in for service, what kind of diagnostics or other methods
can
I
use to try and define the source of this problem?

Has anyone experienced this with this or similar systems?

I had done some 'googling' yesterday and what I found suggested fan,
memory
or other hardware failure, but one person concluded a software problem
(I
forget which) was the source.

Any help greatly appreciated. I really depend on this computer for
many,
many tasks, on a daily basis!

Thanks!

--
Don
Photo Website at:
www.dlcphotography.net
remove "lens cap" for email reply

I downloaded MemTest, and tried running it. It got to around 70%, showed 0
errors, but then rebooted so it couldn't complete

This is pretty suspicious. Memtest86 runs in it's own DOS so that eliminates
virtually anything but hardware. Power supply is my first guess, but memory
is not really ruled out either.
Best to remove everything but video card and RAM and start from there. You
could even remove the hard drive and run Memtest86 again from floppy.

Hi Dan,

Thanks for the reply.

This is pretty suspicious. Memtest86 runs in it's own DOS so that
eliminates
virtually anything but hardware. Power supply is my first guess, but
memory
is not really ruled out either.

Is Memtest different from Memtest86?
Also, I ran it from Safe Mode. I guess I'll download the "official"
memtest86 and copy it to a boot floppy and run it from there.

Also, I was able to install Support Tools, ran dumpchk.exe on a few of the
minidump files it has created (and also found the one generated when my
daughter experienced this problem - it was dated 12/24/03). I can't make
much sense of it, but I've copied below the full text of the report.

This morning it initially wouldn't run for more than a few minutes, but
since those couple of initial reboots, it's been running (in safe mode
repeating memtest, which got up to 750% before I manually stopped it - 0
errors).

Very, very frustrating.

Once again thanks, and any further insights appreciated. My gut also tells
me power supply, but my gut is not 100% reliable!

Don

Minidump report:

C:\WINNT\Minidumpdumpchk mini122403-01.dmp
Loading dump file mini122403-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 09d2f000
PfnDataBase 81ad3000
PsLoadedModuleList 80543530
PsActiveProcessHead 80545578
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 10000050
BugCheckParameter1 b7874e5e
BugCheckParameter2 00000000
BugCheckParameter3 b7874e5e
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805353e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 00000904
DriverListOffset 00003510
DriverCount 00000096
StringPoolOffset 00006198
StringPoolSize 000014f8
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack eb67c6fc
DebuggerDataOffset 00003280
DebuggerDataSize 00000290
DataBlocksOffset 00007690
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Wed Dec 24 15:38:31 2003
System Uptime: 5 days 22:18:11
start end module name
804d4000 806aa280 nt Checksum: 001E311B Timestamp: Thu Apr 24
11:
57:43 2003 (3EA80977)

Unloaded modules:
eb776000 eb79d000 kmixer.sys Timestamp: unavailable (00000000)
eb273000 eb27a000 usbprint.sys Timestamp: unavailable (00000000)
eb776000 eb79d000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb850000 eb857000 usbprint.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb3a4000 eb3ab000 usbprint.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb14c000 eb153000 usbprint.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb27b000 eb282000 usbprint.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)

Finished dump check

Memtest86 is the one I meant, you just unzip the download to a floppy and
boot to it, it auto-runs. In case you haven't already, be sure to re-seat
the RAM.



"Don Cohen" wrote in message
...
Hi Dan,

Thanks for the reply.

This is pretty suspicious. Memtest86 runs in it's own DOS so that
eliminates
virtually anything but hardware. Power supply is my first guess, but
memory
is not really ruled out either.

Is Memtest different from Memtest86?
Also, I ran it from Safe Mode. I guess I'll download the "official"
memtest86 and copy it to a boot floppy and run it from there.

Also, I was able to install Support Tools, ran dumpchk.exe on a few of the
minidump files it has created (and also found the one generated when my
daughter experienced this problem - it was dated 12/24/03). I can't make
much sense of it, but I've copied below the full text of the report.

This morning it initially wouldn't run for more than a few minutes, but
since those couple of initial reboots, it's been running (in safe mode
repeating memtest, which got up to 750% before I manually stopped it - 0
errors).

Very, very frustrating.

Once again thanks, and any further insights appreciated. My gut also
tells
me power supply, but my gut is not 100% reliable!

Don

Minidump report:

C:\WINNT\Minidumpdumpchk mini122403-01.dmp
Loading dump file mini122403-01.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 09d2f000
PfnDataBase 81ad3000
PsLoadedModuleList 80543530
PsActiveProcessHead 80545578
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 10000050
BugCheckParameter1 b7874e5e
BugCheckParameter2 00000000
BugCheckParameter3 b7874e5e
BugCheckParameter4 00000000
PaeEnabled 00000000
KdDebuggerDataBlock 805353e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 00000904
DriverListOffset 00003510
DriverCount 00000096
StringPoolOffset 00006198
StringPoolSize 000014f8
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack eb67c6fc
DebuggerDataOffset 00003280
DebuggerDataSize 00000290
DataBlocksOffset 00007690
DataBlocksCount 00000003


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x80543530
Debug session time: Wed Dec 24 15:38:31 2003
System Uptime: 5 days 22:18:11
start end module name
804d4000 806aa280 nt Checksum: 001E311B Timestamp: Thu Apr
24
11:
57:43 2003 (3EA80977)

Unloaded modules:
eb776000 eb79d000 kmixer.sys Timestamp: unavailable (00000000)
eb273000 eb27a000 usbprint.sys Timestamp: unavailable (00000000)
eb776000 eb79d000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb850000 eb857000 usbprint.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb3a4000 eb3ab000 usbprint.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb14c000 eb153000 usbprint.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)
eb27b000 eb282000 usbprint.sys Timestamp: unavailable (00000000)
eb0df000 eb106000 kmixer.sys Timestamp: unavailable (00000000)

Finished dump check

Memtest86 is the one I meant, you just unzip the download to a floppy and
boot to it, it auto-runs. In case you haven't already, be sure to re-seat
the RAM.

That's what I thought. I actually just donwloaded the 'ISO' image and
burned it making a bootable CD. Interestingly, my system brought up the
same BSOD just seconds after this completed, after it had been running
without problem for perhaps an hour or so.

Memtest86 is now running, and after 18 minutes shows 0 errors.

I know this needs to be done, and it would be convenient if that's all it
is, but somehow I suspect it won't be.

I guess the contents of the 'minidump' file didn't give you any additional
insight either?

Don

Memtest86 should run for many hours, at least 8. Most errors seem to occur
in tests 5 and 6, but run them all. If your machine does that and doesn't
reboot. then I think you've ruled out hardware, maybe.


"Don Cohen" wrote in message
...
Memtest86 is the one I meant, you just unzip the download to a floppy
and
boot to it, it auto-runs. In case you haven't already, be sure to
re-seat
the RAM.

That's what I thought. I actually just donwloaded the 'ISO' image and
burned it making a bootable CD. Interestingly, my system brought up the
same BSOD just seconds after this completed, after it had been running
without problem for perhaps an hour or so.

Memtest86 is now running, and after 18 minutes shows 0 errors.

I know this needs to be done, and it would be convenient if that's all it
is, but somehow I suspect it won't be.

I guess the contents of the 'minidump' file didn't give you any additional
insight either?

Don