A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

DVD Rom causes BSOD



 
 
Thread Tools Display Modes
  #1  
Old September 1st 05, 05:26 AM
Menno Hershberger
external usenet poster
 
Posts: n/a
Default DVD Rom causes BSOD

I just cleaned up a Presario 5852. It had a pretty good dose of spyware.
I don't know if that is pertinent or not since this problem existed both
before and after I cleaned it up. It has a DVD Rom which is original
equipment and an added CDRW drive. Cable select cable and both drives
jumpered for CD. When you insert a CD in the DVD drive, you get an
unrecoverable BSOD. The CDRW drive works alright. If I boot from a
startup disk, both drives work OK. A boot CD will work in either drive,
so it must be a Windows thing.
This is a 550Mhz machine with 128Mb ram.
Right now I'm doing a repair install on it (SE) but I don't really expect
that to fix it. I imagine it's something in the registry that a repair
install won't change.
Any ideas?


--
--- A Freudian slip is when you say one thing but mean your mother. ---
  #2  
Old September 1st 05, 05:40 AM
Gary S. Terhune
external usenet poster
 
Posts: n/a
Default

Well, by now you should know how I feel about "reinstalling" Windows. Too
late, I guess.

What *I* would have done is to boot into Safe Mode, go to Device Manager and
delete the entire IDE tree--ALL drives, ALL controllers (except the FIFOs,
which can't be deleted in Device Manager) and the System device called PCI
Bus. Then restart and let Windows reinstall. Will take at least one more
restart to finish installing the drives.

--
Gary S. Terhune
MS-MVP Shell/User

"Menno Hershberger" wrote in message
...
I just cleaned up a Presario 5852. It had a pretty good dose of spyware.
I don't know if that is pertinent or not since this problem existed both
before and after I cleaned it up. It has a DVD Rom which is original
equipment and an added CDRW drive. Cable select cable and both drives
jumpered for CD. When you insert a CD in the DVD drive, you get an
unrecoverable BSOD. The CDRW drive works alright. If I boot from a
startup disk, both drives work OK. A boot CD will work in either drive,
so it must be a Windows thing.
This is a 550Mhz machine with 128Mb ram.
Right now I'm doing a repair install on it (SE) but I don't really expect
that to fix it. I imagine it's something in the registry that a repair
install won't change.
Any ideas?


--
--- A Freudian slip is when you say one thing but mean your mother. ---



  #3  
Old September 1st 05, 07:50 AM
Don Phillipson
external usenet poster
 
Posts: n/a
Default

"Menno Hershberger" wrote in message
...

. . . before and after I cleaned it up. It has a DVD Rom which is original
equipment and an added CDRW drive. Cable select cable and both drives
jumpered for CD. When you insert a CD in the DVD drive, you get an
unrecoverable BSOD. The CDRW drive works alright. If I boot from a
startup disk, both drives work OK. A boot CD will work in either drive,
so it must be a Windows thing.


Can this be right? CD and hard drives are jumpered for master/slave
connection, not "jumpered for CD."
Secondly, older PCs with two CD drives seem to prefer that the CDRW
drive be connected as master.

--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)


  #4  
Old September 1st 05, 07:56 PM
Menno Hershberger
external usenet poster
 
Posts: n/a
Default

Yeah, I did that. There were a few extra drives still listed that had
been on there before. Came back with the same problem. This whole thing
is turning into a nightmare. I can't do a repair install because after
the install gets the files copied and reboots, I wind up at the command
prompt with a message that the registry is screwed up and to run scanreg.
If I do that, then it boots back into the old install. I even tried
setting it back to the oldest restore date that was available and booting
it up a couple of times to make sure it would stick. But then when I
started the repair install again, it'd do the same thing. It's going to
get a format and fresh install... I've wasted too much time already.


"Gary S. Terhune" wrote in
:

Well, by now you should know how I feel about "reinstalling" Windows.
Too late, I guess.

What *I* would have done is to boot into Safe Mode, go to Device
Manager and delete the entire IDE tree--ALL drives, ALL controllers
(except the FIFOs, which can't be deleted in Device Manager) and the
System device called PCI Bus. Then restart and let Windows reinstall.
Will take at least one more restart to finish installing the drives.




--
--- A Freudian slip is when you say one thing but mean your mother. ---
  #5  
Old September 2nd 05, 12:22 AM
Gary S. Terhune
external usenet poster
 
Posts: n/a
Default

I figured it was headed for the nuclear option. Gotta think malware is
involved somehow. You previously wiped the IDE tree altogether and
reinstalled?

Anyway, have fun, eg.

--
Gary S. Terhune
MS-MVP Shell/User

"Menno Hershberger" wrote in message
...
Yeah, I did that. There were a few extra drives still listed that had
been on there before. Came back with the same problem. This whole thing
is turning into a nightmare. I can't do a repair install because after
the install gets the files copied and reboots, I wind up at the command
prompt with a message that the registry is screwed up and to run scanreg.
If I do that, then it boots back into the old install. I even tried
setting it back to the oldest restore date that was available and booting
it up a couple of times to make sure it would stick. But then when I
started the repair install again, it'd do the same thing. It's going to
get a format and fresh install... I've wasted too much time already.


"Gary S. Terhune" wrote in
:

Well, by now you should know how I feel about "reinstalling" Windows.
Too late, I guess.

What *I* would have done is to boot into Safe Mode, go to Device
Manager and delete the entire IDE tree--ALL drives, ALL controllers
(except the FIFOs, which can't be deleted in Device Manager) and the
System device called PCI Bus. Then restart and let Windows reinstall.
Will take at least one more restart to finish installing the drives.




--
--- A Freudian slip is when you say one thing but mean your mother. ---



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
winME problem with IE 6.0 Red starcut spinnaker Internet 3 April 9th 05 04:09 PM
BSOD and K891711 update Mike General 8 March 25th 05 05:34 PM
BSOD and BSON, so removed 'buggy' Mar 8 05 security update kb891711 (WinMe) [email protected] General 2 March 15th 05 06:55 AM
BSOD: Fatal 0D @ 170F:... DSL-Dave General 3 October 1st 04 03:23 PM
Frequent BSOD with same consistant error.. Maddison General 1 July 20th 04 10:15 AM


All times are GMT +1. The time now is 10:34 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.