Major computer problems
Sunday, July 9th, 2006 04:54 pmPosting this from Dad's computer.
Can't boot up at all. Even in safe mode. I can get in to run a few tests by using various CD-Roms like the XP reinstall disk (which is also supposed to repair, but doesn't seem to be able to fix my problem) and my Norton SystemWorks disk (no viruses at least). In depth hard drive scans all show that the hard drive itself is fine. Surface scan of the hard disk itself came back fine. Appears to be a problem with the boot sector or something like that. Which I no nothing about. Did some research on Mom's computer yesterday - just left me more confused. Initially, I was trying to fix a problem with the LiveUpdate program that's part of Norton SystemWorks. Their tech support finally told me I had to uninstall, delete a bunch of files that they specified, and then reinstall. Never got to the reinstall part. Tried running System Restore to at least restore back to before I uninstalled SystemWorks, but then I got... yep, a Blue Screen of DeathTM. And not just any Blue Screen of DeathTM, but one that was obviously generated outside of Windows. Had a distinct DOS look to it, though it was (is) actually still blue.
Here's the actual, full text of the Blue Screen of DeathTM I get:
There are no viruses. I don't have any newly installed hard drives or controllers or anything like that. If there is such a thing as CHKDSK /F, my computer doesn't want to run it, but I was able to run CHKDSK /P. It said the only other variable for CHKDSK was /R for repair. Not sure what to try next.
Anyway, trying to get on either Mom's or Dad's computer once a day or so to check email, but that's about it.
One slightly more upbeat piece of news... we changed my VNS settings so they're back to a tolerable level - no more pain and trouble breathing. And... would have been nice to be aware of this before, but apparently I'm still receiving the same therapeutic level I was when I was having the pain and trouble breathing. ::sigh:: I still wonder if it's ever going to be worth all this trouble.
Can't boot up at all. Even in safe mode. I can get in to run a few tests by using various CD-Roms like the XP reinstall disk (which is also supposed to repair, but doesn't seem to be able to fix my problem) and my Norton SystemWorks disk (no viruses at least). In depth hard drive scans all show that the hard drive itself is fine. Surface scan of the hard disk itself came back fine. Appears to be a problem with the boot sector or something like that. Which I no nothing about. Did some research on Mom's computer yesterday - just left me more confused. Initially, I was trying to fix a problem with the LiveUpdate program that's part of Norton SystemWorks. Their tech support finally told me I had to uninstall, delete a bunch of files that they specified, and then reinstall. Never got to the reinstall part. Tried running System Restore to at least restore back to before I uninstalled SystemWorks, but then I got... yep, a Blue Screen of DeathTM. And not just any Blue Screen of DeathTM, but one that was obviously generated outside of Windows. Had a distinct DOS look to it, though it was (is) actually still blue.
Here's the actual, full text of the Blue Screen of DeathTM I get:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:
Check for viruses on your computer. Remove any newly installed hard drives or controllers. Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.
Technical information:
*** STOP: 0x0000007B
(0xF7A30524, 0xC0000034, 0x00000000, 0x00000000)
There are no viruses. I don't have any newly installed hard drives or controllers or anything like that. If there is such a thing as CHKDSK /F, my computer doesn't want to run it, but I was able to run CHKDSK /P. It said the only other variable for CHKDSK was /R for repair. Not sure what to try next.
Anyway, trying to get on either Mom's or Dad's computer once a day or so to check email, but that's about it.
One slightly more upbeat piece of news... we changed my VNS settings so they're back to a tolerable level - no more pain and trouble breathing. And... would have been nice to be aware of this before, but apparently I'm still receiving the same therapeutic level I was when I was having the pain and trouble breathing. ::sigh:: I still wonder if it's ever going to be worth all this trouble.
no subject
Date: Monday, July 10th, 2006 12:39 am (UTC)no subject
Date: Monday, July 10th, 2006 12:49 am (UTC)no subject
Date: Monday, July 10th, 2006 12:58 am (UTC)http://support.microsoft.com/kb/316401/en-us
I am currently wiping out my computer and reinstalling everything (luckily I have my work laptop at home).
Cori
no subject
Date: Monday, July 10th, 2006 01:22 am (UTC)This is most commonly seen in setup when drivers for SATA RAID controllers are not inbox. I've no idea why you're seeing it now, unless something has indeed become corrupted. Sometimes poorly written (unsigned - interferring) drivers can cause this and sometimes uninstalling bad software can cause this.
*offers up neck massage & chocolate*
Date: Monday, July 10th, 2006 01:26 am (UTC)no subject
Date: Monday, July 10th, 2006 04:50 am (UTC)no subject
Date: Tuesday, July 11th, 2006 08:09 pm (UTC)no subject
Date: Monday, July 10th, 2006 11:55 am (UTC)no subject
Date: Tuesday, July 11th, 2006 08:09 pm (UTC)So apparently a 0.25 milliAmp output current with a 500 u second pulse width is the same as a 0.5 milliAmp output current with a 250 u second pulse width. I didn't think the change in pulse width played that much of a role in the actual 'dose' you receive, but apparently it does. So nice to learn all these little details along the way.
no subject
Date: Monday, July 10th, 2006 04:21 pm (UTC)no subject
Date: Tuesday, July 11th, 2006 08:03 pm (UTC)no subject
Date: Tuesday, July 11th, 2006 08:55 pm (UTC)