Windows Updates cause BSOD

Topic

New Reply

I’ve already posted this in Windows Forums, but due to the nature of the problem (which is that installing Windows Updates repeatedly caused my computer to fail with BSODs), I think this forum might be the better place to post it.

Windows Forums • Can’t boot Windows 7 since Windows updates installed – View topic
http://forum.mintywhite.com/viewtopic.php?f=24&t=13989&p=36765#p36765

Subject: Windows Updates cause BSOD
Posted: Fri Oct 11, 2013 10:42 am
Frank D

Following up on my previous post, now that my PC was working again, I made a full system image backup, and then tried installing only five of the 26 Windows Updates (labeled “Security”) that were offered — just the first five that dealt with Windows itself and were shown as “Important,” figuring that that was only one-fifth of the risk of installing all 26 at once. I’m sorry now that I didn’t take note of the KB numbers of the updates.

Well, it happened again! :o: At 32%, I got the BSOD! :sick: I had just recovered from this experience earlier in the day. Cold chills ran down my back. The main info on the blue screen was STOP: 0x0000007E, and at the bottom something about “shield.sys“.

I figured that, as fallback, I at least have the new full image backup that I had just done, in reserve. So I tried restarting the machine, twice. Each time it ended up failing at the same point, 32%, with the same BSOD.

