OK Thanks,
One additional bit of info: In previously playing around with the problem, er, excuse me...diligently applying sound scientific troubleshooting... bootrec /scanos would report zero OSes found, even though the Installation DVD DOES seem to find it (when it scans for valid installations to repair).
I haven't tried the /scanos for a while and have tried other things to repair it, so I don't know if it's still valid. I'll look tonight and let you know.
Sounds like maybe the hard drive is having problems. Boot up the Windows disc, and open a command prompt. Enter the following:
diskpart
list vol
Take note of the letter of your Windows partition. It will probably be C.
exi
chkdsk /r /f X: //replace X with the drive letter.
Also run one of these tests on your hard drive: http://www.carrona.org/hddiag.html
Also test RAM. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder. Boot from the CD, and leave it running for at least 5 passes.
Last edited by Jonathan_King; 21 May 2010 at 10:31.
yep, thats what I saw with info found online for this BSOD code was either "OS not found" or "Hard-Drive not found" or "couldn't restore/go into safe mode"......but no solution found that fixed anyones issue.
If your hardware is old, then it might be failing RAM or HDD, but if all your stuff is good quality, then this is most likely not a hardware issue. I wouldn't rule that out completely either. the HD might have a bad sector that wasn't seen or the RAM might have a bad spot that was being written to when the error occured. I dont know. Let us know what happens when you do the /scanos.
I have run memtest86 and it tested clean.
Chkdsk was run on the system partition and it was also clean.
Run one of these hard drive tests: HD Diagnostic
If you are overclocking, stop, and restore everything back to default settings.
What exactly on your machine do you need to save? If hardware checks out clean, I suggest a custom install. That will save your data in Windows.old and do a clean install. You will still need to reinstall your programs, but at least your files will be saved.
I have HDD Regenerator. I'll start running it tonight and see if it finds anything.
Hi Gang, me again...
OK, I ran HDD Regenerator and the drive is clean. When selecting "disable restart, etc." and I get a blue screen, it says "Windows has shut down your system to avoid causing damage to your system", or something like that. The relevant codes are 7B and the second of four was 0xc0000034 .
I tried doing a fresh install, which was successful, but Windows renamed the installation drive to a different letter (C:)(for a variety of reasons, it used to be E:) and I'd need to contact Microsoft to reactivate, so it'd take me a while just to get it running the way I wanted even before reinstalling software. So I'm hoping to give this thing one last try if anyone has any ideas. I've already renamed the Windows folders so that Windows.old (the original) is back to Windows, etc. and it boots the same old way with the same old errors.
Since this installed fine and was running correctly, there shouldn't be anything wrong with the drive. a new table space was created to hold all the files.
Then you imported the windows.old files into the new install? and the problem persists. I would say it is something in the registry or drivers that is causing the errors. I cant think of how to fix this. I will look for a solution maybe copying over part of the registry or doing a selective import from the windows.old file? I will look
Windows.old folder - Restore into a new installation
This is the Tutorial on how to do a restore from the windows.old folder.
Did you follow this?
Or something similar?
or do it another way completely?
Hi Thorsen,
No, I didn't realize that tutorial was there. I just booted in to the installation DVD recovery environment and renamed things.
All that did was put things back the way they were (same old problem). However, it eliminated the concern that it was the bootrec or something, (since a new one was generated).
As someone pointed out at the tutorial link you cited, just renaming folders isn't enough, you have to do stuff with the registry as well.
So, for my next trick, I backed up the old config folder yet again and then copied the "system" hive file from the clean installation. I booted into Partition Manager and ran the "boot corrector" to ensure that all references in that hive file were changed from "c:\" to "e:\" (which is where it's supposed to be on my installation). This time, it booted to a mouse pointer before blowing up. This will allow me to at least get minidumps and ntbtlogs and stuff. I've already generated an ntbtlog (last thing in it was monitor.sys), but haven't tried disabling restart and letting it blue screen yet or looking for minidumps. (This is all extraordinarily time-consuming and I only have so much time to give). More later.
Quote