I’m sorry for the delay in my posts, everyone! What I was experiencing as migraine was actually a symptom, indicative of an underlying bacterial septacemia. And seeing as it was a moderately resistant strain of S.aureus (a MRSA to be more specific) I have been sucking down as much Vancomyocin as possible, short of getting poisoned, all week (intravenously of course) at the local hospital. But I am feeling much better now and I appreciate the kind words.... :)
Now, back to the topic....
{1} since Post #42 When I executed the bootrec command (in accordance with the SF-Tutorial), you may recall that I first experienced an error listed in a the previous post, I rebooted and noticed nothing abnormal at first, but then realized that WinRE was no longer available to me using the Windows 7 system installed version of WinRE on the HDD (neither through the {F8} Advanced Boot Options Menu- “Repair my Computer...” method, by the system specific function keys that normally allow access to onboard Recovery Panel, nor by instigating a “fake problem” by powering-down during the Windows boot sequence during the logo-screen & then rebooting the system.)
So, I have the install DVD as my only means of doing anything now, which works fine, but I’m simply stating that this seems unusual - looking at it as a “symptom”. Might it suggest a boot problem as the underlying issue? Can someone fully and competently answer this or help me find someone that can do so, possibly?
{2} I finally got DISM.exe to “look like” it was working! I changed the location of the “Scratch Directory” and for the first time I got no errors. I executed it using my one and only Win7 system partition (D:) as the image using the add’l switches /CleanUp-Image, /RevertPendingActions, and /ScratchDir:<full drive & path to an empty directory> It echoed that it was working! The HDD light was going crazy and I could hear the drive working for 5...10....15 minutes or so! Suddenly a ‘blinking-cursor’, i.e. “_” appeared in the blank space where one would expect either an error code, a “Command Completed Successfully” message or at least the shell’s “prompt”, e.g. “D:\>” to show up. The HDD continued working but no control was relinquished to the user. So I waited another 15 minutes or so, in and out of the room, and eventually I found the system hung on a BSOD! I can’t say if it rebooted before the BSOD appeared or not, but it was there when I returned. The BSOD is described below:
problem detected, Win has been shut down to prevent damage
DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x000000D1 (0x000000000000000A, 0x0000000000000002, 0x0000000000000000, 0xFFFFF88001202FA5)
*** storport.sys - Address FFFFF88001202FA5 base at FFFFF88001200000, DateStamp 4a5bcace
I realize that more files are needed to diagnose a BSOD, so I had to reboot (via DVD). When I clicked the “Repair a Windows Installation” or whatever the specific title is fr the DVD recovery tools, I got the two windows that pop up, the first has two radio buttons and a text box that has already identified “Windows 7 Home Premium” and then a ‘always-on-top’ window with a blue moving bar that usually takes 10-15 seconds to “search for other OS installations. This time it took forever (10+ minutes). So I had to (ESC) out and it froze so I had to shut down quite hard/cold, i.e. Forced-shutdown with the power button depressed for 5-8 seconds.
Next boot worked fine (from DVD again). I quickly gathered the minidump file folder someone requested (which I will attach), and checked a few log files while I had a chance. The ntbtlog.txt file seemed to show many drivers that were not loading. I had checked it, purged it, and found that only two drivers were not loading at that time (roughly at the beginning of this thread) - NDProxy.sys and vga.sys. The one that was worrying me was vga.sys, and I replaced it with a fresh copy from the DVD (extracted from installation disc, it was the same version and file-size, etc ). The log was purged once again and the replaced drivers still showed up as not loading. I wrote about it and moved on. Now the entire list shows a lot of “Did not load...” driver entries. I think this might be normal, because it appears similar on other PCs running Windows7, But I’ll post it just in case it helps. I think I added the date and a “[1]” to the file name of my copy. After copying it to my flash drive I tried to copy it to the same folder it resides in using a different name (e.g. With the [1] added to the end of it for example.) But when I tried to do so using the “copy” command, I got a pop-up window from the cmd.exe window stating that the operation could not be carried out because the system file system was corrupt! ERRRR!!!!!! Really! I've checked it so many times and directions, using so many methods that it’s beyond ridiculous! A simple “dir” Command listed the files after the pop-up. Although I couldn't copy that one file I had no problems with others!
essenbe said:
I've never had to use it, but at a quick glance it looks like the infinite Loop Tutorial allows you to back up your current registry and restore the system backed up registry. The only thing is, as far as I am aware, we don't know when the system backed up the registry. But, whenever that was, hopefully it was at a time when you had no issues booting.
I'm working on that one presently. My (unsubstantiated) thoughts on how up-to-date the stored/backed-up registry "copy" would likely be is this: Most likely this is the copy that is used when one chooses "Last Known Good Configuration" or whatever the wording is in the Windows Advanced Boot Options menu (F8). I've already tried that several times, so unless there's ANOTHER backup of this type of data, it probably is that very copy that you're talking about. That's just my best guess trying to reason my way through the tangled web that is windows! I'm still going to try it though. No thought is unworthy of exploring to some degree!
But most, if not all of these applications/programs require Windows OS to function, right? Speccy does, that I know - unless they have some new app for booting from a CD/DVD/flash drive that has recently been designed by Piriform that I’m unaware of.
And, YES, I'm still working on the PSU testing S/W, John! I havn't forgotten!
I haven't gotten to some of the things that have been requested yet, I’m working on it! But look at what
I have written and gaze your eyes upon what I've uploaded for anyone and everyone per request (minidump files and ntbtlog). I THINK the problem occurred AROUND 09/20/15 plus or minus a day or two - in case that helps analyzing the dump files.
I'm very appreciative of all of the help you are all giving me, EVERYONE!