You could, because I still don't get it. I solved that problem (without your FREE HELP) by replacing mobo, cpu and IEEE1394 Card.Originally Posted by TooLFooL
+ Reply to Thread
Results 31 to 42 of 42
-
moved to another forum, nobody likes me here...
-
The best time saving strategy for you would be:
- create a new few Gig part. on your HDD
- fresh install a new copy of XP on it and beat your PC to death with burn-in test or similar (game demos etc.) Sandra may be of some help
- if no BSOD then fix your old WinXP (repair or new install)
- don't forget to run chkdsk /r on all partitions
I have a feeling that your XP is limping due to corruption... like I said before... or keep on guessing. Good luck. -
I had the same type of message yesterday.
I ripped Disc Two of the Divinci Code with DVDFabDecrypter and tried to play it in PowerDVD...then I got the almost identical blue screen....but mine was in German and some of the words were not yet in my vocabulary... -
Perhaps you do not understand the concept.
When you suffer any type of catastrophic failure on a PC, and most particularly a power-related one such as frying a processor, EVERY SINGLE PIECE in that PC is now suspect. Floppy and CD-Rom, power supply, fans, cables, EVERYTHING THAT CARRIES OR IS TOUCHED BY POWER. The case and the screws will still be good.
To replace the most obviously dead parts and then suffer intermittent blue screen, hardware errors is extremely common. Many parts that are not obviously dead may very well have been damaged to a lesser extent. They may run sporadically for days, years, or hours and then fail completely.
Ordinarily determining the source of a hardware failure is relatively easy because most parts can be assumed to probably be good, and the problem can be isolated to a very few possibilities. In the case of a previous catastrophic failure, this is no longer true. It would appear that optical and floppy drives, memory, video and sound cards if present, USB connections, various other items and most especially the power supply from the previous afflicted PC may have been re-used. Any of these parts, and most especially the power supply, could very well if defective cause permanent damage to new installed pieces.
You cannot look at most PC parts and say "this is good" or "this is bad". Functionality is determined by installing the part in a PC that is already functioning perfectly, and is KNOWN TO BE GOOD. If the PC fails with the one part changed, that part is bad, assuming correct installation.
However when you start with a collection of parts containing many that are suspect, and most especially the power supply, determining which are good and which are bad becomes exponentially more difficult.
So back to the question, how many parts in the current PC were left over from the one in which you fried the processor? -
Find a way to run check disk (chkdsk.exe) and left it fix any errors. Just fixed a computer for a friend with the same error. Took over an hour to find a way to run the F*in program, five minutes once it started.
Its a pain due to the file system being ntsf not fat.
I'd offer what I did, but I'm not sure what finally made it run. -
Originally Posted by fLYtRapJohn Miller
-
I would bet money right now that there is only one box, and that more than one piece is left over from the damaged one. Most especially the power supply.
-
I agree with Nelson37.Replace the ram.If the problem persists,install everything in a new case,etc.
bmiller,ont.canada -
No, you do not throw it away but you do not spend time determining the cause of a failure when that failure is NOT isolated. If the current failure is connected to the previous one in any way, then that changes the diagnosis.
What it does is bring into play more pieces than would otherwise be suspected. I have already been through this process with this particular poster, as well as several others here and countless others in my personal business. This is not a brand new box with a single, isolated problem. It is a collection of components of which several may have been electrically connected to a PC in which the processor was smoked. This collection of components is now experiencing an unknown hardware failure. The process of diagnosing the current failure changes dramatically with the knowledge of which components were present during the previous catastrophic failure.
This is not something I have done once or twice. The numbers run into the hundreds.
The only parts stated to be replaced were the CPU, mobo, and IEE-1394 card. It is unclear but the indication is that the issue with the 1EEE-1394 card began AFTER the processor was smoked. What other parts were damaged is currently unknown, but the current problem indicates that at least one is defective. It is quite possible that ALL were damaged, and will fail prematurely.
If the power supply was damaged in the previous incident, it is quite possible that several hundred dollars worth of new parts have been destroyed because a $45.00 power supply should have been replaced. I have seen this happen, more than once.
Let me give you a real-world example. You are buying a car, and were told the radiator leaks. You know what you need to replace. Then you are told that the car was run for some time with no water, and the engine block got red-hot. What do you have to replace now? -
It sounds believable but it's not. What if the power supply is still 100% and so is FW card? What would your theory be then? You say you've done it in hundreds, but.... I've got some doubts...
This is not how electricity works. You assume too much. One more thing, if the indication of a problem is generated by the software which condition you cannot judge at a glance you can't assume a solely hardware issue until you eliminate the other.
The key is to replicate the problem in a new software environment. By doing this you create a point of reference. Otherwise it's just what you encouraging: guessing. -
BTW, the power supply is also new. I bought one some time ago and just now on that ocassion I decided to exchanged.
moved to another forum, nobody likes me here...
Similar Threads
-
HELP! Black screen/Blue Screen problem
By will7370 in forum ComputerReplies: 2Last Post: 1st Apr 2012, 09:30 -
DVD Lab Pro 1.6: Links in menus get blue under fresh Windows installation
By Paker in forum Authoring (DVD)Replies: 4Last Post: 2nd Jun 2011, 12:54 -
Windows Vista laptop always starts up to blue screen of death.
By Super Warrior in forum ComputerReplies: 5Last Post: 26th Mar 2011, 18:56 -
Laptop stop on Windows Screen
By Squid_uk in forum ComputerReplies: 22Last Post: 14th Dec 2009, 16:01 -
XPP blue screen error: csrsrv.dll. How to install from XPP CD?
By rbatty11 in forum ComputerReplies: 2Last Post: 1st Feb 2008, 15:28