This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I updated 11 windows xp updates today from Microsoft.com and restarted my pc like it asked me to. (There has definitely been absolutely NO CHANGE in my computer software or hardware installation apart from this updates)
From then on, Windows cannot restart again! It is stopping at the blue screen with the following message:
A problem has been detected and windows has been shutdown to prevent damage to your computer.
PAGE_FAULT_IN_NONPAGED_AREA
Technical Information:STOP: 0x00000050 (0x80097004, 0x00000001, 0x80515103, 0x00000000).
I tried all kinds of restarting option namely, safe modes etc. but everything is returning to the blue screen.
I hope Microsoft technical support has an answer as to how to resolve this problem.
Please respond if anyone has an answer.
Thanks
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
If you are not experiencing the Blue Screen on reboot and you have successfully installed the KB977165 update you do not need to do anything.
The only situation in which you need uninstall the update is if you are experiencing blue screens on reboot.
I hope this helps.
Thanks,
Kevin
If you find that my answer was what you were looking for, please remember to click the "mark as answer" box below!
Hello Everyone,
I wanted to post a link to the MSRC Team Blog that discusses this particular situation.
This is the best place to go for updates regarding the issue being discussed in this thread.
http://blogs.technet.com/msrc/
Thanks to everyone for the great discussion, I will be sure to update the thread as more information becomes available.
Thanks, Kevin
Hello Everyone,
I wanted to thank everyone for the great information and discusion in this thread!
We have found that there is only one patch that requires un-installation to resolve the blue screen issue. KB977165 is the patch in question, the other patches do not seem to cause the blue screen behaviour and do not need to be uninstalled.
With that in mind, here's the updated solution steps:
Once you are in the Repair Screen..
IMPORTANT: If you are able to uninstall the patch and get back into Windows, in order to stay protected you can use the following automated solution which secures your PC against the vulnerabilities that are resolved with KB977165 until you can successfully get the update installed without the blue screens.
Please see the link below for the article describing the vulnerability that is fixed with KB977165 and how you can get protected without installing the actual KB update:
http://support.microsoft.com/kb/979682
I also wanted to thank maxyimus for the great thread, and LThibx for their participation as well!
Thanks,
Kevin
If you find that my answer was what you were looking for, please remember to click the "mark as answer" box below!
I am having the same problem, with endless reboot loops and blue screens of death. I am using Vista Home Premium, 32 bit, SP2. I have a Gateway FX series desktop with an Intel processor. It auto installed the updates and I woke up to a dead computer. Today was when I tried to use it again.
It has gone from bad to worse over the day. I have tried many things to fix it, including starting with memory scans and a brief virus scan while it would still boot into safe mode, and I have tried system restores and startup repair over 5 times each. Ran malwarebytes. This morning, I had 5 system restore points. Now I have no restore points at all, IF it even gets to that point without blue-screening. Tried the recovery CD iso posted a while back. Then I found my OEM restore CD and tried it. Tried a NEW copy of Vista. NOTHING has helped to fix it.
Finally called Microsoft. They walked me through about an hour (veeeery slowly) of trying to fix it in the command prompt, but it did not help. They have told me they are escalating and will call me back tomorrow. The things they had me do basically involved going into my system folder and trying to delete a file (that wasn't there, so didn't work) and then doing the same in my windows folder (file also not there, so didn't work). I am BEYOND pissed off and upset at both Microsoft and myself for not backing up frequently enough. I stand to lose nearly 500 gigs of data.
I do NOT run this microsoft security essentials thing that some of you are claiming causes this. I use mainly AVG. I am NOT lax about security and quite adept with computers. This is the first time I have ever not been able to fix a problem myself, either hardware or software. You insult us by claiming that this is not Microsoft's fault or that we are stupid PC users.
OK, I found a solution which helped me at least, and may help others.
I made another post above which tells of my situation. To make a long story short, I had two XP PCs with this BSOD "7E" error, one was fixed by
removing the KB977165 patch (using the Recovery Console and the "BATCH spuninst.txt"), the other was not, no matter which solution I used in this thread (including replacing the ATAPI.SYS file in the drivers folder).
What I did was hook up the hard drive to another XP PC as a slave, renamed the \windows\System32\Drivers folder on that hard drive to something else. Then copied the entire "Drivers" folder from the working PC to the malfunctioning hard drive.
When I put the hard drive back into the original computer, it booted right up, with a number of driver errors of course. I reinstalled all the needed drivers (network card, video, etc) and everything was back to normal.
I did a complete scan on the hard drive and did find one virus. I have no idea if this, in combination with the MS patch was the cause of the problem or not. It was a "Trojan horse Generic16 GDA" virus, and the virus file was in the user's "Application Data" folder called "syssvc.exe".
So, the problem most definitely lies in something in the "Drivers" folder. I didn't want to spend a week sorting through which file that was. Hope someone else can find it.
