I won't lie. I just registered because I need help as described in the thread title.
I've had successes in using Regedit and recovery console to fix big problems, so I'm fairly savvy about software. But not hardware--nowhere near as much as the really good help I've already read while looking for the same condition that I have.
For 20 minutes today, Dell support tried hard [I pulled all cards and hard drive and replaced CMOS battery]. Nothing changed the status:
a one-line, cryptic white message on a black screen mentioning BIOS and
ending with "P/N A-01234567" but those aren't the actual digits.
He concluded bad mobo but I don't just want to trash my P4. It's 8 years old and I was ready for a new one a month ago. But it's still a good PC for somebody. And I'd rather make the buy decision myself.
I have a multimeter [AC and DC voltages and AC amps] but have no clue how to troubleshoot/diagnose.
Any thoughts would be appreciated.
----------------------------------------------------------------------------
Here is the weird chain of events leading to my P4's death:
1. storm; power outage; PC [etc.] protected by APC UPS; no apparent problems
2. viewed 2 online videos to end but "62%" appeared center screen after both
3. exported a registry key; exited Spider; imported the .REG file [not cheating!]
4. immediate BSOD--STOP 0x019 [this is 36 hours after the storm]
5. twice rebooted to normal-looking desktop but unpopulated systray and hang
6. first of many BSODs with STOP 0x024 [no more 019s]
7. at some point, BIOS mentioned bad memory; pulled one 512MB DIMM
8. no BIOS error, but nothing from safe mode thru last known good worked
9. recovery console worked once: Chkdsk found error 62% of way thru one test
10. 62% again... short story: there is a Ghost DOS-62 virus [strain of Vienna]
11. downloaded Linux "RescueCD" from f-secure; no virus found
12. Seagate Seatools failed HD on every test; Dell diagnostics passed HD on all
13. downloaded AVG rescue CD; no virus
14. used AVG CD Knoppix/Linux file manager to copy all data to flash drives
15. now safe, I explored Linux for a couple of days; ready to reinstall Windows
16. today [9 days after first BSOD]: no spash screen or F2 option; no BIOS
That "62" virus causes gradual loss of control by first infecting one executable; then when it runs, another is infected, and so on. Sort of like from entering Windows but with hangs to one use of recovery console to BSODs over two days. And at one point, anything I tried simply caused reboot, another symptom of infection.
The virus also changes the seconds of one time field to 62 but I didn't see this.
But two checkers found nada. It's an old virus.
The storm and power outage and gradual decline of an unlucky component supposedly protected by APC UPS ... how likely is all that?
How could importing a just-exported, unchanged registry key do anything?
Weird bunch of circumstances.
I still can't shrug off three 62%s on two different days.
I've had successes in using Regedit and recovery console to fix big problems, so I'm fairly savvy about software. But not hardware--nowhere near as much as the really good help I've already read while looking for the same condition that I have.
For 20 minutes today, Dell support tried hard [I pulled all cards and hard drive and replaced CMOS battery]. Nothing changed the status:
a one-line, cryptic white message on a black screen mentioning BIOS and
ending with "P/N A-01234567" but those aren't the actual digits.
He concluded bad mobo but I don't just want to trash my P4. It's 8 years old and I was ready for a new one a month ago. But it's still a good PC for somebody. And I'd rather make the buy decision myself.
I have a multimeter [AC and DC voltages and AC amps] but have no clue how to troubleshoot/diagnose.
Any thoughts would be appreciated.
----------------------------------------------------------------------------
Here is the weird chain of events leading to my P4's death:
1. storm; power outage; PC [etc.] protected by APC UPS; no apparent problems
2. viewed 2 online videos to end but "62%" appeared center screen after both
3. exported a registry key; exited Spider; imported the .REG file [not cheating!]
4. immediate BSOD--STOP 0x019 [this is 36 hours after the storm]
5. twice rebooted to normal-looking desktop but unpopulated systray and hang
6. first of many BSODs with STOP 0x024 [no more 019s]
7. at some point, BIOS mentioned bad memory; pulled one 512MB DIMM
8. no BIOS error, but nothing from safe mode thru last known good worked
9. recovery console worked once: Chkdsk found error 62% of way thru one test
10. 62% again... short story: there is a Ghost DOS-62 virus [strain of Vienna]
11. downloaded Linux "RescueCD" from f-secure; no virus found
12. Seagate Seatools failed HD on every test; Dell diagnostics passed HD on all
13. downloaded AVG rescue CD; no virus
14. used AVG CD Knoppix/Linux file manager to copy all data to flash drives
15. now safe, I explored Linux for a couple of days; ready to reinstall Windows
16. today [9 days after first BSOD]: no spash screen or F2 option; no BIOS
That "62" virus causes gradual loss of control by first infecting one executable; then when it runs, another is infected, and so on. Sort of like from entering Windows but with hangs to one use of recovery console to BSODs over two days. And at one point, anything I tried simply caused reboot, another symptom of infection.
The virus also changes the seconds of one time field to 62 but I didn't see this.
But two checkers found nada. It's an old virus.
The storm and power outage and gradual decline of an unlucky component supposedly protected by APC UPS ... how likely is all that?
How could importing a just-exported, unchanged registry key do anything?
Weird bunch of circumstances.
I still can't shrug off three 62%s on two different days.
