Computer Woes

[Springheel]

I've been having a number of computer problems the last couple weeks, which I think may be related to overheating, but I'm not sure.

 

I've noticed now, however, every time Windows boots up, it gives me the following error report (in one of those, "send to Microsoft" screens):

 

Run a DLL as an App has encountered a problem and needs to close. We are sorry for the inconvenience.

 

Any of our computer-savy members know what the heck this could be referring to?

[Darkness_Falls]

Often Google searches for the error your seeing can help. I tried your's and it came up with some results, including:

http://techrepublic.com.com/5100-6270-5225409.html#

Cause

This error may occur if the primary hard drive or boot partition has been changed/upgraded/replaced and software from the hard drive vendor (such as MaxBlast from Maxtor or Data Lifeguard from Western Digital) has been used to move the data from the old to the new drive.

 

If this doesn't mesh with your situation, keep trying the Google searches. Someone out there has likely posted a solution to your problem.

[Vadrosaul]

Possibly this:

Google group answer

 

Or somewhere in here:

http://www.newbie.org/help/messages/11694.html

[Ishtvan]

If you're worried about overheating, you can also try this "hardware wizard" Sisoft Sandra: http://www.sisoftware.net/ . If you install Sandra and run a diagnostic on CPU, it should tell you what the current temperature is and stuff. Then you can look up the rated temperatures for your CPU. (Note: Some mobo temperature probes may be inaccurate though, as mine apparently is...)

 

Also, consider things like how many intake fans you have, how many exhaust fans you have, is your GFX card really close to your sound card, that sort of thing.

Edited April 10, 2005 by Ishtvan

[Springheel]

Hmm, interesting. I don't *have* any HD partitions. I have two separate drives. Actually, come to think of it, this morning when I booted up windows, my D drive wasn't detected. Rebooting several times didn't solve the problem, until I shut the machine off and started it up again. Then it was there, but I was getting this error message. I suppose that's the connection....

 

Here's the screen I'm getting. I tried two different solutions from the links above (the system restore solution and the adaware solution) but neither of them worked.

 

[oDDity]

IT's something to do with a program you installed, I remember getting this error before, but not exactly why or how I solved it - sorry)

Try to remember what you installed before this started happening, of if you have syste restore turned on, go back to before this started.

Also if you could do a ctrl-alt-del and bring up the task manager - process tab - it may be starting some process when you log on that's cauing this and could be turned off.

Go into msconfig startup tab and check to see what is starting when you log on.

 

edit: Have you an ATI graphics card? I have a vague recollection it may have had something to do with the ATI start centre or confiuration utilite that's installed with the drivers.

Edited April 10, 2005 by oDDity

[Domarius]

Hey... watch it. I'd be backing up what's on that drive. The first I ever knew about my hdd failing a few years ago was an error reading from drive, drive not found... then... 3 years of collected memories (photos of people, stuff I made, etc. etc.) all down the toilet.

[Springheel]

I haven't installed anything recently, but I've been having other problems that might have caused this. Most of the time when I boot up now, the process takes a long time, pausing at the IDE detection for a full minute or two. Sometimes the boot process stalls entirely and I get a 'boot device not detected' error. Other times Windows boots up but my drive D: isn't showing up. That drive's only three months old but I'm going to try disconnecting it and seeing what happens. Luckily there's only one important thing on that drive, which I hopefully can get off.

[Demigod]

Is this the boot drive? It may just need a reinstall of windows, but it does sound most odd. Does the drive click at all?

 

Thinking about it the only time I have seen erors like that is when I overclock. What is your cpu temp? As it gets hotter more erros occur and progs fail. It may also be your memory as a dieing stick can do the same thing.

 

I think the best approch is to do what you are doing. Disconnect the drive and see if the errors still occur.

 

Its not a maxtor drive is it?. I ask as I have a box of Hd's next to me. It has two seagates a 20 and 40 gig, about five years old that still work, but are slow being udma 33. But it also has three maxtor drives all dead, none lasted more than six months.

[Springheel]

It's not the boot drive, which is odd. No strange noises. Heating is a possible problem, but I have an external fan blasting it right now and the problems are still happening.

 

The actual error I get when the boot process fails is:

 

Reboot and Select proper Boot Device

'or insert bootable media' (not sure about second line)

 

A faulty drive D: couldn't affect the boot process when Win is on C: could it?

[Demigod]

No it shouldnt cause any boot problems. This is an odd error.

Do you have a windows cd handy?

 

If so cop these two files to your c: drive

 

X:\i386\NTLDR C:

X:\i386\NTDETECT.COM

 

X being your cdrom drive.

 

Reboot and boot from the cd. It should ask you if you want to repair an instalation select yes next if I remember right it should ask if you want to do it automaticaly or go to the recovery console. Go to the console.

 

type fixboot and hit return

 

type fixmbr and hit returm

 

Hopefuly that should work. Both of the above will mess up any linux bootloader you have though.