As a last resort, I tried rebooting in Safe Mode, which worked. In Safe Mode, I got the message: “Failure configuring Windows updates. Reverting changes. Do not turn off your computer.” (Screenshot posted at http://gyazo.com/3a7a148bb4e76f4718996e1d2d4940cd). This was a welcome sign. At least, I thought, I’m going to be saved from having to restore from my image backup.

It took a half hour, with five automatic restarts and four repeats of that message, before my computer rebooted into normal, working Windows again. Needless to say, I don’t ever want to have to live through that kind of experience again!

On my screen now appeared a “Windows” window with information stating: “Windows has recovered from an unexpected shutdown. Windows can check online for a solution to the problem.” I didn’t bother looking for it. I’ve posted two screenshots of the window (the text was too long for only one shot) at: http://gyazo.com/306dad6469461cb7dc9eaeb5eeb0bf78 and http://gyazo.com/49cbe44f8143b460ae37fd65391925a3. If anybody is interested I can post the contents of those two files mentioned, “that help describe the problem.”

At this point the Windows Updates window popped up, offering 21 updates (screenshot posted at http://gyazo.com/4c5912c068707fad928fe9867ac19d71), five fewer than previously. This might indicate that Windows Update had “learned its lesson” and had given up on the five that I had previously tried to install. Who knows?

All I know now is that I am totally leery of installing any more Windows Updates.

And now I’d like to ask: Can anyone offer any opinions or knowledge about my experience and what I can or should do about it? I know I can’t do without them, but . . . I’d appreciate any help in this regard. Thank you.

Frank D

P.S. There is much talk about using System Restore points to recover from a situation where Windows Updates go wrong. But my question is, how do you run a System Restore when your system won’t boot or only boots to a BSOD? The only answer I know is to use a Windows Install DVD to get to the System Restore option. This is just about as uncertain and time-consuming as running a full system image restore. Any comments?

Reply | Quote

Replies

You stated you can boot to Safe Mode. You can do a System Restore from there.

Jerry

Reply | Quote

Jerry,

I didn’t have that option, since there were no restore points at that time. I had unknowingly wiped out all my previous RPs by restoring from an image backup that didn’t include restore points, and I couldn’t get SR to create any RPs, even after trying three or four repair options. But I’ve got SR working now, so I will follow your suggestion in the future.

Frank

Reply | Quote

I’d boot in Safe Mode and track down the owner of shield.sys to begin with. Then uninstall the software or disable it from starting via Device Manager (Show hidden drivers > non-plug and play section?) or by renaming it.

Copy all minidumps from C:WindowsMinidump to the Desktop, zip and attach them here, we’ll try to analyse them.

Reply | Quote

Satrow,

I found that the owner of shield.sys is Microsoft, and after googling a bit that it is listed as “safe.”

I wouldn’t want to go about trying to disable a Microsoft system file, because of what unintended consequences might follow.

I’ve zipped up the Minidumps folder from Windows and attached it to this post.

I appreciate your and Jerry’s follow-up.

Frank

Reply | Quote

Frank, it looks like shield.sys is part of Rollback RX from http://horizondatasys.com/en/products_and_solutions.aspx?ProductId=1

What these programs do is block any changes to Windows – they must be disabled before running Windows Update.

Reply | Quote

Frank, it looks like shield.sys is part of Rollback RX from http://horizondatasys.com/en/products_and_solutions.aspx?ProductId=1

What these programs do is block any changes to Windows – they must be disabled before running Windows Update.

Satrow,

Bingo! :rolleyes: Thank you for your detective work.

I had installed Rollback Rx, about three months ago, tried it out for about a month, didn’t like it for its invasive behavior, and uninstalled it completely — or so I thought. I guess this is just a leftover piece of trash the uninstaller didn’t take with it. Now that I know what it is I will delete it.

While looking for shield.sys I found two other files, shieldf.sys and shieldm.sys and in Properties found that they belonged to Horizon also. I disabled them pending a reboot, which I will do immediately.

Frank

Reply | Quote

Satrow,

That wasn’t it. 🙁

When I rebooted I got the BSOD! The info at the bottom was STOP: 0x0000007B[/B]. I tried two more times and got the same results. I then tried to boot into Safe Mode and again got the same BSOD! At this point I knew I had asked for trouble. My main concern now was to get those three files back where they were.

I could have booted with the Windows Install DVD and done a System Restore, but on a whim I restarted with Hiren’s Boot CD and went into the Mini-XP mode. I renamed the shieldf.sys and shieldm.sys back to their original names (I hadn’t deleted them) and used the Search function to retrieve the shield.sys file from the Recycle Bin and copied it back to the WindowsSystem32drivers folder. When I rebooted, all was well again, but it wasn’t a pleasant experience.

What I said about Rollback Rx is still true, but apparently that driver is still required by the OS.

So I’m back to where I was at the top of this thread.

Frank

Reply | Quote

Just during the latest crash dump, there are 3x shield*.sys drivers loaded; judging from the dates, Shdbus.sys is another Rollback driver that was loaded. It looks like the issue was caused by Rollback calling a file that no longer exists, I’d guess it’s one that was deprecated/replaced during Windows Updates.

fffff880`00fea000 fffff880`00ff2000 Shdbus Shdbus.sys Wed Jul 31 11:28:49 2013 (51F8E6E1)
fffff880`0119f000 fffff880`011b2000 shield shield.sys Wed Jul 31 11:28:35 2013 (51F8E6D3)
fffff880`015a1000 fffff880`015ac000 Shieldf Shieldf.sys Wed Jul 31 11:28:43 2013 (51F8E6DB)
fffff880`01598000 fffff880`015a1000 Shieldm Shieldm.sys Wed Jul 31 11:28:57 2013 (51F8E6E9)

Code:

[font=lucida console]
BugCheck 1000007E, {ffffffffc0000005, fffff800030bae20, fffff88003acfaa8, fffff88003acf300}
Probably caused by : shield.sys ( shield+12a0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff88001038013, fffff88002e83a88, fffff88002e832e0}
Probably caused by : shield.sys ( shield+1013 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff80003084e20, fffff88003acfaa8, fffff88003acf300}
Probably caused by : shield.sys ( shield+12a0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 1000007E, {ffffffffc0000005, fffff80002e74e20, fffff88002aa2aa8, fffff88002aa2300}
Probably caused by : shield.sys ( shield+11f7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
BugCheck 609, {2, 0, 319a0, 0}
Probably caused by : shield.sys ( shield+69a0 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``[/font]

BugCheck 609, from the oldest crash, is an error not used by MS, it may be an internal Rollback error (self-reporting?) or an error from the compiler used to create Rollback.

If Rollback had been uninstalled successfully, none of those drivers would exist on your drive and you wouldn’t be posting here.

Do you currently have any Comodo security products installed?

Reply | Quote

Do you currently have any Comodo security products installed?

Yes, I have Comodo Programs Manager installed.

I just loaded the program and checked, and I see that Rollback Rx is still shown as installed. :o: Silly question, but should I do the obvious and uninstall it?

Frank

Reply | Quote

There should be a maintenance setting, whereby you can disable Rollback while you update Windows or other software. You could try using that then allow Windows to update, if all goes well after a second test reboot, you should be good to go.

Or, just uninstall Rollback, it’s your choice – you need a mix of security software that doesn’t get in the way too much, yet still keeps your data safe.

Reply | Quote

There should be a maintenance setting, whereby you can disable Rollback while you update Windows or other software. You could try using that then allow Windows to update, if all goes well after a second test reboot, you should be good to go.

Or, just uninstall Rollback, it’s your choice – you need a mix of security software that doesn’t get in the way too much, yet still keeps your data safe.

First: Rollback Rx was not an installed program at this time. I recall uninstalling it back in August, about a month after I started using it, but there must have been components still lingering on. I really don’t know.

Next: More bad news:

I used Comodo Programs Manager to uninstall Rollback Rx (even though the program was NOT installed there were obviously remnants in the Shield folder in C:Programs(386) and tried to run a System Restore. But, as soon as I started it . . .

Disaster! A BSOD saying STOP: 0x0000007A appeared. When I rebooted a black screen appeared and told me that there was no operating system found. I used my Hiren’s Boot Disc and it verified that there was no OS. I used my Windows Installation DVD and verified again that there was no OS. I tried the usual Repair option but it failed. Likewise the System Restore option. Finally, I inserted my backup program’s boot disc and did the inevitable: I restored my previous full system image backup, which was done last night.

Result: I am back in business again, but now I’m unsure of what to do next. Is my only option to contact Rollback and ask them what to do? Or is there some other option?

Frank

Reply | Quote

On a personal level, I’d track down all traces of Rollback with Autoruns and block them from loading; this may be rather more difficult if any parts load from within something like Wininit.exe or Appinit. Autoruns will show all these entries. You can save your Autoruns.arn to zip and attach here if you wish, we’ll look through it for you. http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

Rollback support may be the safest option, no telling how long before they’d respond though, especially over a weekend.

Reply | Quote

I see now that I was wrong when I said that Rollback Rx had been uninstalled. It is still installed. After the crash I had in August, I incorrectly thought I had uninstalled it, and just didn’t think to look for it again. Regardless, I hadn’t run it since then and didn’t realize that its drivers were still present and in force.

I am now gun-shy after my previous uninstall of Rollback Rx and the system crash that occurred as a result (see message #12 above). I have sent a message to Horizon DataSys, vendors of Rollback Rx, and have received a confirmation e-mail from them with a ticket number and assurance that I will be contacted ASAP.

In the meantime I will not try to install any Windows Updates on my PC, and will create System Restore points and system backups after every significant event in case I run into further trouble.

Thank you for your continuing help in this case. 🙂

Frank

Reply | Quote

As you advised, I’ve attached a copy of my Autoruns.arn (zipped) to this message.

Frank

Reply | Quote

Frank, the more data I see from your PC, the worse it looks.

Go with Rollback support on how to use it correctly or how to fully uninstall it.

Then step back and take a long hard look at your other installs; uninstall any duplications, especially any that duplicate Windows’ built-in functions (W7’s defrag is fine, 3rd party auto-starting defraggers can cause problems, including BSODs), how many pdf viewers do you really need?; it’s only going to take one or two false positives from ‘optimizing’ tools or your anti-malware apps to make a real mess of Windows – these may not break it immediately but they’re likely to make any future troubleshooting very complicated.

Try right-clicking on a blank area of your Desktop, then on a few different file-types and on a folder or two – do you really need all those shell handle options/softwares? Pare it back some and get it cleaned up so you only have what’s really needed to keep it safe and lightweight; easy in use, easy to troubleshoot.

Reply | Quote

Frank, the more data I see from your PC, the worse it looks.

Go with Rollback support on how to use it correctly or how to fully uninstall it.[/quote]
I intend to do that as soon as possible.

Then step back and take a long hard look at your other installs; uninstall any duplications, especially any that duplicate Windows’ built-in functions (W7’s defrag is fine, 3rd party auto-starting defraggers can cause problems, including BSODs),

Yes, I do have many duplicate programs installed on my PC. I’m ashamed to admit 😮 that in almost every case, it boils down to “hoarding” — I like to acquire “goodies” that I may find a future use for. However, I do not use them. For example, I never use third-party defragging programs, because I don’t believe that defragging does any good for a Win7 PC. Yes, I should — and will — get rid of them, now that you bring them to my attention.

how many pdf viewers do you really need?;

In this case, what you take to be PDF viewers are in fact PDF converters, both to and from various other formats. They, like video and DVD converters, are so numerous because they are paid versions obtained for free, and there is no certainty as to which specific tool will do what, at the time it is needed with a particular file or document. Each has strengths and limitations. The only “pure” PDF viewer that I have on my PC and use is PDF-XViewer. All the rest are either converters or printers.

it’s only going to take one or two false positives from ‘optimizing’ tools or your anti-malware apps to make a real mess of Windows – these may not break it immediately but they’re likely to make any future troubleshooting very complicated.

I understand your concern. The only optimizer I actually use and have used since WinXP days is Advanced SystemCare, the free version, nothing fancy, doing the most basic of chores. All the rest were acquired as freebies from giveaway sites but never used. I’m very cautious about letting a do-it-all type program actually do it all. Now that you mention them I’ll get rid of them too.

Try right-clicking on a blank area of your Desktop, then on a few different file-types and on a folder or two – do you really need all those shell handle options/softwares?

I’m trying to understand which ones you mean. :confused:

Pare it back some and get it cleaned up so you only have what’s really needed to keep it safe and lightweight; easy in use, easy to troubleshoot.[/QUOTE]
Here we get into a gray area, where the simplicity of the pristine operating system is balanced against its personalization and usability with the use of add-ons and “gadgets.” I’m afraid I am of the latter persuasion. For example, my Firefox currently has about 61 add-ons (!) and it works as smoothly as any tool can possibly work. I tend to treat my OS with the same view. It should do what I want.

In the present instance, where Rollback Rx seems to be the culprit, it is because I was trying it out — it is a respected program that serves as a more powerful substitute for Windows System Restore. It was only when I had a system crash that it became both inoperative and yet remained, unknown to me, involved in the operation of the OS. I erroneously took its subsequent not working as a sign that it was not having any effects on my system, but I see that I was wrong. Knowing now what the culprit is I intend to work with the vendor toward removing it cleanly from my computer.

Thank you for your concerns and your help. 🙂

Frank

P.S. I just uninstalled all system care programs other than Advanced SystemCare and uninstalled all non-MS defrag programs. I ran a System Restore and my PC rebooted uneventfully.

Reply | Quote

Latest: At the Rollback Rx’s vendor’s advice I was told to uninstall Rollback Rx from my computer and install their latest version, which I did, and rebooted. Result: BSOD! Nothing I could do would get my PC to boot again (system restore, restore from backup, using the Windows Install disc, repair, command line, fixmbr, fixboot, etc.). Analysis: The Rollback Rx vendor has no idea what my problem or its solution is, so the answer does not lie with them.

I resolved not to give up and reinstall Windows, thereby losing all my valuable programs and settings, acquired over three years with much care and fine-tuning. To get professional help with this situation I took the PC to a local PC repair shop, explained the situation, and left it with them. A day later I got the news: they could not fix the problem. This exercise cost me $50, but at least I know now that no one can do more than I already did.

As a last resort, I downloaded an updated release (1.6) of my backup/restore program (I had been using 1.0) and tried another restore from backup. Hooray! It worked! 🙂

Bottom line: I am now back online with the latest version of my computer and software, as it was just before the Rollback Rx uninstall/reinstall operation. Although I am happy to be here, the original problem still exists: I can’t uninstall Rollback Rx or install Windows Updates without crashing.

Does anyone have any other ideas? Thank you!

Frank D

Reply | Quote

Have you tried something like Revo Uninstaller? If you do, proceed with care, and examine each proposed registry removal individually. It may be your way out of this.

Reply | Quote

Have you tried something like Revo Uninstaller? If you do, proceed with care, and examine each proposed registry removal individually. It may be your way out of this.

I have used Revo Uninstaller, Comodo Programs Manager uninstaller module, and IObit Uninstaller. Removing the corrupted program is not an option, as doing this takes away operating system files that are needed to boot into Windows. The Rollback Rx program is the culprit here, because it substitutes its own versions of a number of “sys” files for the proper Windows versions during its installation. The program is corrupted, though, and can’t be correctly uninstalled because uninstalling it does not replace the original Windows “sys” files when it is removed, thereby causing the Windows booting procedure to fail.

Frank

Reply | Quote

I have used Revo Uninstaller, Comodo Programs Manager uninstaller module, and IObit Uninstaller. Removing the corrupted program is not an option, as doing this takes away operating system files that are needed to boot into Windows. The Rollback Rx program is the culprit here, because it substitutes its own versions of a number of “sys” files for the proper Windows versions during its installation. The program is corrupted, though, and can’t be correctly uninstalled because uninstalling it does not replace the original Windows “sys” files when it is removed, thereby causing the Windows booting procedure to fail.

Frank

Sorry to say it, it’s looking a bit dire then. I would probably go one of two ways, now:

1. Try a Windows repair install.
2. Backup all your data and perform a Windows clean install.

Either way, once you get rid of that program, be sure not to install it again.

Reply | Quote

I would probably go one of two ways, now:
1. Try a Windows repair install.
2. Backup all your data and perform a Windows clean install.

Thank you, but I’ve already unsuccessfully tried a Windows repair install and have committed myself to not doing a clean install because I will lose my programs, settings, etc. (see my reply #18 above). The repair install fails because Windows sees some spurious information about a legacy scanner being installed and cannot proceed because of it. I have scoured the computer and the registry but have not found the source of that phantom information, so I can’t complete the repair install.

What I plan to do is this: satrow has enabled me to identify four “sys” files that belong to Rollback Rx. (See message #9 at http://windowssecrets.com/forums/showthread//157197-Windows-Updates-cause-BSOD?p=924409&viewfull=1#post924409) In the next day or two I will get genuine Windows copies of these files from a friend’s Windows 64-bit OS. I’ll then replace the Rollback files on my PC with the Windows files and (cross my fingers) reboot. If successful, I’ll try to install a Windows Update. If this works I’ll try more — up to the 27 now available to me — and reboot. If successful, I’ll forget about uninstalling Rollback Rx; I’ll just rename it and consider myself very lucky.

Frank

Reply | Quote

Ok, I understand that. I am also rather conservative regarding the option of having to reinstall all my apps.
I hope that strategy can fix your issues :).

Reply | Quote

Ok, I understand that. I am also rather conservative regarding the option of having to reinstall all my apps.
I hope that strategy can fix your issues :).

Thank you! I’ll reply with my results.

Frank

Reply | Quote

Those 4x drivers are NOT RX’s versions of Windows drivers, they belong to RX and are not replacing anything belonging to Windows.

If you can track them down in Device Manager (you’ll probably need to enable hidden devices), you should see a dropdown option to change the startup type from the Properties/Boot tabs for each driver; change them all to Disabled. (The method here can be used to remove the ghost scanner drivers that block a Repair install: http://www.howtogeek.com/howto/windows-vista/remove-old-drivers-after-upgrading-to-new-hardware/) If there is an option to remove drivers, select it or there’s a high chance that they will be re-enabled/installed at boot.

It may not be possible to remove/block these drivers while RX is active, as it probably has a built-in self-defense module.

Then use Autoruns to track down and disable any other triggers for RX: http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx

Make sure you have a recent backup before attempting the above.

Reply | Quote

I’m very confused:

Those 4x drivers are NOT RX’s versions of Windows drivers, they belong to RX and are not replacing anything belonging to Windows.

You told me that those drivers are Rollback Rx’s, I agree, but when I tried to remove them previously, Windows BSOD’d. It was because of that, that I supposed them to be Rx’s replacements for Windows drivers of the same name. So, if they belong to Rx, why does Windows BSOD when I remove them?

If you can track them down in Device Manager (you’ll probably need to enable hidden devices), you should see a dropdown option to change the startup type from the Properties/Boot tabs for each driver; change them all to Disabled.

Maybe I’m not reading you right. How can I track .sys files in Device Manager? Rollback Rx isn’t a device. What device would they be part of? Do you mean I should use DM to locate the legacy scanner? If so, it does not show up in DM even with hidden devices showing. I did find “shieldm” under “Non-PlugnPlay Drivers” but it’s a Microsoft driver. Its properties are: Provider: Windows Win 7 DDK provider. / Version: 6.1.7600.16385 built by: WinDDK / Copyright: Microsoft Corporation. All rights reserved.” I’m pretty sure that disabling “shieldm” is not what you mean. I did this once before and it resulted in a BSOD.

Then use Autoruns to track down and disable any other triggers for RX: http://technet.microsoft.com/en-us/s…/bb963902.aspx

How would I use Autoruns to recognize, track down or disable triggers for Rx?

I do a full system image backup and a restore point after every change I make to this PC since these BSODs started. However, it has not guaranteed that I can get my OS back. Before I consider implementing any of these recommendations, could you please clear up the confusion in my questions above? This is all way over my head.

Frank

Reply | Quote

3rd party drivers interfering with Windows’ own services/processes are probably the single biggest cause of BSODs. Provider: Windows Win 7 DDK provider = Driver Development Kit = made by a tool provided by Microsoft to create device drivers for Windows – this is NOT the same as a Windows driver because this driver does not exist in Windows or any Windows install DVD, it’s a driver for a 3rd party device.

Your BSODs post -removal of RX drivers were due to the continued triggering of the driver loading process at each boot (which failed with a presumed File not found), what I’m suggesting is that you remove them via DM and then seek out and disable any RX triggers using Autoruns before rebooting. Follow the HTG articles linked to find out how to show the ‘devices’ loaded by Rollback (and the phantom scanner) and disable them from loading using their Properties/Boot tabs.

To set up Autoruns to ignore Windows’ own entries and make the job a little easier, hit Esc after starting it, hide Windows entries and enable driver verification: Options > Filter options and ensure only Verify code signatures and Hide Windows entries are checked the click Rescan. Once done, search through each tab (ignore the Everything tab) looking for any entry that belongs to Rollback RX (Publisher column), also check any locations that don’t have a publisher listed to see if they’re Rollback -related (check the image path). All RX -related entries must be unchecked to disable them. Ctrl+F will search.

The above must be done for all Users, change via the Users options in Autoruns.

Reply | Quote

satrow,

Follow the HTG articles linked to find out how to show the ‘devices’ loaded by Rollback (and the phantom scanner) and disable them from loading using their Properties/Boot tabs.

I didn’t find any HTG articles linked.

Your BSODs post -removal of RX drivers were due to the continued triggering of the driver loading process at each boot (which failed with a presumed File not found), what I’m suggesting is that you remove them via DM and then seek out and disable any RX triggers using Autoruns before rebooting.

I did that. Autoruns found three checked entries for “Horizon,” which is the vendor of Rollback Rx. I unchecked them, presumably disabling them. In DM I found only one entry, that of “Shieldm,” which is set to start automatically. I disabled it.

If this is what you are advising me to do, I will go ahead and reboot. If anything I’ve said is not correct, please let me know. I will not reboot until you give me the “all-clear.”

Thank you!

Frank

Reply | Quote

Linked from #25, this one’s for the phantom device: http://www.howtogeek.com/howto/windows-vista/remove-old-drivers-after-upgrading-to-new-hardware/ I forgot to put the main link there: http://www.howtogeek.com/167094/how-to-use-the-windows-device-manager-for-troubleshooting/

Once you’ve fully unhidden all devices in DM and disabled all 4 RX ‘devices’ from starting and double-checked your Autoruns for all profiles/users for any Horizon/Rollback entries, you should be good to test with a reboot – should any error message or BSOD occur, please make careful notes, they could pinpoint the issue.

Reply | Quote

I’ve done as you advised. However, using Autoruns, I still find the following:
Shield WINNT/2K/XP/2003 Driver Windows (R) Win 7 DDK provider c:windowssystem32driversshield.sys 7/31/2013 6:28 AM
Shieldf WINNT/2K/XP/2003 Driver Windows (R) Win 7 DDK provider c:windowssystem32driversshieldf.sys 7/31/2013 6:28 AM
For one last time before I reboot, shall I disable these two also?

Frank

Reply | Quote

Yes, Frank, disable both of those as well then do a refresh of Autoruns and check again – we really need to block all triggers and drivers to have any chance of success here.

Reply | Quote

Done. I’ll now reboot.

Note: Small delay as I run a quick incremental backup.

Reply | Quote

Fingers crossed here.

Reply | Quote

It didn’t work. BSOD. (I’m typing this on another computer.)

As soon as I can get my PC up and running again I’ll post the picture I took of the blue screen. In brief, it’s 0x0000007B.

I tried System Restore via the Windows Install DVD but it and Repair didn’t work. They have NEVER worked! Why bother?

I’m now restoring from my system image backup and hope it works.

Frank 🙁

Reply | Quote

If it had failed, I suspected it to be with a 0x7B:

STOP 0x0000007B: INACCESSIBLE_BOOT_DEVICE
Usual causes: Hard drive, File system, Boot sequence errors, Device driver, Virus infection (in particular check the MBR)

If you have a W7 DVD or on a bootable USB, try running fixmbr and fixboot, run them 3 times between reboots: http://support.microsoft.com/kb/927392

Reply | Quote

satrow,

I’ve tried all those Windows Install disc options and commands with no results. The same BSOD keeps appearing.

At this point, I’m biting the bullet and giving up trying to salvage my precarious Windows installation. I thank you for all your expert help and assistance toward keeping it running, but the repeated failed attempts have grown too unnerving for me.

I’ve already started installing Windows 7 from scratch. I want the pleasure (regardless of how slight) of using a Windows PC without the daily and even momentary assaults from unsuccessful Windows Updates, failed System Restores and backups, BSODs, etc. The fresh install procedure is retaining all my “stuff” in a Windows.old partition, and I have multiple backups, so I can dip into them to reclaim individual files, e-mails, documents, and so on. I’ll of course be losing a number of irreplaceable programs, but . . . that’s life.

It will be a novel experience for me, rebuilding a Windows environment for the first time in over three years.

It was a good job that I would not have attempted without your help. Thank you! 🙂

Frank

Reply | Quote

I hope that all goes well for you from this point on, Frank.

Reply | Quote

satrow,

Thank you! 🙂

Frank

Reply | Quote

Next time you get one of those nasty problem uninstalls and you have a backup, reimage and boot into safe mode and uninstall it then immediately run CCleaner to rip out broken links. I find this helps. I commend you on keeping regular backups not many people do!
I have only had one of these and a re-install was the only solution, It took 3 days to build my software back to where it was.I too had straight backups of MY documents and apps folders.

Reply | Quote

Next time you get one of those nasty problem uninstalls and you have a backup, reimage and boot into safe mode and uninstall it then immediately run CCleaner to rip out broken links. I find this helps. I commend you on keeping regular backups not many people do!
I have only had one of these and a re-install was the only solution, It took 3 days to build my software back to where it was.I too had straight backups of MY documents and apps folders.

That’s why imaging can be so important. With an up to date image, your 3 days would be surely less than a couple hours.

Reply | Quote

Thank you, Michael, Dick-Y and Ruirib.

Please note that my situation was unusual. It was complicated by the fact that my system backups (using two different programs) did not work because of complications introduced into the backups by a RAM-drive I had been using — NEVER AGAIN will I use a RAM-drive. Otherwise, I agree that a system image restore using either of the backups would have solved all my problems.

I have since corrected my procedures, and have already performed a full system restore from image that worked!

Frank

Reply | Quote

Thank you, Michael, Dick-Y and Ruirib.

Please note that my situation was unusual. It was complicated by the fact that my system backups (using two different programs) did not work because of complications introduced into the backups by a RAM-drive I had been using — NEVER AGAIN will I use a RAM-drive). Otherwise, I agree that a system image restore using either of the backups would have solved all my problems.

I have since corrected my procedures, and have already performed a full system restore from image that worked!

Frank

You’re welcome, Frank :).

I am glad you got your first image done. It’s the mother of all strategies to keep yourself safe from computer related troubles :). Well done :).

Reply | Quote

Like so many here, I have 2 partitions (1 for my W7 system and programs, 1 for my data).
I regularly take images of both.
Yesterday, in “playing around and trying something new, I screwed up my OS.
Using Macrium paid, it took me 7 minutes to restore my image (which I had taken before I “played around”), and be back up and running.

Dick

Reply | Quote

I use Clonezilla for imaging now because it works on both windows and linux. I have a boot usb,CD and DVD versions. It also checks the Images so if your backup drive has errors the image validation fails. I had a crook backup drive and didn’t know Clonezilla made me look closer and retire the drive. Tomorrow is Backup day.
Cheers
Michael

Reply | Quote

I use Clonezilla for imaging now because it works on both windows and linux. I have a boot usb,CD and DVD versions. It also checks the Images so if your backup drive has errors the image validation fails. I had a crook backup drive and didn’t know Clonezilla made me look closer and retire the drive. Tomorrow is Backup day.
Cheers
Michael

Great that you are using imaging, Michael. Validating the images after creation is a very important part of the imaging process. We have been actively discussing imaging, so be sure to check or Maintenance forum :).

Reply | Quote