blue screen of death vxd errors

[mycomputerblows]

I get constant blue screen of death vxd errors. I have got them for months now and cant solve the problem. They occur all the time. Wether im playing a game, unzipping something or searching the internet these blue screens rapiddly occur. The messages vary, but are always .vxd errors. Any help on how to solve my problem would be great---

Thx :p

[KWB Teck]

First thing I would try is replace the memory.

[http://forums.windrivers.com/cgi-bin/forum1/noncgi]

Originally posted by KWB Teck:
First thing I would try is replace the memory.

I agree with KWB Teck. Memory would be my number one suspect.

[PEZ_B0y]

And if that doesnt work (vxds are crappy this way) just reinstall the OS that has worked for me many times in the past you don't even have to reformat just reinstall.

[mycomputerblows]

ive tried reinstalling windows, and reformnatting many times--- but right when I'm done, WHAM! they hit me. I tried taking it in to the store and they didnt fix it. They said its not the memory, and ran tests on the ram. Is it my drivers??? If so how do I tell which ones? Where do I get the new, right ones from?

[3fingersalute]

What brand of processor?

[mycomputerblows]

emachine 466is,intel,128 mb ram , original video card, windows 98

[johny dmonic]

Boot up into DOS. At the command prompt, go to C: drive
Type
dir/a/b/s *.tmp>t.bat Let it finish
then type
dir/a/b/s ~*.*>t1.bat Let it finish. Type in
edit t.bat
Go to search, replace
In replace what, find c:
In replace with, type in deltree/y c:
Choose replace all. Save and exit. Do the same for t1.bat
Then, back at dos screen, type
t then enter,
then t1, then enter. This will clear up 99% of all blue screens and Illegal Operations.

This is a recommendation given in the That Home Site forums under the topic shutdown problems...please help if possible (March 29,2001).

Not tried this though, but according to the one that give the information, it works. Any comment about this one? :rolleyes:

[jeffsr]

This may be a heat problem. Check your CPU and heatsink/fan. I have seen this a number of times before..

[joshuarat]

hey, I'm brand new here....The reinstall usually works for me on those....oh, why on earth do ya have an E- Machine? not flaming ya, just curious.

[PEZ_B0y]

I think its for the same reason people have compaqs and hewlett packards.

[iccrmman]

Originally posted by jeffsr:
This may be a heat problem. Check your CPU and heatsink/fan. I have seen this a number of times before..
I have to agree. I have a e-crap too. I had a similar problem, pulled the heatsink, and there were scorch marks on it. Get a good quality hs/f and some thermal paste(better than what's there now!!).

[chip35]

I don't care what they say, I so far have not seen a memory test that works reliably. You can run them till you're blue in the face and they will still pass anything but a hard error.HOWEVER I find reliable blue screens to be one of two problems:
Corrupt .ini files
Memory.
Check in that order (order of cost)
Windows just happens to be the best memory test around, It just doesn't tell you.
Now another thing. If the memory is bad, after a few days of fighting this you should come up with a registry corrupt message. Windows doesn't really check when backing up the registry to disk on shutdown.It blindly corrupts it then warns you at boot up.

[CornMaster]

Originally posted by Computer_Chip:
I don't care what they say, I so far have not seen a memory test that works reliably. You can run them till you're blue in the face and they will still pass anything but a hard error.HOWEVER I find reliable blue screens to be one of two problems:
Corrupt .ini files
Memory.
Check in that order (order of cost)
Windows just happens to be the best memory test around, It just doesn't tell you.
Now another thing. If the memory is bad, after a few days of fighting this you should come up with a registry corrupt message. Windows doesn't really check when backing up the registry to disk on shutdown.It blindly corrupts it then warns you at boot up.

How would you go about checking for corrupted ini files? I have a similar problem.

[mycomputerblows]

yes how would i check corrupt ini files? And I tried this when testing my ram;
- first i took out the 64 mb chip in slot 2, the comp. worked fine
- i thought i had problem solved, then i got tech. to put 128 in slot 1. I left nothing in slot 2. Blue screens began appearing again one day

is there any others way I could test the memory??
Thx 4 all your help people :)

[Sowulo]

So according to an earlier post you started with 128Mb. Then you took out the 64Mb DIMM from slot2 and it ran fine. That means it worked with a 64Mb in slot1, but when the 64 in slot1 is replaced with a 128Mb DIMM, then you have problems again? This is as you've reported. If all this is true then more than likely the 128 and the original 64 from slot2 may both be bad. Try both 64's in slot1 one at a time. If they both work fine then let us know and we'll put our thinking caps back on.

[DANIMAL]

Originally posted by jeffsr:
This may be a heat problem. Check your CPU and heatsink/fan. I have seen this a number of times before..

Diddo on the heat idea.

[ricco]

Drivers....Drivers....Drivers....Drivers....Driver s....Drivers....Drivers....Drivers....Drivers....D rivers....Drivers....Drivers....Drivers....
Used to manufacture all sorts of machines.
Had this error more with network cards and sound cards.
Do you find this happens when the computer is going to run something specifically orientated around hardware....
I.E. Accessing a sound file and the message pops up, video driver, etc
Oh....Memory causes the same error.
I agree with you chaps.

[mycomputerblows]

ok sorry iy im confusing you with the memory-- here's exactly what has happened::

1. The computer originally had 32
2. Put 64 in second slot--- everything fine
3. Took out 32 in slot 1- put 64 in slot 1. Problems occures (not exact time of switch)
4. Took computer in to get memory tested-- both 64 chips reported fine.
5. Couldnt solve blue screens-- so took 64 out of slot 2-- computer worked for a bit
6. Computer was too slow, so took 64 outta slot 1 and put 128 in. Leaving 128 in slot and notihng in slot 2,, cause slot 2 seemed to be the problem
7. A while after blue screens started coming again-- thats how computer is now

[iccrmman]

Also what brand memory? Some of the generics are NOT compatable with e-macs.

[KINGofBLEH]

Originally posted by jeffsr:
This may be a heat problem. Check your CPU and heatsink/fan. I have seen this a number of times before..

Agreed. I would crack the case and make sure the CPU and box fans are both running. If possible, check the RPMs on the fans to make sure that they are within Intel's specs. This is usually done in the BIOS.

[mycomputerblows]

how exactly do i check them??? I'm kinda a computer newbie

[3fingersalute]

Originally posted by mycomputerblows:
how exactly do i check them??? I'm kinda a computer newbie

Most newer machines will report fan speen and cpu and system temp in the BIOS.

[NTTECH1]

Replace the memory with Kingston Memory<h1>Dont put junk Memory in your Machine</h1>There is a differance in memory and yes you will pay more for quality Memory be sure to check if the memory is PC-100 or PC-133 SDRAM. After you replace the memory FDISK the Drive and reinstall Windows. Be sure to do a full back up of your files first.

[jsh20]

Is there any specifics on the fatal exceptions...as to any vxd files?