bugchecks and strange message about USB

  • Thread starter Thread starter nesredep egrob
  • Start date Start date
N

nesredep egrob

Quite often I get messages about not having alerted the computer to an
imminent removal of a USB device. I have tried to make up for that by
hitting the icon in the taskbar for that and also re-booting. I still
get the message in the middle of some other task I wish to perform.
Today I got a reboot which gave the result as seen in the eventlog. I
have seen reboots prior to this but not looked in the log. Is there a
quick solution or do I have to re-install windows with the usual
backup after the format?

"The computer has rebooted from a bugcheck. The bugcheck was:
0x0000001e (0xc0000005, 0x80469c08, 0x00000000, 0x00000000). Microsoft
Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini030505-01.dmp. "

I looked at that but am sorry to say that was well beyond my
capabilities of understanding.

I have now seen that there have been 13 minidumps since 26 of Jan this
year. Incidentally the bios seems to have changed giving a boot
sequence that I have never seen:
1 Secondary Master WDC WD2000
2 Secondary Slave WDC WD2000
3 Bootable Add in cards

The only thing that has happened in that time is that I have installed
Microsoft Anti Spyware beta 1. I am not sure of the starting date for
that but it might have been just the same date that the minidumps
started :-)

B.Pedersen Latitude -31,48.21 Longitude115,47.40 Time=GMT+8.00
If you are curious look here http://www.mapquest.com/maps/latlong.adp
 
nesredep said:
Quite often I get messages about not having alerted the computer to an
imminent removal of a USB device. I have tried to make up for that by
hitting the icon in the taskbar for that and also re-booting. I still
get the message in the middle of some other task I wish to perform.
Today I got a reboot which gave the result as seen in the eventlog. I
have seen reboots prior to this but not looked in the log. Is there a
quick solution or do I have to re-install windows with the usual
backup after the format?

"The computer has rebooted from a bugcheck. The bugcheck was:
0x0000001e (0xc0000005, 0x80469c08, 0x00000000, 0x00000000). Microsoft
Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini030505-01.dmp. "

I looked at that but am sorry to say that was well beyond my
capabilities of understanding.

I have now seen that there have been 13 minidumps since 26 of Jan this
year. Incidentally the bios seems to have changed giving a boot
sequence that I have never seen:
1 Secondary Master WDC WD2000
2 Secondary Slave WDC WD2000
3 Bootable Add in cards

The only thing that has happened in that time is that I have installed
Microsoft Anti Spyware beta 1. I am not sure of the starting date for
that but it might have been just the same date that the minidumps
started :-)
Click to expand...


The 0x0000001e indicates a hardware problem, also known
as KMODE_EXCEPTION_NOT_HANDLED. And the boot message is
also pointing to hardware issues.

First, make sure that the Master and Slave HD's are set
up and jumpered properly. Next, disable the PnP OS setting
in bios configuration --- not needed for Windows 2000.
Third, all hardware drivers and patches should be current
and direct from their manufacturers. Short of any other
thoughts at this time, these 3 steps might be enough to
make the computer perform more consistently.
 
nesredep said:
Quite often I get messages about not having alerted the computer to an
imminent removal of a USB device. I have tried to make up for that by
hitting the icon in the taskbar for that and also re-booting. I still
get the message in the middle of some other task I wish to perform.
Today I got a reboot which gave the result as seen in the eventlog. I
have seen reboots prior to this but not looked in the log. Is there a
quick solution or do I have to re-install windows with the usual
backup after the format?

"The computer has rebooted from a bugcheck. The bugcheck was:
0x0000001e (0xc0000005, 0x80469c08, 0x00000000, 0x00000000). Microsoft
Windows 2000 [v15.2195]. A dump was saved in:
C:\WINNT\Minidump\Mini030505-01.dmp. "

I looked at that but am sorry to say that was well beyond my
capabilities of understanding.

I have now seen that there have been 13 minidumps since 26 of Jan this
year. Incidentally the bios seems to have changed giving a boot
sequence that I have never seen:
1 Secondary Master WDC WD2000
2 Secondary Slave WDC WD2000
3 Bootable Add in cards

The only thing that has happened in that time is that I have installed
Microsoft Anti Spyware beta 1. I am not sure of the starting date for
that but it might have been just the same date that the minidumps
started :-)
Click to expand...


The 0x0000001e indicates a hardware problem, also known
as KMODE_EXCEPTION_NOT_HANDLED. And the boot message is
also pointing to hardware issues.

First, make sure that the Master and Slave HD's are set
up and jumpered properly. Next, disable the PnP OS setting
in bios configuration --- not needed for Windows 2000.
Third, all hardware drivers and patches should be current
and direct from their manufacturers. Short of any other
thoughts at this time, these 3 steps might be enough to
make the computer perform more consistently.
Click to expand...

I approached this problem in an upside down manner, maybe because I
live in Australia. First I went for the external disk which is on
USB2. The jumpering was set as slave, it is now cable select.
Then In Bios I was looking for the PNP OS setting which I never found.
Looked in the first window and to my horror found that the 2 cables
for the IDE and CD's had been switched so that the CD was the Primary.

It was done at a time when I found the DVD was not working well. I had
heard about the 80 cables and replaced both the IDE and the CD/DVD and
got them the wrong way round.

Thanks and I am thoroughly ashamed

B.Pedersen Latitude -31,48.21 Longitude115,47.40 Time=GMT+8.00
If you are curious look here http://www.mapquest.com/maps/latlong.adp
 
Back
Top